Windows server 2022 - kb5022291 problem

T

tomekniemcy

Well-known member
Joined
Apr 20, 2022
Posts
80
Hello, i have problem with kb5022291 on one of 2022 server
SFC, DISM without errors
CBS.log has over 100 MB so iI paste only Error block. Can You Help ?
 

Attachments

Hi,

Follow these instructions to remove an update.
  • Open the Start menu of Windows and type the command CMD
  • When you see Command Prompt on the list, right-click on it and select Run as administrator.
  • When command prompt opens, copy and paste the following command into it, then press enter.
Code: 
wusa /uninstall /KB:5014021
  • Let me know if it says it was successful or you get the message: The update KB5014021 is not installed on this computer.
 
Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link
  • Open the startmenu and type the command cmd.
  • After you find the Command Prompt, right click on it and select Run as Administrator.
  • Copy and paste the following into the Command Prompt and press enter.
Code: 
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
Right-click on the file FRST64.exe and choose Run as administrator.
  • Copy and paste the following (code) into the Search box and click the Search Registry button.
Code: 
KB5014021
  • When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
  • Post the logfile SearchReg.txt as attachment in your next reply.
 
Rich (BB code): 
2023-01-13 12:40:41, Error                 CSI    000002e5 (F) STATUS_SXS_ASSEMBLY_MISSING #1477870# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2023-01-13 12:40:41, Error                 CSI    000002e6 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #1477736# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = Microsoft-Windows-Dedup-Deployment, version 10.0.20348.740, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~10.0.20348.740.Dedup-Core', rah = (null), manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
2023-01-13 12:40:41, Info                  CBS    Failed to pin deployment while resolving Update: Microsoft-Windows-Dedup-Package~31bf3856ad364e35~amd64~~10.0.20348.740.Dedup-Core from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2023-01-13 12:40:41, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Microsoft-Windows-msmq-powershell-Opt-WOW64-Package~31bf3856ad364e35~amd64~~10.0.20348.859 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

Step 1. Download
56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.

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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-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

Yes, please attempt to update. If it fails attach a new copy of the CBS log(s).
 
Rich (BB code): 
2023-01-14 14:02:14, Info                  CBS    Repr: No owner found for component amd64_microsoft-windows-dedup-filter_31bf3856ad364e35_10.0.20348.740_none_f0a3b1b5e1cb4ff4, it might be a 3rd party component [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]
2023-01-14 14:02:14, Info                  CBS    Not able to get CBS component onwers for component amd64_microsoft-windows-dedup-filter_31bf3856ad364e35_10.0.20348.740_none_f0a3b1b5e1cb4ff4 [HRESULT = 0x800f090c - CBS_E_COMPONENT_NOT_INSTALLED_BY_CBS]

Could you please provide a new copy of the COMPONENTS hive.
 
Please provide a list of the manifest-files in the WinSxS folder.

Open an elevated command prompt and run the following command. Attach Manifest-files.txt to your next post.
Code: 
dir %systemroot%\WinSxS\Manifests\*.* > "%userprofile%\Desktop\Manifest-files.txt"
 
Download
61f7aba7309a1-ComponentsScanner_Icon.png
ComponentsScanner and save it to your desktop.
  • Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
  • Follow the on-screen instructions.
  • Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
  • Post the logfile ComponentsScanner.txt as attachment into your next reply.
 
Code: 
== Missing Files ==
C:\WINDOWS\winsxs\Catalogs\e18ddd8a0d9f1d11d3f82d2dfeece5257c2241af97e0691f2816e5623de01471.cat (CanonicalData\Deployments\microsoft-w..-deployment_31bf3856ad364e35_10.0.20348.740_394a33dcfaec65cf contains CatalogThumbprint value e18ddd8a0d9f1d11d3f82d2dfeece5257c2241af97e0691f2816e5623de01471 but no corresponding file found in WinSxS)

== Missing Registry Keys ==
CanonicalData\Catalogs\e18ddd8a0d9f1d11d3f82d2dfeece5257c2241af97e0691f2816e5623de01471 (CanonicalData\Deployments\microsoft-w..-deployment_31bf3856ad364e35_10.0.20348.740_394a33dcfaec65cf has CatalogThumbprint value e18ddd8a0d9f1d11d3f82d2dfeece5257c2241af97e0691f2816e5623de01471 but no corresponding Catalog key exists)
 
Could you please post the complete logs? as well as the archived log-files in %localappdata%\Sysnative\ComponentsScanner\Reports
 
You must log in or register to reply here.

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

Back
Top