Jesus fucking Christ… Is Microsoft literally vibe-coding everything now? Do these updates not go through any rigorous testing at all before being released into the wild?
The only solution is to re-image?? This is just flat out fucking awful.
Sorry to all those people who went for the LTSC versions of Windows. How the living fuck does this kind of stuff happen.
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
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.
I remember hearing about this shift of theirs way back in the early Windows 10 days and thinking, “That sounds like suicidal stupidity but maybe there’s something I don’t know?”
It’s less the developer team that did it and more the shareholders and executive team that has turned the product to complete trash.
It’s so dumb, even with the AI stuff I wouldn’t care that much if it was just a new thing the OS could do if the rest of the thing was actually stable. But they seem to be allergic to doing some actual house cleaning and instead keep bolting things on.
The fact that the explorer can regularly completely freeze up nowadays or flat out crash is actually insane. That should be at the top of the priority list before anything else gets worked on. But instead they decided: let’s add a new keyboard shortcut to open a really laggy copilot chat interface.
The fact that the explorer can regularly completely freeze up nowadays or flat out crash is actually insane.
This was literally the trigger for my very first Linux experience, it’s fucking asinine that something so fundamental to the UX could perform so poorly for such an extended period of time.
I love having to reboot the explorer.exe process in task manager because my taskbar search stops working.
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.
Jesus fucking Christ… Is Microsoft literally vibe-coding everything now? Do these updates not go through any rigorous testing at all before being released into the wild?
The only solution is to re-image?? This is just flat out fucking awful.
Sorry to all those people who went for the LTSC versions of Windows. How the living fuck does this kind of stuff happen.
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
Add on top of it that they’re forcing engineers to use AI to try and magically bridge this gap and you get a lot of slop like this.
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.
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.
I remember hearing about this shift of theirs way back in the early Windows 10 days and thinking, “That sounds like suicidal stupidity but maybe there’s something I don’t know?”
Nope. It’s exactly as I thought.
Sounds like the development team outsourced the QA work to the customer.
It’s less the developer team that did it and more the shareholders and executive team that has turned the product to complete trash.
It’s so dumb, even with the AI stuff I wouldn’t care that much if it was just a new thing the OS could do if the rest of the thing was actually stable. But they seem to be allergic to doing some actual house cleaning and instead keep bolting things on.
The fact that the explorer can regularly completely freeze up nowadays or flat out crash is actually insane. That should be at the top of the priority list before anything else gets worked on. But instead they decided: let’s add a new keyboard shortcut to open a really laggy copilot chat interface.
*One of two different copilot interfaces. Either the personal copilot or m365 copilot chat…
This was literally the trigger for my very first Linux experience, it’s fucking asinine that something so fundamental to the UX could perform so poorly for such an extended period of time.
I love having to reboot the explorer.exe process in task manager because my taskbar search stops working.
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.