DISM and SFC failing on Windows Server 2019

[philc43]

All looks good. Did SFC and/or DISM work this time? Please send the new CBS.logs if more analysis is needed.

 

[beardedmogul]

SFC is still failing at 73%
DISM has been working since a couple time ago.
CBS Logs are here

 

[philc43]

It doesn't look as if you have run a DISM RestoreHealth since the last fix - can you please do this and post the CBS.log file that is created afterwards. Thanks.

 

[beardedmogul]

Try now. Turns out DISM doesn't work either.

 

[philc43]

Please provide the CBS.log file generated after you last attempted the DISM command.

 

[beardedmogul]

Sorry, I meant they were at the same place: here

 

[philc43]

Ah, I understand what you did now - thanks! I've looked at the new logs and there are new files to replace. However, it is going to take me a little while to source these and I am unavailable for the next day and so I will provide this by early next week.

 

[philc43]

I actually found the files needed sooner than expected.

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. If needed download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the file below, SFCFix3.zip, and save this to your Desktop. Ensure that this file is named SFCFix3.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix3.zip.
5. Drag the file SFCFix3.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. Please Attach this file into your next post for me to check.

Once this is done then redo the SFC /scannow and if it completes with no errors you can try to update again. If there are errors please run another DISM RestoreHealth and then post a new set of logs.

 

[beardedmogul]

@philc43

PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_10.0.17763.1_none_c58009973991fa4c\WSManHTTPConfig.exe
Successfully took permissions for file or folder C:\Windows\WinSxS\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_10.0.17763.1_none_c58009973991fa4c\WSManMigrationPlugin.dll

Successfully copied file C:\Users\adm_darylb\AppData\Local\niemiro\Archive\WinSxS\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_10.0.17763.1_none_c58009973991fa4c\WSManHTTPConfig.exe to C:\Windows\WinSxS\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_10.0.17763.1_none_c58009973991fa4c\WSManHTTPConfig.exe.
Successfully copied file C:\Users\adm_darylb\AppData\Local\niemiro\Archive\WinSxS\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_10.0.17763.1_none_c58009973991fa4c\WSManMigrationPlugin.dll to C:\Windows\WinSxS\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_10.0.17763.1_none_c58009973991fa4c\WSManMigrationPlugin.dll.

Successfully restored ownership for C:\Windows\WinSxS\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_10.0.17763.1_none_c58009973991fa4c\WSManHTTPConfig.exe
Successfully restored permissions on C:\Windows\WinSxS\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_10.0.17763.1_none_c58009973991fa4c\WSManHTTPConfig.exe
Successfully restored ownership for C:\Windows\WinSxS\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_10.0.17763.1_none_c58009973991fa4c\WSManMigrationPlugin.dll
Successfully restored permissions on C:\Windows\WinSxS\wow64_microsoft-windows-w..for-management-core_31bf3856ad364e35_10.0.17763.1_none_c58009973991fa4c\WSManMigrationPlugin.dll
PowerCopy:: directive completed successfully.


sfc failed at 73%

dism completed

scf failed at 73%

Logs are here

 

[philc43]

Let's have a go at capturing what is happening when SFC fails. Follow the instructions below, maybe I can find what is causing the error.

Step#1 - Capture Process Monitor Trace
1. Download Process Monitor and have a practice with it using Ctrl+E (or the toolbar icon) to stop and start monitoring. You can clear the events with Ctrl+X or the dustbin icon .
2. Try running SFC /scannow just like you have in the past and start Process Monitor capturing when it gets close to the point of failure say 70%
3. Stop the Process Monitor capturing as soon as SFC fails.
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 and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

 

[beardedmogul]

Ok, that's in there too.

 

[philc43]

Thanks! Can you also upload the new CBS.log file so that I can compare the time of the error with the times in the process monitor file.

 

[beardedmogul]

Updated

 

[philc43]

I have a new fix for you based on some other files that were found to be corrupt in your most recent CBS.log

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. If needed download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the file below, SFCFix4.zip, and save this to your Desktop. Ensure that this file is named SFCFix4.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix4.zip.
5. Drag the file SFCFix4.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. Please Attach this file into your next post for me to check.

After this please run another DISM RestoreHealth and once it has finished post the new CBS.log.

 

[beardedmogul]

@philc43

Thanks again for all this work.

PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_10.0.17763.1790_none_1d15b7a7d7f7feff\r\cimwin32.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_10.0.17763.107_none_8118018477d41f9c\AcRes.dll

Successfully copied file C:\Users\adm_darylb\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_10.0.17763.1790_none_1d15b7a7d7f7feff\r\cimwin32.dll to C:\Windows\WinSxS\amd64_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_10.0.17763.1790_none_1d15b7a7d7f7feff\r\cimwin32.dll.
Successfully copied file C:\Users\adm_darylb\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_10.0.17763.107_none_8118018477d41f9c\AcRes.dll to C:\Windows\WinSxS\amd64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_10.0.17763.107_none_8118018477d41f9c\AcRes.dll.

Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_10.0.17763.1790_none_1d15b7a7d7f7feff\r\cimwin32.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-w..ovider-cimwin32-dll_31bf3856ad364e35_10.0.17763.1790_none_1d15b7a7d7f7feff\r\cimwin32.dll
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_10.0.17763.107_none_8118018477d41f9c\AcRes.dll
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-a..ence-mitigations-c1_31bf3856ad364e35_10.0.17763.107_none_8118018477d41f9c\AcRes.dll
PowerCopy:: directive completed successfully.


DISM ran fine. Logs are here.

 

[philc43]

All appears to be error free. Does the SFC scan complete yet or is there still more work to be done?

 

[beardedmogul]

Unfortunately, it is still failing at 73%. I updated the logs.

 

[philc43]

There still seems to be a problem with some of the file hashes:

2022-02-08 14:02:00, Info                  CSI    00001c71 Hashes for file member [l:9]'appid.sys' do not match.
 Expected: {l:32 ml:4096 b:e71bb1cc2eea09f9426ba4a072ed70b26fe9ef787889b8edb05954c554566871}.
 Actual: {l:32 b:6d2c4fda7fee1db45e2c8dbec3884c379994bf0eed7089cd22319c1ce73708d0}.
2022-02-08 14:02:00, Info                  CSI    00001c72 [SR] Repairing corrupted file \??\C:\Windows\System32\Drivers\\appid.sys from store
2022-02-08 14:02:00, Info                  CSI    00001c73 Hashes for file member [l:10]'srpapi.dll' do not match.
 Expected: {l:32 ml:4096 b:3d3a5f67d0e84e09276b3d2ef2d4c478a5a773124ec806cc4fc0484844aecee2}.
 Actual: {l:32 b:38c1e669cfc0fe064b587e2da6d60db1ba13f222b6cba5fbd51c6af5490445ed}.
2022-02-08 14:02:00, Info                  CSI    00001c74 [SR] Repairing corrupted file \??\C:\Windows\System32\\srpapi.dll from store

It looks as if the SFC repair may not have worked. I'm going to check on these two files on your system.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
8. Attach this file into your next post for me to analyse please

 

[beardedmogul]

Here is the result

 

[philc43]

Please send me the Winners hive from your Registry.

Export SideBySide

1. Click on the Start button and in the search box, type regedit
2. When you see regedit on the list, right-click on it and select Run as administrator
3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
4. Once selected, click File > Export....
5. Change the Save as type: to Registry Hive Files (.)
6. Name this file SxS (with no file extension) and save it to your Desktop.

Once done please upload this file via Dropbox or OneDrive or SendSpace.