nt62, are you using 10166? The "Disabled" setting isn't working for me for some reason.
Don't forget to click on apply.
After rebooting, go to the settings app and check the time stamp on when the last update occurred.
If disabled, the time and date will not change unless the user manually checks for updates.
I am using a fresh install of 10166, so it's hard to tell because there are no updates for it right now.
But when you did it, your button actually changed text and color in the Settings app, right? Mine isn't doing that. And it looks like yours has a red message indicating that settings are being managed by the administrator, which mine also is not showing.
Are you running Home, Pro, or Enterprise? And x86 or x64?
Nothing special. x64 - Pro - 10166 - However, I AM using a Microsoft Account -
It shouldn't matter if it's local or MSA, as long as you are a user with Administrative Priviledges.
This is still the 10 Preview, so all installs I would think have Admin rights
unless you're using someone else's setup.
If you can, post a screenshot of your gpedit setting and then a screenshot of your settings app result
I actually posted one in a previous post a few posts back. The Settings app is over top of the Group Policy Editor. Can you tell anything from it? I tried running GPUPDATE /FORCE and restarted the computer, and it made no difference.
Okay, I left the machine by itself, and it is now showing exactly how yours is showing. I have absolutely no idea what (if anything) changed. I've never had a Group Policy take that long to take effect, and I've certainly had no policy not work through reboots.
In any case, thanks for your help! Glad that it works. If anyone has a problem setting it, just let it sit for about 15 minutes, and it will automagically work at some point.
Tutorial has been updated to help.
Please apreciate this as a bit of positive criticism, in the end trying to help the community :
First off, possibly because of your updating the OP, it is not consistent now. I mean, what the Registry appliances do, is not represented by the GroupEditor means. This is related to the Disable, which is not dealt with in the GPEdit outlay at all (but one of the registry entries does).
Next, IMO you must be quite careful for what happens at July 29 and beyond, because Windows 10 Updates can not be prevented in the RTM, if all is right. That is, for under Enterprise and Enterprise still can, they say.
Lastly, and I can't be sure whether you are aware of it, the explicit issue of Windows 10 is thus that it can not prevent fom Auto Updates. This is just MS strategy. And now comes this thread, people looking for means to shut off auto updates. IOW, if all is right, this thread will be obsolete soon hence will provide explicitly wrong information, soon.
And don't ask me how it will look like; maybe GPEdit won't show the possibility but the Registry entry is still respected (with all its current possible values). We can only tell when the RTM is there.
Currently I use other means myself to stop the updates, but for that too we need to wait for the RTM to see whether that is still effective. And if not, I'm usually creative enough for some counterattacks.
Anyway, main reason to post is to let know that while this thread should be about very explicit stopping the updates (for those who don't want that), at this moment it's just a thread like it could exist for Windows 8 etc. But for W10 it's really a big deal. And just saying : The Preview Builds nicely testified how things got worse and worse. Nobody wants that.
Lastly FYI, if you didn't know already :
Home (version) users will receive all the updates, they say. When they stop complaining finally (update now "works fine") the update will be provided to Pro etc. users.
PS: If this is already dealt with somewhere in the forum, I apologize (I did not search). But in that case this thread here is still a kind of "obsolete" .