Does Windows 10 Version 1511 Corrupt System Files?


  1. srfinva
    Posts : 2
    Winows 10 Version 1511
       New #1

    Does Windows 10 Version 1511 Corrupt System Files?


    Hello,

    My wife has a Lenovo ThinkPad X230 (Type 2306-CTO) that shipped with Windows 7 and has been successfully upgraded to Windows 10. It has been running Windows 10 (retail release plus updates) smoothly for a couple months.


    Yesterday (11 Dec 2015) my wife ran the Windows 10 system file checker (sfc /scannow) in an elevated command prompt on her laptop. She did this to make sure everything was still okay after updating Windows 10 to version 1511 (OS Build 10586). It wasn't okay:


    |-- sfc /scannow results --|


    Microsoft Windows [Version 10.0.10586]
    (c) 2015 Microsoft Corporation. All rights reserved.


    C:\WINDOWS\system32>sfc /scannow


    Beginning system scan. This process will take some time.


    Beginning verification phase of system scan.
    Verification 100% complete.


    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.


    C:\WINDOWS\system32>


    |-- end --|


    In the past, when SFC couldn't fix problems we have been able to fix corrupt system files by using the Deployment Image & Servicing Management (DISM) tool. We ran this series of commands in an elevated command prompt:


    Dism /Online /Cleanup-Image /CheckHealth
    Dism /Online /Cleanup-Image /ScanHealth
    Dism /Online /Cleanup-Image /RestoreHealth


    SFC indicated these steps did not fix the corruption. We then tried to specify the source of good versions of the files that could be used for repairing corrupt files with this command:


    Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:"Full Path to install.esd file":1


    We tried this command with an install DVD created yesterday with Microsoft's Media Creation Tool and a mounted ISO file also created with the Media Creation Tool. Unfortunately, DISM couldn't find the source even though we checked and rechecked the path we included here.


    Having spent way too much time on this including wiping the hard drive and installing Windows 10 from scratch, we tried calling Microsoft's Tech Support line for help. The support person took control of my wife's laptop remotely and spent two hours trying to fix the problem. Nothing the support person tried worked. She then suggested that my wife hang up and allow her to continue working on the problem. Within an hour or so, the chat ended and Microsoft mysteriously stopped working to resolve the problem. No "Sorry I couldn't help." or "We'll check on this and get back to you." Just gone.


    As our final step we wiped the drive and reinstalled Windows 7. After Windows 7 was installed and fully updated, SFC reported no corrupt files found. We then upgraded to Windows 10 using Windows Update. Immediately after getting to the Windows 10 (Version 1511) desktop SFC reported corrupt files it couldn't fix.


    Here's where things stand now: we have two Intel Core I7 desktop systems running Windows 10 Version 1511 with no system file corruption problems. Both of these systems have conventional hard drives. We also have two Lenovo ThinkPad laptops (my wife's and my X201, Type 3249-CTO) with system file corruption problems that appeared after the Version 1511 upgrade. Both of our laptops have SSD drives. At this point, we have spent 16-18 hours on this problem, and we don't know if the problem is Lenovo firmware or drivers, Version 1511 incompatibility with SSD drives, or other Windows 10 bugs. We only know we're frustrated and mad as hell.


    Note: We tried to attach the CBS.log file to this post, but it is 4.7MB and exceeds tenforums.com's file size limit. Here's a link to a copy on Google Drive:

    CBS.log - Google Drive


    Thanks for reading.
      My Computer
    Quote Quote

  3. gvp9000
    Posts : 11
    Win10 Pro x64 Version 1909 OS Build 18363.720
       New #2

    I had the same problem.

    Solution:
    1. convert your install.esd to install.wim using WinReducerESWimConverter.
    (WinReducer ES Wim Converter - WinReducer.net)
    2. run as admin
    Code:
    Dism /Online /Cleanup-Image /RestoreHealth /source:wim:C:\ . . . . \install.wim:1 /limitaccess
      My Computer
    Quote Quote

  4. Word Man
    Posts : 1,579
    Windows 10 Pro
       New #3

    Alternatively, you can download the ISO from Techbench: http://www.microsoft.com/en-us/softw...load/techbench

    People have had better luck using install.wim from that source for DISM /source repairs although yes you can extract what you need from MCT using GVP9000's route or other routes to get what you need.

    However, you may be out of luck if it's the opencl.dll mismatch in your CBS.log file that's causing the problem - others here at TenForums have had the same dead end recur for opencl.dll and are still waiting for MS to address it.
      My Computer
    Quote Quote

  6. lx07
    Posts : 5,478
    2004
       New #4

    This is the problem
    Code:
    2015-12-12 09:53:39, Info                  CSI    00004fa3 [SR] Verify complete
