Mandatory Windows 10 Update Is Causing Machines to BSOD

Status
Not open for further replies.
Megalith

Megalith

24-bit/48kHz
Staff member
Joined
Aug 20, 2006
Messages
13,000
Microsoft recently released Cumulative Update 1703 for Windows 10, which updated the OS to build 15063.674 as part of its Patch Tuesday update cycle: unfortunately, it has resulted in the Blue Screen of Death for many users. The latest reports say it has something to do with Windows Server Update Services (WSUS).

This appears to actually only affect WSUS users, despite multiple reports of others having issues updating outside of the Enterprise environment. Although Microsoft itself hasn't commented yet, some MVPs, forum volunteers and gurus have chimed in and even posted workarounds and fixes for those bricked (BSOD) machines that applied a Delta patch as well as the Cumulative Update (the former of which has been expired and won't download anymore) and therein was the problem. The Delta patch shouldn't have gone out with the KB update, and this has now been rectified.
 
And of course, due to it being Windows 10 and it knowing better than everybody else, the update was applied to thousands of systems 'automatically' with no simple way to prevent installation until the problem was solved...

Thanks Windows 10! (y)
 
Nice of the "new" version to also begin silently installing shit like the Facebook app and "Photos Add-on" on top of reinstalling literally all of the stupid shit I de-provisioned using PowerShell. Oh, and silently un-installing f.lux as part of the update. I presume it did this to help push me to the new night light shit that MS integrated into the OS. Thanks for notifying me that "All my files are where they used to be" you goddamned liars.

*Oh, and I forgot it also used up over 28GB of my SSD's space to do the update... I guess that explains the uproar I'm seeing on a lot of forums about their HDD space being maxed out all of the sudden and the drive activity being pegged for hours and hours.

I'm on the fast-path to converting my primary system into a hypervisor so I can contain Win10 in a pfSense-isolated box whose only purpose is gaming.

I'm done with Windows for primary use at this stage since MS has decided my PC is theirs to toy with. I have no choice at work, sadly. It would seem that even GPO isn't enough to prevent it from doing insane shit, either. My workstation silently installed the photos add-on application this morning.
 
This is why i put my ethernet connection as "metered" and defer all updates by a week.
 
Seventyfive said:
This is why i put my ethernet connection as "metered" and defer all updates by a week.
Click to expand...

That is not effective. I have way more preventive measures in place. My home machine doesn't even talk to windows update directly. It only gets updates from WSUS in my cluster. Yet gee whiz, what's this? "Try the Facebook app, it's already on your machine!"

"What the fuck?"

MS has gone way beyond annoyances and straight into the land of "Go fuck yourself, your PC is our PC and you will consume what we push onto it."
 
I remove all the bloat from the Windows ISO using toolkit from MDL, disable auto updates, and make nightly macrium reflect images to a non-windows NAS just in case. It will only get worse with time.
 
throwheadsbackinlaughter-gif.39093
 
Tesla cars are like this as well. Bought a VW Mk7 R last winter and the first thing I did was buy weathertech mats and surgically remove their CarNet box that networks the car. Turned out to be a powerful computer with a capable processor, 1 gig of RAM, DAC tied to the car mic, cell modem, and GPS chip.
 
