Win11 slow startup? Change two numbers
Win11 slow startup? Change two numbers, and one user went from 150 seconds down to 30. A newly bought high-spec computer actually boots slower than an old machine that's been used for years. The desktop shows up, the icons are there, but WeChat takes forever to pop up and DingTalk just keeps spinning. You try to click the Start menu, and even the mouse cursor lags half a beat. By the time these startup apps have all finished showing their faces, two minutes are gone. My first instinct was a hard drive problem. It wasn't until I dug through Microsoft's documentation that I realized
Slow Windows 11 Boot? Change Two Numbers — One User Went from 150 Seconds to 30
You buy a high-spec new PC, and it boots slower than an old machine you've used for years. The desktop shows up, the icons are there, but WeChat won't pop up for ages and DingTalk just keeps spinning. You try to click the Start menu and even the mouse cursor lags half a beat. By the time all those startup apps have finally shown their faces, two minutes are gone.
My first instinct was that it's a hard drive problem. But after digging through Microsoft's documentation, I realized the hardware isn't necessarily to blame.
A Reddit user named PersianMG ran into the same situation. His machine isn't weak — after login it has to launch about 30 startup items, plus 6 AutoHotkey scripts and a pile of background services. Windows itself gets to the desktop pretty fast; it's just that after the desktop appears, programs pop up one after another, and loading everything takes two and a half minutes.
He didn't rush to swap out the hard drive. Instead he pulled out the Windows Performance Toolkit to see where the time was actually going. The result was surprising: no single program was a particular bottleneck — there were long stretches of idle time between programs.
Put simply, your computer being idle doesn't necessarily mean it wants to be idle — it might be the system queuing things up.
Microsoft documented this mechanism in its developer docs long ago. For programs in the Run and RunOnce registry keys, the system doesn't guarantee they'll launch the moment you log in — it can defer them and pick a time that won't interfere with foreground activity. Microsoft engineer Raymond Chen also explained on The Old New Thing blog that Windows first gets things you can see at a glance, like Explorer, ready, and only then deals with the programs in the startup group. The reason isn't hard to guess: the moment you log in is when resource contention is fiercest — a bunch of programs reading the disk at once, and even the Start menu might not open. The first time I read that, it hit me that those two minutes were deliberately left there by the system.
Queuing is a good thing in principle, but queuing too long gets annoying. The fix PersianMG found was to tweak two registry numbers.
The path is under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer. Most machines don't have a Serialize key, so you have to create one yourself. Once it's created, add two DWORD 32-bit values inside it, both set to 0: one called StartupDelayInMSec, which controls how long Explorer waits before launching startup programs; the other called WaitForIdleState, which decides whether the system waits for an idle state before pulling programs up. Setting both to zero is essentially telling the system not to wait — just go all at once. Changes take effect after a reboot.
The effect is real. In the user tests cited by Windows Latest, after PersianMG made these changes, the time for all startup apps to be ready dropped from about 150 seconds to 30 seconds. Before the change, programs didn't start loading until 1 minute 50 seconds after boot; after the change, they started at 20 seconds and were all running within 5 seconds. Another user with a Core Ultra 7 270K Plus and an RTX 5080 set WaitForIdleState to 0 and saw the wait drop from 90 seconds to 47 seconds, then adjusted the startup order and got it down to 36 seconds.
When I saw those numbers, I got tempted too and almost went to edit the registry. But on second thought, there's a catch to get past first.
There's another side to this. Windows Latest tested it themselves. On a lower-spec virtual machine, load times did shorten, but it still took about a minute. The author's judgment was that machines with modest performance aren't suited to turning off this delay. When a bunch of apps start at once, CPU, memory, and disk all get contended for, and the desktop actually becomes more sluggish. That's exactly the situation with my old laptop, so after reading that part I pulled my hand back.
There's also a limitation that's easy to miss. The developer of Wintoys points out that this trick mainly affects programs launched via the Startup folder — most Microsoft Store apps and software launched through other mechanisms don't play by these rules at all. And it only changes when programs start launching; it can't do anything about how fast the programs themselves load.
My own take is that this falls into the category of "good to know, but whether to actually do it depends on your machine." If you've just upgraded to an SSD and have plenty of RAM, with only a dozen or so startup programs, tweaking it is fine. If you're on an old machine with a pile of software running in the background, honestly leaving the system's delay in place will probably feel better than messing with the registry. I'm not touching it on my old laptop.
In the end, the more hassle-free approach for most people is the dumb one: go into Settings > Apps > Startup and just turn off the startup programs you don't need. Fewer programs competing for resources is more direct than editing the registry. And if you do make the change and something feels off, deleting the Serialize key you created restores everything to how it was — just remember to create a system restore point before you start.
Written by our editorial team; tools listed here are tested or verified against public sources. Links point to official sites or GitHub repos for reference only — no paid placements.