Windows 10: 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 *Mad


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

:)

 

Windows 10 DIsm cannot find souce file

OK, I have it sorted. - Dism Finished successfully !

You need to get a copy of the 1511 / 10586.11 build (Its been taken down but it can still be found here

How to Download Official Windows 10 Build 10586 (v.1511) MCT (ISO) / ADK / SDK / WDK / HLK / Mobile Emulator - Tech Journey

Once you have the ISO, you will find the install.esd in the Sources directory. Convert it to a WIM. I used NTLite.

Then follow the instructions here:

Corrupt files on 3 computers after upgrading to TH2 Solved - Windows 10 Forums

 

Missing Desktop contents after upgrade to Windows 10

Interestingly, I am noticing the similar questions(more of them) after TH2 release.I can be wrong, but seriously there is something wrong when you upgrade to TH2 from either TH1 or Windows 7/8.

Irony is that they show a banner that

Your Files are as in same state as before

 

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

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

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

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

 

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.

 

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!

 

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

 

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

 

Didn't work for me. "The source files could not be found".
Edit: Fixed It. Thanks.

 

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.

 

I had a load of corrupted dll's not only opencl, but again after fixed them and installed next nvidia driver all is good so dunno about overwrite from nvidia, at least I am not experience that

 

Nvidia may overwrite its opencl.dll (105k) after reboot after install, not right after install. Since it is hardlink to WinSxS, WinSxS version (27k) becomes overwritten too, hash is lost and SFC can't restore it. It is Microsoft bug because WinSxS opencl.dll version is obsoleted.

 

How did you fix it? I'm desperately struggling with this problem.