sfc unable to repair / file hash mismatch

Hi,

From the log you did dism /online /cleanup-image /restorehealth /source:wim:c:\Users\Administrateur\Desktop\W2012\sources\install.wim:1

Did you adjust the wim index to match the server Edition that you have installed?

The DVD I have from Microsoft with Server 2012 include multiple editions:
Code: 
Details for image : f:\sources\install.wim

Index : 1
Name : Windows Server 2012 SERVERSTANDARDCORE
Description : Windows Server 2012 SERVERSTANDARDCORE
Size : 7.195.580.708 bytes

Index : 2
Name : Windows Server 2012 SERVERSTANDARD
Description : Windows Server 2012 SERVERSTANDARD
Size : 11.999.848.937 bytes

Index : 3
Name : Windows Server 2012 SERVERDATACENTERCORE
Description : Windows Server 2012 SERVERDATACENTERCORE
Size : 7.176.243.455 bytes

Index : 4
Name : Windows Server 2012 SERVERDATACENTER
Description : Windows Server 2012 SERVERDATACENTER
Size : 11.995.224.677 bytes
 
Hi,

yes I tried with the index 4 (DATACENTER) first and even the index 1, 2 and 3 (we can always dream :-)) but I still have the same error 0x800f081f
 
Hi,

We checked the logs and there are no errors recorded that could explain the problem!

It seems Windows Update is working so you can ignore this or dig further using procmon...


Capture Process Monitor Trace
  • Download Process Monitor and save it to the Desktop
  • Open an elevated Command Prompt
  • Run Process Monitor from the Desktop. Leave this running while you perform the next steps
  • Return to the Command Prompt and run dism /online /cleanup-image /restorehealthjust like you have in the past
  • Stop Process Monitor as soon as dism fails You can simply do this by clicking the magnifying glass on the toolbar as shown below.
    11908d1430506241-windows-updates-fail-repeatedly-stop-jpg
  • 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.
  • Zip up and attach the LogFile.PML file as well as your CBS.log.
 
Hi,

Sorry for the long delay....

BrianDrab checked the logs provided and he thinks we can fix the Dism problem by deleting some values from the registry.

Do you want to try?
 
Hi,

No problem, I can install kb in manual.

yes why not but do not you think it's better to remake the entire server?
I do not want you to spend time for "nothing"...
 
Hi,

The fix suggested by Brian is simple.

From a Command Prompt running as Administrator execute the following two commands:
Code: 
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide" /v "StoreCorruptTimestamp" /f

reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide" /v "CorruptionsDetected" /f

After this restart the computer and try dism /online /cleanup-image /restorehealth.
 
Hi,

Sound like you have a plan, sorry that this didn't worked for you.
 
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