Rollback, Delay Update logistics

Windows 11 Home, Version 24H2, Installed on 5/11/2025, OS build 26100.4061
Experience Windows Feature Experience Pack 1000.26100.84.0
--
Been on Win11 24H2 for about 3 weeks. I previously had held off doing 24H2 update while offered as optional. But then back on May 11 it popped up with no functional option other than to let it install. A couple of annoyances with it, one is in Settings->Privacy & Security->Location every item is grayed out, cannot turn location on. Not a huge deal I can always quickly update area code at any site. But that's not the reason for my post. What I'm really curious about is what actually plays out even if I had rolled back the 24H2 Update.
I've read about ways to set most all windows updates OFF. But even if I had rolled the update back in time, how long before Windows would again force me to install it. Or in other words how long can one safely and functionally stop all updates without other side effects.
Just curious what paths the experts take on this?

RH247a said:

Or in other words how long can one safely and functionally stop all updates without other side effects.

Click to expand...

Probably only good until around November when 25H2 becomes available. On that, I am not 100% certain.

TargetReleaseVersion is permanent (if applied correctly).

It doesn't matter how many years will pass, if you have locked in the currently installed version as your target.

• TargetReleaseVersion cannot force Windows Update to downgrade Windows (going backwards isn't supported).
• TargetReleaseVersion can be used to force Windows Update to upgrade to a new matching version. Some users want to trigger the upgrade as soon as MS makes it available to install.
• Otherwise, TargetReleaseVersion can keep you on the existing Windows release.
• Not specifying TargetReleaseVersion allows Windows Update to move ahead any time 60 days or later (usually many months later) after your current Windows has reached the end of the service for general public users.
• Specifying TargetReleaseVersion does not interfere with Monthly Updates (until there are no more updates because your Windows has reached end of service), and it will not block future Defender updates.

Kudos for those replies, that sounds like something I'd like. Makes me wish I'd known that when I was on 23H2 which I liked the best. Thanks guys for the info packed replies. I surmise I'm one the few now days to have never known about the target release premise. However I still have the 23H2 ISO, wondering if any reason I could not do a schneegans answer file to clean install the 23H2 with no internet and then do a Target Version Lock before I enable the internet. But of course I need to first educate myself on the Target Version Lock at the page you gave. And sorry for the late reply I injured my hand this morning sharpening a mower blade, had to go get stiches. Just now it took me forever to type (peck) this reply out. But thanks again.
EDIT Add, Well I'll keep reading on the Tutorial. If it sounds feasible for my purposes I may purchase one of those OEM Win11 Pro Keys just to try this since I read it doesn't work on Home edition.

You don't need to immediately do TargetReleaseVersion on install (although it could be automated). In reality, it takes a while before Windows Update starts the process because it has to run a compatibility check, and declare your PC as eligible for 24H2.

This compatibility check runs overnight, so you have enough time after a clean install to get to it.

But if you want to Schneegan it, scroll down to "Run custom scripts" / System scripts / 3. Run as .reg file

Copy this text:

garlin said:

You don't need to immediately do TargetReleaseVersion on install (although it could be automated). In reality, it takes a while before Windows Update starts the process because it has to run a compatibility check, and declare your PC as eligible for 24H2.

This compatibility check runs overnight, so you have enough time after a clean install to get to it.

But if you want to Schneegan it, scroll down to "Run custom scripts" / System scripts / 3. Run as .reg file

Copy this text:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"ProductVersion"="Windows 11"
"TargetReleaseVersion"=dword:00000001
"TargetReleaseVersionInfo"="23H2"

Click to expand...

Thank you much for that. I will check that out.

You can tell if it worked (after the install), by querying the registry as Administrator:

reg query HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate