And it can take alot of researching to find the cause and the solution.Microsoft Community Chat Helpful resources I don’t like Microsoft, but this experience does show that sometimes problems are caused by third party software. This problem was solved in newer version of Macrium Reflect. So the problem was Macrium Reflect not removing the reference ro their winmount.sys, even after uninstalling Macrium Reflect.
I exported that other laptop registry key for the winmount location, removed some stuff that were not needed and imported it into the registry of the laptop that I was tyring to upgrade to v18.09. On that other laptop I had not installed Macrium Reflect. I then saw at the winmount location in the registry that it was refering to a Macrium Reflect driver, and that was different than what the registry in win10 on my other laptop showed. I then found similar problems mentioned at these websites: That info gave me some terms to search for on the internet. The error seems to be not being able to mount the winre.wim file that is in the C:\$Windows.~BT\Sources\SafeOS dir. I searched the log file for errors and warnings and found a warning about a missing Macrium Reflect winmount.sys file. The setup program had created a 14 MB setupact.log file in C:\$Windows.~BT\Sources\Panther. After a day of trying various things and doing research I finally found the solution.
I then booted to Windows 10 v18.03, mounted the v18.09 iso and ran it’s setup file. I booted to Linux and downloaded the v18.09 iso from the Microsoft website. Here is my past experience of upgrading Windows 10 v18.04 to v18.09: Now You: do you have a specific strategy when you run into errors on Windows?
Users who give up in frustration may leave their system open to attacks, as vulnerabilities may not be patched because of the update error. While experienced users and administrators known what to do, usually, it is inexperienced users that may have a hard time understanding what is going on. It can be quite frustrating to run into error code 0x80070422 when trying to update Windows.
If the manual approach is not working, you may want to run the Windows Update troubleshooter to find out if it can correct the issue on the Windows device. When you run a check for updates after you have started the service, updating should work fine and updates should be found and installed on the device just like before. The following two screenshots highlight the changes that you need to make: