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.