Server 2016 Std | unable to install CUs after 2022-02 CU | error 0x800F0922

Max R 1 Reputation point
2023-05-24T14:45:51.8+00:00

Hello,

new customer of mine has 10 domain controllers (2 physical and 8 virtual). These domain controllers were on a very old state "2019-05 Cumulative Update" or "2019-12 Cumulative Update". I wanted to update these domain controllers to the current state "2023-05 Cumulative Update".

But on each server I always got the error 0x800F0922 no matter if I tried to install the update from WSUS or manually downloaded from MS Update Catalog. Then I tried to install previous Cumulative Update 2023-04, 2022-08, 2022-06, 2022-04 and I always got the error 0x800F0922. After that I went forward instead of backward and was able to install 2019-12, 2021-08 and 2022-02 successfully.

Starting with 2022-02, I get the 0x800F0922 error message again for all future Cumulative Updates (i.e. 2022-03, 2022-04, ...).

I have tried some things I found as solutions on the web.

  • ren C:\Windows\SoftwareDistribution & ren C:\Windows\System32\catroot2
  • empty %temp% and C:\Windows\Temp
  • DISM /Online /Cleanup-Image /RestoreHealth & SFC /ScanNow
  • manual install Edge Browser
  • installation via sconfig
  • disabled Antivires & Firewall

It looks to me like with the 2022-03 version (KB5011495) there must be a prerequisite that I don't have. I can't find any sign of an error in EventViewer. Do you have any suggestions what I can check or test? Now that I have all domain controllers all up to 2022-02, I can test many things at the same time.

Windows for business Windows Server User experience Other
0 comments No comments
{count} votes

7 answers

Sort by: Most helpful
  1. Anonymous
    2023-05-30T10:45:46.7433333+00:00

    Looks like some sort of Encrypted File System debug info. May not have anything to do with it.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

  2. Max R 1 Reputation point
    2023-05-30T11:43:31.41+00:00

    I have found the issue.
    This registry key was to much
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Microsoft-Windows-EFS/Debug
    After deliting it, the update could be installed.

    Thanks anyway.

    0 comments No comments

Your answer

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