Windows Booting very slow after 2004 update ,

@JonGraef Thanks for the EVENT logs. Other than the winlogon ones, I don't think the others are very significant.

On most users systems, the Event Log is cluttered with many unimportant "events" which are often minor functional code "logs", where various ways to start something are tried, to cover different scenerios or app or interface software versions, and error events are expected. Timing issues can cause these too, often during shutdowns and startups, where complex functions are not quite ready, next try works, but you can still get 1 or 2 error events.

HOWEVER: if you are concerned about the PERFLIB events (that may well have NOTHING to do with your long reboot times), you COULD try the commands below.

CAUTION: unless you have a system backup (system image pereferrably), do NOT perform any ADMIN commands stuff, in case it breaks your system!

Copy/paste the commands below at an ADMIN command/powershell prompt:

Solution 01:

1.) Open a CMD prompt as admin (right click on the windows start icon, choose command prompt (admin) or powershell (admin))

2.) enter

C:\Windows\system32\lodctr.exe /R

and then

C:\Windows\SysWOW64\lodctr.exe /R

If you get the error "Error: Unable to rebuild performance counter setting from system backup store, error code is 2"

(usually with the first command,repeat that command). If you get error 5, it means you were not ADMIN.

3.) Now re-register the computer´s performance libraries with the following commands

C:\Windows\System32\wbem\winmgmt.exe /RESYNCPERF

C:\Windows\SysWOW64\wbem\winmgmt.exe /RESYNCPERF

Thank you for looking over the error log.

I will hold back with any more trials/fixes, until, as you mention I have made my image backup. I will tolerate the slow startup, and see if it gets a fix in the next update.

I have a mixture of SATA DAS and iSCSI drives.  None are SSD. 

I feel positive that I had Disk Defragmentation turned off prior to the update.  However, after the update, there was a huge amount of disk activity due to a "Scheduled" optimization in progress.   This was especially annoying to me since my thin provisioned iSCSI drives were being defragmented as well as my dedicated DAS Pagefile partition.

Turning optimization off reduced my disk usage tremendously.  This is something you can easily try on your system.

If you want to turn it off, click on the Windows start prompt and type "Defrag".  Select the Defragment and Optimize Drives app.  For each drive, ensure that Scheduled optimization is turned off.

@JonGraef Thanks for the EVENT logs. Other than the winlogon ones, I don't think the others are very significant.

On most users systems, the Event Log is cluttered with many unimportant "events" which are often minor functional code "logs", where various ways to start something are tried, to cover different scenerios or app or interface software versions, and error events are expected. Timing issues can cause these too, often during shutdowns and startups, where complex functions are not quite ready, next try works, but you can still get 1 or 2 error events.

HOWEVER: if you are concerned about the PERFLIB events (that may well have NOTHING to do with your long reboot times), you COULD try the commands below.

CAUTION: unless you have a system backup (system image pereferrably), do NOT perform any ADMIN commands stuff, in case it breaks your system!

Copy/paste the commands below at an ADMIN command/powershell prompt:

Solution 01:

1.) Open a CMD prompt as admin (right click on the windows start icon, choose command prompt (admin) or powershell (admin))

2.) enter

C:\Windows\system32\lodctr.exe /R

and then

C:\Windows\SysWOW64\lodctr.exe /R

If you get the error "Error: Unable to rebuild performance counter setting from system backup store, error code is 2"

(usually with the first command,repeat that command). If you get error 5, it means you were not ADMIN.

3.) Now re-register the computer´s performance libraries with the following commands

C:\Windows\System32\wbem\winmgmt.exe /RESYNCPERF

C:\Windows\SysWOW64\wbem\winmgmt.exe /RESYNCPERF

@Robert Mumps - yes, if the first command show it is consistent, that is not the issue. The 2004 Feature Update was a BIG update, and different configs are behaving differently, and the majority (especially those with SSD disks) are OK. I have been prodding the Performance Group (AskPerf) to start topics and dialogue, but I am just a mere user, so don't hold your breath for fixes. It depends on how many users shout loudly at MS of course... (and how much telemetry they get back that shows issues).

You did not need to do the other  commands as it is consistent and in sync. I suspect the errors are due to other service dependencies, and it would need to be done from a "safe mode" boot. If you still have a long booting time then it is something else, maybe a large external disk or NAS that it is trying to check out during the blank screen phase?

I don't have any attached drives at boot, or NAS.

Was the Events.evtx of any use to identifying any issue that needs to be fixed.

Events log