How to fix
KB5063878 installation failure
on Windows 11
KB5063878 is a crucial cumulative security update for Windows 11 version 24H2. Some users face issues where the update fails to install, often rolling back during the process. This article provides solutions to successfully install the update.
Is this your error?
Match two or more signs — you are likely dealing with KB5063878 installation failure.
What causes KB5063878 installation failure?
- Insufficient disk space
- Corrupted system files
- Damaged Windows Update components
- Conflicts with drivers
- Security software interference
- Network interruptions
Fix in 9 steps
Use the built-in troubleshooter to detect and fix update issues.
Ensure Windows Update services are running and set to automatic.
Stop services, rename folders, and restart services to reset components.
Ensure at least 20GB of free space is available for the update.
Temporarily disable antivirus software during the update process.
Use Disk Cleanup to remove unnecessary files and free up space.
Use SFC and DISM commands to repair system files.
Download and install the update directly from the Microsoft Update Catalog.
Perform an in-place upgrade to reinstall Windows 11.
Repairs Windows system files, removes malware, and restores a clean OS state — without reinstalling.
Fix 1. Run the Windows Update troubleshooter
The built-in troubleshooter can detect and fix issues preventing KB5063878 from installing.- Type troubleshoot in Windows search and press Enter, or go to Start > Settings > System > Troubleshoot.
- From the list of Options, pick Other troubleshooters.
- Scroll down to locate Windows Update and click Run.
- Wait for it to finish, then apply changes and reboot the system.
Fix 2. Check services
- Type in Services in Windows search and press Enter.
- Locate Windows Update Service.
- If it is already running, right-click and select Restart.
- If the service is not running, double-click it to open Properties.
- Under the Startup type, select Automatic from the drop-down menu.
- Click Start, Apply, and OK.
- Locate Background Intelligent Transfer Service (BITS), Cryptographic service, and Windows Installer service, and repeat the process.
Fix 3. Reset Windows Update components
- Type in cmd in Windows search.
- Right-click on Command Prompt and select Run as administrator.
- User Account Control window will show up - click Yes when prompted.
- Stop the Windows Update Services by entering the following commands, one at a time, and pressing Enter after each: net stop wuauserv net stop cryptSvc net stop msiserver net stop bits
- Rename the SoftwareDistribution and Catroot2 folders with the following commands: ren C:WindowsSoftwareDistribution SoftwareDistribution.old ren C:WindowsSystem32catroot2 catroot2.old
- Restart the services you stopped earlier with these commands: net start wuauserv net start cryptSvc net start msiserver net start bits
- Close the Command Prompt window and try updating Windows again.
Fix 4. Check disk space
Insufficient disk space can prevent updates from installing. Ensure there is at least 20GB free.- Navigate to Settings > System > Storage.
- Review available space on all drives. If space is low, consider deleting unnecessary files or moving data to an external drive.
- Empty the Recycle Bin and remove Temporary Files using Disk Cleanup.
Fix 5. Disable third-party antivirus software
Third-party antivirus software can interfere with Windows updates. Temporarily disable it during the update process.- Locate your antivirus icon in the system tray.
- Right-click and select Disable or Pause protection.
- Choose a time frame that covers the update process.
- After the update, re-enable your antivirus to maintain protection.
Fix 6. Perform Disk Cleanup
- Type Disk Cleanup in Windows search and hit Enter.
- If your Windows is installed on drive C, pick it from the list (it should be by default) and press OK.
- Click Clean up system files.
- Select your main disk again and click OK.
- Select the largest portions of the data used - these typically include Temporary Internet Files, Windows Update, Temporary Files, Recycle Bin, Delivery Optimization Files, and others.
- Click OK - the process should be finished shortly.
Fix 7. Run the System File Checker and DISM
- Open Command Prompt as administrator.
- Copy and paste the following command, pressing Enter after: sfc /scannow
- Wait till the scan is finished. If Windows finds system file integrity violations, it will attempt to fix them. After this, use the set of the following commands, pressing Enter each time: DISM /Online /Cleanup-Image /CheckHealth DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth
- (Note: if you get an error executing this last command, add /Source:C:RepairSourceWindows /LimitAccess to it and try again).
- Close down the Command Prompt and restart your computer.
Fix 8. Install the update manually
- Go to the official Microsoft Update Catalog website.
- Type the KB number into the search bar (in this case, KB5063878), and click Search.
- You will find many different versions on the update – you need to find the one that matches your PC specs and Windows version (as a home user, ignore Windows server versions).
- After picking the correct version, click the Download button and proceed with the on-screen instructions.
- Restart your computer to implement the new updates.
Fix 9. Use Media Creation Tool
The Media Creation Tool can be used to perform an in-place upgrade, which can help bypass certain update errors by reinstalling Windows 11 while keeping files and applications intact.- Visit the official Microsoft website and download Windows 11 installation media.
- Double-click the installer and select Yes when UAC shows up.
- Agree to terms.
- Select Upgrade this PC now and select Next.
- Windows will now download all the necessary files – it might take a while.
- Agree to the terms once again and click Next.
- Before installing, ensure you are happy with your choices (otherwise, you can click the Change what to keep option).
- Click Install to begin the upgrade process.
Fix 10. Work around 0x80240069 errors with Known Issue Rollback (KIR)
Microsoft has acknowledged that some enterprise-managed devices encounter 0x80240069 when installing KB5063878 via WSUS. A Known Issue Rollback (KIR) policy is being rolled out, but administrators can apply it manually to affected devices.- Download the Known Issue Rollback Policy [direct download link].
- On the affected device or domain controller, open Group Policy Editor (gpedit.msc) or Group Policy Management Console for domain policies.
- Navigate to the policy path where the KIR setting is provided for Windows 11 version 24H2.
- Enable the KIR Group Policy provided by Microsoft for KB5063878.
- Apply the policy to the targeted devices (either via local policy or domain-wide).
- Restart the affected devices to ensure the setting takes effect.
- Once applied, try installing KB5063878 again.
Bottom line
To fix the installation failure of KB5063878, you can run the Windows Update troubleshooter, check services related to Windows Update, and ensure your system meets all prerequisites. If these steps do not resolve the issue, consider using the automatic PC repair tool or further advanced repairs.
Frequently asked questions
The error code indicates issues with Windows Update services being unable to authenticate or connect to update servers.
Ensure there is at least 20GB of free disk space.
Yes, temporarily disable third-party antivirus software during the update process.
Try running the Windows Update troubleshooter and resetting update components.
Yes, download the update from the Microsoft Update Catalog and install it manually.
9 comments
The top answer is outdated — running `sfc /scannow` is a good start, but also try resetting Windows Update components. Check for Windows Update troubleshooter under Settings > Update & Security > Troubleshoot. If that doesn't work, consider temporarily disabling security software to rule out conflicts.
Cheers, Marcus! That actually makes a lot of sense. I was wondering if it was just a simple update glitch or something deeper. I’ll definitely give the `sfc /scannow` a go and check my disk space. I’ve heard about those legacy drivers causing trouble too. If I get stuck again, I might take a peek at the Event Viewer like you suggested. Grand advice, mate!
Yeah, Marcus, I totally agree! The real issue is probably linked to those Windows Update components you mentioned. I’ve actually seen problems like this in production environments before. From a best practices standpoint, it’s also smart to ensure that security tools aren’t blocking any processes. Since 0x80240069 can be tricky, maybe also consider clearing the Windows Update cache? That’s often overlooked but can actually help resolve conflicts. Edit: to add more context—checking the Event Viewer is a great idea to get to the bottom of this!
Oh, cheers for that, Marcus! Totally agree, the error codes can be a right pain. I’ve seen the `sfc /scannow` mentioned a few times, but I haven’t tried it yet. I’ll give that a go and check the space and drivers too. Just one silly question: how do I actually check the Event Viewer for those logs? Thanks a million!
Leave a reply




