Stop Windows 10 1607 upgrading to 1709

Makes no sense to me.
When a branch gets EOL then they keep updating this old branch with cumulative updates.
But they will force it to a new branch anyway...And will keep making news CU for the olds one.

 

If a build reached EOL it means no updates at all for those . Additionally the nagging goes to a new stage, as tested on my 14393 (EOL in april), where update service got re-enabled automatically by the Tasks mentioned earlier. It also actively ignored the hidden status for feature updates.

 

Windows 10 is getting slower by the day (all these tons of ads, data collecting apps, hidden tasks etc). I wouldn't think for a second to downgrade to RTM and lock WU at the initial first bootup.

 

All still works as usual, on 16299.248

 

Define 'RTM', there were already 5 (TH1/TH2/RS1/RS2/RS3) another one (RS4) is coming soon .

 

The one that signed off as Windows 10 in 2015. (it had 0 ads).

Well, you get the point. No one wants a fu bloated system I'm still gonna wait a while with updating.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

The ads appeared in 1703 (15063), not before and can be avoided by reg entries and GPO .

 

folder Properties -> Security -> Advanced -> Disable inheritance -> Remove all...

 

You use Windows 10 version without disabling AU (policy or metered) and its schedue tasks?

i still have 10240 Pro VM that i use to check new nag updates or feature update links, works as expected
WUMT

 

I used to have my connection set to metered, WU service disabled and feature Update deferred in advanced settings and additionally set to hidden (using Powershell WU Sniplet). Now with the disabled tasks no problems left .

 

You need to login to view this posts content.

 

@s1ave77, you are kind but the thanks is not needed. am glad i could be useful.

 

Without your hint i wouldn't have noticed, so i add it as always .

 

10240 and 14393 have both the LTSB version, the latter has Server2016 on the same build so you will see updates to them for 5+5 years since the release, but likely they will block the installation on Home/Pro after their EOL date.

So the most obvious way to not be forcefully "upgraded" to 1709 is to move to LTSB or Server

 

The problem with that is... i don't own a LTSB or Server license for my device and don't wanna to back to piracy with Windows.

 

Thank you and @ipx for that. I found I could just rename the %programfiles%\rempl folder, so now remsh.exe can't run. Do you see any downside to that?

 

Think to this.

Buy a 1st class ticket for a train travel. Then take a seat on 2nd class. Are you pirating your railway company?

LTSB according to MS marketing mumbo jumbo is exactly this: a second class OS, that lacks features and feature updates.

So calling that "piracy" seems a bit exaggerate to me.

Whatever, each one has his own morality view and I'm not get to argue further on this