Lorene Melone
How To Fix Windows 11 Update KB5063060 Installation Error 0x800f0991
If you’re seeing the error code 0x800f0991 pop up while trying to get the KB5063060 update on Windows 11, you’re definitely not alone. This one’s a bit of a pain because it stalls the update process, and honestly, Windows can be kinda good at making this more complicated than it needs to be. So, here’s a rundown of some steps that have actually helped, based on experience. Not everything’s perfect, but at least it’s a shot in the dark that might get you closer to a working update.
Prerequisites
Before jumping into the troubleshooting, make sure you’ve got:
- Admin privileges on your Windows 11 setup (because otherwise, good luck running most commands).
- Internet connection—obvious, but can’t hurt to mention.
- A recent backup of anything critical—because dealing with updates sometimes leads to funky stuff, even if it’s supposed to be safe.
Step 1: Start the App Readiness Service
First off, I’ve seen this service kinda drone on in the background, and sometimes it just needs a little nudge or a fresh start. This helps Windows get ready to install updates properly, especially if some services are misbehaving or not running. Open Services by pressing Windows + S and typing services. Find App Readiness, right-click, then pick Properties. Set the Startup type to Automatic, hit Apply, then press Start if it’s not already running. Click OK. Sometimes, the service already starts on its own, but just making sure it’s set correctly can save headaches down the line.
Step 2: Move the $WinREAgent Folder
This part might be a bit weird, but on several machines, this folder causes conflicts with updates. Navigate to This PC > Local Disk (C:) > $WinREAgent. If you don’t see it, flick on Hidden items from the View tab. Copy the whole folder to your desktop for backup, then delete it from the original location. Because of course, Windows has to make it harder than necessary. Sometimes, it’s the leftover files that trip up the update process, so clearing this out can clear the way. Just make sure to restore it if things go sideways.
Step 3: Run the Windows Update Troubleshooter
Windows has this built-in troubleshooter that’s not perfect but can catch common issues. Open Settings with Windows + I. Navigate to System, then Troubleshoot. Click on Other troubleshooters and find Windows Update. Hit Run. Follow whatever it suggests—sometimes, it plans to reset some services or fix registry issues. Doesn’t always fix the problem, but it’s quick and easy to try first.
Step 4: Restart Windows Update and BITS Services
This is about giving Windows a fresh start on crucial services. Open Services again (Windows + S, type services). Find Windows Update, double-click, then set to Automatic. Hit Start if it’s stopped, then click OK. Doing the same for Background Intelligent Transfer Service (BITS) can help keep the download process smooth—because of course, Windows has to hog resources somewhere, and BITS is key for updates.
Step 5: Use the Windows 11 Installation Assistant
If update stubbornness persists, using the official Windows 11 Installation Assistant sometimes kicks the process that auto-updates won’t. Download it, run it, and follow the prompts. Not gonna lie, this can sometimes fix that pesky error by forcing the upgrade/installation over the broken bits.
Step 6: Use the Microsoft Update Catalog for the KB
Another option—if you’re comfortable with manual installs—is to head over to the Microsoft Update Catalog. Search for KB5063060. Download the x64 version (or ARM if your device uses it). Install it manually by running the downloaded file, then restart. Sometimes, the update throws a hissy fit when auto-installation fails, and manual installation skips the worst of the errors.
Step 7: Reset Windows Update Components
If all else fails, a deep reset of the update components can clear corrupted files and settings. Open Notepad, paste these commands:
SC config trustedinstaller start=auto
net stop bits
net stop wuauserv
net stop msiserver
net stop cryptsvc
net stop appidsvc
Ren %Systemroot%\SoftwareDistribution SoftwareDistribution.old
Ren %Systemroot%\System32\catroot2 catroot2.old
regsvr32.exe /s atl.dll
regsvr32.exe /s urlmon.dll
regsvr32.exe /s mshtml.dll
netsh winsock reset
netsh winsock reset proxy
rundll32.exe pnpclean.dll,RunDLL_PnpClean /DRIVERS /MAXCLEAN
dism /Online /Cleanup-image /ScanHealth
dism /Online /Cleanup-image /CheckHealth
dism /Online /Cleanup-image /RestoreHealth
dism /Online /Cleanup-image /StartComponentCleanup
Sfc /ScanNow
net start bits
net start wuauserv
net start msiserver
net start cryptsvc
net start appidsvc
Save it as Wufix.bat on your desktop. Right-click, run as administrator, and let it do its thing. Expect it to take a few minutes, and then restart your PC. Sometimes this smashes through stubborn update errors completely.
Step 8: Use the Media Creation Tool
When all else fails, grab the Media Creation Tool. It’s a bit heavy-handed, but it forces the OS to repair itself or upgrade cleanly. Run it, follow the prompts to make a bootable USB or upgrade directly, then see if the update finally sticks.
Extra Tips & Common Issues
Keep services set to Automatic. Sometimes, when updates hang, they’re just waiting for a service to kick in, but Windows hasn’t started it. If you get stuck midway, double-check all service settings and make sure none are disabled. Also, some people report that rebooting after each major step actually helps the changes take effect.
Summary
- Check that key services like App Readiness and Windows Update are running with correct startup types.
- Clear or move problematic folders like $WinREAgent.
- Run the built-in troubleshooter.
- Reset Windows Update components manually if needed.
- Try manual install via the Microsoft Update Catalog or Media Creation Tool.
Hopefully this shaves off a few hours for someone. Sometimes, fixing Windows updates feels like a game of whack-a-mole — but at least now, there are some options that actually work instead of just hitting snooze on the problem.