Resolved issues in Windows 10, version 1909 and Windows Server, version 1909
See a list of known issues that have been resolved for Windows 10, version 1909 and Windows Server, version 1909 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.
|Summary||Originating update||Status||Date resolved|
|Stop error 0x7E in nwifi.sys with a blue screen when making WPA3 Wi-Fi connections|
You are more likely to encounter this issue when reconnecting to a Wi-Fi network.
|OS Build 18363.1350|
|Some games might fail to open, or you might receive an error|
You might have issues with some Direct3D games when using in-game overlay feature of Discord.
|OS Build 18363.1350|
|Resolved External||2021-02-08 |
|You might encounter issues with KB4524244|
You might encounter issues trying to install or after installing KB4524244
|“Reset this PC” feature might fail|
“Reset this PC” feature is also called “Push Button Reset” or PBR.
|Domain controllers in your enterprise might encounter Kerberos authentication issues|
Authentication and renewal issues for Kerberos ticket after installing updates released November 10, 2020.
|OS Build 18363.1198|
|Certificates may not be present after updating to a newer version of Windows 10|
Devices in a managed environment using update management tools or ISO images might lose certificates when updating.
|OS Build 18363.1110|
|Compatibility report shows unexpectedly during update to new version of Windows 10|
The dialog saying, "Continuing with the installation of Windows will remove some optional features."
|OS Build 18363.1016|
|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 18363.1139|
Stop error 0x7E in nwifi.sys with a blue screen when making WPA3 Wi-Fi connections
|Status||Originating update||History||Resolved KB5001028||OS Build 18363.1350|
|Resolved: 2021-02-11, 10:00 PT
Opened: 2021-02-11, 09:41 PT
You might receive stop error 0x7E in nwifi.sys with a blue screen when you attempt to use a Wi-Fi Protected Access 3 (WPA3) connection. You are more likely to encounter this issue when reconnecting to a Wi-Fi network after disconnecting, or when waking from sleep or hibernation. Note Most Wi-Fi networks are currently using WPA2 and are not affected.
Workaround: To mitigate this issue, you can do one of the following:
Resolution: This issue was resolved in the out-of-band update KB5001028. If you have automatic updates enabled, you will receive this update automatically and do not need to take any further action. It is a cumulative update, so you do not need to apply any previous update before installing it. The update is available on all release channels including Windows Update, Microsoft Update Catalog and Windows Server Update Services (WSUS).
Some games might fail to open, or you might receive an error
|Status||Originating update||History||Resolved External||OS Build 18363.1350|
|Last updated: 2021-02-08, 07:16 PT
Opened: 2021-02-08, 06:29 PT
Microsoft and Discord have found incompatibility issues with some games using Direct3D 12 when the in-game overlay feature of Discord is enabled. When attempting to open affected games you might receive an error, or the game might close silently.
Workaround: To mitigate this issue, you can turn off the in-game overlay in settings within the Discord app.
Resolution: This issue is now resolved in an update to the Discord app. To verify you're on the latest version, right click on the Discord icon in the notification area and select "Check for updates...". If there are updates to install, it should install automatically but you might need to select the arrow icon in the upper right corner of the app to install the updated version. There is no update for Windows needed to resolve this issue.
Domain controllers in your enterprise might encounter Kerberos authentication issues
|Status||Originating update||History||Resolved KB4594443||OS Build 18363.1198|
|Resolved: 2020-11-19, 10:00 PT
Opened: 2020-11-14, 01:39 PT
After installing KB4586786 on domain controllers (DCs) and read-only domain controllers (RODCs) in your environment, you might encounter Kerberos authentication issues. This is caused by an issue in how CVE-2020-17049 was addressed in these updates. As noted in CVE-2020-17049, there are three registry setting values for PerformTicketSignature to control it, but in the current implementation you might encounter different issues with each setting:
Note This issue only affects Windows Servers, Windows 10 devices and applications in enterprise environments.
Resolution: This issue was resolved in the out-of-band update KB4594443. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB4594443, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB4594443 is not available from Windows Update and will not install automatically.
Certificates may not be present after updating to a newer version of Windows 10
|Status||Originating update||History||Resolved||OS Build 18363.1110|
|Resolved: 2020-11-17, 02:11 PT
Opened: 2020-10-30, 05:16 PT
System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later and then proceed to update to a later version of Windows 10 from media or an installation source which does not have an LCU released October 13, 2020 or later integrated. This primarily happens when managed devices are updated using outdated bundles or media through an update management tool such as Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager. This might also happen when using outdated physical media or ISO images that do not have the latest updates integrated.
Note Devices using Windows Update for Business or that connect directly to Windows Update are not impacted. Any device connecting to Windows Update should always receive the latest versions of the feature update, including the latest LCU, without any extra steps.
Workaround: If you have already encountered this issue on your device, you can mitigate it within the uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you’re updating to. You will then need to update to the later version of Windows 10 after the issue is resolved in your environment. Note Within the uninstall window, you can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You must make this change before the default uninstall window has lapsed. For more information, see DISM operating system uninstall command-line options.
Resolution: This issue is now resolved when using the latest feature update bundles and refreshed media. Feature update bundles were released November 9, 2020 for Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. Refreshed media was released November 3, 2020 on Volume Licensing Service Center (VLSC) and Visual Studio Subscriptions (VSS, formerly MSDN Subscriptions). For information on verifying you're using the refreshed media, see How to address feature update refreshes in your environment. If you are using or creating custom media, you will need to include an update released October 13, 2020 or later.
Note If you are updating to Windows 10, version 20H2, this is only resolved with the feature update bundle released November 9, 2020. Refreshed media is not yet available on VLSC or VSS. Refreshed media for VLSC and VSS will be released in the coming weeks to address this issue and another known issue that requires a media refresh. Please check the known issue here for the status of the remaining Windows 10, version 20H2 known issue.
When installing incorrectly formatted third-party drivers, you might receive an error
|Status||Originating update||History||Resolved||OS Build 18363.1139|
|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:
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.
Compatibility report shows unexpectedly during update to new version of Windows 10
|Status||Originating update||History||Resolved KB4579919||OS Build 18363.1016|
|Resolved: 2020-10-13, 10:00 PT
Opened: 2020-09-18, 04:26 PT
When updating to Windows 10, version 1903 or Windows 10, version 1909 from any previous version of Windows 10, you might receive a compatibility report dialog with "What needs your attention" at the top and the error, "Continuing with the installation of Windows will remove some optional features. You may need to add them back in Settings after the installation completes." You might receive this compatibility warning when LOCAL SYSTEM accounts are blocked in a firewall from accessing the internet via HTTP. This is caused by the Windows 10 Setup Dynamic Update (DU) being unable to download required packages.
Workaround: If your device has access to HTTP blocked for LOCAL SYSTEM accounts, to mitigate this issue you can enable HTTP access for the Windows 10 Setup Dynamic Update (DU) using the LOCAL SYSTEM account. After you have allowed access, you can restart installation of the update and you should not see the warning. You can also continue by clicking the OK button or use the /compat IgnoreWarning command to ignore compatibility warnings but this might also ignore other warnings that your device might be affected by.
Resolution: This issue was resolved in KB4579919.
You might encounter issues with KB4524244
|Status||Originating update||History||Resolved||N/A |
|Resolved: 2021-01-12, 05:33 PT
Opened: 2020-02-15, 12:02 PT
You might encounter issues trying to install or after installing KB4524244.
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.
Resolution: This issue was resolved in KB4535680. This update should only be offered if it is applicable to your device. You might need to update UEFI firmware of your devices or adjust other settings before deploying this update. For more information, see KB4535680.
“Reset this PC” feature might fail
|Status||Originating update||History||Resolved KB4598479||N/A |
|Resolved: 2021-01-12, 10:00 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”.
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:
Resolution: This issue was resolved in KB4598479.