Windows 10: Version 1607 trying to update my Windows 10 Professional

I have set my Settings > Update & Security > Windows Update > Advanced options to "Defer upgrades". But, now I see in my Notifications that my computer is scheduled to Restart to install Version 1607. Has Microsoft overridden all users of Windows 10 Pro to install 1607 now?

:)

 

need fix for Update for Windows 10 Version 1607 for x64-based Systems (KB3211320) - Error 0x8e5e0152

When windows 10 professional version 1607 build 14393.222 is updated it displays:

Update for Windows 10 Version 1607 for x64-based Systems (KB3211320) - Error 0x8e5e0152

Is this a wait for Microsoft update or is there a way to fix the failed update?

 

need fix for: Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3213986) - Error 0x8e5e0152

When windows 10 professional version 1607 build 14393.222 is updated it displays:

Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3213986) - Error 0x8e5e0152

Is this a wait for Microsoft update or is there a way to fix the failed update?

 

I'm seeing the same thing here - 2 latops with Pro and Defer Upgrades set have both started to download 1607 (or at least tried - I need to free up some disk space before it will succeed).

 

It's been 6 Months since 1607 was released and I think the defer time has elapsed.

Jim

 

Yep.

Definition of defer is to postpone or delay, not eliminate.

https://support.microsoft.com/en-us/...-in-windows-10

The "several months" has passed.

 

I can't remember the exact 1607 release date but I thought it tipped into August 2016? (Despite the name 1607.)

 

August 2nd 2016. Version number 1607 (build 14393) is a bit (two days) misleading but due the name Anniversary Update it was made to correspond with original release version 1507 (build 10240), released on July 29th 2015.

 

@Lou Svach, Welcome to TenForums.

Defer updates is a delay, not a total block. You are effectively switching your machine from the Current Branch to the Current Branch for Business.

Overview of Windows as a service (Windows 10)

1607 was released to the CBB on 29th Nov 2016, so can no longer be deferred.
Windows 10 release information - current branch, build history

 

Your explanation sounds logical and I will accept the upgrade to version 1607.

Lou

 

If you find it causes issues for you, you have just 10 days to go back to your earlier build, after that the windows.old folder is automatically removed to release disk space. This was reduced from 30 days to 10 with the Anniversary Update, Microsoft said their telemetry showed that virtually everyone who switched back would do so in the first few days.

 

Thank you again. I had not read about the change in November.

Lou

 

But it was deferred for a couple more months.
I don't think 29 Nov is the date which matters for the Defer Upgrades settings. I suspect that as Phone Man mentions it's 6 months or possibly 180 days after the release date (or possibly build date) of 1607.

I did read somewhere that by going into Group Policy editor, it's possible to defer for up to 8 months, so I imagine one can still do this if the update hasn't triggered yet.

 

When this message came up last week, it didn't complete (because I've told Windows this WiFi connection is a metered network).
I took a precautionary backup image overnight and connected with an ethernet cable, and pressed Check for Updates.

There were Defender updates and a couple of others, but I was surprised that Feature Update to 1607 did not appear today, even though it was appearing a week ago on this computer.

I'm going to use an ISO instead but it suggests to me that MS are throttling how 1607 goes to computers which had Defer Upgrades set.

 

peeps should of been on 1607 already not only for their safety but for everyone's safety.