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?
Windows Booting very slow after 2004 update ,
Windows for home | Windows 10 | Performance and system failures
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.
128 answers
Sort by: Newest
-
Anonymous
2020-07-09T10:07:49+00:00 -
Anonymous
2020-07-09T09:40:26+00:00 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.
-
Anonymous
2020-07-09T09:30:13+00:00 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?
-
Anonymous
2020-07-09T08:50:43+00:00 Here are the errors from the Event log dump, last two days
-
Anonymous
2020-07-09T08:48:45+00:00 So all that means?