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

Well this is 100% wrong. It installed over the weekend on my pc.

So I just put that in cmd while running as admin or? Also could you make a command for when I want to remove them when the issues get fixed or if I plan on updating anyway?

Running as admin.

When you want to remove the block, you can either update Manually using ISO file or,

reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v ProductVersion /t REG_SZ /d "Windows 11" /f && reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v TargetReleaseVersion /t REG_DWORD /d 1 /f && reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v TargetReleaseVersionInfo /t REG_SZ /d "23H2" /f

And all it does is:

1. don't press the red stuff for feature update.
2. turn off the purple stuff for preview update.

As the computerworld.com article stated that all you did was introducing the possibility that you might trigger some bug by being cute with trying to bypass it. All the OP heard was blah blah blah, some guy's computer got a feature update with no consent. What he did not hear was that that guy probably did a cute bypass and trigger a bug which forced a feature update on him. Of course, this is the internet so none of these people would admit that their cute bypass triggered a bug which forced an update on them.

And none of the pausing stuff works when your computer is at 3-5 months before the end of life date. Microsoft will simply force an update on your computer regardless of registry edits and group policy edits...

https://www.bleepingcomputer.com/news/microsoft/microsoft-starts-force-upgrading-windows-11-21h2-devices/

Instead of spending hours and hours trying to bypass Microsoft's machinery (which is equivalent to sticking your head in the sand), waiting for Microsoft to find out that xxx driver caused problems to the feature update, waiting for Microsoft to block the computers with that xxx driver, waiting for Microsoft to push a newer driver to your computer so that the feature update can be done successfully...

The best practice has always been open every category in device manager, make a list of all the drivers on your computer, manually update all your drivers (from your computer maker, chipset maker or microsoft update catalog) BEFORE each pending feature update. Actually doing something constructive.

https://answers.microsoft.com/en-us/windows/forum/all/updating-drivers-question/b382099a-02ef-4550-b88a-06d754ee94c5

The Settings app has a control that lets you pause updates ...

Start > Settings > Windows Update > Pause updates

... whereby you can pause updates for up to 5 weeks. However, I don't know whether this pauses all types of updates or only some updates - and I'm too lazy to find out - because in any case, I want a pause that lasts 90 days. I'm sure there's more than one way to do this, and I prefer to use the Group Policy Editor.

(As an aside: I avoid working directly in the Windows registry at all costs.)

You have to be signed in to an Administrator account to use the Group Policy Editor. Open the Group Policy Editor and go to Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage updates offered through Windows Update > Select when Preview Builds and Feature Updates are received

(This manages when they are received.)

Double-click to open 'Select when Preview Builds and Feature Updates are received.' I provided an illustration below. Double-click on the picture to see a larger size image in a new tab.

The text refers to Feature Updates and Quality Updates. That's old terminology that Microsoft no longer uses. You can replace Feature Updates with 'new versions of Windows'. Full disclosure: Microsoft can, at its discretion, decide to include other updates in that category.

If the Policy is 'Not Configured' then 'Enable' it and set your chosen delay. You can see that I chose 90 days.

I previously delayed for 120 days. However, I no longer feel I need to wait that long, because Microsoft has gotten better at identifying problems with updates and either fixing them or blocking incompatible portions from going out to affected configurations. On that other hand, I'm not that confident in Microsoft, so I dropped down to 90 days.

I do this because I don't feel I need to have the newest thing as soon as it comes out. That's my opinion, anyway, and it's quite different from the FOMO crowd who get all uppity if they're not first on their block. I can wait. That's one of the ways I avoid computer problems.

Ho do I set it to delay? And is that only for feature updates like 24H2 or also for any other update?