Lemme Fix: Windows 10 updates forcing you to upgrade to Build 1709

Several pages reporting that Microsoft is forcing you to upgrade Windows 1703 (or an older build) to Build 1709. Several KB’s are the cause here, because Microsoft added a UpdateOrchestrator UpdateAssistant to the Windows Tasks Scheduler. It’s definitely wrong that this has something to do with telemetry related settings because these two tasks are there no matter which telemetry option you set (basic, advance,…) and there not only KB4023814 + KB4023057 related, several other KB’s also managing this.

Windows performance

Is Microsoft forcing you to upgrade?

The tasks are created to make it easier to offer upgrades but the UpdateOrchestrator task might have some problems which overriding some settings, so you systems wrongly gets the upgrade notification no matter what. I already informed Microsoft about this several weeks ago.

If you’re currently running Windows 10 Version 1507, Version 1511, Version 1607 or Version 1703, you can expect to receive a notification that states that your device has to have the latest security updates installed. Windows Update will then try to update your device. When you receive the update notification, click Update now to update your device.

This update is also offered directly to Windows Update Client for some devices that have not installed the most recent updates.

Windows 10 Version 1507 and Version 1511 are currently at “end of service”. This means that devices that are running these operating systems no longer receive the monthly security and quality updates that contain protection from the latest security threats. To continue receiving security and quality updates, Microsoft recommends that you update the system to the latest Windows version, Windows 10 Version 1709. Windows 10 version 1607 and version 1703 are not yet at “end of service”. However, they must be updated to the latest versions of Windows 10 to ensure protection from the latest security threats.


Microsoft is aware that this notification was incorrectly delivered to some Windows 10 Version 1703 devices that had a user-defined feature update deferral period configured. Microsoft mitigated this issue on March 8, 2018.

Users who were affected by this issue and who upgraded to Windows 10 Version 1709 can revert to an earlier version within 10 days of the upgrade. To do this, open Settings > Update & Security > Recovery, and then select Get started under Go back to the previous version of windows 10.


Microsoft

Microsoft already responded in the KB4023814 to the issue and offered a workaround for this. The problem is fixed with the Security Patchday from March.

Workarounds

Disabling the tasks fixes the problem

If you control panel -> Programs and Features panel lists an entry called “Upgrade Advisor to Windows 10” just uninstall it, in additional you can also disable the tasks – you not need to delete it it’s not necessary.

  • Open taskschd.msc and navigate to the following paths:
  • Task Scheduler Library\Microsoft\Windows\UpdateOrchestrator\UpdateAssistant
  • Task Scheduler Library\Microsoft\Windows\UpdateOrchestrator\UpdateAssistantCalendarRun

Task Scheduler

You also can check if the C:\WINDOWS\UpdateAssistant folder is empty or not, if not, delete it’s content.

Rollback

You can use the setting under Settings > Update & Security > Recovery, or restore a backup image if you have one to rollback to a previous Windows Build. In case you deleted the windows.old folder you might be out of luck in that case only an image helps.

Some people don’t have the tasks why?

If you’re already on Build 1709 or you used some ‘privacy’ tools you might not see such entries because there deleted or not existent it’s also depending what was set via Group Policy Editor (gpedit.msc).

Final Words

The original intent behind this is to provide you with an upgrade if you really need it, sadly it can wrongly install the upgrade for you which is not the expected behavior. It could be a problem with the Update Assistant or on purpose to avoid that you run into a build which is end of life (and there not [yet]).

Some people saying this is due security threats which is not incorrect because you should upgrade in order to stay secure especially Windows Defender got several improvements but it’s unclear what Microsoft really mean by that forcing the user to install the upgrade without the change to react or block this is not the best way in my opinion.

Update

The problem was meanwhile fixed by Microsoft itself. There now aware of the issue and you not need to apply the workaround, however it could help to clean the folders anyway to avoid fugue update issue.

Uninstall the KB and ensure you catch the latest update, which addresses the issue.

Comments are closed.

Blog at WordPress.com.

Up ↑

%d bloggers like this: