Results 1 to 15 of 15
  1. #1
    Super Moderator
    Join Date
    Aug 2012
    Location
    Durham UK
    Posts
    7,604
    Thanks
    188
    Thanked 998 Times in 950 Posts

    SFC /SCANNOW After Threshold 2

    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...n-1511-issues/

  2. #2
    Super Moderator
    Join Date
    Jun 2011
    Location
    New England
    Posts
    5,062
    Thanks
    186
    Thanked 711 Times in 625 Posts
    Yes, but I had unfixable errors there before the 10586 update as well as after.

  3. #3
    WS Lounge VIP Coochin's Avatar
    Join Date
    Jun 2014
    Location
    Queensland, Australia
    Posts
    2,392
    Thanks
    37
    Thanked 351 Times in 306 Posts
    Yes, I have run sfc /scannow and it didn't find any errors.
    Computer Consultant/Technician since 1998 (first PC was Atari 1040STE in 1988).
    Most common computing error is EBKAC: Error Between Keyboard And Chairback
    Confuscius said: "no use running harder if you're on the wrong road" and "any problem once correctly understood is already half-solved".

  4. #4
    3 Star Lounger KIWIpeteW's Avatar
    Join Date
    May 2015
    Location
    New Zealand
    Posts
    263
    Thanks
    121
    Thanked 16 Times in 16 Posts
    I ran "sfc /scannow" straight after the 10586 update ant it found no problems.

  5. #5
    Super Moderator
    Join Date
    Aug 2012
    Location
    Durham UK
    Posts
    7,604
    Thanks
    188
    Thanked 998 Times in 950 Posts
    Another example of mixed results for some following an update then.

  6. #6
    Super Moderator jwitalka's Avatar
    Join Date
    Dec 2009
    Location
    Minnesota
    Posts
    6,917
    Thanks
    119
    Thanked 816 Times in 731 Posts
    I ran SFC and it found errors that it repaired.

    Jerry

  7. #7
    Super Moderator
    Join Date
    Aug 2012
    Location
    Durham UK
    Posts
    7,604
    Thanks
    188
    Thanked 998 Times in 950 Posts
    I wonder if there'll ever be an answer as to why they are occurring for some following TH2.

  8. #8
    Super Moderator jwitalka's Avatar
    Join Date
    Dec 2009
    Location
    Minnesota
    Posts
    6,917
    Thanks
    119
    Thanked 816 Times in 731 Posts
    Quote Originally Posted by Sudo15 View Post
    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

  9. #9
    Super Moderator
    Join Date
    Aug 2012
    Location
    Durham UK
    Posts
    7,604
    Thanks
    188
    Thanked 998 Times in 950 Posts
    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.

  10. #10
    jwoods
    Guest
    Haven't seen anything major reported by Woody, Thurrott, or Supersite...

    It would be interesting to know HOW they were upgraded (WU, Media Creation Tool?)

  11. #11
    Super Moderator
    Join Date
    Aug 2012
    Location
    Durham UK
    Posts
    7,604
    Thanks
    188
    Thanked 998 Times in 950 Posts
    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 \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911 c22\opencl.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 \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911 c22\opencl.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.Remot eFX clientVM and UMTS files and regkeys"
    2015-11-14 21:03:45, Info CSI 00004e2f Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.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 \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911 c22\opencl.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:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
    Last edited by Sudo; 2015-11-18 at 04:28.

  12. #12
    jwoods
    Guest
    There have been issues reported with opencll.dll and previous Windows 10 builds.

  13. #13
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,791
    Thanks
    60
    Thanked 1,087 Times in 1,010 Posts
    What issues reported where?

    cheers, Paul

  14. #14
    jwoods
    Guest
    Quote Originally Posted by Paul T View Post
    What issues reported where?

    cheers, Paul
    opencl.dll missing/corrupted in Windows 10 builds...

    Sysnative -

    http://www.sysnative.com/forums/wind...t-files-2.html

    NVIDIA GeForce forum -

    https://forums.geforce.com/default/t...omment=4730455

  15. The Following User Says Thank You to jwoods For This Useful Post:

    Sudo (2015-11-19)

  16. #15
    Super Moderator
    Join Date
    Aug 2012
    Location
    Durham UK
    Posts
    7,604
    Thanks
    188
    Thanked 998 Times in 950 Posts
    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 ?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •