Installing 2017 11 Cumulative Update For Windows 10 Version 1607

-->

Apr 20, 2020 This update replaces the following updates: 2017-05 Cumulative Update for Windows 10 Version 1607 for x86-based Systems (KB4019472) 2017-05 Cumulative Update for Windows 10 Version 1607 for x86-based Systems (KB4023680) 2017-06 Cumulative Update for Windows 10 Version 1607 for x86-based Systems (KB4022715). Apr 12, 2017 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4015217). This is the update not installing on my laptop.

Find information on known issues for Windows 10, version 1607 and Windows Server 2016. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). Want the latest Windows release health updates? Follow @WindowsUpdate on Twitter.

Windows 10, version 21H1 is now available
Find out how to get the update >
IT tools for Windows 10, version 21H1
Explore the latest tools and resources to support your rollout >

Known issues

This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

SummaryOriginating updateStatusLast updated
Apps might have issues accessing event logs on remote devices
Event logs might not be accessible from remote devices unless both devices have updates released June 8, 2021 or later.
OS Build 14393.10001
KB5003638
2021-06-08
Resolved
KB5003638
2021-06-08
10:00 PT
Windows Presentation Foundation (WPF) apps might close, or you may receive an error
Microsoft and third-party applications which use the .Net UI framework called WPF might have issues.
OS Build 14393.4225
KB4601318
2021-02-09
Mitigated
2021-02-11
20:41 PT
Cluster service may fail if the minimum password length is set to greater than 14
The cluster service may fail to start if “Minimum Password Length” is configured with greater than 14 characters.
OS Build 14393.2639
KB4467684
2018-11-27
Mitigated
2019-04-25
14:00 PT

Issue details

June 2021

Apps might have issues accessing event logs on remote devices

StatusOriginating updateHistory
Resolved KB5003638OS Build 14393.10001
KB5003638
2021-06-08
Resolved: 2021-06-08, 10:00 PT
Opened: 2021-06-07, 16:10 PT
After installing KB5003638 or later updates, apps accessing event logs on remote devices might be unable to connect. This issue might occur if the local or remote has not yet installed updates released June 8, 2021 or later. Affected apps are using certain legacy Event Logging APIs. You might receive an error when attempting to connect, for example:
  • error 5: access is denied
  • error 1764: The requested operation is not supported.
  • System.InvalidOperationException,Microsoft.PowerShell.Commands.GetEventLogCommand
  • Windows has not provided an error code.
Note Event Viewer and other apps using current non-legacy APIs to access event logs should not be affected.
Affected platforms:
  • Client: Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This is expected due to security hardening changes relating to Event Tracing for Windows (ETW) for CVE-2021-31958. This issue is resolved if the local and remote devices both have KB5003638 installed.

February 2021

Windows Presentation Foundation (WPF) apps might close, or you may receive an error

StatusOriginating updateHistory
MitigatedOS Build 14393.4225
KB4601318
2021-02-09
Last updated: 2021-02-11, 20:41 PT
Opened: 2021-02-11, 17:49 PT
After installing KB4601318, Windows Presentation Foundation (WPF) apps might close, or you may receive an error similar to:
Exception Info: System.NullReferenceException at System.Windows.Interop.HwndMouseInputProvider.HasCustomChrome(System.Windows.Interop.HwndSource, RECT ByRef)
at System.Windows.Interop.HwndMouseInputProvider.GetEffectiveClientRect(IntPtr)
at System.Windows.Interop.HwndMouseInputProvider.PossiblyDeactivate(IntPtr, Boolean)
at System.Windows.Interop.HwndMouseInputProvider.Dispose()
This occurs when disposing an HwndSource whose RootVisual is null, a situation that arises in Visual Studio when docking or splitting windows, and could arise in other apps.
Affected platforms:
  • Client: Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server, version 1803; Windows Server 2016
Workaround: To mitigate this issue when using Microsoft Visual Studio, update to the latest version. This issue is resolved starting with the following releases:
Developers can mitigate this issue in their own apps by setting two AppContext switches using one of the methods described in AppContext Class (System) under the heading “AppContext for library consumers”. The switches are named Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix and Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix; both should be set to “true”. The first switch avoids the crash, but re-introduces the issue addressed in this update. The second switch is currently ignored, but will be recognized in a future .NET update that addresses the issue for the null-reference crash; it restores the behavior originally intended to be addressed in this update.
For example, using the app.config file method to apply the workaround at application scope:
<AppContextSwitchOverrides value='Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix=true; Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix=true ' />
Next steps: We are working on a resolution and will provide an update in an upcoming release.

