Is Microsoft forcing upgrades in Windows 10 V1607?

[German]Today (October 17, 2017) Microsoft is rolling out the Windows 10 Fall Creators update. German blog reader Stefan told me last Sunday about an interesting observation of the Windows 10 Anniversary Update. After the last patchday, Windows 10 Anniversary Update automatically changes the startup type of the Windows Update service (so that updates are forced).


Advertising

Stefan’s observation

Stefan told me via e-mail:

I still use Windows 10 V1607 on a system (I wanted to skip V1703 and upgrade to V1709 soon).

I always want to install updates manually whenever I want to (before that I always do a backup). That’s why I disabled the Windows Update Service. So far it’s been great, I’ve done a lot of updates in that way and the service has been deactivated again and again.

Now I have recently installed updates again… and suddenly the following happens: The deactivated Windows Update Service is automatically set from deactivated to manual by the system after about one day (see below).

Stefan found the following entry within Windows event mangager (it was a German Windows):

Protokollname: System

Quelle:        Service Control Manager

Datum:         15.10.2017 10:33:12

Ereignis-ID:   7040


Advertising

Aufgabenkategorie:Keine

Ebene:         Informationen

Schlüsselwörter:Klassisch

Benutzer:      SYSTEM

Computer:      R2D2

Beschreibung:

Der Starttyp des Diensts “Windows Update” wurde von Deaktiviert in Manuell starten geändert.

Ereignis-XML:

<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>

<System>

<Provider Name=”Service Control Manager” Guid=”{555908d1-a6d7-4695-8e1e-26931d2012f4}” EventSourceName=”Service Control Manager” />

<EventID Qualifiers=”16384″>7040</EventID>

<Version>0</Version>

<Level>4</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8080000000000000</Keywords>

<TimeCreated SystemTime=”2017-10-15T08:33:12.941298800Z” />

<EventRecordID>76285</EventRecordID>

<Correlation />

<Execution ProcessID=”868″ ThreadID=”1700″ />

<Channel>System</Channel>

<Computer>BIG</Computer>

<Security UserID=”S-1-5-18″ />

</System>

<EventData>

<Data Name=”param1″>Windows Update</Data>

<Data Name=”param2″>Deaktiviert</Data>

<Data Name=”param3″>Manuell starten</Data>

<Data Name=”param4″>wuauserv</Data>

</EventData>

</Event>


Stefan suspects that Microsoft has implemented a function in Windows to force updates install, although the user has deactivated Windows Update service. According to Stefan, this happens without further inquiry. In his opinion, it should be left to the user to decide which services he wants to use and which not.

Are October updates to blame?

Stefan believes that this behavior must be triggered by one of the updates from the following screenshot.

Updates

Stefan states that it didn’t happen that the startup type was changed before installing these updates. Even on another computer with Windows 10 version 1703 this does not happen according to his statement.

A workaround

A workaround is to set the logon data of the Windows Update Service (Service) with a user name and with an incorrect password. Then the service (service) cannot start.

Stefan assumes on the basis of the above observations that Microsoft wants to “force” older Windows 10 version 1607 installations to the current state. Has anyone else observed this behavior? At this point I would like to thank Stefan for the advice.


Advertising


This entry was posted in Update, Windows and tagged , . Bookmark the permalink.

3 Responses to Is Microsoft forcing upgrades in Windows 10 V1607?

  1. Pingback: Is a Win10 1607 cumulative update re-enabling a disabled Windows Update service? @ AskWoody

  2. PABear WI-MVP says:

    Interesting. One is left wondering:

    Is Stefan running Win10 Home, Pro or Enterprise?

    Was KB4023057 and/or KB4037589 also installed?

    Did Stefan choose to install/upgrade to Anniversary Update manually?

Leave a Reply

Your email address will not be published. Required fields are marked *