When we’ll be done with our testing, we’ll let those updates flow in, or perhaps we never will, it all depends on what we see fit at that time.
In this article, I’ll walk you through the steps to disable Adobe Reader XI updates with Group Policy.
In my example, it is an empty GPO, but there’s no reason why you can’t add this to an existing GPO.
If you open now the Adobe Reader application and you click on Help menu, you will see those updates are available.The registry entry is named b Updater and is a DWORD value. (Note: This DWORD value does not exist by default and either has to be created manually or by some other automated method like Group Policy.) Here’s what it looks like in the Registry if you create the entries manually: You could set this manually, but there’s actually a much easier way to do this in Group Policy.First off you’ll need a Group Policy Object (GPO) that applies to your computers that need to have the updater disabled.Here’s how to disable the Reader update checks so that your end users don’t see messages like this: This tutorial is intended for systems administrators that are using some kind of systems management product for updating 3rd party software like SCCM, Landesk, etc.Many of the security flaws in 3rd party software can lead to malware infections and/or compromised computers.: Of course there are many other methods of pushing registry changes to workstations.In this article I will show you an easy way to disable automatic Adobe Reader XI updates from running per users requests.So how do we block Adobe updates from being installed by our end users?A common and very useful way of doing that in a domain environment is using Group Policy.This tutorial applies to Adobe Reader X (32-bit) running on a x86/32-bit versions and x64/64-bit versions of Windows.Disabling the Adobe Reader X update notifications is actually pretty easy.