The error code 0x80240069 can indeed be frustrating, but it typically signals an underlying issue rather than a fundamental flaw with the update itself. The steps outlined in the article are generally sound, particularly the focus on resetting Windows Update components, which addresses many common problems.
It's also worth considering checking for any disk space issues or fragmented files that could impede the installation process. You might also want to review compatibility with existing drivers or security software, as conflicts in those areas often lead to installation failures. If the problem persists after these steps, using the System File Checker (`sfc /scannow`) can be a prudent measure to identify and repair corrupted system files. Finally, if you prefer a more automated approach, leveraging the built-in repair tools may yield quicker results. Good luck!
Yeah, I totally agree with you, Marcus! The `sfc /scannow` is definitely a best practice for picking up any underlying issues, especially when dealing with those frustrating installation codes. It's interesting how temporary files can mess with the whole process too. Actually, what you want to do here is ensure that all your drivers are up to date, as they can often create those conflicts you mentioned. Just a classic Windows moment, right? Haha! Edit: to add more context — I've seen this before in production environments too!
Hi Marcus! You’ve made some excellent points about addressing underlying issues that can lead to installation failures. Checking for disk space and driver conflicts is always a good call. I’d also emphasize that running the System File Checker (`sfc /scannow`) can really help identify any corrupted files that might be causing trouble. If anyone is feeling overwhelmed, remember that the built-in repair tools can simplify things, too! Thanks for sharing your insights!
Thanks for sharing those insights, Marcus! I completely agree that error codes like 0x80240069 often point to underlying issues rather than the update itself being the problem. Checking disk space and potential driver conflicts is definitely a good call. Also, using the System File Checker (`sfc /scannow`) can be a great step for anyone experiencing persistent issues. If anyone needs a step-by-step for that or the built-in repair tools, just let me know and I'm happy to help! Happy troubleshooting!
Hey Marcus, I get where you’re coming from, but I’d put my money on the idea that this is a hardware issue lurking under the surface. Before diving deep into those software fixes, run CrystalDiskInfo on that drive and check for errors. Nine times out of ten, it’s the hardware causing these headaches. Keep an eye on your temps too—could be a failing PSU. Just my two cents!