Probably everyone knows the feeling: the upgrade is running, the bar slowly inches forward – and suddenly it's over. Aborted. Error code 0x8007042B pops up and you're left standing there. What happened? In most cases, some program running in the background interfered with the installation. The usual suspect: the virus scanner. It notices that masses of system files are being changed all at once, considers this dangerous, and shuts everything down. But it can also be other software getting in the way. Either way – with these five steps you can get it working again.
1. Turn off the virus scanner
Yes, it sounds odd at first. But antivirus programs and Windows upgrades often simply don't get along. The scanners see all the file operations and raise the alarm, even though everything is fine. So: before the upgrade, shut down the protection completely. Not just the real-time protection – ideally the entire program. Once everything is fully installed, you of course turn it back on immediately.
2. Start Windows without the extra baggage
It's not only the virus scanner that can cause trouble. Tuning tools, cloud-sync programs, printer services – anything that spreads out in the background is a potential source of interference. That's why a so-called clean boot is worthwhile.
Here's how: press Win + R, type in msconfig, and hit Enter. On the „Services“ tab, first tick the box for „Hide all Microsoft services“, then click „Disable all“. After that, open the Task Manager (Ctrl + Shift + Esc) and, under „Startup“, remove everything that is active there. Restart the PC. Now only bare Windows is running – perfect for the upgrade.
3. Clear out the old update clutter
If previous upgrade attempts went wrong, there may be broken files lying around in the update cache. These can sabotage the next attempt right away.
To clear the cache, you need a Command Prompt with administrator rights. There, first stop the update services: net stop wuauserv, net stop bits, net stop cryptsvc, net stop msiserver. Then rename the cache folders – Windows simply recreates them afterwards: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old. Finally, bring the services back up, this time from bottom to top: net start msiserver, net start cryptsvc, net start bits, net start wuauserv.
4. Check whether Windows itself is still intact
It's all pointless if the system itself is already damaged. So before the next attempt, run the built-in tools over it once. Open the Command Prompt as administrator again and type in one after another: first sfc /scannow, then dism /online /cleanup-image /scanhealth, then dism /online /cleanup-image /restorehealth. And since it doesn't hurt: run sfc /scannow once more afterwards. Restart the computer.
5. Once more from the top – this time it works
Now everything is tidied up. The virus scanner is out of the way, no background program is interfering, the update cache is fresh, and the system files are in order. Just start the upgrade again. As a rule, it now goes through smoothly.
