Installing 2017 11 Cumulative Update For Windows 10 Version 1607

Posted By admin  On 29.06.21

  1. Installing 2017 11 Cumulative Update For Windows 10 Version 1607 Download
  2. Installing 2017 11 Cumulative Update For Windows 10 Version 1607 Problems
  3. Installing 2017 11 Cumulative Update For Windows 10 Version 1607 To 1990

May 13, 2017 In reply to abbeyroad58's post on May 14, 2017. I have had this problem for several weeks: 2017-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4019472) - Failed to install on 5/14/2017. My computer runs Windows Pro and is very clean with no unusual changes. I have tried everything, clearing the Download file, cutting.

Installing 2017 11 cumulative update for windows 10 version 1607 to 1990-->

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.

Installing 2017 11 Cumulative Update For Windows 10 Version 1607 Download


February 2021

Installing 2017 11 Cumulative Update For Windows 10 Version 1607 Problems

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

Installing 2017 11 Cumulative Update For Windows 10 Version 1607 To 1990

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.