Since my last visit at my parent’s home, I have a little support case lying around here. The notebook of my mother (Sony Vaio, Win 10) was very slow and came up with strange behaviour. The result of my analysis was, that the cumulative Windows Update 2017-09 was causing the problems. And what does this beautiful piece of software called Windows Update do? It downloads the update again, and again, and again and tries to install it again, and again and …
So, obviously this slows down the machine. Ok, so I downloaded the specific Windows Update again manually and tried to install it. And again: Error message. 0x80073712. The error means that there is something wrong with the Windows Update files or the update package itself.
The first advice found after a short search was to disable all software, that might interfere the Windows update. So I deactivated anti-virus scanner, Vaio update and other suspect software and restarted the installation. Same problem.
I remembered that in former Windows version you were able to change to a Safe Mode to do some administrative tasks and repair the system. You can still do this in Win10: Just hold the Shift key and click the restart button in the start menu. Windows than asks you which kind of repair procedure you want to use.
Okay, so Windows booted in Safe Mode and I thought I could run the update now manually to fix the issues. Instead of starting the update procedure windows prompted me, that it is not possible to run update in Safe Mode. What the fuck? I wanted to repair that fucking machine and install latest updates and it is even in Safe Mode by design not possible?
Ok, next idea: Repair the Windows Update installation. There is a specific command for that:
DISM.exe /Online /Cleanup-image /Restorehealth
I’ve started Power Shell with administrative rights and after this, I was finally able to execute the Windows update. After that the latest updates run automatically again, like they should.
So, if you have any issue with this problem, I suggest to run the command at first and try again. Some Microsoft sites tell you that you should run the parameter /ScanHealth at first. But the execution takes some time and it saved me a lot of time to just repair it immediately.
This has become a little ranting, sorry about that. For the future this will serve as a kind f knowledge base article for me, because tech support in family comes regularly especially around Christmas. 😉