Reply to thread

Message

<blockquote data-quote="AlexCa" data-source="post: 726347" data-attributes="member: 52267">I haven&#039;t made any changes in that portion of the program, no timeout increases. I&#039;ve also just tested it (to disable the &quot;Windows Management Instrumentation&quot; service) in 2 computers running Windows 10 (one with SSD and the other without a regular HDD, just to make sure) and also in one VM running windows 7, and the result is that WRT will throw those alerts, but still starts fast, so my guess is that must be something else in your computer.In the same folder where&#039;s the Windows Repair Toolbox executable, there&#039;s a file named &quot;Windows_Repair_Toolbox (fast start, no monitors).bat&quot;. You can use it to start without monitors.Or you can start Windows Repair Toolbox from cmd using the argument /safe , it&#039;s the same thing <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="AlexCa, post: 726347, member: 52267"] I haven't made any changes in that portion of the program, no timeout increases. I've also just tested it (to disable the "Windows Management Instrumentation" service) in 2 computers running Windows 10 (one with SSD and the other without a regular HDD, just to make sure) and also in one VM running windows 7, and the result is that WRT will throw those alerts, but still starts fast, so my guess is that must be something else in your computer. In the same folder where's the Windows Repair Toolbox executable, there's a file named "[I]Windows_Repair_Toolbox (fast start, no monitors).bat[/I]". You can use it to start without monitors. Or you can start Windows Repair Toolbox from cmd using the argument [I]/safe[/I] , it's the same thing :) [/QUOTE]

Verification