Microsoft Pulls Another Windows 10 Update Following BSOD Reports

Megalith

24-bit/48kHz
Staff member
Joined
Aug 20, 2006
Messages
13,000
Windows 10 version 1803 Build 17134.441 (KB4467682) is no more: Microsoft began investigating the November 2018 cumulative update following reports of BSODs on Surface Book 2 units and has decided to pull it completely after users realized the only fix was uninstalling it. The "good" news is that the update is optional and only affects devices still on the April 2018 Update.

After installing this optional update some users have reported getting a blue or black screen with error code, “System thread exception not handled.” As a precaution, we have removed this optional update from Windows Update and Microsoft Update Catalog to protect customers. Fixes and improvements will be available in the December 2018 security update release and will include a resolution for this issue.”
 
:facepalm:

It would seem to be apparent that Windows 10 users are in for a long bumpy ride when MS is blue screening their own hardware with their own updates.

After all these decades you would think they would have this all figured out.
 
I have had a couple of BSOD lately, but no telling when they hit as both have been while there was no load on the computer so its not my modest OC on the threadripper.
 
:facepalm:

It would seem to be apparent that Windows 10 users are in for a long bumpy ride when MS is blue screening their own hardware with their own updates.

After all these decades you would think they would have this all figured out.

They had it figured out till they went to a 6 month update cycle. Now the updates create stability issues
 
Last edited:
I still haven't been sent the "October" update.

I'm not sure it's rolled out wide. Although it's available, I've read that it was a soft rollout for users willing to do it manually.

None of the systems I've used (numerous) have received that update.
 
Wouldn't it be nice is MS had a QA team

Then they wouldn't have to pull updates
I was gonna say, it must be difficult for CEOs to understand this, but there are causes and effects related to actions. Maybe getting rid of a QA department for the most used desktop OS in the world wasn't as brilliant as it seemed at the time.

I'd say short term savings tend to lead to long term costs, but they're one of the most valuable companies in the world, so I guess I don't know how that all works.
 
I was gonna say, it must be difficult for CEOs to understand this, but there are causes and effects related to actions. Maybe getting rid of a QA department for the most used desktop OS in the world wasn't as brilliant as it seemed at the time.

I'd say short term savings tend to lead to long term costs, but they're one of the most valuable companies in the world, so I guess I don't know how that all works.
They used the money they spent on QA to build treehouses for the employees
 
I have this update on my desktop and I haven't seen any BSOD. I think their Surface products are sensitive.
 
Do people on here actually believe that 5 years ago (or any arbitrary date in the past) Windows patches didn't have problems? I know there were enough issues 5-10 years ago that I quit applying updates for at least 2 weeks. I rarely do that now, because no patch has negatively affected me (AFAIK) since roughly October 2015.
 
I’m about to hack my win10 and kill the updates. Should have stayed on win7. Just like I thought.
 
they really need to go back to giving end users control of Windows Update...I used to always wait 2-3 weeks before installing any new patches...
 
Do people on here actually believe that 5 years ago (or any arbitrary date in the past) Windows patches didn't have problems? I know there were enough issues 5-10 years ago that I quit applying updates for at least 2 weeks. I rarely do that now, because no patch has negatively affected me (AFAIK) since roughly October 2015.

They're objectively worse than they've ever been, with a particular string of bad ones in the 180x's. AskWoody, Mary Jo Foley, Thurrott - even the pro-MS bloggers are no longer ignoring it. Ever heard of Susan Bradley, aka "The Patch Lady"? She penned an excellent open letter to MS that - with no frills or bias or axe to grind beyond being a longtime expert on the subject area: https://www.computerworld.com/artic...microsoft-management-re-windows-updating.html

Without backlash, MS would have no reason to fix the problems they've created any faster than they are.
 
:facepalm:

It would seem to be apparent that Windows 10 users are in for a long bumpy ride when MS is blue screening their own hardware with their own updates.

After all these decades you would think they would have this all figured out.
They figured it out all right. They figured it out that they can get away with a skeleton QA team, if they use the users as testers.
 
Sorry: someone at HardOCP is mistaken. "Windows 10 version 1803 Build 17134.441" is still the March 2018 version number, not the September 2018 version number.
AFAIK, as of today's date: the latest September 2018 version is "Windows 10 version 1809 Build 17763.168".
This was further updated again Dec. 11, which is "Update Tuesday": the second Tuesday of the month.
After Dec. 11, the version & main build number will again be "version 1809 build 17763.xxx"
Edit: as of 11 Dec. is now "version 1809 build 17763.194"
The pattern being: version 1803 = 2018 & month number 3; version 1809 = 2018 & month number 9.
At a command prompt, type "winver" for the version & build number for any particular Windows system.
 
Last edited:
They had it figured out till they went to a 6 month update cycle. Now the updates create stability issues
No, they had it figured out until someone had the bright idea that a good way to save money was to kill off the QA team. Updates always have issues, but I think the 6 month cycle would not be as bad as it is if Microsoft had kept their QA team.
 
I have a lovely issue with Win10 and the USB on my X99 board (appears to be a common issue)

I always replied to these kinda Win10 threads with "Its working ok for me"

Well now its not...Fucking MS shit
 
I could see this spin.

The problem is isolated to individuals that have blocked the report home data feed of windows 10. This is a neccessary function of windows 10 and needs to be enabled or it destabilizes the system.
 
windows 10... all aboard the failboat.jpg
 
tbh im surprised no one has made any memes of some dips with their trademark baby oil hair with the dandruff flakes on top.

seems like there'd be oodles of captions.

just sayin' ;)
 
Quite often you simply don't get a choice. You can try third party hacks, but I've found their effectiveness to be limited.

Luckily the few windows computers I really care about are all managed by a WSUS server. Hmm. I have a Windows Home Server still; I should load WSUS on it for my home computer. WSUS on Server 2008 doesn't know how to handle the feature updates so you have to manually install them with the update assistant - which is just fine by me.
 
Back
Top