This beta did the trick. Everything working as expected and I didn´t changed anything about temp folder. Still pointing to another drive (HDD in case) instead of default. Thanks for this beta and I hope it remains OK for now.
No, no encrypted partition or whatever. The situation here at my point of view is not a discussion where the windows temp folder should be or what should come first in order to work properly: the Adguard service or the drive mount. We have the risk to fall into an useless discussion of what came first...the egg or the chicken.Or he has encrypted partition(s) && they are mounted too late for example at user login. If Adguard service is set to automatic start, when does it exactly start? At pre-boot state/when first user log in or ?
In my point of view, design an app for one expected behaviour is always dangerous. Specially talking about windows, that is highly customizable and grants to the user so many possible changes. This temp dir thing we are talking on this topic is an example. Despite of the meaning of why such checking is made, and judging it is necessary for Adguard, why program the app to look at one direction only? This situation reminds me programs like google chrome for example, which don´t have the option to choose the path where to install...
Dealing with variables and forms other than the default is pretty much necessary these days.
@avatar: Just curious about what is different on the beta...since the startup problem is solved.