Windows server 2022 - kb5022291 problem

Hmm, You've sent a private message yesterday after running ComponentsScanner which reported 286 warnings? Is that log file deleted?
 
Last edited:
Why? You deleted all those files yourself in this folder %localappdata%\Sysnative
 
Hi,

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Here's the next fix.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Again the same situation, dism ok, update failed. Files attached
I think it is imossible to resolve this issue
 

Attachments

I think it is imossible to resolve this issue
This type of error could be hard to fix, because we'll need to replace all the missing registry keys and/or associated files.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

The same dism ok update failed. Another package showed error... I think it is good time to stop, we are wasting out time. What do You think?
 
Maybe i run powershell script to compare registry keys and files in specifica directory ? It can help or not ?
 
Fixing this problem could be time consuming, at least we need to replace several components for:

20348.51 (Insider Preview Build*)
20348.469 KB5009555
20348.617 KB5011558 (Preview)
20348.681 KB5012637 (Preview)
20348.740 KB5014021 (Preview)
20348.768 KB5014678
20348.803 KB5014665 (Preview)
20348.859 KB5015879 (Preview)
20348.946 KB5016693 (Preview)
20348.1006 KB5017316

So this could be a tough job to fix, but it is possible most of the times. However, almost all the issues - and the suspected issues - are related to preview updates.

Option 1: Perform an in-place upgrade, sometimes it will resolve this issue as well.
Option 2: Rebuild the complete server.

Just to note: I never recommend installing preview updates, especially on production servers and client systems.
 
  • Thanks
Reactions: tmp
No, this problem is more complicated! So we need to replace each component reported in the CBS log and this could be result in multiple fixes. In this case approx tens of runs or more.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top