Forced W11 upgrade to 24H2 over the past week

Posted by dekkar@reddit | sysadmin | View on Reddit | 21 comments

Hi, I've had about 50 machines (I'm guessing the rest will follow) upgrade from 23H2 to 24H2 even though we haven't approved it in WSUS or Intune (for machines that are enrolled). Our WSUS policies are set to not look at Windows Update for anything, so not sure how this happened.

I cant seem to find any announcement from MS that they are forcing 24H2, but it looks like that is what they are doing.

Is anyone else seeing this?

[-]

Practical-Alarm1763@reddit

Yeah, I set the deferral period to 365 days to fix it. I don't know if it's a bug 🤷‍♀️

When ready to go to 24H2, set it back to 0 or whatever you were using.

Since half the fleet was already on 24H2 I fixed all the problems with webcam drivers, and teams on 24H2 using a few config profiles and scripts to edit some registry values. Then I just to ut my hands up and upgraded all to 24H2.

[-]

MisterFives@reddit

We've been having issues like crazy with 24H2, especially with teams (webcam issues, slowdowns when sharing screen/apps), what were some of your fixes?

[-]

hazsmix@reddit

For performance, uninstalling Dell Trusted Device app and a restart. Apparently there is a newer version that it's fixed but I never found it so the advice is just remove. Don't event know what it's for.

For webcam, updating the Intel AI Driver somehow fixes it (symptoms are webcam very "laggy" or crashing our entirely).

Just a bit of a shit show as users can't do these themselves easily.

[-]

hazsmix@reddit

Yeah 24H2 is definitely a bit cooked. I'm having issues with webcams, performance in general too. We're a Dell shop. We're also having a weird issue where the screen rotation "flips" on undocking/sleep. This is on regular laptops that are not convertible at all. Have to go into display settings and unflip it and lock rotation. Have you been running into this too?

[-]

BeardedThunderNC@reddit

We've seen this on several of our Dells. Some systems had rotation lock already enabled.

[-]

fuzzusmaximus@reddit

Do you know what update installs 24H2? We only have a couple of machines with W11 so far and they are either 22 or 23H2.

[-]

bit0n@reddit

Do I remember that one of the big updates was accidentally tagged as a security update so got pushed out? Sever 2025 or something? Does WSUS show 24H2 as a feature pack in the logs still?

[-]

joeyyung@reddit

just wondering, is there any reason why you are not using LTSC in a corp environment. It has a 5 years lifespan and you don't have to worry about this stuff happening and have to upgrade every year. It's more stable and less issues too.

[-]

dekkar@reddit (OP)

We used to when it was first released and it was amazing. There was some reason we retired it. This would have been almost a decade ago, but something really stung us with it, so we migrated away from it. Office 365? Cant remember.

[-]

joeyyung@reddit

We mainly use Office LTSC with the exception of a few users using O365 (which i know it has limited support). We have yet needed support for Office. OS wise, we get tech support from Microsoft.

[-]

ddaw735@reddit

Well Officially Office 365 apps aren't supported and they can't use the windows store.

[-]

joeyyung@reddit

We mainly use Office LTSC with the exception of a few users using O365 (which i know it has limited support). We actually block users from installing apps from the Store, it's good for us that LTSC doesn't come default with the Store. We push apps, like the new Teams, when we have to.

[-]

Sajem@reddit

Because general use is not the intended purpose for LTSC. No MS support if you need it. No support of O365 apps.

You don't need to upgrade Win 11 every year either, you've got a two-year life cycle with Pro and 3 years for Enterprise.

[-]

Mizerka@reddit

Wudo disabled?

[-]

CPAtech@reddit

No, if you have it blocked by whatever your method of choice is it won't be forced.

[-]

dekkar@reddit (OP)

We used to when it was first released, but there was some reason we retired it. This would have been almost a decade ago, but something really stung us with it, so we migrated away from it.

[-]

We had this GP set for 180 days, I think it may have been a CIS benchmark. 🤷‍♂️

Welp, that time has passed.

Using 'Select Target Feature Update Version' GP now to keep people on 23H2.