[SOLVED] WS2022 Windows Update issues and DISM errors (3/3)

Looking over your log now, back ASAP.
 
Looks like another permutation of the problem with first two machines, so let's hope this one goes as smoothly as the other 2 did.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download SFCFix.exe and save it to your desktop.
  • Download the attachment SFCFix.zip and also save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

Looks good:


Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-02-13 11:55:44.476
Microsoft Windows Server 10 Build 20348 - amd64
Using .zip script file at C:\Users\administrator.MEDAPRO\Downloads\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_tsportalwebpart_31bf3856ad364e35_10.0.20348.1_none_be04efa9b8a1c1d2
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.1_none_d80315864c9f50f3\tls_branding_config.xml

Successfully copied file C:\Users\administrator.MEDAPRO\AppData\Local\niemiro\Archive\amd64_tsportalwebpart_31bf3856ad364e35_10.0.20348.1_none_be04efa9b8a1c1d2\allusers_tswa.log to C:\Windows\WinSxS\amd64_tsportalwebpart_31bf3856ad364e35_10.0.20348.1_none_be04efa9b8a1c1d2\allusers_tswa.log.
Successfully copied file C:\Users\administrator.MEDAPRO\AppData\Local\niemiro\Archive\amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.1_none_d80315864c9f50f3\tls_branding_config.xml to C:\Windows\WinSxS\amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.1_none_d80315864c9f50f3\tls_branding_config.xml.

Successfully restored ownership for C:\Windows\WinSxS\amd64_tsportalwebpart_31bf3856ad364e35_10.0.20348.1_none_be04efa9b8a1c1d2
Successfully restored permissions on C:\Windows\WinSxS\amd64_tsportalwebpart_31bf3856ad364e35_10.0.20348.1_none_be04efa9b8a1c1d2
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.1_none_d80315864c9f50f3\tls_branding_config.xml
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.1_none_d80315864c9f50f3\tls_branding_config.xml
PowerCopy:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2023-02-13 11:56:39.319
Script hash: fo67nwUWdw9hdk6YqcJ5xQiBbzBy0Unt4UuZsdKe470=
----------------------EOF-----------------------

DISM ran successfully and updates are done.

Ok now to the question, what did you do? Just in case something like this happens again.

I can't thank you enough
 
You're welcome, glad we were able to resolve your problems.

Ok now to the question, what did you do?
Click to expand...

I replaced files that your various CBS.logs said were either corrupted or missing.

The corruptions in the case of these 3 machines were logged as hash mismatches, so the sha256 hash of the files you had installed did not match the file hashes logged in their corresponding Registry entries.

I sourced replacement files with the appropriate matching file hashes from a WS2022 Virtual Machine that I setup, and updated for that purpose.

Sadly things aren't always as straight forward as that, and updates can fail for a wide variety of reasons, so we have to treat each case individually.

If you have any problems in future, you know where we are, and we're always happy to help if we can.
 
Wow, that's a deeper analyses than I thought. Thank you very much again! Quick question, do you support update issues on Hyper-V Core Server?
 
You're welcome.

Quick question, do you support update issues on Hyper-V Core Server?
Click to expand...

I don't personally, but I daresay that some of the Experts here have had some experience working with Hyper-V Core Servers.
 
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