Beware the Windows 10 Fall Creators Update
-
My main work system applied the FC update today and when it rebooted, I was greeted with a CRITICAL_PROCESS_DIED error and a frowny BSOD. I spent the rest of the day trying to recover, to no avail. My backups were all corrupt so I also need to confirm that our main NAS isn't going bad (we just moved locations over the past week so something may be loose etc). Tomorrow I get to reinstall Windows and all my work apps, utils, music etc etc etc.
Thanks Microsoft.
-
step1: install wsus
step2: do not approve feature updates automatically
step3: shoot yourself in the foot when being forced to approve feature updates/upgrade after current_build goes EOL after 18 months
step4: get yelled at by staff because their systems are useless pieces of junk for approx 4h's to complete a feature update/upgrade
step5: GOTO step 3 in 18 months -
I disabled auto-applying updates a long while back. It seems to be respecting it, but pops up a nag screen once a day.
-
Naah approved FCU for test group about 20 users… No problem at all, upgrade took about 30 mins in backhround and then another 30 after reboot.
Really no issues whatsoever but have a long way to go. 350 machines mixed 8.1 and 10 versions, should be finished till next major upgrade lol :) -
it depends what build they start from i guess.
i had around 200-ish on build 1511 …. was painstakingly slow (around 2h's if SSD ; around 4hs on platters)
-
Mine are either 1607 or above and 8.1
For those 8.1 it will take time… -
So it turns out that a bad DIMM in my system was the cause of my problems. It borked the FC update, and it also made all my backups appear to be corrupt. I only clued in when a fresh install of Windows started crashing on me, as did Firefox installing & running. Good old memtest86 showed what was up, and now I'm running on new DIMMs. Previous "corrupt" backup restored perfectly and I'm off & running.
I take back my cursing of Microsoft in this one specific instance.
-
I really want my next system to have ECC memory. I have memory errors. If you can't trust you memory, you can't trust anything.
-
Only servers need that! ::)
I totally agree. It would have helped me not waste so much time. This also happened at the tail-end of a corporate move so the timing was less than ideal.
-
@KOM:
So it turns out that a bad DIMM in my system was the cause of my problems. It borked the FC update, and it also made all my backups appear to be corrupt. I only clued in when a fresh install of Windows started crashing on me, as did Firefox installing & running. Good old memtest86 showed what was up, and now I'm running on new DIMMs. Previous "corrupt" backup restored perfectly and I'm off & running.
I take back my cursing of Microsoft in this one specific instance.
There's a lesser known issue with DIMMS, where over time where chassis & CPU fan vibration causes the point contacts in the socket wear a small hole in the pads on the DIMM. Swapping the DIMMS around usually moves the issue out by a few months or sometimes years !! . . . . . but can get you running again long enough to sort out backups while replacements are on order.
-
it breaks enterprise folder redirection too soo…......
