It's less the vibe coding and more: this is what happens when you have the developers do all the QA and fire the actual QA staff.

They've been screwing up the Windows updates since Windows 10, vibe coding wasn't a thing at that point.

In a way they are. Their QA was sent overseas and at some point was cut down to basically skeleton crew.

Every engineer at MSFT was recently ordered to use AI.

The bulk of where MSFT makes money is not from its OS but from selling your data and being a cloud provider. They don't really care about the user experience anymore and that has very clearly shown to be their lowest priority for a few years on now.

A lot of what the other comments have said is right, but also add that to on top of all the layoffs theyve had and they keep telling their devs to double their efforts. Its been in so many meetings that at this point a single engineer should be able to do the work of the whole company...

the shareholders keep demanding doubling pace from their engineers but they just wont listen smh

They should just fire all the engineers already theyre clearly slacking off /s

Do these updates not go through any rigorous testing at all

Lol no, MSFT infamously dropped their entire Hardware QA team after WIndows 7 and instead relied on the also infamous insider hub to get QA "feedback" from home users instead, leading to the also infamous Windows 8 disaster and slightly less infamous critical CVEs that went unaddressed because MSFT ddidn't even bother to read the insider hub posts.

Oh and they didn't learn anything and kept running with the insider hub well into Windows 10 & 11.

It's a combination of vibe coding and absolutely no QA testing, because they fired a fuck ton of QA people 10 years ago. Microsoft is making it's users beta test their fucking software through telemetry bug reporting. And we fucking pay for that privilege.

You thought that because the headline is pretty deliberately misleading. Clickbait trash.

Even Microsoft (probably) isn't that stupid or desperate yet. What seems much more likely to me is that they will keep introducing AI features and more invasive ads gradually and making them opt-in or removable with the intention of making them mandatory later on.

I 100% believe that Microsoft fully understands that a lot of people aren't happy with most of these changes, but profit must grow and they are elbow-deep in their AI gamble so they must keep pushing just slowly enough to avoid most users and businesses feeling like looking for alternatives is worth the effort. They are treading a fine line and are sometimes pushing too hard, but that in itself can be a solid negotiation tactic to manipulate people into accepting bad deals and my guess is that it's fully intentional.

It's genuinely bad, even if entire universe isn't affected. Shows sloppiness. Headline is too kind for implying this could be "some kind of design upgrade", instead of FUBAR.

It is pretty bad. It's specifically Enterprise that is effected, and if they're pushing these kinds of bugs on Enterprise customers then they really don't have the QA they need. Think about how much they care about what they push on standard customers.

It's Microsoft, same thing.

The right click context menu for me has been unusable in certain circumstances for me for the past year or so. It's happened on multiple devices, including corporate issued dell and Lenovo machines. The menu options just stop responding to clicking. After getting fed up with this and all the other crap I didn't ask for, I finally just ripped the bandaid off, ditched dual booting, am now on full single boot Linux mint.

And, it's so fucking refreshing. I finally feel like the machines I built and own are mine again.

Task Manager is launched by the listener in winlogon if you use the Ctrl + Shift + Esc method though, right? I'm pretty sure you can still launch Task Manager, and from there attempt to relauch Explorer, even if Explorer is borked or not running. You'd just have to know how to do that and that you can.

That's what I always do when Explorer's ears inexplicably catch fire and I'm either too lazy or too naively hopeful to reboot.

For anyone following along at home, Windows Explorer is also responsible for displaying the start menu/taskbar. In the example in the article there's something else funky going on inside Explorer, though, because the taskbar and even the desktop icons are all there, it's just not rendering correctly. (Explorer is also responsible for showing all of your desktop icons.)

This is the way.

I wonder if win+r works to launch stuff and commands

the only troubleshooting step apple has is to reimage.

That's not entirely true. More often than not, the only troubleshooting step the "Apple Certified Professionals" there offer is to buy a new Mac.

