UpdateGate: KB3035583 is back as recommended update!

A new version of KB3035583, the main component responsible for upgrading to Windows 10, is currently being deployed to Windows 7 and Windows 8.1 systems.

Here are the details about it:

Update for Windows 7  (KB3035583)  (This could be titled "for Windows 8.1", and "x64" could be added to this title, it depends on your system)
 Update KBID: 3035583
   Available update Identity Revision=200
   Available update Identity UpdateID=32855aab-2367-4855-8be7-c42f67080a37
   Available update LastDeploymentChangeTime=2016/02/23  (YYYY/MM/DD)
   Update DownloadPriority=2
   Available Update superseded KBIDs: 73209c3e-0511-4f6c-b61c-e155c4eaa434

Interestingly, it supersedes the previous version of KB3035583 dated 2015/12/15

As always, Microsoft does not say much about it:

All we can see is that the Gwx files have been updated recently:

File nameFile versionFile sizeDateTimePlatform
Config.datNot applicable91,12030-Nov-201514:08Not applicable
Detectorn.datNot applicable19,77630-Nov-201514:08Not applicable

We have installed this new KB3035583 on several of our test machines that have previously been patched by Win10wiwi: So far, these machines have not shown any attempt or notification to upgrade to Windows 10.

However, users who want to avoid any surprise may want to run Win10wiwi again in order to prevent this new update from being installed.


Win10wiwi version is out!

Thanks to some user's feedback, we discovered an issue with one of the components we use and that was recently updated.
v1.1.0.14 could be problematic in case there was no Internet connection or if there was a problem with the Internet connection.

Win10wiwi needs an Internet connection to get the list of available updates from Microsoft, since this is the only way they can be hidden. MS could have made it possible to hide uninstalled updates without getting the list of available ones, but they did not.
We worked all day to release v1.1.0.15 that corrects the issue we detected.

v1.1.0.14 will now display a message telling the users that a newer version is out. It may display an error dialog (similar to the one above) if you choose to go to the download page when you are incited to do it. If that is the case, close Win10wiwi v1.1.0.14 by clicking the cross in the upper right corner of Win10wiwi11014 interface, or right-click Win10wiwi icon in the task bar and close it from there.
Then download v1.1.0.15 and run it, it should not have any problem.


2016 February 09: a patch Tuesday without any change to Upgrade to Windows 10 program. Really ?

As you may expect, Win10wiwi team is very carefully monitoring all updates deployed by Microsoft through "Windows Update".
The important updates that have been deployed last Tuesday are almost all security updates and thus should not been related to "Upgrade to Windows 10". We monitor them all the same and so far, none of them have been involved in the upgrade program.

In the batch of updates deployed this week, only one update can be related to "Upgrade to Windows 10" program: kb3135449. This is an update to Windows Update client itself. Because Windows Update Client is the end-user component that is responsible for getting all the components involved in the so called updategate, changes to this client may have an impact or even been required for the upgrade process to work.
As usual, there are not much details on Microsoft web site regarding this update:

This is what we can read on microsoft web site: 
Windows Update Client for Windows 8.1 and Windows Server 2012 R2: February 2016
This article describes an update that contains some improvements to Windows Update Client in Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2. This update has a prerequisite.
About this update
This update contains some improvements to Windows Update Client in Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2.

Now, since this is an important update, and even if it has some potential incidence on the updategate program, it may also be required for other things such as deploying security patches etc.
Furthermore, this update alone, even if it embeds things that may be used for the updategate, is not enough to be a game changer. Windows Update client is just a vehicle, not the content itself. Disabling it would be like banning all cars because some of them are used to carry illegal or unwanted stuff or persons.

Something else that we found out is that this update is not available for Windows 7 nor has it any equivalent in the updates deployed to Windows 7 with this Patch Tuesday batch.

For these reasons, we have decided not to ban KB3135449 from the updates that Win10wiwi disables. Yet, we are still in the process of examining the changes that KB3135449 involves. This takes some time... If we find something strange or suspicious, we will do what we think is needed to increase the control Windows 7 and Windows 8 users have on their systems.

We studied the optional updates too and nothing in this patch Tuesday's batch optional update is related to the updategate.

Stay tuned !


UpdateGate KB2952664, KB2976978, KB3135445 and KB3123862 2016/02/02 versions

Microsoft is currently rolling out several new Windows Updates that are clearly aimed at pushing Windows 10 to existing Windows 7 and Windows 8.x system. And it begins to become more aggressive each time.

Namely, these updates are KB2952664, KB2976978, KB3123862 and KB3135445

They are (almost all) optional.
For now... But there is something very weird.
Check below.

Here is what can be read on the support pages for these updates, as well as some details that we were able to gather about them:


Compatibility update for upgrading Windows 7

This update helps Microsoft make improvements to the current operating system in order to ease the upgrade experience to the latest version of Windows.

The optional update says:

Last Deployment Change Time=2016/02/02  (YYYY/MM/DD)
Download Priority=2

And the Important Update says:

Last Deployment Change Time=2016/01/12   (YYYY/MM/DD)
Download Priority=2

You read correctly!
There can be two versions of KB2952664 pushed simultaneously. v203 is an important update while v200 is an optional update. Usually however, you should get only the latest one.

We have the same pattern for KB2976978, which is to Windows 8 what KB2952664 is to Windows 7.


Compatibility update for Windows 8.1 and Windows 8

This update performs diagnostics on the Windows systems that participate in the Windows Customer Experience Improvement Program. These diagnostics help determine whether compatibility issues may be encountered when the latest Windows operating system is installed. This update will help Microsoft and its partners ensure compatibility for customers who want to install the latest Windows operating system.

Optional update says:

Last Deployment Change Time=2016/02/02    (YYYY/MM/DD)
Download Priority=2

and important update says:

Update ID=f3b7944b-c9bb-4ea3-9d9a-22b76e35f48b
Last Deployment Change Time=2016/01/12   (YYYY/MM/DD)
Download Priority=2

Now the two other updates that are related to "updategate" upgrade to Windows 10 are the following:


Updated capabilities to upgrade Windows 8.1 and Windows 7

The update adds capabilities to some computers that lets users easily learn about Windows 10 or start an upgrade to Windows 10. Before you install this update, see the Prerequisites section. For more information about Windows 10, see Windows 10.

Identity Revision=202
Identity UpdateID=e347fcd7-3075-4818-99fb-0eb7367554cb
Last Deployment Change Time=2016/02/03   (YYYY/MM/DD)
Download Priority=2


Windows Update Client for Windows 7 and Windows Server 2008 R2: February 2016

This article describes an update that contains some improvements to Windows Update Client in Windows 7 Service Pack 1 (SP1) and Windows Server 2008 R2 SP1.

Identity Revision=200
Identity UpdateID=a4bc0109-346e-4af2-b13c-6cf5ea04f694
Last Deployment Change Time=2016/02/02    (YYYY/MM/DD)
Download Priority=2

So far, the two last updates are marked optional, meaning that they should not get installed on too many systems by default. We advise users who do not want to upgrade to Windows 10 not to install these updates.

Systems that have opted-out the upgrade to Windows 10 with win10wiwi should not have any problem with these updates, as the core upgrade engine has been disabled. But if you have any doubt or if you feel that your Windows 7 or Windows 8 systems became slower lately (since the upgrade process can take quite a lot of resources), you can re-run win10wiwi again, it will not do any harm. And it will prevent the two versions of KB2952664 to be offered to your system.

However, win10wiwi ecosystem will soon be updated to take these new updates and this new behavior into account.