Reply to thread

Message

<blockquote data-quote="TairikuOkami" data-source="post: 726327" data-attributes="member: 61892"><p>By the way, what has changed since about 2 versions ago? I have &quot;Windows Management Instrumentation&quot; service disabled, to prevent fileless malware, so it generates tons of errors obviously (I just cancel them), but WRT used to start ASAP, now it sits there for about 4 mins, until it starts, so I guess, that timeout has increased? The first error, which comes after those 4 mins, is about free space. I guess this could be prevented, if WRT would remember &quot;Minimal mode&quot;, but I understand, that this is not an issue, since most people do not disable that service, most likely noone except me, just wondering, if there is a workaround, like starting it with a parameter, like /minimal? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>

[QUOTE="TairikuOkami, post: 726327, member: 61892"] By the way, what has changed since about 2 versions ago? I have "Windows Management Instrumentation" service disabled, to prevent fileless malware, so it generates tons of errors obviously (I just cancel them), but WRT used to start ASAP, now it sits there for about 4 mins, until it starts, so I guess, that timeout has increased? The first error, which comes after those 4 mins, is about free space. I guess this could be prevented, if WRT would remember "Minimal mode", but I understand, that this is not an issue, since most people do not disable that service, most likely noone except me, just wondering, if there is a workaround, like starting it with a parameter, like /minimal? :) [/QUOTE]

Verification