Windows 10 image always corrupted after Update ?

[ITSupport]

Hi All,

Can anyone here please share some thoughts and clarification about the SFC /SCANNOW result in Windows 10 ?

I have a brand new Surface Pro 4 tablet that comes with the Windows 10 Professional. So I have update it to the latest using Internet directly to get all available update last week on 11th March 2016 with no big issue. But the SFC end up in error like below ?

C:\>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.​

As per company policy, all Windows 10 must be Enterprise Edition for Bitlocker feature,
So I upgrade it to Windows 10 1511 Enterprise, which bring the Winver to 10586.164, However the image is always end up corrupted as the above again ?

is this normal or I shouldn't need to worry ? or is this just Windows 10 bug after any Windows Update ?


Any help and sugestion would be greatly appreciated.

Thanks.

 

[GreyFox7]

Well there are rumors of some bug or problem with this process however it may be repairable as well.

Have you run DSIM /Online /Cleanup-Image /RestoreHealth?
You may need to make sure its using the correct image for Enterprise with
Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1

Where D:\sources\install.wim is a mounted wim file matching your version. it's also possible you may need to specify install.esd instead of install.wim as explained in the tutorial below.

There's a good Tutorial on another forum, if you search for "DISM - Repair Windows 10 Image" you should find it....

DSIM is your friend.

 

[jnjroach]

It appears that the last Firmware Update corrupted a couple of specific DLLs and the procedure Grey list above fixes it...

 

[ITSupport]

@GreyFox7 & @jnjroach I did that already as per your suggestion, but somehow it is always end up as corrupted:

C:\>dism /online /Cleanup-Image /RestoreHealth /Source:wim:\sources\install.wim:1

Deployment Image Servicing and Management tool
Version: 10.0.10586.0

Image Version: 10.0.10586.0

[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.

C:\>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 and successfully repaired
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.
​

Does it means that no matter how many times you run the DISM command above, every windows update will always corrupting the Windows Image ?

Is this normal ?

 

[jnjroach]

@GreyFox7 & @jnjroach I did that already as per your suggestion, but somehow it is always end up as corrupted:

C:\>dism /online /Cleanup-Image /RestoreHealth /Source:wim:\sources\install.wim:1

Deployment Image Servicing and Management tool
Version: 10.0.10586.0

Image Version: 10.0.10586.0

[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.

C:\>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 and successfully repaired
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.
​

Does it means that no matter how many times you run the DISM command above, every windows update will always corrupting the Windows Image ?

Is this normal ?

You followed the instructions and it still shows corrupted files?

 

[ITSupport]

You followed the instructions and it still shows corrupted files?

Yes, As you can see above from the quoted text, after the DISM command finished, I re-execute the SFC /scannow again for the scond time, it is still showing as invalid ?

 

[jnjroach]

Yes, As you can see above from the quoted text, after the DISM command finished, I re-execute the SFC /scannow again for the scond time, it is still showing as invalid ?

Follow these: http://answers.microsoft.com/en-us/...s/occaisional-black-screen-unable-to-wake-on/

If you have a 1511 ISO you don't need to download a new one...

 

[ITSupport]

Follow these: http://answers.microsoft.com/en-us/...s/occaisional-black-screen-unable-to-wake-on/

If you have a 1511 ISO you don't need to download a new one...

@jnjroach, I'm using the SW_DVD5_WIN_ENT_10_1511_64BIT_English_MLF_X20-82288.ISO file to upgrade the Out of the box Win 10 Pro 1511 to Win 10 Enterprise 1511.

The URL that you've provided seems to be broken ?

Page Not Found
We are sorry we weren't able to find what you are looking for.

 

[jnjroach]

http://answers.microsoft.com/en-us/...on/7c0684b2-795a-4f77-8178-87b3cb74dca2?auth=

Somehow it was truncated...

 

[ITSupport]

http://answers.microsoft.com/en-us/...on/7c0684b2-795a-4f77-8178-87b3cb74dca2?auth=

Somehow it was truncated...

OK, got it. So basically the fix was to run this single command line:

DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:\Sources\Install.wim:1 /LimitAccess​

everytime there is problem with file corruption after the Windows Update. Maybe create a scheduled task to run it after the WSUS update week ?

 

[GreyFox7]

So is the same file "corrupted" every time or different files?
/LimitAccess says it prevents DISM from contacting WU (Windows Update) for repair of online images.
Then is the file actually corrupt or is the signature damaged or ... the process flawed or ... ;-)

If its the same file(s) every time seems it would be simpler to just replace the files rather than run a full DSIM job to do the obvious.

BTW: I will be at unknown [not on the map] location(s) this week with limited or no Internet access.