Group policy does not stop it from eventually rebooting. Though it will stop the "rebooting right after applying an update" horror show.

With Group Policy: if you are logged in, Windows will pop a modal dialog in your face and you can preempt it there, but just leaving an application running and being AFK will not prevent reboot if Windows has decided it has waited long enough. The amount of time I can ignore the "restart" request in Windows Updates varies from days to weeks for me.

I hate the behavior with a passion, but I can see why Microsoft wants to force reboots eventually. Having un-updated Windows is not good for 90% of the people out there.

Honestly speaking, Windows 10 is as far from the spirit of the "I'm a PC" and "Windows 7 was my idea" ad campaigns as you can get. Now it's just "You will bend over and take what we give you, for the greater good"

If you want full control of your OS, you need to switch to a BSD or Linux, with appropriate expectations about the applications you will or won't find there.

Edit: fix grammar/punctuation a bit

That is not true. There is a group policy to disable updates. I know, because I have to run updates by hand on my work computer, otherwise I stay months behind on security patches.

Stop spreading lies. It does work. (I also have hot had ads in Windows on all Windows machines I own. But this is a Microsoft product, which always raises these long list of myths.)

First, I said rebooting, not disabling updates.

Instead of name-calling, maybe post the group policy here that allows you to never reboot after updating.

Updates requiring reboot are not applied unless you reboot... so don't apply updates requiring reboot? It's useless to install them if you refuse to reboot. You can't have it both ways.

So the solution, as I said, is to not install these updates. (Or reboot, but you say you don't want reboots.)