Microsoft patches the patch that put Windows 11 in a coma

Microsoft is patching another patch that dumped some PCs into recovery mode with an unhelpful error code. The glitch was caused by the May Patch Tuesday update, which failed to install on a small number of Windows 11 machines. The broken patch mostly hurt virtual boxes, leaving them in recovery mode with a boot error. This …

[ChrisElvidge]

Perhaps a class action lawsuit to the effect that unauthorised changes to computer systems is illegal.

Take aim at dodgy terms of use - make the software companies pay for outages.

[Jim Mitchell]

Sure, then the other class action for not patching their software hits from the other side!

[PCScreenOnly]

Turned off

They still throw patches when you think you have stopped them all so you can patch manually and in a controlled manner.

Amount of times my machines have all rebooted and patched overnight when I do not want them to is staggering.

Let me patch machine A, if it breaks I can use B or C. Don't patch and break them all so I am fucked

[Michael Strorm]

> "Perhaps a class action lawsuit to the effect that unauthorised changes to computer systems is illegal."

I can guess- and in truth assume with complete confidence- that there's going to be something *somewhere* in that 379 page EULA you "accepted" (but didn't read) which says you authorise MS to make any changes they "need" or want to your computer.

It's most likely near the bit covering ownership of your firstborn.

[Missing Semicolon]

A turnaround

I used to wonder that using Ubuntu as my work PC os was exposing me to the risk of spending too much time fixing it. It seems Windows is catching up, and I needn't worry.

[Andy Non]

Coming next week...

A patch for the patch for the patch.

Windows 11 will soon be patches all the way down.

[Gene Cash]

Re: Coming next week...

Well, I mean... if you read Raymond Chen's blog, it apparently already is, and has been so for years.

[bemusedHorseman]

Re: Coming next week...

Reminds me of how I used to think "KB" stood for kilobyte, that a patch being named "KB1234567" meant that it was patching the 1,234,567th kilobyte somewhere in the system... I had some wacky thoughts of how to computer, as a kid.

...On the other hand, I still maintain that the G in 4G/5G/etc is and always was originally intended to stand for gigabit, as in, that's the connection speed that that type of cell network is "supposed" to be capable of!

[abend0c4]

And yet...

... there's still effort available to make frivolous changes to Notepad.

[Michael Strorm]

Windows in a coma, I know, I know...

...it's serious.

[Anonymous Coward]

Apply the bumper patch: macos or Linux.

[Tron]

The workaround is to up the scaling to 125 or 150 percent.

That's not a workaround, that is a bodge. You should not rely on a software company that fails this much.

Do insurance companies pay out when you lose cash over a MS failure? Surely use of MS counts as a pre-existing condition.

[billdehaan]

This is rapidly turning into a Monty Python sketch

Python: "We apologise again for the fault in the subtitles. Those responsible for sacking the people who have just been sacked have been sacked."

Microsoft: "We apologise again for the fault in the patch. The patch for the OS has been replaced with a patch for the patch to the OS."

Of course, this is the same day that El Reg reports Windows 11 market share stalls ahead of Windows 10 cutoff, with numerous reasons given, but Microsoft's trashing the OS not even making the cut.