Corrupt files on 3 computers after upgrading to TH2

Page 1 of 5 123 ... LastLast

  1. Posts : 11
    windows 10 pro 64
       #1

    Corrupt files on 3 computers after upgrading to TH2


    Hello guys, first post but reading forum for years...
    can some of you do an sfc /scannow and check your results with the November update installed?
    I always do this when i finish installations, and on 3 computers and 4 installations on them, 2 on one computer just to be sure i am getting corrupt files and struggling with my anger to not go back to windows 7 and get rid of all win 10 problems and MS ignorance.
    here is my results, many corrupted files in the log.. but is long so i don't post it...

    Microsoft Windows [Version 10.0.10586](c) 2016 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.


    Thanks in advance for any replies
      My Computer


  2. Posts : 2,799
    Linux Mint 20.1 Win10Prox64
       #2

    Download the the Installation ISO: Windows 10 Download - Tech Bench

    1. Mount the ISO and copy install.wim from the source folder to Desktop
    2. Create a folder on desktop: mount


    Open Admin Command prompt, copy/paste each line and run:

    1. Dism /mount-wim /wimFile:%USERPROFILE%\Desktop\install.wim /index:1 /MountDir:%USERPROFILE%\Desktop\mount
    2. Dism /Online /Cleanup-Image /CheckHealth
    3. Dism /Online /Cleanup-Image /RestoreHealth /Source:%USERPROFILE%\Desktop\mount\windows /LimitAccess
    4. Dism /unmount-wim /Mountdir:%USERPROFILE%\Desktop\mount /discard
    5. re-run: sfc /scannow
      NOTE: Might have to run multiple times until it's clean
      My Computer


  3. Posts : 11
    windows 10 pro 64
    Thread Starter
       #3

    Ow thanks for the reply and the solution! /hat off
    It works miracles if someone has the problem i had with corrupt files
    after running it 2 times all 3 computers came with that message :

    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 did not find any integrity violations.
      My Computer


  4. Posts : 39
    Win 10 1803 (17763.253) Pro for Workstations
       #4

    Thanks Topgundcp!
    After seeing this post, I checked all of my Win 10 installations (2 upgrade from 8.1 & 3 Insider Preview) and found all 5 had corrupt files on them:
    1. Desktop upgrade from 8.1, WU to 1511 (10586)
    Upgraded to 1511 and then Clean install from iso.
    2. Laptop upgrade from 8.1 WU to 1511 (10586)
    Alienware, i7-4710 (No clean install yet)
    3. 3 each Insider Preview (i7-4790K) WU to 1511
    Completing the steps from Post #2 cleared all of them.
    I will be more diligent in the future by running "sfc /scannow" after all major upgrade/updates!
      My Computers


  5. Posts : 2,799
    Linux Mint 20.1 Win10Prox64
       #5

    Great. Glad you got it sorted. Please mark the thread "SOLVED" to help others.
      My Computer


  6. Posts : 56,806
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #6

    dgrigo said:
    Hello guys, first post but reading forum for years...
    can some of you do an sfc /scannow and check your results with the November update installed?
    I always do this when i finish installations, and on 3 computers and 4 installations on them, 2 on one computer just to be sure i am getting corrupt files and struggling with my anger to not go back to windows 7 and get rid of all win 10 problems and MS ignorance.
    here is my results, many corrupted files in the log.. but is long so i don't post it...

    Microsoft Windows [Version 10.0.10586](c) 2016 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.


    Thanks in advance for any replies
    If you're interested, this will filter out all the SR entries from the CBS log and create a .txt on your desktop. Scroll thru it to find what it could not fix.

    findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >"c:\users\xxxxxx\desktop\sfcdetails.txt"

    Sub your name for xxxxxx (the name that appears under "users" on your OS drive.
      My Computers


  7. Posts : 11
    windows 10 pro 64
    Thread Starter
       #7

    f14tomcat said:
    If you're interested, this will filter out all the SR entries from the CBS log and create a .txt on your desktop. Scroll thru it to find what it could not fix.

    findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >"c:\users\xxxxxx\desktop\sfcdetails.txt"

    Sub your name for xxxxxx (the name that appears under "users" on your OS drive.
    Very Handy tip, thanks very much, both of you
      My Computer


  8. Posts : 5
    Windows 10
       #8

    Didn't work for me. "The source files could not be found".
    Edit: Fixed It. Thanks.
    Last edited by NarekUnited; 17 Nov 2015 at 15:56.
      My Computer


  9. Posts : 54
    Windows 10
       #9

    It is waste of efforts to restore opencl.dll since NVIDIA driver overwrites it on its next install, so error returns back.
      My Computer


  10. Posts : 13
    Windows 10 IP
       #10

    Ache said:
    It is waste of efforts to restore opencl.dll since NVIDIA driver overwrites it on its next install, so error returns back.
    Interesting. I never knew that. I just an SFC and guess what. The only 2 corrupt files were:

    2015-11-18 16:14:39, Info CSI 00004b54 [SR] Verifying 100 (0x0000000000000064) components
    2015-11-18 16:14:39, Info CSI 00004b55 [SR] Beginning Verify and Repair transaction
    2015-11-18 16:14:45, Info CSI 00004b5f [SR] Repairing corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll" from store
    2015-11-18 16:14:49, Info CSI 00004bd9 [SR] Verify complete
    2015-11-18 16:21:35, Info CSI 000060fc [SR] Repairing corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll" from store
    2015-11-18 16:21:36, Info CSI 000060fe [SR] Repair complete
    2015-11-18 16:21:36, Info CSI 000060ff [SR] Committing transaction

    SFC managed to "fix" them though without DISM required.
      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 10:27.
Find Us




Windows 10 Forums