Windows 10: How to Prevent automatic restart in Windows 10 Anniversary Update?

Is this what you all want.....

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]"NoAutoRebbotWithLoggedOnUsers"=dword:00000001

 

This does not work on me.

 

Are you SURE? Is "Rebbot" a typo? Have you tested this?

 

It does not matter rebbot or reboot, this policy setting does not work, did not work either year before it was posted by SonicBlue. *Wink
Windows just ignores all policy settings, at least for me on PRO.

 

No I have not and I am sorry for not testing it. I actually saw it on the net a few days before I read this post. Actually if my pc ever rebooted on me it would get formatted then a new install. The registry can be messed with so easily by updates too.

 

Is this still working for everyone? It now does not update the standard windows interface when the registry keys are changed, i.e. though changing things in the interface does indeed update those keys, when you change those keys, the interface reverts to 8AM to 5PM.

 

What "this"? Script? It still working for me. What windows version do you use? Some insider crap?

 

I wasn't more specific, because I meant the idea. Script, program, whatever you use to set the registry key. And I'm on the standard track, not insider. 1607/14393.576.

So you're saying that if you set the registry keys, it's still reflected in the user interface?

 

Sure it's reflected. And I have the same build as yours.

 

May be it's some kind of user permission problem? Don't you accidentally changed permissions for registry keys, that user 'SYSTEM' can not access it anymore?

 

I'm doing it programmatically through a c# program; I can see the key change, but it's not reflected in the Windows UI. In fact the UI changes to the default (8-5) Queen the keys are altered, and the values that I'm using are well within the 12 hour limit.

 

Sorry I can not help you. Look carefully for everything, check if provided in the thread batch file working for you, if it works, then you do something wrong, if it's not working also, then there is some windows corruption on base level or security permissions.

 

The only problem is that it consistently doesn't work, no matter how I do it, across four different machines, so I can be pretty sure it's not a machine issue. But thanks; I just wanted to ask someone else to see if they were having the same problem.

 

Is it Enterprise or PRO? Does it have local or MS account?

 

All of them are Home, and using the same MS account.