Support NeoGAF

[Nitty_Grimes]

Honestly, I still don't understand why they've not released a consumer Windows OS WITHOUT all that stupid bloat that is caused from backwards compatibility.

How they going to sell all your data to their preferred partners if they did that?

 

[Trilobit]

Hmm... interesting behaviour.

*boots up my gaming console*

 

[Brigandier]

I haven't liked Windows since W7.. shame there's no competition.

 

[manfestival]

Oh this explains what was happening to my system the other day and why I was so confused about it just sitting there and not updating on my laptop.

 

[Lucifers Beard]

Lol I think I may have made a mistake updating my PC this morning!

 

[nemiroff]

Lol I think I may have made a mistake updating my PC this morning!

Why, did something break? I mean, most people, including me, most likely won't experience issues. As almost always. Been running this update for a week now without any indication of problems.

Hmm... interesting behaviour.

*boots up my gaming console*

Hmm... that's a random and bland soapbox.

*casually powers on my PC*

 

[Bojji]

Lol I think I may have made a mistake updating my PC this morning!

I had updates turned on but this one didn't install (it's not even showing when searching manually). I just turned off updates for 5 weeks, lol.

W11 update team needs to be fired.

 

[Fake]

If they stop forcing updates all their problem are solved.

They want consumers to beta testing and rush update, not to mention the test team is no more. The perfect recipe for disasters like that.

 

[Trilobit]

Hmm... that's a random and bland soapbox.

*casually powers on my PC*

 

[Boglin]

Why, did something break? I mean, most people, including me, most likely won't experience issues. As almost always. Been running this update for a week now without any indication of problems.

For me it was a mistake, but it wasn't the worst thing in the world. The update caused my computer to fail to boot and to fix it I had to roll back the update from the recovery menu at boot, run safe mode, and then reinstall a bunch of drivers.

I pushed back the update 5 weeks now, so hopefully it's fixed by then

 

[StereoVsn]

Honestly, I still don't understand why they've not released a consumer Windows OS WITHOUT all that stupid bloat that is caused from backwards compatibility.

They have that on ARM side basically.

 

[nemiroff]

Now, that is much better

For me it was a mistake, but it wasn't the worst thing in the world. The update caused my computer to fail to boot and to fix it I had to roll back the driver from the recovery menu at boot, run safe mode, and then reinstall a bunch of drivers.

I pushed back the update 5 weeks now, so hopefully it's fixed by then

Damn, that sucks.

 

[mcmanic]

2024-12 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5048667)
Successfully installed on ‎12/‎12/‎2024

been fine here.

 

[rodrigolfp]

to fix it I had to roll back the driver

What driver??

 

[Boglin]

What driver??

Sorry, I meant update. It was listed as "quality update" in the recovery menu. Trying to roll back the "feature update" resulted in it failing.

 

[intheinbetween]

Dozen and more users are reaching out to me with complaints of Windows 11 KB5048667 installation issues.

Dozen and more

No issues in here so far, another thread for doom and gloom

 

[Valonquar]

I manage roughly 4000 machines. Of those about 15% are still on W10 (can't\won't be upgraded) and the rest are on W11. The most common issue I've seen with the 24H2 update is the common thing I see with EVERY feature update: generic MS drivers fucking up things spectacularly by the update replacing working drivers with "new" incorrect ones. In nearly all cases, downloading, packaging, and pushing out newer driver packages from the hardware vendors has fixed things, or in smaller cases, just doing a driver rollback via Device Manager. People immediately slam MS on this shit all the time, but I'd still rather have these minor issues every now and then, rather than what my Mac counterpart has to deal with every major OS update with the entire configuration going out the window often taking months to correct.

 

[nemiroff]

I manage roughly 4000 machines. Of those about 15% are still on W10 (can't\won't be upgraded) and the rest are on W11. The most common issue I've seen with the 24H2 update is the common thing I see with EVERY feature update: generic MS drivers fucking up things spectacularly by the update replacing working drivers with "new" incorrect ones. In nearly all cases, downloading, packaging, and pushing out newer driver packages from the hardware vendors has fixed things, or in smaller cases, just doing a driver rollback via Device Manager. People immediately slam MS on this shit all the time, but I'd still rather have these minor issues every now and then, rather than what my Mac counterpart has to deal with every major OS update with the entire configuration going out the window often taking months to correct.

Yeah, I completely agree.

Anyway, speaking of enterprise workstations.. Considering the plethora of shit (background processes) running on corporate computers, I'm just amazed that any of them are working at all.

And funnily, within a company of ~10,000 employees, I'm among the few trusted ones with administrative rights, granting me fantastic privileges like the ability to delete desktop icons!

 

[Complistic]

Ah so this is why my games are running like ass now

 

[Magic Carpet]

I manage roughly 4000 machines. Of those about 15% are still on W10 (can't\won't be upgraded) and the rest are on W11. The most common issue I've seen with the 24H2 update is the common thing I see with EVERY feature update: generic MS drivers fucking up things spectacularly by the update replacing working drivers with "new" incorrect ones. In nearly all cases, downloading, packaging, and pushing out newer driver packages from the hardware vendors has fixed things, or in smaller cases, just doing a driver rollback via Device Manager. People immediately slam MS on this shit all the time, but I'd still rather have these minor issues every now and then, rather than what my Mac counterpart has to deal with every major OS update with the entire configuration going out the window often taking months to correct.

For the recent Apple iPhone updates I noticed for the first time (I don't know when they started doing it) Apple now has a message in the battery health section saying the update is still doing stuff in the background, this way users can expect poor battery life after the update.
Before users would always complain about poor battery life after an update because people did not know these background stuff was going on.

Windows needs these same messages. As it is now it's best for Windows users to hold off updating as long as possible.

 

[Valonquar]

To be fair there has been a pretty reasonable mantra of never allowing a feature update out to prod for about a month (or longer) from initial drop.

 

[Celcius]

After a little over a month of 24H2 I finally encountered the black screen bug. I turn on my computer and it starts booting up, I see the bios splash screen, then it starts loading windows. Once windows loads I just have a black screen, no video signal. I reboot and then everything is fine. I’m looking forward to that January update…

Ah so this is why my games are running like ass now

The November update for 24H2 slightly lowered my performance in 3d applications such as games.