Startup apps artificially delayed on Windows 11?

Anonymous
2024-02-15T07:04:15+00:00

I'm running Windows 11 23H2 with all the updates installed. I have several (5) programs added to shell:startup so they can launch automatically at boot.

I'd expect these apps to start launching maybe up to 5 seconds after seeing the desktop, but for some reason, most of the time the startup of these programs is delayed by up to 1-3 minutes. Looking at Task Manager indicates very little resource usage, so insufficient processing power is not the cause (this desktop computer is running on latest Core i7 and a very fast NVMe drive). Additionally, the same apps I have added in shell:startup I can also launch manually the very second my desktop is visible and they'll launch immediately.

This installation of Windows 11 should still be good as new. It's barely 3 months old, no strange tweaks done to it, just basic programs installed. sfc and dism checks return no problems. There are also no other issues with this computer besides that one.

Is there something that could be done to make these applications run immediately after logon with no delay?

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2024-04-29T08:58:54+00:00

And here we are again. MS guys don't know anything about their product)

I found a solution:
Changing registry is dangerous, make backup and blablabla
open regedit Win+R -> regedit

goto "Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer"

Create key with name "Serialize"
Create REG_DWORD value in it with name "WaitForIdleState" (case-sensitive!) with value 0.
Optionally create REG_DWORD value in it with name "StartupDelayInMSec" (case-sensitive!), and specify value to lower startup delay. I am good with 0, but YMMV.

Hope, that helps. Cheers!

p.s.: the answer is found on another forum, not sure if i can post links to other resources here.
This situation is somehow connected with a new way of calculating startup delay. It used to be a static value in milliseconds, which worked fine. But they made it even better by making it dynamic, so windows will wait for cpu idle state and only then it will launch startup apps. i guess, this is made because modern cpus are much weaker than old ones and putting a little bit of load on them is excessive *sarcasm*

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments

18 additional answers

Sort by: Most helpful
  1. Anonymous
    2024-10-16T07:13:33+00:00

    Very well said, Kamil!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-10-15T16:14:39+00:00

    Hello everyone,

    Just to share with you my point of view on this keys.

    perhaps that help you, but the initial issue not in the OS but what you do with or what you have on.

    Performance issue mean you have some blockers on the windows client that do not means windows is not efficient.

    if you will use this key you compromise the windows client support and assistance specialy on Enterprise context, do what you do on your personnal Operating system.

    but WaitForIdleState make sens and need to be in place for many reasons.

    if you bypass this requirements you will met other issue on windows.

    you are informed

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-08-16T18:00:45+00:00

    sometimes, you might encounter a Green Screen of Death (GSOD) because of this.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-06-03T06:56:56+00:00

    I get the below error. Any clue?

    Kind regards, Kenneth

    Was this answer helpful?

    0 comments No comments