November 2018

Cluster service may fail if the minimum password length is set to greater than 14

StatusOriginating updateHistory
MitigatedOS Build 14393.2639
KB4467684
2018-11-27
Last updated: 2019-04-25, 14:00 PT
Opened: 2018-11-27, 10:00 PT
After installing KB4467684, the cluster service may fail to start with the error '2245 (NERR_PasswordTooShort)' if the Group Policy 'Minimum Password Length' is configured with greater than 14 characters.
Affected platforms:
  • Client: Windows 10, version 1607; Windows 10 Enterprise LTSC 2016
  • Server: Windows Server 2016
Workaround: Set the domain default 'Minimum Password Length' policy to less than or equal to 14 characters.
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.

My PC keeps trying to upgrade to the windows version 1607 and it keeps on failing. It ends up at a spinning disk on restart that I have left on for over 12 hours. I reboot the computer and then it reverts to the previous installation build. I have tried running trouble shooting 'Fix problems with Windows Update' before hand and it doesn't solve the problem. I also tried the this fix

https://www.classiccomputers.info.com/en-us/download/details.aspx?id=53942

Update

doesn't seem to solve the problem either. This is the most frustrating problem I have ever had with a Windows system especially now that it force feeds you these updates that don't work.
You watching: Feature update to windows 10, version 1607 failed to install


This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
I have the same question (119)
Subscribe Subscribe Subscribe to RSS feed

Replies (20) 


* Please try a lower page number.

* Please enter only numbers.


1 2 Next

* Please try a lower page number.

* Please enter only numbers.


Previous Next

A. User
Replied on April 11, 2017

Hi Jet,

Windows updates may fail to install if there are corruption errors. For example, an update might not install if a system file is damaged.To address your concern, we suggest that you follow these methods:

Method 1: Run the Windows Update troubleshooter.

Method 2: Reset Windows Update components.

Method 3: Fix Windows Update errors by using the DISM or System Update Readiness tool.

Method 4: Disable the Anti-Virus.

Note: If you have to temporarily disable Anti-Virus software to install updates, you should re-enable it as soon as you're done.

If you need further assistance, feel free to reply on this post.


13 people found this reply helpful

·

Was this reply helpful?
Yes No

Sorry this didn't help.


Great! Thanks for your feedback.

How satisfied are you with this reply?


Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?


Thanks for your feedback.


CO
CommunityUser001
Replied on May 14, 2017
In reply to A. User's post on April 11, 2017

I just tried all three methods. Still stuck in an update loop.After method 3, it looks like the Update 1607 downloaded again. Then when I restarted, it tried to install. Went all the way up to about 70% (restarting a few times). Finally, it gave up and showed a message 'Restoring Windows to a previous version...' What's weirder -- when I go into Windows Update > Advanced Options > View your update history... -- there is no mention that the update failed, it just shows the last update that passed.

I've already spent 3 hours trying to get this update working, going through each method twice. This is beyond ridiculous.


Was this reply helpful?
Yes No

Sorry this didn't help.


Great! Thanks for your feedback.

How satisfied are you with this reply?


Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?


Thanks for your feedback.


RG
Rachelle Gra
Replied on May 14, 2017

Installing 2017 11 Cumulative Update For Windows 10 Version 1607 Anniversary Update


In reply to CommunityUser001's post on May 14, 2017

Hi,Corrupted Windows Update database could be one of the reasons why you're having issues with updating Windows. If the issue persists after performing the troubleshooting steps, we suggest that you try to manually install the update. Here's how:

Find the most recent update KB for the version of Windows 10 you have – it’s usually at the top of the list – and either write the KB number down or copy it.Select the link for the download, and then choose Download.SelectSave if you are prompted.When the download completes, select Opento start the update.

Feel free to update us on the result.
See more: What Will A Computer Boot Without A Hard Drive ? Question: Can A Computer Run Without A Hard Drive


Was this reply helpful?
Yes No

Sorry this didn't help.


Great! Thanks for your feedback.

How satisfied are you with this reply?


Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?


Thanks for your feedback.


