[Tuturial] Bloquear actualizações Windows 10

[Jorge-Vieira]

How to block Windows 10 upgrades on your business network (and at home, too)
Microsoft's aggressive upgrade campaign for Windows 10 rubs some people the wrong way. Here's how to say no to the new version in 30 seconds or less, without installing third-party software.


<figure class="image image-full-width shortcode-image">http://zdnet3.cbsistatic.com/hub/i/r/2016/01/07/d60c1443-5a02-4c13-b0c2-58dea10e1b5f/resize/770xauto/e0fa11112f7573fe25a20bfb55748b78/stop-windows-10-for-business.gif</figure>Microsoft wants you to upgrade to Windows 10. They really, really, really want you to upgrade to Windows 10.


We are almost halfway through the one-year, free, no-strings-attached upgrade offer that Microsoft has made available for its customers running Windows 7 and Windows 8.1, and the offers are getting more insistent.
Personally, I think Microsoft has done a good job with Windows 10 and I recommend the upgrade for consumers. It actually is significantly more secure than Windows 7, thanks to features like Secure Boot, device encryption, and built-in antivirus software, not to mention dozens of architectural changes. Windows 10 also solves most of the (justified) complaints people had with the Windows 8.x Start screen.
But some people have legitimate reasons to avoid the upgrade and continue using a previous, supported version of Windows. For them, the continual upgrade prompts are a nuisance.
<figure class="image image-original shortcode-image">http://zdnet4.cbsistatic.com/hub/i/2016/01/07/4924f2dc-8aad-425e-a5d7-5e60cbd70685/c0af683bbc7420c1b66c49b3d50e2040/windows10-upgrade-ad.png</figure>And on some systems, you'll find Windows 10 waiting for you in Windows Update. That's a tremendous convenience if you want the upgrade, but annoying otherwise. (No, it won't install automatically, but it might start the installation process.)
<figure class="image image-original shortcode-image">http://zdnet3.cbsistatic.com/hub/i/2016/01/07/21b10354-8f54-4abd-bb6e-d3e3a29c0c10/a336571e674ab4e50c1405eaf8d84697/win10-upgrade-via-wu.png</figure>
I'd be very happy if Microsoft found a less annoying way to push this upgrade. Even something as simple as a "Remind me again in 30 days" button would be an improvement over the current prompts.
But until they do, here's how you make those prompts go away. It's a 30-second process, involving two simple registry edits. It doesn't involve any untrusted third-party software, which most security experts recommend avoiding. If you're an IT pro or consultant managing PCs at a small business, you can even automate the process, as I explain in this post.
Note that none of this applies to Microsoft's enterprise customers. If your business is running Windows 7 or 8.1 Enterprise, the upgrade offers and the accompanying Get Windows 10 (GWX) icon don't exist. The same is true on Windows 7 Professional or 8.1 Pro machines that are joined to a domain.
<section class="sharethrough-top"> </section>For businesses that aren't joined to a Windows domain, or for home users who aren't ready to upgrade, here are the two changes you need to make.
(Note: Editing the registry is not for amateurs. If you're not comfortable making direct registry edits, you shouldn't open Regedit. At the end of this post, I've included links to .reg files that you can use instead.)
First step: Disable automatic upgrades through Windows Update. To accomplish this task, you need to navigate to the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\
WindowsUpdate\OSUpgrade
Find the AllowOSUpgrade value and change it from 1 to 0. (If the key doesn't exist, you'll need to create it as a DWORD key. If that sentence makes no sense, you probably shouldn't be using Regedit.)
Here's what it looks like.
<figure class="image image-original shortcode-image">http://zdnet2.cbsistatic.com/hub/i/2016/01/07/05542a8e-1482-42c0-b8ee-161554347f25/3ac814811731248bd42c46f2e93e316f/regedit-allow-os-upgrade.jpg</figure>Second step: Make the GWX icon, with its nagging notifications, vanish from the taskbar. To do that, you need to create the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Win dows\GWX
Then create a DWORD value called DisableGWX and set it to 1, like so:
<figure class="image image-original shortcode-image">http://zdnet2.cbsistatic.com/hub/i/2016/01/07/42307f69-059c-413d-8787-a0ba3466c70c/559b0ede827cdf11d496575fe07c4f5e/regedit-disable-gwx.jpg</figure>Restart your computer and the GWX icon should be gone. I've tested this procedure on multiple installations of Windows 7 and Windows 8.1 with no problems.
You can automate the process by saving the necessary registry changes to files that you execute by clicking and running from an account with administrator rights.
Here's the first file, which I saved as DisallowOSUpgrades.reg:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\WindowsUpdate\OSUpgrade]
"AllowOSUpgrade"=dword:00000000
"ReservationsAllowed"=dword:00000000
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\WindowsUpdate\OSUpgrade\State]
That file includes some additional tweaks that probably aren't required but might be useful.
The second file is DisableGWX.reg:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Win dows\GWX]
"DisableGWX"=dword:00000001
Both files are available from this link (http://1drv.ms/1ORNHvw). They're plain text files, so you can inspect them before running. Download the two files and run each one from an account that is signed in with administrative rights.
If you encounter any issues, feel free to send details to me using this email address: gwx@realworldwindows.com. I can't guarantee a response, but I promise to look at all reports.



Noticia:
http://www.zdnet.com/article/how-to-block-windows-10-upgrades-on-your-business-network-and-at-home-too/

[Jorge-Vieira]

Banishing 'Get Windows 10' nagware isn't as easy as you thinkhttp://images.techhive.com/images/article/2016/01/1200px-emblem_nag-100637270-primary.idge.jpg <figure itemprop="image" itemscope="" itemtype="http://schema.org/ImageObject" class="hero-img"><figcaption> </figcaption> </figure> <section class="deck"> In spite of what you've read, dodging Microsoft's 'Get Windows X' campaign takes more than two registry changes

If you're running Windows 7 or 8.1 on a computer that isn't attached to a domain, you're no doubt familiar with the "Get Windows 10" ads that try to convince you -- sometimes subtly, sometimes forcefully -- to install Windows 10. Microsoft's intrusive campaign has drawn much well-deserved ire among Windows customers. I think it represents a new low in Microsoft marketing -- right down there in the Scroogled end (http://www.infoworld.com/article/2613486/internet-privacy/microsoft-is-attacking-gmail-for-tactics-it-uses-itself.html) of the gene pool.
<figure class="well-img"> http://core4.staticworld.net/images/article/2015/08/thinkstockphotos-186993441-100609670-carousel.idge.jpg (http://www.infoworld.com/article/3006555/microsoft-windows/windows-10-vs-os-x-which-gives-sys-admin-more-control.html) </figure> Windows 10 vs. OS X: Which gives sys admins more control? (http://www.infoworld.com/article/3006555/microsoft-windows/windows-10-vs-os-x-which-gives-sys-admin-more-control.html)
Microsoft is adopting Apple's approach to PC management, while also keeping the familiar Configuration
Read Now (http://www.infoworld.com/article/3006555/microsoft-windows/windows-10-vs-os-x-which-gives-sys-admin-more-control.html)

Back in August, Microsoft posted KB 3080351 (https://support.microsoft.com/en-us/kb/3080351), a discussion of new Group Policy settings and two obscure registry entries -- DisableOSUpgrade and ReservationsAllowed -- that, taken together, are supposed to "prevent Windows 7, Windows 7 for Embedded Systems, Windows 8.1, and Windows Embedded 8.1 Pro clients from upgrading" to Windows 10.
<aside class="fakesidebar">[ Your one-stop shop for Microsoft knowledge: Everything you need to know about Windows 10 (http://www.infoworld.com/resources/77753/microsoft-windows/everything-you-need-to-know-about-windows-10#tk.ifw-infsb), in a handy PDF. Download it today! | Survive and thrive with the new OS: The ultimate Windows 10 survivor kit (http://www.infoworld.com/resources/85854/microsoft-windows/the-ultimate-windows-10-survivor-kit#tk.ifw-infsb). | Stay up on key Microsoft technologies with the Windows newsletter (http://www.infoworld.com/newsletters/signup.html#tk.ifw-infsb). ]</aside>Yesterday, my old friend and erstwhile co-author Ed Bott ran an article on ZDNet (http://www.zdnet.com/article/how-to-block-windows-10-upgrades-on-your-business-network-and-at-home-too/#ftag=RSSbaffb68) that explains how to change two different registry entries -- AllowOSUpgrade and DisableGWX -- to "block Windows 10 upgrades on your business network (and at home, too)."


Both approaches temporarily block the immediate threat of "Get Windows 10" by removing the GWX icon in the Win7 and Win8.1 system tray and by derailing some of the Windows 10 update programs that are currently installed. Neither approach, however, will remove background tasks that bring GWX back, reclaim the 3GB to 6GB of hidden installation files Microsoft may have surreptitiously stored in the $Windows.~BT folder, nor will they keep your system protected if future Microsoft-initiated GWX attacks similar to the old ones occur again.
<aside class="nativo-promo smartphone" id=""> </aside>I've been talking about Microsoft's scummy GWX campaign since April, when researchers first identified KB 3035583 (http://www.infoworld.com/article/2906002/operating-systems/mystery-patch-kb-3035583-for-windows-7-and-8-revealed-it-s-a-windows-10-prompter-downloader.html) as the source of the attack. As best I can tell, KB 3035583 was modified, fortified, and re-released nine times in 2015. Through it all, Josh Mayfield, the inventor of GWX Control Panel (http://blog.ultimateoutsider.com/2015/08/using-gwx-stopper-to-permanently-remove.html), has kept his program updated to protect against the slings and arrows of outrageous fortune.
I asked Mayfield about the registry edit approach to protecting against GWX. He reminded me that GWX Control Panel (then GWX Stopper (http://www.infoworld.com/article/2979572/microsoft-windows/gwx-stopper-an-easy-way-to-permanently-delete-get-windows-10-nagware-in-windows-7-and-81.html)) started out last August as an easy way for nonprogrammers (and others afraid of manually editing the Registry) to keep themselves protected. But it's evolved into much more.
Here's what Mayfield told me:


The DisableGWX value, which GWX Control Panel has been setting since version 1.0, does one thing, and one thing only: When the scheduled GWX.EXE task runs, it checks for that registry value, and if it's set, GWX.EXE quits itself. That's how you remove the icon from your notification area. but this doesn't do anything about the several background tasks that Microsoft installs along with GWX.EXE.
Beginning in version 1.3 of GWX Control Panel, I've included additional logic to help people whose Windows Update control panels get hijacked by Windows 10. Version 1.4 and beyond can even rescue you from an already-initiated unwanted Windows 10 upgrade.
As your own AskWoody.com (http://AskWoody.com) visitors (and mine) have confirmed many times over by now, KB3035583 needs to be rehidden each time Microsoft pushes a new version. If you don't want to install it, and if you happen to get more than one version installed, uinstalling it no longer gets rid of the update. (I walk through this in more detail in my troubleshooting guide (http://blog.ultimateoutsider.com/2015/11/gwx-control-panel-troubleshooting-guide.html).) This is why I added the new Delete Windows 10 Programs feature in version 1.7.
Beginning about a month ago the KB3035583 update started installing a new background task -- beyond the ones previous versions already installed -- that resets the AllowOSUpgrade value to 1 (enabled) twice a day. Not all users have this background task -- I don't know how Microsoft decides how these things get distributed -- but for those who do, changing this value like [Bott] suggests will only help you for 12 hours or less.


Of course, changing any of the four Registry values won't delete the 3GB to 6GB of files Microsoft surreptitiously installed (http://www.infoworld.com/article/2983777/microsoft-windows/how-to-clean-the-windows-10-crapware-off-your-windows-7-or-81-pc.html) on many machines in the hidden $Windows.~BT folder. Changing Registry values won't uninstall or hide KB 3035583. Changing the Registry is a good starting point, but it doesn't clean out the crapware underneath.
<aside class="nativo-promo tablet desktop" id=""> </aside>It's important to realize that nobody has any idea how Microsoft will circumvent these protections in the future. What we do know is that Microsoft has wiggled around the stopgaps in the past -- having new versions of KB 3035583 reset the AllowOSUpgrade value, for example -- and it's clear that Microsoft has no fear of alienating diehard Windows 7 users. As Mayfield said this morning, "I'm still hearing from people who've had their Windows Update control panels hijacked, and Microsoft said they were gonna stop that nonsense months ago. Windows is a moving target, and Microsoft can and do change their policies/tactics at will."
Last October, Windows honcho Terry Myerson promised (https://blogs.windows.com/windowsexperience/2015/10/29/making-it-easier-to-upgrade-to-windows-10/): "You can specify that you no longer want to receive notifications of the Windows 10 upgrade through the Windows 7 or Windows 8.1 settings pages."
I haven't seen anything in any Win 7 or 8.1 settings pages that allow you to just say no to the Windows 10 upgrade process. If you've seen something, please hit me in the comments.
As Mayfield says, "[GWX Control Panel is] based on both my first-hand experience and reports I've received from hundreds of users (most of whom are IT consultants and tech support professionals). The Windows 10 push is much bigger than what those Registry values cover. Period."
If you want to keep Microsoft from nagging you about Windows 10, you can change a couple of Registry values and hope that history doesn't repeat itself. Or you can hit it with a full barrage. Neither comes with a guarantee that Microsoft will play fair as it pushes the Win10 juggernaut. But I know which one I'll choose.



Noticia:
http://www.infoworld.com/article/3020460/microsoft-windows/banishing-get-windows-10-nagware-isnt-as-easy-as-you-think.html </section>