Windows 11 24H2 update fails - Error 0x800F0922

gbecaernsk-8578 20 Reputation points
2025-12-04T12:44:53.31+00:00

I want to update Windows 11 23H2 Enterprise to Windows 11 24H2 Enterprise. Every time, the installation fails at approximately 71% with error code 0x800F0922. I find the following message in setuperr.log:

Operation failed: Add [1] package C:\Windows\SoftwareDistribution\Download\f83350afb4c1d64276dd0ea60099a021\Windows11.0-KB5070186-x64.cab to C:$WINDOWS.~BT\Sources\SafeOS\SafeOS.Mount. Error: 0x800F0922[gle=0x000000b7]

The official solution to Error 0x800F0922 from Microsoft does not help because the entry SecureBootEncodeUEFI does NOT exist in the registry and I can't find any staged update packages: https://learn.microsoft.com/en-us/troubleshoot/windows-server/installing-updates-features-roles/error-0x800f0922-installing-windows-updates

Clearing the Windows Update cache did not help either.

sfc /scannow did not help either: https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e

Windows for business | Windows 365 Business
0 comments No comments
{count} votes

Answer accepted by question author
  1. Harry Phan 9,835 Reputation points Independent Advisor
    2025-12-04T13:30:23.4833333+00:00

    Hello gbecaernsk-8578

    Error 0x800F0922 during the upgrade to Windows 11 24H2 Enterprise often points to a problem with the SafeOS phase of setup, normally caused by corrupted system files, insufficient space in the System Reserved partition or driver/firmware conflicts. Since clearing the update cache and registry checks didn’t help, the next step is to repair the OS image, check partition space, and attempt an in‑place upgrade using the ISO with logging tools like SetupDiag to pinpoint the failure.

    Few steps I would recommend:

    1. Verify the System Reserved partition has at least 500 MB free.
    2. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to repair system files.
    3. Update storage, chipset, and BIOS/UEFI drivers to the latest versions.
    4. Temporarily disable antivirus or security tools during the upgrade.
    5. Use SetupDiag to analyze logs for the exact blocking component.
    6. Attempt an in‑place upgrade with the 24H2 ISO (setup.exe → “Keep files and apps”).

    Try and let me know if it works.

    Harry.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.