Last month’s second Tuesday cumulative update for Win10 1803 is bricking Surface Book 2

Topic

New Reply

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.

Bat.1, Karlston, dononline, Cybertooth

Reply | Quote

Replies

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 victims customers 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.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

6 users thanked author for this post.

HiFlyer, Fred, BobbyB, lurks about, Karlston, dononline

Reply | Quote

Not 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.

woody

Reply | Quote

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.

HiFlyer, woody, dlsdjh, Cybertooth

Reply | Quote

I 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.

HiFlyer, woody, Fred, BobbyB, EstherD, Bat.1, MikeFromMarkham, Cybertooth, Microfix, Karlston, dononline, dlsdjh, JCCWsusser

Reply | Quote

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

Windows 11 Pro version 22H2 build 22621.2361 + Microsoft 365 + Edge

1 user thanked author for this post.

Elly

Reply | Quote

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.

Reply | Quote

Surface is broken with all updates. MS is not caring about it customers.

Reply | Quote