Yea, we've had a hell of a time with Windows 10 wanting to upgrade itself to newer versions without getting permission. We're FIGHTING to stay on 1511 but some PCs (even though they've been explicitly directed not to via GPO) have upgraded themselves to 1607.
 
Almost only effecting enterprise. If using update no worries. If deploying that's where the issues lie. I had 5 test machines go down. Easy fix, go to restore point.
 
"The Delta patch shouldn't have gone out with the KB update, and this has now been rectified."

So if a machine hasn't updated yet this should no longer be an issue? Great, time to check all my WSUS consoles.
 
When I eventually get around to dual booting and adding W10 for a new gaming build, it will not be updated.
 
When is it going to be enough? Isn't this a big enough deal to at least try an alternative? Or do you need your computers to literally melt before you'll even consider something not Windows?

If you really want to try something else, try Ubuntu. It updates when YOU want.
 
there are updates to the article, problem was supposedly usb c (UCSI). fixed now, actually reddit had a fix last night....

i didn't get hit, everything was fine for me. oh and paint and media player are still here in 1709 build 16299.15
 
trparky said:
And yet I had no issues at all on any of my systems.
Click to expand...

Yay! Me, too!

A lot of others are having issues, though. That's what this is about.

I didn't have any issues with Vista, either. From beta all the way until 7 was in beta. Not a single issue. So, that should make it an amazing OS that was super stable and successful! Let's take a look at the stats of this OS!
 
I have disabled windows 10 udpates. I know they are bullshit.
 
cortexodus said:
I'm on the fast-path to converting my primary system into a hypervisor so I can contain Win10 in a pfSense-isolated box whose only purpose is gaming.
Click to expand...

absolutely agree. the last windows for general use for me is 8.1. gaming will get 10 in isolation. and all future stuff is linux and mac (for work) for me. wheeee
 
mandatory?

I disabled Windows Update service, and haven't had an update for months. I only get windows defender updates.
 
My solution was using an actually good operating system. Namely, Ubuntu Linux. Updates actually make things better, and don't take days to download and apply.
 
WetMacula said:
I remove all the bloat from the Windows ISO using toolkit from MDL, disable auto updates, and make nightly macrium reflect images to a non-windows NAS just in case. It will only get worse with time.
Click to expand...

Yep. I use MSMG Toolkit to rip all the bloatware out by the roots from the Windows 10 ISO - no more spyware, cortana, Edge mobile browser, Store + cellphone apps, onedrive, xbox gaming crap, Candy Crush, etc. Forced updates disabled as well.

The problem is a lot of the default crap you can't get rid of once it's installed - at best you're able to hide them, but they'll keep lurking and updating in the background. So the key is not letting them install in the first place.

http://www.majorgeeks.com/files/details/msmg_toolkit.html
 
Last edited:
Of course Microsoft pushing broken updates is stupid and should not happen, but I feel like the news articles are glossing over some significant information regarding this particular glitch.

I've seen it mentioned multiple times that this glitch only happens on systems configured for WSUS. My understanding of WSUS is that it is a service controlled by network administrators on a domain, who's sole purpose is to allow them control over when client machines are updated. So an update went out that only affects systems with managed updates, but somehow was automatically installed on launch day untested.

Sounds like this should be a wake-up call for a bunch of admins to actually test their updates before deploy, or not use WSUS, as they clearly aren't.
 
CrazyRob said:
Of course Microsoft pushing broken updates is stupid and should not happen, but I feel like the news articles are glossing over some significant information regarding this particular glitch.

I've seen it mentioned multiple times that this glitch only happens on systems configured for WSUS. My understanding of WSUS is that it is a service controlled by network administrators on a domain, who's sole purpose is to allow them control over when client machines are updated. So an update went out that only affects systems with managed updates, but somehow was automatically installed on launch day untested.

Sounds like this should be a wake-up call for a bunch of admins to actually test their updates before deploy, or not use WSUS, as they clearly aren't.
Click to expand...

The problem is MS apologists have always insisted Microsoft's sloppy windows 10 updates didn't affect businesses because WSUS was a "safe haven." Clearly that's not the case.

All this really reinforces is what's been obvious to many people all along: nobody's actually safe from Microsoft's untested Windows 10 updates. Not end users, not enterprise/business on WSUS or a third party patch manager. You have to vet every single windows update, and even then probably wait 3-6 months before considering any.

Pretty sad because there were many years that as an IT administrator of Windows servers and workstations, you didn't really have to look over your shoulder and question every single update that came down. You needed to test them, yes, but you didn't have to be suspicious of them. Those days are long gone.
 
Last edited:
N4CR said:
When I eventually get around to dual booting and adding W10 for a new gaming build, it will not be updated.
Click to expand...

That's what I do. I dual boot with Linux and only boot to Windows 10 for games. After I do my ~weekly system backup, I'll re-enable updates, do any updates and then disable updates again. Not going to let Windows do the update on it's schedule!
 
  • Like
Reactions: N4CR
like this
DPI said:
The problem is MS apologists have always insisted Microsoft's sloppy windows 10 updates didn't affect businesses because WSUS was a "safe haven." Clearly that's not the case.

All this really reinforces is what's been obvious to many people all along: nobody's actually safe from Microsoft's untested Windows 10 updates. Not end users, not enterprise/business on WSUS or a third party patch manager. You have to vet every single windows update, and even then probably wait 3-6 months before considering any.

Pretty sad because there were many years that as an IT administrator of Windows servers and workstations, you didn't really have to look over your shoulder and question every single update that came down. You needed to test them, yes, but you didn't have to be suspicious of them. Those days are long gone.
Click to expand...

So are you saying that the update was forced despite WSUS being configured to block? If so, then that's an even bigger F-Up. I haven't seen any info one way or the other.
 
All of you guys who are so blasé, like "oh, I just disable updates" feel free to fill in the rest of us on how this simple thing you're doing which somehow works better than literally isolating windows 10 "enterprise" machines from communicating to sets of DNS records in excess of 20k entries. I'd love to know how this simple feature you're ticking on and off somehow works better than domain-level GPO configurations which are supposed to expressly forbid these machines from even talking to anything involving the word "updates" which does not exist only within the domain in which that machine sits.

Please, pretty-fucking-please, elaborate on the easy-mode fix you have which will consistently keep workstations from updating whenever the hell they want to and resetting everything on the machine in the process. Or, receiving new "features" like silently-installed Facebook UWP applications or auto-photo-album-assembling "DLC" for existing UWP apps.

Honest. No joke. 'Cause I think your success is laudable at minimum and I'll exalt in the brilliance of your very existence if you can demonstrate an iron-clad set of proof for your statements. I very much want this magical simple solution you seem to know about...

DPI mentions using the MSMG toolkit, and I've spent literally days tinkering with answer files in the WAIK, and it's a non-stop-drag-out fight to keep Windows 10 "enterprise" systems from doing shit like auto-upgrading during someone's lunch break costing them hours of work time. Then, once the "upgrade" is done, you get to remove all the packages it put back on that you killed before. You know, useful stuff like the "Xbox" app.
 
Brand new custom build with pro fully up to date. 3rd gen 9470 m hp. Hp 5th gen all in one and a custom system 2nd gen . all intel. All win 10 pro or home. No issues
 
cortexodus said:
All of you guys who are so blasé, like
Click to expand...
<snip>

I think, don't quote me, but I think disabling the Windows update service does work. But I've been off of 10 since February. Went back to 7. I believe it stopped my Pro install from updating at the time. Not the most ideal solution I know.
 
BloodyIron said:
When is it going to be enough? Isn't this a big enough deal to at least try an alternative? Or do you need your computers to literally melt before you'll even consider something not Windows?

If you really want to try something else, try Ubuntu. It updates when YOU want.
Click to expand...
Going through these issues is still less of a pain in the ass than dealing with linux.
 
cortexodus said:
, and silently un-installing f.lux as part of the update.
Click to expand...
You know there are actually people that are defending this kind of behavior... and believes the system works better without having the software you need to run. O.O
Its crazy but true...
 
DPI said:
Yep. I use MSMG Toolkit to rip all the bloatware out by the roots from the Windows 10 ISO - no more spyware, cortana, Edge mobile browser, Store + cellphone apps, onedrive, xbox gaming crap, Candy Crush, etc. Forced updates disabled as well.

The problem is a lot of the default crap you can't get rid of once it's installed - at best you're able to hide them, but they'll keep lurking and updating in the background. So the key is not letting them install in the first place.

http://www.majorgeeks.com/files/details/msmg_toolkit.html
Click to expand...
That does not look too complicated. Thanks
 
Google surfaced this forn me in my news feed. I haven't heard anything from our TAM at Microsoft yet. Kind if upset about that...

https://support.microsoft.com/en-us...to-boot-after-installing-october-10-version-o

Basically if you have synced and downloaded since Tuesday at 4pm PDT you are in the clear (thankfully we waited long enough to avoid getting the bad update).

We haven't seen this in testing so far.

This kind of stuff is getting beyond stressful. Microsoft needs to hire back their testers and straighten this crap out, like yesterday. I am seriously angry about this...
 
  • Like
Reactions: DocNo
like this
MSMG Toolkit seems rather legit to me I won't miss edge, cortona, store, and most importantly the dreaded candy crush.
 
Status
Not open for further replies.
Back
Top