SFC /SCANNOW After Threshold 2

Topic

New Reply

Has anyone run a sfc /scannow since installing Threshold 2.

SFC and DISM errors have been reported among other problems.

http://wind8apps.com/windows-10-fall-update-version-1511-issues/

Reply | Quote

Replies

Yes, but I had unfixable errors there before the 10586 update as well as after.:(

Reply | Quote

Yes, I have run sfc /scannow and it didn’t find any errors.

Reply | Quote

I ran “sfc /scannow” straight after the 10586 update ant it found no problems.

Reply | Quote

Another example of mixed results for some following an update then.

Reply | Quote

I ran SFC and it found errors that it repaired.

Jerry

Reply | Quote

I wonder if there’ll ever be an answer as to why they are occurring for some following TH2.

Reply | Quote

I wonder if there’ll ever be an answer as to why they are occurring for some following TH2.

The link you gave is the only place where I’ve seen that being reported and its a pretty cryptic entry with no description of the problem. They could well have had the problem with the previous version for all we know. I’ve seen no reports of SFC/DISM errors unique to TH2 in the Microsoft forums.

As I stated, SFC did find and repair errors for me but I have no idea if it would have found the same errors prior to the upgrade.

Jerry

Reply | Quote

I’m dealing with a thread on another forum where the errors are a direct result of TH2 and the /restorhealth cmd returned it couldn’t find the source file, which would support what has already been listed in that article.

A Google produced other reports but with different errors, so it’s difficult to nail down just what is happening as they could be machine specific that perhaps wouldn’t have shown up during the Insider Fast Ring trials – but given the complaints, MS are going to have to have another look at TH2.

Restoring to prior TH2 gives a clean sfc.

The CBS log that was the only type that could be posted was the full one and I haven’t had time to trawl through it all yet, but a SFCFix.exe came back clean so I’m going to have to spend some time to see what that CBS log does report as corrupt.

NB – Just had the Instructions underneath the reply box again when I hit the Preview button – first for a while.

Reply | Quote

The majority of the errors relate to duplicate or other ownership problems of files with these reported as cannot fix –

CSI 00004e27 [SR] Repairing 1 components
2015-11-14 21:03:45, Info CSI 00004e28 [SR] Beginning Verify and Repair transaction
2015-11-14 21:03:45, Info CSI 00004e29 Hashes for file member SystemRootWinSxSwow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22opencl.dll do not match actual file [l:10]”opencl.dll” :
Found: {l:32 JjN1YsKOnCOJFw8U1daxx0PJlZE7NN1fVwvGsGsM59I=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-11-14 21:03:45, Info CSI 00004e2a [SR] Cannot repair member file [l:10]”opencl.dll” of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-14 21:03:45, Info CSI 00004e2b@2015/11/15:02:03:45.435 Primitive installers committed for repair
2015-11-14 21:03:45, Info CSI 00004e2c Hashes for file member SystemRootWinSxSwow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22opencl.dll do not match actual file [l:10]”opencl.dll” :
Found: {l:32 JjN1YsKOnCOJFw8U1daxx0PJlZE7NN1fVwvGsGsM59I=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-11-14 21:03:45, Info CSI 00004e2d [SR] Cannot repair member file [l:10]”opencl.dll” of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-14 21:03:45, Info CSI 00004e2e [SR] This component was referenced by [l:125]”Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys”
2015-11-14 21:03:45, Info CSI 00004e2f Hashes for file member ??C:WINDOWSSysWOW64opencl.dll do not match actual file [l:10]”opencl.dll” :
Found: {l:32 JjN1YsKOnCOJFw8U1daxx0PJlZE7NN1fVwvGsGsM59I=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-11-14 21:03:45, Info CSI 00004e30 Hashes for file member SystemRootWinSxSwow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22opencl.dll do not match actual file [l:10]”opencl.dll” :
Found: {l:32 JjN1YsKOnCOJFw8U1daxx0PJlZE7NN1fVwvGsGsM59I=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-11-14 21:03:45, Info CSI 00004e31 [SR] Could not reproject corrupted file [l:23 ml:24]”??C:WINDOWSSysWOW64″[l:10]”opencl.dll”; source file in store is also corrupted

Reply | Quote

What issues reported where?

cheers, Paul

Reply | Quote

That link for Nvidia looks particularly interesting – Thanks.

I’ll check to see if that OP has Nvidia graphics, but don’t know why Threshold 2 would have produced the duplicate ownership of files unless it relates to the graphics as well, with Nvidia pulling one way and MS the other ?

Reply | Quote