![]() |
MS-DEFCON 2:
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it.
|
-
Last month’s second Tuesday cumulative update for Win10 1803 is bricking Surface Book 2
Home › Forums › AskWoody blog › Last month’s second Tuesday cumulative update for Win10 1803 is bricking Surface Book 2
Tagged: BSOD, KB 4467682, Win10 1803
This topic contains 7 replies, has 5 voices, and was last updated by
anonymous 2 months, 2 weeks ago.
-
AuthorPosts
-
See what I mean about testing cumulative updates before they’re rolled out? KB 4467682, last month’s second cumulative update for Win10 1803 (the “non
[See the full post at: Last month’s second Tuesday cumulative update for Win10 1803 is bricking Surface Book 2]4 users thanked author for this post.
-
From the report in The Register:
As for the afflicted users, uninstalling the cumulative update appears to do the trick. The only problem is that customers face a sphincter-clenchingly short window in which to actually log in, leap into Update History, find the install, and click uninsta…
Oh heck, it blue screened again.
Hence some users have had to resort to reinstalling the operating system from scratch.
MSFT kindly allows its Windows 10
victimscustomers to defer updates for limited periods. Perhaps this deferral period (make it 30 days, or better yet 30 months) should be built-in into their patches as the default value, with an option to “Install Now–I can’t wait to enjoy your goodness!!!” for those who like serving as cannon fodder. -
anonymousNot to minimize this idiotic bug but …
If I understand the problem, this is a misuse of the verb “to brick.” Something is bricked when it is both nonfunctional and irreparable, i.e. it’s only useful as a brick. If you can load an operating system, it’s not bricked. This makes the headline seem a little sensational.
1 user thanked author for this post.
-
It’s a fair point, I think the term “brick” becomes overused because people tend to think of it in a sense of the computer being reduced to the usefulness of a paperweight in the short-term, not necessarily whether the system is irreparable.
In this day and age where the standard “fix” for many Windows issues is to give up and reinstall the operating system though, perhaps we need a new adjective to describe the state of “inoperable due to Windows needing another reinstall.”
Perhaps just an acronym, WHFF: Windows Has Failed to Function.. flows nicely into referring to your computer as “whiffed.” Also works with a lot of more colorful phrases.. “Windows has Fallen on it’s Face”.. or “Windows has..” well you get the idea.
4 users thanked author for this post.
-
-
anonymousI don’t think it’s fair to expect Microsoft to test every possible iteration of hardware, especially when that hardware comes from obscure manufacturers like Microsoft.
There’s always going to be problems, and it’s partially the consumer’s fault for buying first-party merchandise and expecting it to play nicely with the systems it was designed for. That’s why you pay extra for the name brand, so you have the privilege of seeing the blue smiley face more often.
13 users thanked author for this post.
-
Now added to known issues:
After installing this optional update some users may get a blue or black screen with error code, “System thread exception not handled.”
For customers who are currently experiencing this issue, please follow these instructions Troubleshoot blue screen errors and uninstall KB4467682.
Note For Surface Book 2 customers, we are only blocking this optional update. You will receive the required December 2018 security update release.
A resolution for this issue will be available in the December 2018 security update release.
https://support.microsoft.com/en-us/help/4467682
Cannon fodderChumpDaft gluttonIdiotSuckerMore intrepidCrazy/ignorantToxic drinker"Saluted blockhead" (Group ASAP)1 user thanked author for this post.
-
Yep. Looks like they won’t fix it, but they will block it – and fix it next week.
Looks like the “seekers,” once again, are the ones that got hit. If you didn’t specifically click “Check for updates,” you didn’t get this patch.
BTW, I should mention that it’s nice to get straightforward reports from MS about their bugs, even if it took ’em a week to sort it out. On their own hardware.
-
-
anonymousSurface is broken with all updates. MS is not caring about it customers.
-
AuthorPosts
Comments are closed.
-
-
It's easy to post questions about Windows 10, Win8.1, Win7, Surface, Office, or browse through our Forums. Post anonymously or register for greater privileges. Keep it civil, please: Decorous Lounge rules strictly enforced.

Plus Membership
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments. Click here for details and to sign up.
Search The Lounge
Recent Replies
-
Kirsty on How many Internet domains own MS, Google, Apple, Amazon? Try tens of millions20 minutes ago
-
ibe98765 on Tell me the truth – Which is better, Chrome or Firefox?27 minutes ago
-
OscarCP on Cimpanu: The US Govt Accountability Office recommends the US adopt GDPR-like privacy legislation32 minutes ago
-
mn– on Patch Lady – Access gets beat up again47 minutes ago
-
b on Win10 updating terminology is changing again – but this time maybe it’s tied to a major improvement1 hour, 18 minutes ago
-
warrenrumak on Patch Lady – Access gets beat up again1 hour, 54 minutes ago
-
mn– on Neon or Kubuntu?2 hours ago
-
Sueska on Pale Moon vs. Waterfox and their quirks2 hours, 9 minutes ago
-
NetDef on Gralla: Why Windows 10 may never get another killer feature2 hours, 15 minutes ago
-
anonymous on Win10 updating terminology is changing again – but this time maybe it’s tied to a major improvement
2 hours, 26 minutes ago -
anonymous on Cimpanu: The US Govt Accountability Office recommends the US adopt GDPR-like privacy legislation
2 hours, 30 minutes ago -
anonymous on Win10 updating terminology is changing again – but this time maybe it’s tied to a major improvement
2 hours, 34 minutes ago -
slatus on OneNote being periodically set as default printer2 hours, 41 minutes ago
-
brian1248 on Disable Firefox Experiments v60+2 hours, 53 minutes ago
-
anonymous on Brown on brownish
4 hours ago -
Kirsty on Anomalous, buggy behavior on AskWoody4 hours, 6 minutes ago
-
JNP on Pale Moon vs. Waterfox and their quirks4 hours, 22 minutes ago
-
OscarCP on A note on anonymous posters4 hours, 41 minutes ago
-
cesmart4125 on Anomalous, buggy behavior on AskWoody4 hours, 43 minutes ago
-
OscarCP on Brown on brownish4 hours, 50 minutes ago
Recent Topics
-
How many Internet domains own MS, Google, Apple, Amazon? Try tens of millions
20 minutes ago
-
Patch Lady – Access gets beat up again
47 minutes ago
-
Neon or Kubuntu?
2 hours ago
-
Why am I getting this update again
10 hours, 4 minutes ago
-
Profile picture
12 hours, 38 minutes ago
-
Several Cryptojacking Apps Found on Microsoft Store
12 hours, 54 minutes ago
-
Machine keeps flipping into airplane mode
6 hours, 46 minutes ago
-
Trashing this post using Profile Post/reply del function
13 hours, 7 minutes ago
-
remote access using an Android phone
13 hours, 20 minutes ago
-
Cjoint dot com security issue?
12 hours, 45 minutes ago
Search for Topics
Recent blog posts
- Patch Lady – Access gets beat up again
- Anomalous, buggy behavior on AskWoody
- Cimpanu: The US Govt Accountability Office recommends the US adopt GDPR-like privacy legislation
- Microsoft updates its schedule for SHA-2 ‘critical’ Win7 update, now due in March
- Pssssst… I still don’t believe the part about Microsoft testing 20H1, then jumping back to 19H2