Windows 11 General Discussion

[Onasi]

Hey, this actually took less than the 22H2 did last time. Probably won’t jump on it JUST yet, but good to have it available.

 

[lexluthermiester]

View attachment 372856
Hey, this actually took less than the 22H2 did last time. Probably won’t jump on it JUST yet, but good to have it available.

Give it 3 or 4 months then grab it, lets say March. They're still working out the kinks..

 

[RUSerious]

Give it 3 or 4 months then grab it, lets say March. They're still working out the kinks..

Good advice. There have been some annoyances pop up that I'd didn't notice when I first installed it - and others have had it worse.

 

[lexluthermiester]

Good advice. There have been some annoyances pop up that I'd didn't notice when I first installed it - and others have had it worse.

As stated elsewhere, a fresh install does not have most or all of the issues being experienced. So if you're willing to fresh install you're golden.

 

[Onasi]

@lexluthermiester
Which is rather interesting, by the by, since the update re-installs the OS anyway. Wonder what’s conflicting that’s causing the issues. MS probably won’t tell us, but would be interesting to know. Would be funny if it’s a dreaded comeback of the XP “.dll hell” of sorts and something gets stuck wrongly in the SxS system on an update.

 

[lexluthermiester]

Wonder what’s conflicting that’s causing the issues.

There's a catch...

since the update re-installs the OS anyway.

...this is only partly true. Existing driver assets, user apps & files, user settings are preserved, even much of the OS assets are kept unaltered. As some of the ways the kernel and base services run have changed, dramatically in a few ways(though invisible to the user), some of those settings have to be just right and they're not. This is where microsoft is trying to appeal to those of us complaining about our configs and setting being changed after updates plays into it all.

In all fairness to microsoft, they're trying to get just right something that is VERY complicated. This is why you don't see me complaining too much about this round of update problems and recommending a fresh install.

MS probably won’t tell us, but would be interesting to know.

They kinda have but it's not "public" per-se.

Would be funny if it’s a dreaded comeback of the XP “.dll hell” of sorts and something gets stuck wrongly in the SxS system on an update.

That particular problem can't and won't happen again.

 

[Onasi]

Decided to actually YOLO it and see what happens. If only to see what MS decides to do on the update other than the update itself. So far so good. Of course, they force installed Teams and Bing Search alongside the update (thanks MS!) which were immediately terminated. Also curious how they seemingly totally reset the Services list - the Print Spooler is back, even though it was disabled. So that seemingly doesn’t carry over. Didn’t reset anything in my Settings or CP, so that’s good. Did return the Search Web results because they reset THAT group policy, which is annoying. At least they didn’t try to reset the default browser to Edge, thankfully. No CoPilot nonsense. Immediately searched for and applied the latest KB, so that’s nice, apparently lots of bug fixes in that. Overall, very smooth update process and surprisingly quick. We’ll see how it holds up.

 

[Onasi]

Well, after a couple days of using it without any REAL issues 24H2 is pretty good. I am a tad butthurt about some stuff moving around in settings and the fact that they STILL haven't modernized some things that really should be new by this point, like the new Task Manager still just being a ModernUI skin on top of the old runtime. But the new OS is noticeably snappier than 23H2. This is not placebo or anything, there are less hang ups and apps don't get stuck on processing as much. Obviously, there is a tiny delay on fresh opening of different windows and tools, but it's CONSISTENT now and not random as hell. It uses about the same amount of RAM as it used to, though it SEEMS like it's more aggressive about caching things into said RAM, so it might LOOK like it uses more, but I do not see that as a downside - using RAM when availiable isn't a sin, like some obsessive tweakers think.