24H2 blocked, still installs?!?!?!?!?! GPO not working.

Mitch said:

Can I take it that only the 23H2 Cumulative Updates would be installed and that I would need to select "Download & Install " the 24H2 button specifically for that to happen? I want to stay on 23H2 for a few more months and don't want 24H2 to be downloaded with the 23H2 Updates next week. Thanks Mitch.

Click to expand...

Yes. With 'Get the latest updates....' turned off it is quite safe to check for updates. 24H2 will not install, only if you deliberately click its 'Download & install' button.

Hi Bree. Thanks for clearing that up. I think we'll wait a few months until everything has settled down before 24H2. The printer/scanner usb issue with 24H2 could affect us but we can't be sure so best to wait. Thanks again.

Bree said:

Yes. With 'Get the latest updates....' turned off it is quite safe to check for updates. 24H2 will not install, only if you deliberately click its 'Download & install' button.

View attachment 118592

Click to expand...

If I ever saw that option to click on the "X", I would have done that for 24H2. I have reset the Windows Update a few times just to make sure it is nothing messed up there that caused the auto-install of 24H2.

Mitch said:

Hi Bree. Thanks for clearing that up. I think we'll wait a few months until everything has settled down before 24H2. The printer/scanner usb issue with 24H2 could affect us but we can't be sure so best to wait. Thanks again.

Click to expand...

we had a few machines at my work where the blocking didn't work, had to do the gpupdate /force to make sure it got all the policies.

andrew129260 said:

we had a few machines at my work where the blocking didn't work, had to do the gpupdate /force to make sure it got all the policies.

Click to expand...

I think you were spying on me.

I just thought about using gpupdate /force to see if that made a difference. I know gpedit/regedit changes most apply after a restart, but after dealing with Windows servers all the time, I do use gpupdate /force to make sure those changes do get applied.

Nipdawg said:

I think you were spying on me.

Click to expand...

nope, just been in the IT trenches for about a decade + now. Probably same as you.

Still have a lot to learn but I have been where you were before, and long before lol

andrew129260 said:

nope, just been in the IT trenches for about a decade + now.

Still have a lot to learn but I have been where you were before, and long before lol

Click to expand...

I started back in 1986 in this IT world/work.

Nipdawg said:

I started back in 1986 in this IT world/work.

Click to expand...

then you likely know more than me

Gotta love group policy........when it works :)

andrew129260 said:

then you likely know more than me

Gotta love group policy........when it works :)

Click to expand...

This is why UNIX Security was so darn good back then. Once you set up a group with correct permissions, it was set. Then came along Microsoft NTFS/GPO infiltration.

It will be interesting to see if others who have set a target version in GPO has the same thing happen to them or if this is some kind of fluke in your case.
Possibly your group policy has somehow gotten corrupted in the registry. If that is the case, Steve Gibson's method won't work either. You might try resetting GPO settings back to default. Restart and then set your policies up again. Reset All Local Group Policy Settings to Default in Windows 11

For me, group policy settings have always been honored in the past. It's one of the reasons I've always bought PRO, so I could have more control. But I'll say that a lot of what I thought I knew and understood to be true both about Windows and MS always honoring a user's settings has been thrown out the window when it comes to Windows 11 in general, not specifically 24H2. But 24H2 has really been the icing on the cake when it comes to weird and unexpected things happening.

I'm the resident pessimist here. Others have disagreed with me, but I've said all along that MS can and will over-ride any policy change or regedit change we've made, if they so choose to. They can do anything they damn well please. It's my belief that just because they've honored an end user's settings or work-arounds in the past may no longer be 100% guaranteed. That goes for regedits and GPO too. I also believe having Pro as a consumer user may be a false elusion because MS knows when it is not being used in a corporate machine. Despite all our efforts, whether we use Home or Pro, If they want us to have something, we're going to get it. On the flip side, they can keep us from having what they don't want us to have....and they can do either on a machine to machine basis.

We were offered 24H2 4 days ago and have run Check For Updates several times and every time it shows 24H2 available but doesn't begin downloading which is what we want and as @Bree confirmed. None of the feature updates we have done before have downloaded without deliberately selecting download. The printer issue is the main thing we are looking to be fixed.

Mitch said:

The printer issue is the main thing we are looking to be fixed.

Click to expand...

yeah......been there......who knew that microsoft would make printers even more frustrating?

glasskuter said:

Despite all our efforts, whether we use Home or Pro, If they want us to have something, we're going to get it.

Click to expand...

I don't mind getting all the cumulative updates and other updates, but I do like to do so at a time on my choosing. So for all my Pro machines I do have one group policy enabled. It's 'Configure Automatic Updates' and it's set for '2: Notify for download and auto install'.

@andrew129260 . I know. I've tried to find our if our Canon Pixma printer/scanner is affected by 24H2. We use a USB cable to connect but can't get a definitive answer.

glasskuter said:

I'm the resident pessimist here. Others have disagreed with me, but I've said all along that MS can and will over-ride any policy change or regedit change we've made, if they so choose to. They can do anything they damn well please.

Click to expand...

I'm not an IP/EULA attorney but Section 6. of the Windows EULA appears to give Microsoft a wide berth when changing and updating the OS.

6. Updates. The software periodically checks for system and app updates, and downloads and installs them for you. You may obtain updates only from Microsoft or authorized sources, and Microsoft may need to update your system to provide you with those updates. By accepting this agreement or using the software, you agree to receive these types of automatic updates without any additional notice.

Click to expand...

NB: The underlines are mine.

My experience is just like @Bree.

I got offered the update a few days ago. I can still run check for updates and it gets things that are available, but 24H2 is a separate download and install button. I've done nothing whatsoever to prevent it from installing.

Mitch said:

@andrew129260 . I know. I've tried to find our if our Canon Pixma printer/scanner is affected by 24H2. We use a USB cable to connect but can't get a definitive answer.

Click to expand...

One of the Canon suggestions is to use a USB cable, but even when I tried USB, the scanner was not detected. As I listed in this post, network or USB connection the scanner is not detected or recognized.

Marcus Vinicus said:

I'm not an IP/EULA attorney but Section 6. of the Windows EULA appears to give Microsoft a wide berth when changing and updating the OS.



NB: The underlines are mine.

Click to expand...

What the EULA states versus what Microsoft does are two different things.

When something does not work in 24H2 that previous worked flawlessly in 23H2, that is when I prefer to not to upgrade. Anyone would feel the same. For Microsoft keep forcing the 24H2 update is stupid and wastes a lot of users time.

Nipdawg said:

What the EULA states versus what Microsoft does are two different things.

When something does not work in 24H2 that previous worked flawlessly in 23H2, that is when I prefer to not to upgrade. Anyone would feel the same. For Microsoft keep forcing the 24H2 update is stupid and wastes a lot of users time.

Click to expand...

That is why I us this on my second PC

windowsxlite

Nipdawg said:

What the EULA states versus what Microsoft does are two different things.

When something does not work in 24H2 that previous worked flawlessly in 23H2, that is when I prefer to not to upgrade. Anyone would feel the same. For Microsoft keep forcing the 24H2 update is stupid and wastes a lot of users time.

Click to expand...

Take it up with the MS then. I must say I cannot recall MS ever forcing a new major update/new version onto Windows in any of my computers via Windows Update.
Disclaimer: I'm a Microsoft agnostic, I neither like nor dislike them, I just use their software.