Bork Tuesday, Any Problems Yet?

Yeah, it's nice to know I'm safe ... for now ...

 

It doesn't install anything as long as you have the "let me choose.." option set for Windows Update. '583' may be offered again, but all that needs to be done is to hide it again.

 

The article is not about how windows settings work, it is about how '583' and '664' work in tandem and why they keep regenerating. You are correct that 'notify and let me choose' is the best setting to help avoid receiving the upgrade. Hide and seek just about every Tuesday - so much fun.

 

Yes for sure JR. That has to be unchecked.

I was surprised to read that if the W10 upgrade did get downloaded by those who received it as recommended, it automatically started the install. Woody Leonhard said he unchecked it, but it installed anyway. He also said that the EULA had been moved to the end, so you agree or decline after W10 has installed all its files. That's new.

 

And wrong! That's the type of behaviour you expect from Ransomware.

 

Very strange. It should definitely be there for Win 7 Pro (it is on mine).
Are you running as Administrator?

 

Are update KB3050265 (Windows Update Client for Windows 7: June 2015) and/or update KB3065987 (Windows Update Client for Windows 7 and Windows Server 2008 R2: July 2015) installed?
According to the information in the KB3050265 Knowledge Base Article and in the article How to manage Windows 10 notification and upgrade options, those updates KB3050265 and KB3065987 (Windows Update Client for Windows 7 June and July 2015) are the updates that install the Group Policy object that enables you to block upgrades to the latest version of Windows through Windows Update.
Without KB3050265 and/or KB3065987 for Windows 7 that Group Policy object probably won't be available.

 

Forgotten about that. I am sure you have hit the nail on the head @Stupendous Man . The hazards of trying to identify and ignore all Win X-related optional updates
Wonder if GWX Control Panel would handle it anyway, even without these KB's installed.

 

Wise choice IMO ...
....and it's light as a feather on system resources , and I can't see any "phone home" activity..... " belt and braces " approach ....
... what's not to like ?

@Adric - that UpBork (KB3035583 ) is certainly a notorious offender , with a shocking rap-sheet .

But I'm really not sure it's the only one that exposes the user to the GWX crapware.

 

So far, I appear to be winning in the war against the Win 10 PUP. We have to be prepared for casualties though!

*Patrick Stewart aka Jean-Luc Picard voice* ~ "The Romulans; it's always a game of chess with them, isn't it?"

 

hi Stupendous Man
under w7 i have not installed KB3050265 & KB3065987 or i have installed & uninstalled with a script release in this forum
same for w8.1 i haven't installed KB3050265 & KB3065987 or again i have uninstalled
in short they are not present on my machine
thanks

 

If one uninstalls all Windows Update Client updates since and including Windows Update Client updates June and July 2015, then there's no Windows Update Client version available that installs the Group Policy object that enables you to block upgrades to the latest version of Windows through Windows Update. In that case that Group Policy object will not be available.

But if the Windows Update Client updates June and July 2015 are not installed, but still a later Windows Update Client version is installed, perhaps (or probably!) such later Windows Update Client version installs the Group Policy object that enables you to block upgrades to the latest version of Windows through Windows Update, so that Group Policy object will be available. This is because Windows Update Client versions may probably be cumulative.

Perhaps on your Windows 8.1 system one or more Windows Update Client update versions are still installed (even though you thought there wasn't) (perhaps some recent Windows Update Client update version?) so that the Group Policy object that enables you to block upgrades to the latest version of Windows through Windows Update is still available.

 

It is for me on Win7. On Win8, KB3035583 was superseded by KB3064683 then by KB3072318 then by KB3035583-v3 - all of which add the GWX component . There are no other KBs up to now that I am aware of that add the GWX component that everyone is complaining about.

 

hi
maybe ,with the w10 launch , with windows update it's really hard to understand what we are/were updating

 

For various versions of Windows, these are the offending updates (not all of them apply to all versions):

• KB 295 2664 (several times over)

• KB 297 6978

• KB 297 7759

• KB 299 0214

• KB 302 1917

• KB 303 5583 (several times over)

• KB 304 4374

• KB 310 2429 (useless update for most)

• KB 311 2343

• KB 312 3862

• KB 313 5445

• KB 313 5449

Not having these on my system does not seem to have hurt anything. I had not heard about KB3064683 or KB3072318, but I don't run W8 and they are not on W7 systems I run. I also don't have KB3050265 and KB3065987, and I never blocked or hid any of those four. I don't know what they do.

"Several times over" means you can hide them and something changes and they come back in a future update. Turn off automatic updates (to let me decide), uninstall them, hide them, run GWX Control Panel (disable everything with it.) Good to go.

You don't really want to clear the update cache unless you really need to. The instructions in the GWX Control Panel interface say "See the user guide for details..." which is good advice. Read the user guide. If you don't actually start and back out of the "upgrade" to W10, you probably don't need to clear the update cache. If you find after making changes, that Windows Update doesn't work, clearing the update cache may fix the problem. Read the user guide.

I wait 2 days to see if any problems have been encountered by braver souls. Then I look for these in the pile. If they are there, they get hidden. When they are not there, I update.

GWX Control Panel edits the registry for you (for DisableOSUgrade), but you can do the same thing manually. If you are a victim of the GWX icon in the SysTray notification area, then create DisableGWX.

This information is published by Microsoft at https://support.microsoft.com/en-us/kb/3080351 ...but here is the short version:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

Create a DWORD value called DisableOSUpgrade and set it to 1.

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\GWX

Create a DWORD value called DisableGWX and set it to 1.

Shutdown, restart...

If you change your mind, set those two values to 0 or just go to Microsoft's Get Windows 10 web page.

 

hi
thanks a lot for the deep information
you run w7 right , may i know if you have in the Group Policy Turn off the upgrade to the latest version of Windows through Windows Update
thanks

 

Regarding KB2990214, yes, it says "Update that enables you to upgrade from Windows 7 to a later version of Windows", but also read the Microsoft TechNet article "Windows Servicing Releases – April 14, 2015", stating:

Also quoted in the April 16, 2015, InfoWorld article "Microsoft elaborates on KB 2990214, KB 3044374 Win10 nagware"

 

That will only be applicable if nwbob (or anyone else) runs the Windows 7 Professional edition.
The Windows 7 Home Premium edition does not offer Group Policy.

And as I mentioned in my two previous posts #1984 and #1989, at least one of the Windows Update Client update versions that install the Group Policy object that enables you to block upgrades to the latest version of Windows through Windows Update needs to be installed for that Group Policy object to be available - Windows Update Client June and July 2015 are the two mentioned by Microsoft, and probably any of the later Windows Update Client update versions would do also.

Have you checked if you have any of those Windows Update Client update versions installed on your Windows 7 Professional system?
If none are installed, you can download and install KB3050265 Windows Update Client for Windows 7: June 2015 and/or KB3065987 Windows Update Client for Windows 7 and Windows Server 2008 R2: July 2015.

 

hi
yes i have checked ,nothing , i run reg seeker , total commander ,everything nothing
my w7 pro is updated with the lastest update outside KB3139929

 

I'm not quite sure what you mean.

Firstly, you can check for installed Windows Update Client update versions in Windows Update, View update history.
Windows Update Client for Windows 7 June 2015 is KB3050265, the July version for Windows 7 is KB3065987, October KB3083710, December KB3112343, February 2016 is KB3135445, and Windows Update Client for Windows 7 March 2016 is KB3138612.
However, if you first installed Windows Update Client updates and later uninstalled them, I'm not sure if that shows in Windows Update, View update history.

Secondly, if you find that none of the Windows Update Client update versions since and including Windows Update Client June are installed (June, July, October and December 2015, February and March 2016), in that case it is only logical that the Group Policy object that enables you to block upgrades to the latest version of Windows through Windows Update is not available.

As I mentioned, if none of the Windows Update Client update versions since and including Windows Update Client June are installed, if you like, you can download and install KB3050265 Windows Update Client for Windows 7: June 2015 and/or KB3065987 Windows Update Client for Windows 7 and Windows Server 2008 R2: July 2015.

And finally, as I mentioned before, at least one of the Windows Update Client update versions that install the Group Policy object that enables you to block upgrades to the latest version of Windows through Windows Update needs to be installed for that Group Policy object to be available.
But I'm not sure if you need those Windows Update Client update versions installed for manually setting the DisableOSUpgrade = 1 registry object. Perhaps manually that registry setting can be made even without one of the mentioned Windows Update Client update versions installed.
For manually setting the DisableOSUpgrade = 1 registry object, see the Microsoft article How to manage Windows 10 notification and upgrade options,
or see the How-To Geek article How to Stop Windows 7 or 8 from Downloading Windows 10 Automatically, that even offers a zipped DisableWindows10.reg file, to make things easier.

 

In addition to my previous post,

I notice that the moderator removed the direct link to How-To Geek's zipped DisableWindows10 file.
I'm sorry, I hadn't thought of the forum rule not to link to direct downloads.

If you need it, in the How-To Geek article How to Stop Windows 7 or 8 from Downloading Windows 10 Automatically, you can find the zipped DisableWindows10 file under "download our registry hack file".

 

Hi Stupendous Man
you are incredible ,really ,i really appreciate it a lot
i'm not here on my machine , but i will check better
at home i have checked installed update and not view update history
here in this computer w7 pro , in view update history seem that the search feature doesn't work
i tried to type KB no results
work pc
http://i.imgur.com/3SWro2F.png
http://i.imgur.com/vP5BmR2.png

but is there a command line to have a list of all my update history in a text file?

thanks Stupendous Man

 

I know, that search feature for update history is rather useless.
But if sorted by installation date, you could check for the mentioned KB's by eye, it's not too much updates since June 2015.

However, as I mentioned before, if you first installed Windows Update Client updates and later uninstalled them, using some script, I'm not sure if that shows in update history. Previously installed and later uninstalled updates may still show in update history as installed, so that history may be of no help.

Perhaps there is, but I don't know about it, I'm sorry.
Perhaps someone else knows about such command?
By the way, to be useful, such command should not list uninstalled updates, or it should list those as uninstalled.