Thanks for your response - I hadn't considered trying sfc /scannow from the DVD. I tried the various suggestions in your message with the following outcomes:
- sfc /scannow
I get the following
"Beginning system scan. This process will take some time
There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again."
At this stage I wasn't sure whether to rerun sfc from the startup repair command prompt or directly in windows? I tried again from the CD and got the same message so then I did this in an Administrator
command prompt on Windows. This ran but the CBS.log file still has many errors e.g.
"2016-01-14 14:25:53, Info CSI 0000038a [SR] Verify complete 2016-01-14 14:25:54, Info CSI 0000038b [SR] Verifying 100 (0x0000000000000064) components 2016-01-14 14:25:54, Info CSI 0000038c
[SR] Beginning Verify and Repair transaction 2016-01-14 14:25:56, Info CSI 0000038d Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-wmi-scripting_31bf3856ad364e35_6.1.7600.16385_none_60e78eba5410cd9e\wbemdisp.dll do not match actual file [l:24{12}]"wbemdisp.dll"
:
Found: {l:32 b:vl9w2Zz/zR3zybQLxrbSnZUg47Q1qTc4V0Udv7u0ftg=} Expected: {l:32 b:hkTQpVxGw/CB8KtD0lPRPlbnfYkzaocQjbjEfW7cOmQ=} 2016-01-14 14:25:56, Info CSI 0000038e [SR] Cannot repair member file [l:24{12}]"wbemdisp.dll" of Microsoft-Windows-WMI-Scripting,
Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2016-01-14 14:25:57, Info CSI
0000038f Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-wmi-scripting_31bf3856ad364e35_6.1.7600.16385_none_60e78eba5410cd9e\wbemdisp.dll do not match actual file [l:24{12}]"wbemdisp.dll" :
Found: {l:32 b:vl9w2Zz/zR3zybQLxrbSnZUg47Q1qTc4V0Udv7u0ftg=} Expected: {l:32 b:hkTQpVxGw/CB8KtD0lPRPlbnfYkzaocQjbjEfW7cOmQ=} 2016-01-14 14:25:57, Info CSI 00000390 [SR] Cannot repair member file [l:24{12}]"wbemdisp.dll" of Microsoft-Windows-WMI-Scripting,
Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2016-01-14 14:25:57, Info CSI
00000391 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery" 2016-01-14 14:25:57, Info CSI 00000392 Hashes for file member ??\C:\Windows\SysWOW64\wbem\wbemdisp.dll
do not match actual file [l:24{12}]"wbemdisp.dll" :
Found: {l:32 b:vl9w2Zz/zR3zybQLxrbSnZUg47Q1qTc4V0Udv7u0ftg=} Expected: {l:32 b:hkTQpVxGw/CB8KtD0lPRPlbnfYkzaocQjbjEfW7cOmQ=} 2016-01-14 14:25:57, Info CSI 00000393 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-wmi-scripting_31bf3856ad364e35_6.1.7600.16385_none_60e78eba5410cd9e\wbemdisp.dll
do not match actual file [l:24{12}]"wbemdisp.dll" :
Found: {l:32 b:vl9w2Zz/zR3zybQLxrbSnZUg47Q1qTc4V0Udv7u0ftg=} Expected: {l:32 b:hkTQpVxGw/CB8KtD0lPRPlbnfYkzaocQjbjEfW7cOmQ=} 2016-01-14 14:25:57, Info CSI 00000394 [SR] Could not reproject corrupted file [ml:58{29},l:56{28}]"??\C:\Windows\SysWOW64\wbem"[l:24{12}]"wbemdisp.dll";
source file in store is also corrupted "
- I ran DISM.exe /Online /Cleanup-image /Scanhealth
The output from this shows a number of errors:
"Summary:
Seconds executed: 889
Found 9 errors
CheckSUR Registry Failure Total count: 1
CSI Manifest Failed Catalog Check Total count: 4
CBS MUM Corrupt Total count: 3
CBS Catalog Corrupt Total count: 1
Unavailable repair files:
winsxs\manifests\amd64_6da8ff6d9860e7896741f7e8706f8ab1_31bf3856ad364e35_11.2.9600.17041_none_8533fcec1ecb6dcb.manifest
winsxs\manifests\amd64_e6b1511c3edf6eb70f2db938173c8636_31bf3856ad364e35_11.2.9600.17041_none_7879e277ff200848.manifest
winsxs\manifests\amd64_fae088ee990409cb9975d902d294b62c_31bf3856ad364e35_11.2.9600.17041_none_6b96240a992ce896.manifest
winsxs\manifests\amd64_8078519738a275dcf189976b0aada9d0_31bf3856ad364e35_11.2.9600.17041_none_b32e68c79d9f39d9.manifest
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
servicing\packages\Package_37_for_KB2929437~31bf3856ad364e35~amd64~~11.2.1.0.mum
servicing\packages\Package_for_KB2929437_RTM~31bf3856ad364e35~amd64~~11.2.1.0.mum
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat
servicing\packages\Package_37_for_KB2929437~31bf3856ad364e35~amd64~~11.2.1.0.cat
servicing\packages\Package_for_KB2929437_RTM~31bf3856ad364e35~amd64~~11.2.1.0.cat "
- I tried running DISM.exe /Online /Cleanup-image /Restorehealth
This starts to run, then I get the following:
"Error: 87
The restorehealth. option is no recognized in this context.
For more information, refer to the help.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log"I'm not sure what to try now! Thanks for your help.