KB5017389 Fails to install in Windows 11 on Error 0x800f0922

Several users complained about getting an error code 0x800f0922, 0x8007054f, or 0xe0000100 when installing the KB5017389 on their PCs. KB5017389 is basically an enablement package that upgrades Windows 11, version 21H2 to version 22H2.

This new version of Windows 11 brings several new fixes, and quality improvements to the taskbar, task manager, File Explorer, and others. That’s the reason why many users are willing to update their devices to this new version. If you are one such user and are facing this trouble, learn what you may do to overcome this issue.

KB5017389 Fails to Install on Error 0x800f0922

Read Also: KB5017389 Fixes Major Issues on Windows 11 22H2

When Will I receive KB5017389 Update?

Microsoft releases new feature updates in batches, so if you haven’t yet found this enablement package on your PC, wait for some more time. Since this optional update isn’t available to all users and so many users are continually upgrading to this version, this might some more time to reach your device.

What causes KB5017389 to fail on Error 0x800f0922

If you have already received this optional update, however, it is failing on some error code, there must lie some internal glitches within your system. In such cases, even after you download this enablement package, it might fail to install on some error code 0x800f0922, 0x8007054f, or 0xe0000100. A few users reported that the installation begins and after some time, it starts rolling back to the previous version.

Well, there could be different reasons that are blocking this feature update to install on your computer. However, you may try a few troubleshooting methods and see if you can download this KB5017389 without getting into an error code.

The potential fixes are as follows –

1] Run Windows Update troubleshooter

Go to Settings > System > Troubleshoot > Other troubleshooters, and hit Run available beside Windows Update. Follow the on-screen instructions and comply as the troubleshooter says.

2] Purge SoftwareDistribution and Catroot2 folders

These two are basically Windows cache folders and retain all updates-related information. When their sizes exceed the permissible limit, this may result in different error codes including the ones you are getting while upgrading to Windows 11 22H2. Follow this article on how to clear these folders and have your device upgraded to Windows 11 2022.

3] Lack of Storage Spaces

Windows 11 requires at least 64 GB of free storage space to install version 22h2 successfully. If your root drive lacks this much space, it’s not possible to upgrade to version 22h2 on your PC. Go to Settings > System > Storage, and clear temporary files. If possible, remove the installed spaces to generate even more disk spaces and attempt again to install Windows 11, version 2022.

4] Remove Third-party Antivirus Program

If you are using some third-party antivirus program, this may also restrict upgrading to Windows 11, version 22H2 on your computer. This happens when the installed antivirus has some compatibility issues with the new version. You may even provide feedback to its manufacturer so that the issue resolves at the earliest.

For now, you may uninstall or temporarily disable the antivirus that you are using and check if you can now upgrade your system to Windows 11, version 2022.

5] Manually install KB5017389 on your PC

If neither of the above fixes addresses this error code 0x800f0922 on your PC, you are left with only one option. This involves manually downloading KB5017389 from Microsoft Update Catalog and later installing that on your computer.

Since the downloaded standalone package is in the .msu file format, double-click on it, and your system starts upgrading to the latest OS Build version. Make sure to download the file matching your system architecture.

If you are still struggling with error codes 0x800f0922, 0x8007054f, or 0xe0000100 while installing Windows 11, version 22h2, follow in-depth articles on these issues.

Leave a Reply

Your email address will not be published. Required fields are marked *