Anyway to not update to 24H2 but still get security updates?

So install that Reg add will fix my issue of not wanting to upgrade to 24H2? As it will brick my OS.(as i understand it.)

Yes my rig is unable to support 24H2, as my Core 2 Quad 9650 3.0Ghz over clocked at 4.1Ghz for over 10 years now on Asus Formula Maximus II motherboard, dual Samsung Evo 830 in Raid 0, 8 Gigs of CAS 9 Latency Ram etc etc... Upgraded to USB 3.0 with Pcie card. M2 drive as well in x16 slot.with Video Asus Rog R9 390.. Which i got last year practically unused for $25. On ebay, nice upgrade!

Built this when i was a Geek, Tradesman now and don't want to learn to build another.

If I am forced to learn anything it will be Linux OS.

Is just fine playing games. when I so chose. Dont want to upgrade my computer, $$$..

"If it ain't broke dont fix it"

I run Plex, Utorrent, Multi Task with 2 monitors and at times play some games at same time. Don't tell me to upgrade this ancient artifact :)

Anyone can post these registry "fixes" but if you have problems, they are nowhere to be found to help you out.

These registry fixes have 2 problems:

1. Microsoft has stated firmly that they will force a feature update on you 3-4 months before your End-of-Life date regardless of your intention to delay stuff. They will ignore your 7 day delay request in their UI and they will ignore any registry delay.

So basically, even when these registry fixes work as intended, you are going to forget the fact that you put a delay months ago and then Microsoft forced a feature update "out of nowhere" at the "worst" time for you. Then of course, you blame Microsoft instead of blaming yourself.

The best practice is don't do anything, don't press the feature "download and install" button and you have a physical reminder to remind you that there is a feature update available for you to download and install in your own time. When you do the registry hacks, then you lose the reminder and you are going to forget that feature update is available and you are not going to do it in your own time and Microsoft is going to force it on you at the worst time.

2. the computerworld.com article specifically stated that the people complaining about a feature update forced on them were precisely the same people doing all these delaying hacks --- which triggered a microsoft bug.

So if these people didn't do the registry hacks, then they wouldn't have triggered the bug and they wouldn't have a feature update forced on them.

You can never prevent a new version of Windows from installing.

There is literally a registry fix posted above your answer that does exactly that.

GWSMO doesn't support 24h2 at the moment.

Thank you!

I just rolled-back from the 24H2 update for a very good reason:

The synchronisation connector GWSMO between Outlook and Googla Apps (email, calendar, contacts) does not work after the 24H2 causing a lot of problems for many users.

Outlook does not restart any more and the connector for a new Outlook profile does not work.

I rolled back last night after nearly two days of hassle and all work again.

I only found one post on this by an IT company having a lot of clients with this issue and as neither Google nor Microsoft make any comments on this there is not other solution than to roll-back!

If you want to roll-back it needs to be done within 10 days after the update!!

/JSN