DISM and SFC failing on Windows Server 2019

[beardedmogul]

Here

 

[philc43]

Please do the following fix:

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

Assuming the changes have been made successfully, you can try the SFC scan again.

 

[beardedmogul]

RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-appidcore_31bf3856ad364e35_none_20753233820f2d87\10.0.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-appidcore_31bf3856ad364e35_none_20753233820f2d87.

Successfully deleted registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-appidcore_31bf3856ad364e35_none_20753233820f2d87\10.0.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-appidcore_31bf3856ad364e35_none_20753233820f2d87\10.0.

Failed to open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-appidcore_31bf3856ad364e35_none_20753233820f2d87\10.0 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-appidcore_31bf3856ad364e35_none_20753233820f2d87\10.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-appidcore_31bf3856ad364e35_none_20753233820f2d87.
RegistryScript:: directive failed to complete successfully.

 

[philc43]

Although the file suggests that the script did not work - I think you will find that it did. Please verify that the entry was made and you have the following values:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-appidcore_31bf3856ad364e35_none_20753233820f2d87\10.0]
@="10.0.17763.2366"
"10.0.17763.1"=hex:01
"10.0.17763.2366"=hex:01

 

[beardedmogul]

It was indeed.

Did another SFC scan which failed at 73%

 

[philc43]

Please provide the CBS.log and I'll look for any new errors.

 

[beardedmogul]

You, my friend, are a stubborn SOG. Here, and God bless you.

 

[philc43]

Nothing showed up in the latest log that I can find. I went back to the Process Monitor record you took of the moment when it fails and all I can see is that it coincides with Windows Defender activity. I will not get much time this weekend on the forums but if you want to experiment you could try repeating the SFC scan with Windows Defender turned off. To do this go to Windows Security and Virus and Threat Protection and select Manage Settings and turn off Real Protection while the scan runs.

 

[beardedmogul]

Unfortunately, this did not help either. I ran both DISM and SFC with Real Time Protection off and it still fails.

 

[philc43]

I had a feeling that might happen. I am coming to the conclusion that this might be something that only Microsoft can fix. I have another thread where there is a TiWorker crash happening at the same time as the SFC scan fails. I'm wondering if you see this same effect. You can check in event viewer for errors at the same time as the SFC fail occurs.

 

[philc43]

I had a feeling that might happen. I am coming to the conclusion that this might be something that only Microsoft can fix. I have another thread where there is a TiWorker crash happening at the same time as the SFC scan fails. I'm wondering if you see this same effect. You can check in event viewer for errors at the same time as the SFC fail occurs.

Did you have opportunity to look through event viewer for any errors at the time of the SFC failure?

 

[beardedmogul]

Sorry I went dark for a while. I've been busy with other things. I was not able to correlate any events with the SFC failure.