LH
LHJr

Replied on May 14, 2017
In reply to A. User's post on April 11, 2017

Hallelujah!*****


Was this reply helpful?
Yes No

Sorry this didn't help.


Great! Thanks for your feedback.

How satisfied are you with this reply?


Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?


Thanks for your feedback.


CO
CommunityUser001
Replied on May 14, 2017
In reply to Rachelle Gra's post on May 14, 2017

There are two forKB4019472:

2017-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4019472)2017-05 Delta Update for Windows 10 Version 1607 for x64-based Systems (KB4019472)

Do I need to download and install both?

When I ran the download it said 'This update is not applicable for your computer.' So how do I know which KB version to download, should I just get the newest one for Windows 10 x64 (aka. go straight to Windows 10 Version 1703)...?

So I tried the one for Windows 10 Version 1703, and that also returned'This update is not applicable for your computer.' OK, so I clearly need to download the one for my 'version', but when I look around the 'About your pc' it doesn't say what version I have besides Windows 10 Home x64. When I run 'winver' it says I have Version 10.0 (Build 10240)...?


Was this reply helpful?
Yes No

Sorry this didn't help.


Great! Thanks for your feedback.

How satisfied are you with this reply?


Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?


Thanks for your feedback.


RG
Rachelle Gra
Replied on May 15, 2017
In reply to CommunityUser001's post on May 14, 2017
If you're still having issues with updating Windows, we suggest that you create Windows 10 installation media to install the latest Windows 10 build. Kindly check thislink to download the tool, then follow the steps under Using the tool to upgrade this PC to Windows 10.Do let us know should you need further assistance.

Was this reply helpful?
Yes No

Sorry this didn't help.


Great! Thanks for your feedback.

How satisfied are you with this reply?


Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?


Thanks for your feedback.


CO
CommunityUser001
Replied on May 19, 2017
In reply to Rachelle Gra's post on May 15, 2017

Installed to USB drive. Ran install. 'Download latest updates...' After a few hours of all this, I now get 'We couldn't install Windows 10.'

'The installation failed in the SECOND_BOOT phase with an error during MIGRATE_DATA operation.'


Was this reply helpful?
Yes No

Sorry this didn't help.


Great! Thanks for your feedback.

How satisfied are you with this reply?


Thanks for your feedback, it helps us improve the site.

Installing 2017 11 Cumulative Update For Windows 10 Version 1607 For X64 Based Systems

How satisfied are you with this reply?


Thanks for your feedback.


JF
John Fer
Replied on May 19, 2017
In reply to CommunityUser001's post on May 19, 2017

Hi,

The error that you get may be caused by a conflict within your system while downloading the update. We suggest that you refer to the reply of Andre Da Costa on thisthread.

Let us know if you need further assistance.


Was this reply helpful?
Yes No

Sorry this didn't help.


Great! Thanks for your feedback.

How satisfied are you with this reply?


Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?


Thanks for your feedback.
See more: Solved: Copy Method Of Worksheet Class Failed In Excel 2010, Excel Vba Copy Method Of Worksheet Fails


MU
Mahir Uddin
Replied on May 19, 2017

My PC keeps trying to upgrade to the windows version 1607 and it keeps on failing. It ends up at a spinning disk on restart that I have left on for over 12 hours. I reboot the computer and then it reverts to the previous installation build. I have tried running trouble shooting 'Fix problems with Windows Update' before hand and it doesn't solve the problem. I also tried the this fix

Installing 2017 11 Cumulative Update For Windows 10 Version 1607 Download

https://www.classiccomputers.info.com/en-us/download/details.aspx?id=53942

doesn't seem to solve the problem either. This is the most frustrating problem I have ever had with a Windows system especially now that it force feeds you these updates that don't work.

Installing 2017 11 Cumulative Update For Windows 10 Version 1607 Download

Hi,

I am sorry to see that you are having some problems installing the windows 10 anniversary update. The best solution to solve this problem is by installing the latest version of windows 10 (Creators Update) manually through classiccomputers.info's website

Then click update now.Follow the instructions carefully and update your PCWindows 10 will download in the background so you may still continue to use your PC or be able to shut it downyou product of windows 10 will still remain activated after the update is completed

Installing 2017 11 Cumulative Update For Windows 10 Version 1607 Build 14393 0

I hope that this has solved your problem.