We're experiencing frustrating delays of 3 to 13 minutes when starting apps on various devices, largely due to the extensive security tools we've implemented. Even after staggering the launch of some non-essential security services, the user experience is still subpar. Unfortunately, our security team is hesitant to reduce features, and Microsoft Support tends to redirect us towards generic solutions with little specific help. Recently, we found some registry tweaks that seem promising, like WaitForIdleState and StartupDelayInMSec, but information on the risks of modifying these keys is scarce. I'm concerned about the possible side effects of altering these values, especially if I set them to 0, since Microsoft likely had reasons for including these delays. Has anyone tried adjusting these keys in a business setting? What risks should I consider?
4 Answers
I wouldn’t recommend trying hacks like that. The real issue here is your security team not optimizing those tools properly, which is what's slowing everything down for your users.
Have you checked the hardware specifications? If you're facing bad startup times, it might also be an indication that the devices need better specs, although from what you said, it sounds like the problem persists even with newer machines.
There’s definitely a risk involved when you start tampering with the registry. Always back it up first, make sure to test changes carefully, and be ready to roll back if things go sideways.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures