Windows 10: W10 v1511 Corrupt files?

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 /Source:wim:K:\Sources\install.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!

:)

 

W10 v1511 restarts automatically exactly 24 hours after it was shutdown?

I have 6 systems running W10 v1511 and only one of them has this obsession to restart itself exactly 24 hours after It has been shutdown. I have tracked this behavior for at least a week. Each day it restarts exactly 24 hours after it was shutdown. The
physical time I shut the system down does not change the 24 hour timeframe for it's unattended startup. I have another W10 v1511 (one of the six mentioned above) with almost exactly the same hardware and software and it does not have this problem.

Can someone please give me a few hints on what the heck I should be looking at to make this system stay shutdown. W10 v1511 is a relative fresh install on all the systems.

 

Windows 10 Novermber 1511 update not working with Media Creation Tool

Hi!

What do you mean by "Windows 10 Novermber (November) 1511 update not working with Media Creation Tool"??

I have both a 32 bit and 64 bit USB thumb drive with W10 Home/W10 pro - v1511 that was created with the MCT. Running on W10 pro 32 bit v1511 and a W10 home 64 bit. ISO's had nothing but trouble but did work.

As for Chrome, I have had nothing but trouble when installed. Google updater is installed with it. The updater runs in the background as a foreground process. Its like a nightmare I have over and over. I could see it clouding up the MCT download process.

 

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

 

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!