Windows 10 Windows 10 -10041, sfc/scannow, really?

bochane

Excellent Member
Joined
Oct 18, 2012
Messages
1,390
Part of an answer of Microsoft on a problem with dwm.exe (see my topic W10 on small / marginal systems) is run sfc/scannow. That was a disaster, when I returned after an hour or so, I found my PC trying to install W10 TP 10041. I just rebooted, it told me that it could not install and all looks normal now.

My question
Maybe my installation is corrupt, maybe sfc/scannow is broken (maybe even both are corruped) so I really like to know if anyone of you successfully ran sfc on build 10041?

Added:
Maybe the scan interferred with the automatic installation of 10049......
 

Last edited:
Solution
Build 10049 SFC works fine:
An image from 'Windows 10 -10041, sfc/scannow, really?'. Windows Command Prompt shows sfc /scannow completed with corrupt files repaired successfully.
Forget this question, it was interfering with the installation of 10049...

Sorry
 

Last edited:
sfc is still broken on windows 10
 

It can be fixed. See this thread:
http://windowsforum.com/threads/how-to-repair-the-sfc-in-build-10041.207569/

Am testing build 10049 now.
 

Build 10049 SFC works fine:
An image from 'Windows 10 -10041, sfc/scannow, really?'. Windows Command Prompt shows sfc /scannow completed with corrupt files repaired successfully.
 

Last edited by a moderator:
Solution
Back
Top