Windows Booting very slow after 2004 update ,

So does that mean those initial three commands are of no value if it says the WMI repository is consistent? 

In other words, since the repository is not the culprit, do you feel this is something that an update or patch from Microsoft will have to fix?

So does that mean those initial three commands are of no value if it says the WMI repository is consistent? 

In other words, since the repository is not the culprit, do you feel this is something that an update or patch from Microsoft will have to fix? 

How would I know? I am asking the question just like yourself. Perhaps you have replied to the wrong post by mistake.

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?

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

@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).