Never in my life have I needed to reimage any Linux machine, but I have had to reimage many, many, many windows machines and quite a few Apple devices too. I have a long career in IT (and even before that, I've been building computers since I was 12), so my sample size consists of thousands of computers going back decades.

I've only ever reimaged Linux systems when I felt like distro hopping for fun. Maybe I've just been lucky, but I think it's probably more to do with the fact that Linux tends to be extremely reliable once you have it set up (unless you manage to break it, but even then there are usually multiple ways to fix it without reimaging).

Out of interest, which aspect don't you believe? The article is clear the broken update effects a specific subset of enterprise users, on a specific mix of base versions and cumulative updates.

This seems like a classic windows update issue. In fairness to Microsoft it is difficult to prevent bugs when there is a huge install base, with a huge range of hardware, with a huge range of users on different mixes of updates and updating at their own. I personally think that's totally believable.

What's not clear is perhaps the implied overarching story that W11 is worse for this than other versions of Windows. I can't answer that about windows updates themselves, but I certainly believe W11 is the worst version of Windows I've ever used (and I've used every version back to 3.11 as a kid). I have to use W11 at work: the UI is absolutely terrible and unfriendly but far worse it constantly and inexplicably slows down, programs become unresponsive repeatedly and I come across errors constantly.

I work in a big organisation and I don't even bother to report most errors now - we hop between PCs because of the nature of my Job, and I've come up across so many I just can't be bothered opening more tickets. I'd describe it as a mostly large volume of minor issues and inconveniences that cumulatively, on top of the bad design, that make it a shit experience. But I've also had numerous major errors since we moved from W10 to W11 on different PCs - they all have the same hardware and software yet the problems are different on each. I've given up reporting the problems and just avoid the PCs, and I think a lot of my colleagues are the same.

My organisation (I work in a large Hospital), is already stretched due to high work volume and low staffing and we now have a constantly little drag from Windows 11 on everything we do. It's like Microsoft sprinkle a little bit of shit onto every computer, every day, all day. The cumulative effect in just my organisation must be massive - I shudder to think how bad it is across the whole economy.

From the article:

The latest kerfuffle will only be seen by Enterprise users running Windows 11 24H2 or 25H2 who have a July 2025 cumulative update installed as well.

Are you running Windows 11 Enterprise?

Because everyone left at the company is as bad as he is or worse?

Because all of them have AI shares.

Because line go up

dmenu suddenly stops opening

Because the rigour and quality of work that is needed to do good software to get to market is insanely higher than the one required for keeping the money machine alive once you are a monopoly. So as you hire more and more to get your hands in as many pies as possible, have fewer and fewer experienced staff to train the new hires, and do questionable hires in leadership positions, the culture invariably shifts to doing less and less effort, or putting effort in the wrong place, and there you have it.

Now in Microsoft's case, the quality was never that high to begin with (but the scummy practices made up for that), and the pockets are deep aplenty, so I think we are in for quite the shitshow (it can, and it will, get even worse).

Because they fired the QA department years ago, in favour of non-rigorous testing by users crazy enough to run whatever Microsoft's version of a nightly build is. Because there's no testing plan, some sets of conditions never do get tested.

Surely ME was worse than Vista?

Were you not around for Windows ME? I'd take Vista any day over that hot streaming pile of regret.

vintage 🤌

It's blogspam. You can click through to the original article. It only happens in certain environments.

Yeah, lol the article and the way OP posted it insiniuate that Microsoft somehow decided to get rid of it while that's not the issue, I did hear there's some bugs but yeah, wouldn't be Windows if it weren't.

Per the Microsoft KB for it, this only happens if Windows updates are installed before a user logs in for the first time. So basically re-images and especially VDI environments are at risk of this happening.

oldest supported

So, Windows 11 then, right?

Technicians are baffled how, even with an astounding 90% hallucination rate, this still was more reliable than windows search.

Just think about what's happening behind the scenes on Azure. I work with it daily and even it feels like a bloated slow mess.

They're still allowing you to hold back updates? So nice of them.

Iirc, you can with Pro, but not with home.

To be fair, I've had updates break my DE on Linux too. It's one of the reasons why I no longer use Fedora.