Supporting Windows Question

RunOnce bug in Windows 10??

08/14/2015 12504 views
Just wondering if anyone else has tried this...

With Windows 7 and 8, the HKLM RunOnce and RunOnceEx registry keys run prior to the desktop loading, as designed. The desktop won't appear until they have completed.  With Windows 10 the keys kick off but the desktop appears after a few moments regardless of whether the keys are still running.

Any thoughts about how to workaround this?
0 Comments   [ + ] Show comments


All Answers

I think you will need to configure your runonce entries to run synchronously. The following technet article gives some pointers:


Answered 08/15/2015 by: EdT
Red Belt

  • Thanks but I'm not sure if that applies here. I don't have any problem launching tasks that run in order, the specific issue is that the desktop isn't supposed to load until the RunOnce keys have finished.
    • >the specific issue is that the desktop isn't supposed to load until the RunOnce keys have finished.
      ...except that, as explained, this behaviour has changed in W10. This is to give the illusion that Windows is loading faster.
      • And where is this explained??
Because of my own interest I start googling around, and first found this article, but only applies to Windows 7 & 8.
Then I found some tools to delay start up of applications here, perhaps it is a good alternative...

For Windows 10 wants look at fast as possible...that you still have to wait for other apps to load doesn't matter.
So long you can watch the nice photoshop picture on the background...

What you could investigate is your own recurring 3th party update, for that is the only thing that can slow down the desktop appearance. (Previous version this was possible).
Please share if you do find a solution!
Answered 08/17/2015 by: dedenker
3rd Degree Black Belt

  • After many hours of doing my own research, I stumbled across the solution that worked for me.
    The first answer was sort of correct. Prior to 10, Windows would run the RnOnceEx commands synchronously. This has now been changed to asynchronously which means the Explorer shell can run when it wants to, instead of after the RunOnceEx commands/keys have completed, as confirmed in this article, which is also where the answer lies -
    Therefore, you need to add the following reg key - reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer /v AsyncRunOnce /t REG_DWORD /d 0 /f

    While the article states to add a line to your Unattend.xml file, I like to do this old school. My Setupcomplete.cmd file calls up my reg tweaks in a separate file using the following -
    I also run the disable animation tweak as that really bugs me too!!!
This content is currently hidden from public view.
Reason: Determined to be spam through moderation For more information, visit our FAQ's.
This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