Scannow detects multiple errors but fails to repair most of them

[Ronnz]

Hi Guy's,

I'd be very grateful for some help to understand and hopefully repair the considerable number of errors shown in the latest sfc /scannow report that I have run on my PC which has just been upgraded to 8.1 and includes XP run inside Virtual Box. It has Classic Shell and other tweaks to make it more Desktop friendly.

The scans were run after installing virtually all the applications I need for normal use. Installation for the most part went smoothly but it presented a Bad Pool Header screen once and hung for no obvious reason on two other occasions, both of which necessitated powering off and rebooting. Apart from these instances it is running pretty well.

The "failed", "invalid", "warning" and "cannot repair" errors appear in just four distinct patterns but are considerable in number so I have only presented examples of the error patterns at this stage in the hope that someone much more knowledgeable than myself might be able recognize what issue(s) are involved without having to go to a heap of trouble.

Thank you in advance.

Ronnz

The following text has been extracted from the 4th consecutive scan.

Pattern 1 (51 instances of “failed”)
2015-03-30 15:04:11, Info CBS SQM: failedto start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]

2015-03-30 15:04:11, Info CBS SQM: failedto start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]

2015-03-30 15:04:11, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6

2015-03-30 15:04:11, Info CBS SQM: warning: failedto upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]


Pattern 2 (51 instances of “invalid”)
2015-03-30 15:04:19, Info CBS failedto internally open package. [HRESULT = 0x800f0805 - CBS_E_invalid_PACKAGE]

2015-03-30 15:04:19, Info CBS failedto OpenPackage using worker session [HRESULT = 0x800f0805]


Pattern 3 (2I92 instances of “warning”)
2015-03-30 22:29:30, Info CSI 000000ed [DIRSD OWNER warning] Directory [ml:520{260},l:88{44}]"\??\C:\Windows\Help\Windows\IndexStore\en-US" is not owned but specifies SDDL in component Microsoft-Windows-Assistance-CollectionFiles-Help.Resources, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral


Pattern 4 (12 instances of these paired corrupt file messages)
2015-03-30 22:38:21, Info CSI 00000572 [SR] cannot repairmember file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch

2015-03-30 22:38:22, Info CSI 00000573 Hashes for file member \SystemRoot\WinSxS\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB do not match actual file [l:36{18}]"Amd64\CNBJ2530.DPB" :
Found: {l:32 b:ri9QfQEXmdiibR/Y44R+jYmtk9zoLZnHaqO83a36nU8=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}

2015-03-30 22:38:22, Info CSI 00000574 [SR] cannot repairmember file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch

 

[donetao]

Not a W8 user, but have you tried the Repair feature!

Refresh Windows 8

Repair Install Windows 8

 

[Ronnz]

Thanks for your suggestions Donetao. You were quite right. The most straightforward solution was to refresh Windows and all but start over again.

I had used Paragon Back Up to take several images of the OS system, the first being after the fresh install followed by two others as I progressed rebuilding the machine. When mounted, these all scanned with no errors at all. From this I determined that the errors were introduced when I reached the point of testing out various third party browsers to replace the 8.1 File Manager. A particular culprit was OldNewExplorer but it may not have been the only one to mess with the system.

In the end, I replaced File Explorer with Directory Opus (it's all that File Explorer should have been plus much more) and since then have reloaded 150+ applications to get close to the full complement that I need. I have completed another scan just now that fortunately reported no violations.

Thanks again for your help.

Ronnz

 

[donetao]

Hi Thanks for your feed back. It seems you got-er-done. Paragon is a great program. I prefer Macrium Reflect but either one will allow you mount the image as a drive. I never thought about scanning the mounted image for errors. That makes sense however. I usually verily the image to make sure its good.
I'm going to try scanning. Did you use sfc /scannow on the mounted drives to check for system errors??

 

[Ronnz]

Yes, I have a spare partition that had a copy of XP installed on it for emergenices should my actual working copy have got unexpectedly corrupted so I successivwely mounted and scanned the progressive copies of 8.1 on the spare partition using:

sfc /scannow /offbootdir=C:\ /offwindir=D:\windows

which avoided shuffling the boot order. Each scanned with no detected errors.

Glad to hear you have had good success with Macrium Reflect. I'm no techie and found Paragon easier to use. I'ts never let me down.

Best,

R