2016 server, Package KB5068864 failed to be changed to the Installed state. Status: 0x800f0922.

Davies, David 0 Reputation points
2025-12-04T09:53:44.1033333+00:00

Hi

I have a 2016 Standard server, that up until the November update has been fine.

The update was pushed and the server rebooted. When logging in first noticed that the server manager was all red, then went to check and the update had failed. I set the server to reboot over night and tried to manually add the updated, downloaded from the Microsoft Catalogue.

Rebooted overnight and had the same result.

Did a sfc /scannow found a few errors.

Did a dism /online /cleanup-image /restorehealth

Rebooted, tried to patch same result.

Did a sfc /scannow got no errors.

In the event viewer i found this error message

Package KB5068864 failed to be changed to the Installed state. Status: 0x800f0922.

I am now stuck as to what to do now, this is a first for me after 25 years in IT.

So please be gentle on me.

Thanks in advance for any help offered.

Windows for business | Windows Server | Devices and deployment | Install Windows updates, features, or roles
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Q&A Assist
    2025-12-04T09:54:06.03+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error code 0x800f0922 typically indicates that there is a problem with the installation of Windows updates, often related to corrupted scheduled tasks or issues with the Windows Update components. Here are some steps you can take to resolve this issue:

    1. Check for Staged Packages: Use the following command in an elevated Command Prompt to find any staged update packages:
         Dism /english /online /get-packages /format:table | findstr /i "Staged"
      
      If you find any staged packages, you can remove them with:
         Dism /online /remove-package /PackageName:<Your_Package_Name>
      
      Replace <Your_Package_Name> with the actual package name found in the previous step.
    2. Clean Up Corrupted Tasks: The error may be related to a corrupted scheduled task. You can identify the SecureBootEncodeUEFI GUID using:
         reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI" /v ID
      
      Once you have the GUID, you can delete the registry values associated with it to clean up the corrupted tasks.
    3. Run DISM and SFC Again: Since you have already run DISM and sfc, ensure that you are connected to the internet when running these commands, as DISM can retrieve necessary files from Microsoft Update servers. Run:
         DISM.exe /Online /Cleanup-image /Restorehealth
      
      Followed by:
         sfc /scannow
      
    4. Reboot and Retry the Update: After performing the above steps, reboot your server and try to install the update again.
    5. Contact Microsoft Support: If the issue persists after trying the above steps, consider reaching out to Microsoft Customer Service and Support for further assistance.

    These steps should help you troubleshoot and hopefully resolve the update installation issue you are experiencing.


    References:

    0 comments No comments

  2. Quinnie Quoc 7,700 Reputation points Independent Advisor
    2025-12-04T10:49:18.0133333+00:00

    Hello Davies, David,

    First, calm down David. Don't worry!

    The error code 0x800f0922 on Windows Server 2016 typically indicates that the update could not complete due to either missing system components, issues with the servicing stack, or insufficient space in the system-reserved partition. Since you’ve already run SFC and DISM successfully, the next steps would be to check whether the Servicing Stack Update (SSU) for Server 2016 is installed, as missing SSUs often cause cumulative updates to fail. You may also want to verify that the system-reserved partition has enough free space, as updates can fail silently when this partition is full.

    Another helpful step is to clear the SoftwareDistribution and Catroot2 folders, then reboot and attempt the update again. If the issue persists, installing the update using an in-place upgrade repair (keeping files and roles intact) often resolves stubborn servicing issues on Server 2016.

    I hope these suggestions help you move forward and get the server patched successfully.

    If this response helps resolve your issue, please consider clicking “Accept the Answer” so others in the community can benefit from the solution as well. and it also support me too.

    Thank you so muchh!

    Best regards, QQ.


  3. Davies, David 0 Reputation points
    2025-12-09T09:22:13.0866667+00:00

    Hi I have tried all the suggestions above and still have the same issue.

    Any other suggestions?

    0 comments No comments

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.