Windows Security Update Error Feb 2025 : 0x800f0922

Anonymous
2025-03-13T14:24:46+00:00

Hi all,

Getting Error on around 40 devices for Windows Updates: Installing Feb 2025 Security Update Win 10 64 bit (KB5051974)

We have 1000 devices total and it only seems to be occurring on around 40 of them, but its the same problem on each.

Windows Update forces restart and then after booting back up it says cannot complete update, reverting changes.

Have tried SFC Scannow / DISM Repairs but same issue repeatedly occurs. Also tried manually completing the updates by downloading from the catalog but same error occurs there.

Error Code Showing in Windows Update is : 0x800f0922

Any help would be appreciated.

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

51 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ramesh Srinivasan 88,100 Reputation points Independent Advisor
    2025-03-13T17:13:03+00:00

    Hi Haydar,

    It's the same issue on the other system.

    Let me know if the clean boot method helps. If not, we can try rebuilding the EFI partition via Windows RE.

    In that case, please open Disk Management and maximize it. Adjust the column widths in the top pane to make all the entries visible. Post a screenshot.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-03-13T17:01:34+00:00

    Thanks Ramesh - I did notice it mentioned an error related to the partition, but was unsure how to proceed as I was unable to extend the partition space to see if that would sort the issue.

    Here are the logs from another affected machine and I'll try the clean boot on one of the machines to see if that sorts it as well. https://1drv.ms/f/c/c1fe5b084b25142c/EmPLN6t0jLZJu6emSzEBo90BRW3NrWX1H6P9wUiiOhPJnA?e=04GhbP

    Do you know why it would be affecting only 30 of our devices and the remaining devices would all have taken the update ok?

    Thanks,

    Haydar

    Was this answer helpful?

    0 comments
  3. Ramesh Srinivasan 88,100 Reputation points Independent Advisor
    2025-03-13T16:27:41+00:00

    Hi Haydar,

    The update failed while copying the boot files to the EFI partition. A 3rd party security suite can cause this, but I don't think there is any 3rd party antivirus installed on the computer.

    Please do the following:

    1. Clean boot windows . A clean boot is the process of starting Windows without loading third-party apps and services. Please see this Microsoft article for more information.

    How to perform a clean boot in Windows - Microsoft Support:

    https://support.microsoft.com/en-us/topic/how-t...

    (Step 3 is very important. You need to first enable "Hide all Microsoft Services" before clicking "Disable all".)

    1. Collect the CBS logs from another affected computer. Let me check if it's caused by the same issue.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-03-13T16:12:00+00:00

    Was this answer helpful?

    0 comments
  5. Ramesh Srinivasan 88,100 Reputation points Independent Advisor
    2025-03-13T15:59:11+00:00

    Hi Haydar,

    It appears that the update is rolling back due to a fatal error. We must inspect the CBS logs to determine why the update failed to install.

    Please upload your CBS logs to OneDrive and share the link here. To collect the CBS logs, open admin PowerShell and run:

    GCI -Path 'c:\windows\logs\cbs\*.*', 'c:\windows\inf\setupapi.dev.log' | Compress-Archive -destination (join-path ([environment]::GetFolderPath('Desktop')) \CBS.zip)

    This creates a file named CBS.zip on your desktop.

    Share the file on OneDrive and post the link here.

    ***************************

    Share OneDrive files and folders - Microsoft Support:

    https://support.microsoft.com/en-us/office/shar...

    :: OneDrive sharing options - screenshot ::

    https://imgur.com/a/vZyxpY9

    Was this answer helpful?

    0 comments