Windows 10, version 1607 and Windows Server 2016

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 20H2 is now available Windows 10, version 20H2 is now available
Find out how to get the update >
What’s new for IT pros What’s new for IT pros
Explore the latest features and servicing innovations in Windows 10, version 20H2 >

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
When installing incorrectly formatted third-party drivers, you might receive an error
You might receive, “Windows can’t verify the publisher of this driver software” or other errors.
OS Build 14393.3986
KB4580346
2020-10-13
Resolved
2020-10-20
10:06 PT
Unable to access Security Options section in Group Policy Management Console
You might receive an error "MMC has detected an error in a snap-in." or “MMC cannot initialize the snap-in”.
OS Build 14393.3930
KB4577015
2020-09-08
Resolved
KB4580346
2020-10-13
10:00 PT
“Reset this PC” feature might fail
“Reset this PC” feature is also called “Push Button Reset” or PBR.
N/A
KB4524244
2020-02-11
Mitigated
2020-02-15
01:22 PT
You might encounter issues with KB4524244
You might encounter issues trying to install or after installing KB4524244
N/A
KB4524244
2020-02-11
Mitigated
2020-02-15
01:22 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

October 2020

When installing incorrectly formatted third-party drivers, you might receive an error

StatusOriginating updateHistory
ResolvedOS Build 14393.3986
KB4580346
2020-10-13
Resolved: 2020-10-20, 10:06 PT
Opened: 2020-10-13, 09:37 PT
When installing a third-party driver, you might receive the error, “Windows can’t verify the publisher of this driver software”. You may also see the error “No signature was present in the subject” when attempting to view the signature properties using Windows Explorer.

This issue occurs when one or more of the following is present in a driver package:
  • an improperly formatted catalog file is identified during validation by Windows. Starting with this release, Windows will require the validity of DER encoded PKCS#7 content in catalog files. Catalogs files must be signed per section 11.6 of describing DER-encoding for SET OF members in X.690.
  • a driver catalog file extension is not one of the supported extensions.
Affected platforms:
  • Client: Windows 10, version 20H2, Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1
  • Server: Windows Server, version 20H2, Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2
Next steps: If this happens you should contact the driver vendor or device manufacturer (OEM) and ask them for an updated driver to correct the issue.

September 2020

Unable to access Security Options section in Group Policy Management Console

StatusOriginating updateHistory
Resolved
KB4580346
OS Build 14393.3930
KB4577015
2020-09-08
Resolved: 2020-10-13, 10:00 PT
Opened: 2020-09-23, 06:37 PT
Accessing the Security Options data view in the Group Policy Management Editor (gpedit.msc) or Local Security Policy Editor (secpol.msc) might fail with the error "MMC has detected an error in a snap-in. It is recommended that you shut down and restart MMC" or “MMC cannot initialize the snap-in”. This occurs from the MMC window, when the console tree is expanded in the following sequence: select Computer Configuration, then Policies, then Windows Settings, then Security Settings, then Local Policies, then Security Options.

The resulting error dialog provides options to continue using the Management Console to view other nodes normally. Note: This issue does not affect the application of the Security Options or any other Group Policy Objects (GPOs) to devices in your environment.

Affected platforms:
  • Client: Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server 2016
Resolution: This issue was resolved in KB4580346.

February 2020

“Reset this PC” feature might fail

StatusOriginating updateHistory
MitigatedN/A
KB4524244
2020-02-11
Last updated: 2020-02-15, 01:22 PT
Opened: 2020-02-15, 12:02 PT
Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update.

If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
  5. Upon restart use the “Reset this PC” feature and you should not encounter this issue.

Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

You might encounter issues with KB4524244

StatusOriginating updateHistory
MitigatedN/A
KB4524244
2020-02-11
Last updated: 2020-02-15, 01:22 PT
Opened: 2020-02-15, 12:02 PT
You might encounter issues trying to install or after installing KB4524244.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Workaround: To help a sub-set of affected devices, the standalone security update ( KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
 
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

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, 02: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.