[SOLVED] Server 2022 - error 0x800f081f + 0x80070643

Please do the following first.

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.
650ef5dbdfd06-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.

Afterwards run the following command in an elevated prompt and copy paste the result in your next post.
Code:
icacls C:\Windows\Servicing\Packages\Microsoft-Windows-TS-merged-Package~31bf3856ad364e35~amd64~~10.0.20348.2652.cat
 

Attachments

This looks good, so please attempt to update again and post the result..
 
Code:
2024-08-15 11:49:00, Info                  CBS    File already exists when adding the catalog: \\?\C:\Windows\Servicing\Packages\Microsoft-Windows-TS-merged-Package~31bf3856ad364e35~amd64~~10.0.20348.2652.cat
2024-08-15 11:49:00, Info                  CBS    Failed to delete existing package catalog '\\?\C:\Windows\Servicing\Packages\Microsoft-Windows-TS-merged-Package~31bf3856ad364e35~amd64~~10.0.20348.2652.cat' [HRESULT = 0x80070005 - E_ACCESSDENIED]
2024-08-15 11:49:00, Info                  CBS    Failed to install catalog for package: Microsoft-Windows-TS-merged-Package~31bf3856ad364e35~amd64~~10.0.20348.2652 [HRESULT = 0x80070005 - E_ACCESSDENIED]

Yes, please disable or uninstall Cylance AV because it's failing on the same file.
 
Rich (BB code):
2024-08-15 13:10:20, Error                 CSI    0000002b@2024/8/15:11:10:20.642 (F) onecore\base\wcp\componentstore\csd_winners.cpp(558): Error STATUS_SXS_ASSEMBLY_NOT_FOUND originated in function CCSDirectTransaction::PerformChangeAnalysis expression: (null)
[gle=0x80004005]

Please attempt to update again with Process Monitor running.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor a minute after Windows Update failed to be sure everything is logged. You can simply do this by clicking the capture icon (CTRL +E) on the toolbar as shown below.

Process-Monitor.png


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer | Send Large Files Fast - Up To 2GB Free and provide the link.
6. Upload also the latest CBS log for the time stamps.
 
It seems the ProcMon trace is stopped to early, it's just 68MB unzipped?

Please perform the same steps again, and stop Process Monitor a minute after Windows Update failed. Please attach also the latest CBS logs for the time stamps as requested.
 
No luck, but there's a gap between [8/15/2024 2:20:20.3343891 PM] and [8/15/2024 2:49:04.0104677 PM]

Did you leave Process Monitor running continuously or interrupted?
 
Hi

Yes I left Procmon open just did stop/start between captures.
Here new capture from scratch hope this one will be fine.

thanks
 

Attachments

Hi,

When you open Process Monitor the capture process will start automatically, so please do the following.
1. Open Process Monitor and let it run.
2. Attempt to update.
3. When it failed wait a minute and stop the trace.
4. Attach the zipped *.PML file and the latest CBS logs.
 
Hi,

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.
650ef5dbdfd06-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

Please run the following commands in an elevated prompt and copy paste the result in your next post.
Code:
dir /s /a %systemroot%\WinSxS\amd64_microsoft-windows-slbmuxdriver.resources_31bf3856ad364e35_10.0.20348.946_en-us_9305473cbcb20da1
certutil -hashfile %systemroot%\WinSxS\Manifests\amd64_microsoft-windows-slbmuxdriver.resources_31bf3856ad364e35_10.0.20348.946_en-us_9305473cbcb20da1.manifest SHA256
 

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

Back
Top