Windows Booting very slow after 2004 update ,

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.

@JonGraef - that is an interesting observation, BUT it might be an effect rather than a cause. Nontheless, I have seen old and new reports where the Windows WMI (WBEM) repository can get out of sync with "reality" (i.e. what bits and peices under the "hood" are where, and other properties), and cause that event 6006, and a slow boot or slow display of login screen. There is an easy way to check it out, and if the first "verify" command works, then go no further, it has probably got rebuilt OK:

"

• To perform a repair/re-sync of the  Windows 10 WMI repository:
  1. Open an elevated command prompt. (right click the start menu icon, choose admin cmd or powershell)
  2. Verify the WMI repository is not corrupt by running the following command:
  winmgmt /verifyrepository
• If the repository is not corrupted, a “WMI Repository is consistent” message will be returned; if you get something else, go to step 3, otherwise if the repository is consistent, more troubleshooting will be required as the repository is not likely the problem.

1. Run the following commands to repair WMI: winmgmt /salvagerepository

• If the repository salvage fails to work, then run the following command to see if it resolves the issue: winmgmt /resetrepository
• After the last command, there should be a “WMI Repository has been reset” message returned that verifies the command was successful.

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.

Mine is a weird & wonderful situation. The Restart just hangs near two minutes but from thereon in, everything is normal. The Shutdown is very good and a cold boot is fast enough, but it's just this Restarting thing that hangs!

I was replying to Andoheb's post. This does vary, does not fix it for everyone.

FYI: it sounds like you stopped the services, but forgot to right-click on each one, and go to "properties" then change from automatic (or whatever it was set to) to DISABLED - that is an important step otherwise it will just start up on reboot.

Not sure what you mean by each one. When I checked in there, I only saw the one thing and disabled it. Nothing changed. 

As JC says, this isn't working for him & doesn't do anything on this end either. Why am I still suspecting this has to do with an update?