Corrupt files on brand new install, unable to fix


  1. Posts : 6
    Windows 8.1
       #1

    Corrupt files on brand new install, unable to fix


    Hey everyone,

    I've reinstalled windows a couple of days ago and after installing all my drivers and files and applications, I decided to run sfc /scannow just to be sure everything went right. It found some corrupted files, and was unable to fix them. Rather than try to diagnose the problem, I decided to just reinstall again. So I did, and right after I reinstalled windows I ran sfc /scannow again. Again it found corrupted files! I have no idea where they're coming from, since the install is completely fresh. It's even installed on a new SSD I bought a couple of days ago.

    I tried running DISM, but that failed as well. Here's the output from Command Prompt:
    Code:
    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>Dism /Online /Cleanup-Image /RestoreHealth
    
    
    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0
    
    
    Image Version: 10.0.10586.0
    
    
    [==========================100.0%==========================]
    
    
    Error: 0x800f081f
    
    
    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
    
    
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    
    
    C:\Windows\system32>
    And the logs are attached to this post. Does anyone have an idea what might be causing this? I've already checked the SSD's S.M.A.R.T. status, since I figured it might have been delivered faulty, but it reports no errors.

    I'd take a look at the logs myself but I'm unsure what I should be looking for. Thanks in advance!
      My Computer


  2. Posts : 5,442
    windows 10 Pro ver 21H2 build 19044.1348
       #2

    You need the Install.wim which can be obtained by downloading the ISO from Tech Bench.

    https://www.microsoft.com/en-us/soft...load/techbench


    Once you have the iso downloaded, right click at the ISO > click Mount > leave it there.
    Then open the elevated command prompt and copy and paste this................

    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:H:\sources\install.wim:1 /limitaccess

    Note : H is the drive where the iso is mounted. Change it if your driver letter is different.

    When it is completed, you should get the report that the operation is successful.
    Now run the sfc /scannow again. It should be ok this time.
      My Computer


  3. Posts : 1,366
    Windows 10 Pro x64
       #3

    Have you tried memtest or something like it to test the memory?
      My Computer


  4. Posts : 5,185
    64bit Win 10 Pro ver 21H2
       #4

    Qub1 said:
    Hey everyone,

    I've reinstalled windows a couple of days ago and after installing all my drivers and files and applications, I decided to run sfc /scannow just to be sure everything went right. It found some corrupted files, and was unable to fix them. Rather than try to diagnose the problem, I decided to just reinstall again. So I did, and right after I reinstalled windows I ran sfc /scannow again. Again it found corrupted files! I have no idea where they're coming from, since the install is completely fresh. It's even installed on a new SSD I bought a couple of days ago.

    I'd take a look at the logs myself but I'm unsure what I should be looking for. Thanks in advance!
    Hi Qub1,

    I've had a look at your CBS log and the corrupt file turns out to be opencl.dll. This is a known problem and is due to the graphics card driver changing the file. It actually does not cause a problem and I believe a future Microsoft update will fix the issue so that the sfc scan will not false alarm. Do you have an NVidia graphics card by any chance?
      My Computers


  5. Posts : 6
    Windows 8.1
    Thread Starter
       #5

    davidhk said:
    You need the Install.wim which can be obtained by downloading the ISO from Tech Bench.

    https://www.microsoft.com/en-us/soft...load/techbench


    Once you have the iso downloaded, right click at the ISO > click Mount > leave it there.
    Then open the elevated command prompt and copy and paste this................

    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:H:\sources\install.wim:1 /limitaccess

    Note : H is the drive where the iso is mounted. Change it if your driver letter is different.

    When it is completed, you should get the report that the operation is successful.
    Now run the sfc /scannow again. It should be ok this time.
    Thanks for the info, I'll try this if I run into any further issues. As per phil's answer, if it is a known issue, I'd rather not run any "fixing" operations on a fresh install, as they might cause more problems.

    DeaconFrost said:
    Have you tried memtest or something like it to test the memory?
    Ran one last week, it passed.

    philc43 said:
    Hi Qub1,

    I've had a look at your CBS log and the corrupt file turns out to be opencl.dll. This is a known problem and is due to the graphics card driver changing the file. It actually does not cause a problem and I believe a future Microsoft update will fix the issue so that the sfc scan will not false alarm. Do you have an NVidia graphics card by any chance?
    Ah, so that's probably what's causing the issue, as I do indeed have an NVidia graphics card (GTX 780). If it's a known issue like you said, I think I'll just ignore the error for a while. Is there any ongoing thread or discussion where I can follow the progress of Microsoft fixing the issue? Perhaps on the Microsoft site?
      My Computer


  6. Posts : 5,185
    64bit Win 10 Pro ver 21H2
       #6

    Have a look at post #226 on this thread:

    Latest NVIDIA GeForce Graphics Drivers for Windows 10

    Some of the insiders have discovered the issue has been fixed on their latest builds.
      My Computers



  7. Posts : 1
    Windows 10
       #7

    Thank you!!!!!


    davidhk said:
    You need the Install.wim which can be obtained by downloading the ISO from Tech Bench.

    https://www.microsoft.com/en-us/soft...load/techbench


    Once you have the iso downloaded, right click at the ISO > click Mount > leave it there.
    Then open the elevated command prompt and copy and paste this................

    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:H:\sources\install.wim:1 /limitaccess

    Note : H is the drive where the iso is mounted. Change it if your driver letter is different.

    When it is completed, you should get the report that the operation is successful.
    Now run the sfc /scannow again. It should be ok this time.
    Thank you SO SO Much! I just registered on this forum to express my thanks. This fixed my issue perfectly!!!!!
      My Computer


  8. Posts : 1
    Windows 10 Professional 64-bit
       #8

    davidhk said:
    You need the Install.wim which can be obtained by downloading the ISO from Tech Bench.

    https://www.microsoft.com/en-us/soft...load/techbench


    Once you have the iso downloaded, right click at the ISO > click Mount > leave it there.
    Then open the elevated command prompt and copy and paste this................

    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:H:\sources\install.wim:1 /limitaccess

    Note : H is the drive where the iso is mounted. Change it if your driver letter is different.

    When it is completed, you should get the report that the operation is successful.
    Now run the sfc /scannow again. It should be ok this time.
    Thank you so much for posting your concise instructions how to solve this problem when the sfc/scannow cmd reports finding corrupt files and perversely states that it can't (won't) fix them. Using the Win 10_1511 iso for RestoreHealth worked for me.
      My Computer


  9. Posts : 5,442
    windows 10 Pro ver 21H2 build 19044.1348
       #9

    fooflighter787 said:
    Thank you SO SO Much! I just registered on this forum to express my thanks. This fixed my issue perfectly!!!!!
    PiusM said:
    Thank you so much for posting your concise instructions how to solve this problem when the sfc/scannow cmd reports finding corrupt files and perversely states that it can't (won't) fix them. Using the Win 10_1511 iso for RestoreHealth worked for me.
    You are very welcome.
    Good to know both of you have the problem resolved.
    Happy computing.
      My Computer


 

  Related Discussions
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 18:14.
Find Us




Windows 10 Forums