Another good tip - use
Update Manager for Windows 1.1b on Github. On that page, just download the zip file, and use it - no installation. It's a simple little app that manages the Windows Update process for you.
It's been around a while, and it works great on Windows 11.
Here is an article about it on TheWindowsClub for Windows 10, in the day.
I recommend this, because you can run it, hit the search button, and it will show you the KB5037858 download. You select it, hide it. Then, open Windows 11 Settings/Windows Update. Click "Pause for a Week". Then click "Resume Updates". Windows Update will run, process any other updates you may have, and you will not see the offending cumulative update! Windows Update is now clean, and you can easily get other updates and wait for the next cumulative update that fixes this.
****By the way, IMHO I think this is a Windows/MS problem. People not using Parallels have reported the same error(s) on other forums, and what some risky souls did was move to a newer build - Canary, Dev builds - and the problem is not there. Now, don't do that without thinking about it, as those builds are much less stable than the Beta build, and it's much harder to go back down to Beta build from them, vs. moving up to Dev/Canary builds. But it does offer some confidence that this could be fixed soon, even in the next update.
If you have not reported it on the Windows Insider Feedback Hub, please do so!!! The more that do, the higher visibility the problem has!
Click to expand...
