I have six machines that I've upgraded/fresh installed W10. Seems like somewhere along the W10 upgrade obstacle course 5 of the 6 systems say that the window files are corrupt and "SFC /SCANNOW" cannot correct the problem(s). I haven't checked the sixth system!
I then run "DISM /Online /Cleanup-Image /RestoreHealth /wim:K:Sourcesinstall.wim:1 /limitaccess"
using the W10 V1511 ISO that I downloaded from Tech Bench, Reboot and Run "SFC /SCANNOW" again This time it says it was able to fix the system files.
In each case the reason I ran "SFC /SCANNOW" was because the system was doing crazy stuff like rebooting out of sleep or refusing to shutdown or losing the mouse pointer or not being detected by Discovery etc., etc. In each case fixing the system files executing the above solved the strange behavior - at least for now!
Is it me or does the frequent W10 upgrades and fixes leave problems behind? I can't believe that I have five different systems with different hardware and each one gets corrupted system files? I used Windows on many different systems over the years and never experienced this stuff!
[QUOTE=Ken429;525002]I have six machines that I've upgraded/fresh installed W10. Seems like somewhere along the W10 upgrade obstacle course 5 of the 6 systems say that the window files are corrupt and "SFC /SCANNOW" cannot correct the problem(s). I haven't checked the sixth system!
I then run "DISM /Online /Cleanup-Image /RestoreHealth /wim:K:Sourcesinstall.wim:1 /limitaccess"
using the W10 V1511 ISO that I downloaded from Tech Bench, Reboot and Run "SFC /SCANNOW" again This time it says it was able to fix the system files.
In each case the reason I ran "SFC /SCANNOW" was because the system was doing crazy stuff like rebooting out of sleep or refusing to shutdown or losing the mouse pointer or not being detected by Discovery etc., etc. In each case fixing the system files executing the above solved the strange behavior - at least for now!
I have six machines that I've upgraded/fresh installed W10. Seems like somewhere along the W10 upgrade obstacle course 5 of the 6 systems say that the window files are corrupt and "SFC /SCANNOW" cannot correct the problem(s). I haven't checked the sixth system!
I then run "DISM /Online /Cleanup-Image /RestoreHealth /wim:K:Sourcesinstall.wim:1 /limitaccess"
using the W10 V1511 ISO that I downloaded from Tech Bench, Reboot and Run "SFC /SCANNOW" again This time it says it was able to fix the system files.
In each case the reason I ran "SFC /SCANNOW" was because the system was doing crazy stuff like rebooting out of sleep or refusing to shutdown or losing the mouse pointer or not being detected by Discovery etc., etc. In each case fixing the system files executing the above solved the strange behavior - at least for now!
Is it me or does the frequent W10 upgrades and fixes leave problems behind? I can't believe that I have five different systems with different hardware and each one gets corrupted system files? I used Windows on many different systems over the years and never experienced this stuff!
the only way to find out is through the cbs log files...More then likely it is caused by bad drivers that MSFT downloaded. Usually it is the graphics driver and that one causes a lot of pain throughout the system.
I keep the Techbench ISO in my downloads just in case I need to mount it and it has happened a few times. I went and re installed all the correct drivers that they replaced and haven't had any problems yet. Actually my system is running just as good, if not better than my win 7 setup. Win 10 when working correct and tweaked correctly is pretty awesome. But then again I've spent a lot of hours to get it just right.
Also go into all the driver power management tabs and uncheck wake from sleep
[QUOTE=AnEdge;525150]That is why many people prefer using the ISO files instead of using Windows Update.I have six machines that I've upgraded/fresh installed W10. Seems like somewhere along the W10 upgrade obstacle course 5 of the 6 systems say that the window files are corrupt and "SFC /SCANNOW" cannot correct the problem(s). I haven't checked the sixth system!
I then run "DISM /Online /Cleanup-Image /RestoreHealth /wim:K:Sourcesinstall.wim:1 /limitaccess"
using the W10 V1511 ISO that I downloaded from Tech Bench, Reboot and Run "SFC /SCANNOW" again This time it says it was able to fix the system files.
In each case the reason I ran "SFC /SCANNOW" was because the system was doing crazy stuff like rebooting out of sleep or refusing to shutdown or losing the mouse pointer or not being detected by Discovery etc., etc. In each case fixing the system files executing the above solved the strange behavior - at least for now!
Now that we can do Clean Install right away without going through the upgrade process, even more people will do just that.
Yeah, but I did install from a USB drive and yes several of the systems were installed "Fresh" with W10 v1511. Yes, I have unchecked "Wake from Sleep" on all the Network Drivers. It seems MS likes to re-check "Wake from Sleep" after some updates?! But that' a minor issue. I've used various version of Windows literally since day one and I really like W10 but...I've never experienced so many strange happenings!
