Because 2004 is a bit immature and the drivers are not available yet for many manufacturers, if you see a similar issue, consider rolling back to 1903/09.
https://www.yourwindowsguide.com/2020/05/uninstall-windows-10-version-2004.html
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Because 2004 is a bit immature and the drivers are not available yet for many manufacturers, if you see a similar issue, consider rolling back to 1903/09.
https://www.yourwindowsguide.com/2020/05/uninstall-windows-10-version-2004.html
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?
It's not an external disk, so that's out of the question. Personally, I think we're all huffing and puffing & then the update will slide down the tubes and that will be the end of this conversation.
Stay healthy man! Thanks for your efforts & helps!
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
@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).
I'm one of those who is using an SSD & that's what's making me think as you suggest, a big update brings a lot of lovely griefs with it. Thanks for the reply!
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.
Possibly but you're still supposed to know the answer!