2015-12-12 09:53:39, Info                  CSI    00004fa4 [SR] Repairing 1 components
2015-12-12 09:53:39, Info                  CSI    00004fa5 [SR] Beginning Verify and Repair transaction
2015-12-12 09:53:39, Info                  CSI    00004fa6 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 15Zo6QE4AUfojzxIYHfgI35HXL9fri8ouLdmre4jJQc=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-12 09:53:39, Info                  CSI    00004fa7 [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-12-12 09:53:39, Info                  CSI    00004fa8@2015/12/12:14:53:39.099 Primitive installers committed for repair
2015-12-12 09:53:39, Info                  CSI    00004fa9 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 15Zo6QE4AUfojzxIYHfgI35HXL9fri8ouLdmre4jJQc=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-12 09:53:39, Info                  CSI    00004faa [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-12-12 09:53:39, Info                  CSI    00004fab [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-12-12 09:53:39, Info                  CSI    00004fac Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 15Zo6QE4AUfojzxIYHfgI35HXL9fri8ouLdmre4jJQc=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-12 09:53:39, Info                  CSI    00004fad Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 15Zo6QE4AUfojzxIYHfgI35HXL9fri8ouLdmre4jJQc=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-12 09:53:39, Info                  CSI    00004fae [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2015-12-12 09:53:39, Info                  CSI    00004faf@2015/12/12:14:53:39.130 Primitive installers committed for repair
2015-12-12 09:53:39, Info                  CSI    00004fb0 [SR] Repair complete
    The opencl.dll is like this on a clean install. There are steps to fix it here Solved SFC some corrupt files can not be fixed - Windows 10 Forums

    As mentioned above you need install.wim (not esd). You can either convert it or download a new ISO from Tech Bench which unlike the media creation tool contains install.wim by default.

    There is an issue fixing it if you have Nvidea GPU but I believe X201 and X230 have integrated Intel graphics so you should be OK (I have Intel Graphics also and fixed it OK using Tech Bench ISO).
      My Computer
    Quote Quote

  7. srfinva
    Posts : 2
    Winows 10 Version 1511
    Thread Starter
       New #5

    A HUGE thank you to everyone who helped us with our situation. We downloaded the 1511 ISO from TechBench (per Word Man), mounted the ISO file, and issued the command recommended by gvp9000. As noted by lx07, our ThinkPads used integrated video controllers, so it's good to know that the root problem has to do with a file related to Nvidia chipsets and won't require additional steps in our case. One pass with DISM and SFC fixed my X201, while my wife's X230 required two passes. Our ThinkPads are working great with no corrupt system files, and we're happy campers. Can't thank you enough.
      My Computer
    Quote Quote

  8. Word Man
    Posts : 1,579
    Windows 10 Pro
       New #6

    Good job! Please make sure to mark your thread solved for others' future reference.
      My Computer
    Quote Quote

 

  Related Discussions
Cause of corrupt system files?
in AntiVirus, Firewalls and System Security

I've been in the process of removing data from a Win 10 machine for several weeks now, during which time it has not been connected to the internet, and no new programs have been installed on it. However, today, when I was trying to run malware...
Happy to start of this post by saying, I performed a factory reset on my machine and it is up and running. Though my computer is thankfully functional again, I'm not sure what went wrong in the first place... so I'm posting generally, soliciting...
How to upgrade windows version 1511 to version 1607
in Windows Updates and Activation

Right now I'm using windows 10 version 1511 , then I have to install windows update KB3199986 , the bad thing is that I have to upgrade my windows version to 1607 enable to have to install KB3199986? How can I upgrade my windows 10 version 1511 to...
Hello all. Running windows 10 pro 64 bit. I've updated from Version 1511 to the anniversary update, 1607. Or at least, I thought I did.
When I run sfc /scannow, these are the problems that can't be fixed: 2016-04-17 17:10:09, Info CSI 000051ab Cannot repair member file "Snipping Tool.lnk" of Microsoft-Windows-SnippingTool-App, version 10.0.10586.0, arch...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 14:33.
Find Us




Windows 10 Forums