Windows Booting very slow after 2004 update ,

Note: Please don't run the Verifier.exe command, unless you are stress-testing a computer. I did it by mistake, and just reporting here what I did.

I have jumped through so many different hoops on this issue....

Slowest time it took from password to OneDrive starting was 8+ minutes

However recently I noticed a speedy shutdown (they were slow also).

Booted up today and looked in the Diagnostics-performance of Event Viewer and it confirms today's quick boot up at 86725ms which is ok considering I don't have any super/prefetch enabled.

So the things I had done to try to improve this were. Installed a Samsung SSD 860 QVO 1TB SATA. and Ram now 32Gb from 16Gb. This gave some improvement in boot times especially up to the point of password. Also works well in normal program launch etc, pleased to have that different type of storage (would have gone for the NVMe type but motherboard is not capable...

Now, what I did recently that appears to have fixed things in my case.

from command window

sfc /scannow

dsim /online /cleanup-image /checkhealth

I also went through a nightmare and I don't suggest doing this from the command window, but run the Verifier.exe gui in system32 folder so that you can see what is going on.(are any things being checked on every boot) If you run the "verifier /standard /all" from a command window it will do that action on every boot until you issue the command to not do it. I was stuck at the logon screen for 30 mins and the task did not complete in that time. In the end I had to boot into safe mode and fire up the gui version and reset all the verfy jobs it had in the list. (Booted up properly after that which for me was about 30 rotations of the busy icon after entering password). It was at this point that I did the "sfc" and "dsim" commands that found and fixed some issues and I am back to normal boot times.... phew

Hope this is helpful to someone.

Anybody found a fix for this issue yet? It's been like 3 months and still not fixed. I've updated BIOS and every driver that I can find and boot times is still 10-15 minutes. Every program has to be opened twice after a restart for them to respond.

@JonGraef - those are useful observations and feedback. However, it seems that you ran the verifier, and then the sfc and dism commands. It is a shame that you did not run those 2 commands BEFORE running the verifier, and then run them again afterwards.

The problem might have been that as the verifier is designed to"stress test" drivers, it might result in unexpected things happening (especially if a Kernel Mode driver, or badly designed driver is being checked). Kernel mode can read and write anywhere, and MIGHT have ended up corrupting something, that THEN had to be fixed up by the sfc and dism commands.

Did you happen to note down WHAT items were found and fixed? Did BOTH commands find a problem?

It is always possible that this resulted in a "better" driver being used, than was there initially.  If you do have the info on what was fixed up, please post it here in case it is useful for others.

@JonGraef - those are useful observations and feedback. However, it seems that you ran the verifier, and then the sfc and dism commands. It is a shame that you did not run those 2 commands BEFORE running the verifier, and then run them again afterwards.

The problem might have been that as the verifier is designed to"stress test" drivers, it might result in unexpected things happening (especially if a Kernel Mode driver, or badly designed driver is being checked). Kernel mode can read and write anywhere, and MIGHT have ended up corrupting something, that THEN had to be fixed up by the sfc and dism commands.

Did you happen to note down WHAT items were found and fixed? Did BOTH commands find a problem?

It is always possible that this resulted in a "better" driver being used, than was there initially.  If you do have the info on what was fixed up, please post it here in case it is useful for others.

Sorry, but in the intensity of the moment I did not note what was fixed.

We can only hope that a Microsoft employee has the same issue on their home computers after the 2004 update. That was the action that broke things for ones posting in this thread.

I was really impressed with the robust nature of Windows 10, until 2004 update. Never had any issues with blue screen.....

Similar issue for me.

Since the 2004 update, the boot times have increased to 5 minutes!!

Event viewer contains this entry, but I have no idea how to fix.

Quote = The winlogon notification subscriber <Profiles> took 266 second(s) to handle the notification event (Logon).

Just tried a Reboot. That took 8:50 to the point where OneDrive has completed checking for changes.

Yikes! That's worse than mine! Maybe the following directions TD47 will bring calmness into our lives. 

I have just installed the 2004 update and have encountered no problems fortunately.My boot time is 24  secs which is what it was before the update.