Windows 11 is now available
Explore this latest release.
Windows 10, version 1909 and Windows Server, version 1909
Find information on known issues and the status of the rollout for Windows 10, version 1909 and Windows Server, version 1909. 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.
Current status as of May 11, 2021:
As of May 11, 2021, the Home and Pro editions of Windows 10, version 1909 and all editions of Windows Server, version 1909 have reached end of servicing. Devices running these editions will no longer receive monthly security and quality updates containing protections from the latest security threats. Education, Enterprise, and IoT Enterprise editions of Windows 10, version 1909 will reach end of servicing May 11, 2022.
As always, we recommend that you update your devices to the latest version of Windows 10 as soon as possible to ensure that you can take advantage of the latest features and advanced protections from the latest security threats. For information about servicing timelines and lifecycle, see the Windows 10 release information and Lifecycle FAQ - Windows.
- How to get Windows 11
Explore the upgrade experience.
Known issues
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| Receiving a prompt for administrative credentials every time you attempt to print This issue affects devices in environments in which the print server and print client are in different times zones. | OS Build 18363.1801 KB5005566 2021-09-14 | Resolved KB5006667 | 2021-10-12 10:00 PT |
| Custom printing properties might not be correctly provided to print server clients This issue will not cause printing operations to fail, but clients might print with default settings only | OS Build 18363.1832 KB5005624 2021-09-21 | Resolved KB5006667 | 2021-10-12 10:00 PT |
| Apps might fail to open, close unexpectedly or become unresponsive Devices using Microsoft Exploit Protection Export Address Filtering (EAF) might have issues with some apps. | OS Build 18363.1766 KB5005103 2021-08-26 | Resolved KB5006667 | 2021-10-12 10:00 PT |
| Installation of printers might fail when attempted over some network connections This issue has been observed in devices which access printers via a print server using HTTP connections | OS Build 18363.1801 KB5005566 2021-09-14 | Resolved KB5005624 | 2021-09-21 15:00 PT |
| Azure Virtual Desktops may not be able to update via Windows Server Update Services Manual download and installation of security updates is available, and may be necessary. | N/A | Resolved KB5005566 | 2021-09-14 10:00 PT |
| Installation of printers via Internet Printing Protocol (IPP) might not succeed Affects organizations that share an IPP printer using printer connections | OS Build 18363.1801 KB5005566 2021-09-14 | Confirmed | 2021-10-13 16:16 PT |
Issue details
October 2021
Receiving a prompt for administrative credentials every time you attempt to print | ||
| Status | Originating update | History | Resolved KB5006667 | OS Build 18363.1801 KB5005566 2021-09-14 | Resolved: 2021-10-12, 10:00 PT Opened: 2021-10-15, 17:21 PT |
After installing KB5005566 or later updates, you might receive a prompt for administrative credentials every time you attempt to print in environments in which the print server and print client are in different times zones. Note The affected environments described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations. Affected platforms:
Resolution: This issue was resolved in KB5006667. If after installing KB5006667 you still receive the prompt every time you print, see Q1 in the "Frequently ask questions" section of KB5005652—Manage new Point and Print default driver installation behavior (CVE-2021-34481). | ||
Custom printing properties might not be correctly provided to print server clients | ||
| Status | Originating update | History | Resolved KB5006667 | OS Build 18363.1832 KB5005624 2021-09-21 | Resolved: 2021-10-12, 10:00 PT Opened: 2021-10-13, 12:28 PT |
After installing KB5005624 on a print server, printing properties defined on that server might not be correctly provided to clients. Note this issue is specific to print servers and does not impact standard network printing. This issue will not cause printing operations to fail, however, custom settings defined on the server – for example, duplex print settings – will not be applied automatically, and clients will print with default settings only. This issue results from an improper building of the data file which contains the printer properties. Clients which receive this data file will not be able to use the file content and will instead proceed with default printing settings. Clients who have previously received the settings package prior to the installation of KB5005624 are unaffected. Servers which use default print settings and have no custom settings to provide to clients are unaffected. Note: The printer connection methods described in this issue are not commonly used by devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations. Workaround: IT administrators with admin privileges can still install printer drivers on the client through other means, such as copying packaged drivers from a known good package location. Additionally, clients can still be modified manually to adopt desired printer settings. Resolution: This issue was resolved in KB5006667. Affected platforms:
| ||
Installation of printers might fail when attempted over some network connections | ||
| Status | Originating update | History | Resolved KB5005624 | OS Build 18363.1801 KB5005566 2021-09-14 | Resolved: 2021-09-21, 15:00 PT Opened: 2021-10-13, 12:26 PT |
After installing KB5005566, devices which attempt to connect to a network printer for the first time might fail to download and install the necessary printer drivers. Devices which had connected to and installed the printer prior to the installation of KB5005566 are unaffected and operations to that printer will succeed as usual. This issue has been observed in devices which access printers via a print server using HTTP connections. When a client connects to the server to install the printer, a directory mismatch occurs, which causes the installer files to generate incorrectly. As a result, the drivers may not download. Note: The printer connection methods described in this issue are not commonly used by devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations. Workaround: IT administrators with admin privileges can still install printer drivers on the client through other means, such as copying packaged drivers from a known good package location. Only the automatic download and installation processes are impacted by this issue. Resolution: This issue was resolved in KB5005624. Affected platforms:
| ||
Installation of printers via Internet Printing Protocol (IPP) might not succeed | ||
| Status | Originating update | History | Confirmed | OS Build 18363.1801 KB5005566 2021-09-14 | Last updated: 2021-10-13, 16:16 PT Opened: 2021-10-13, 12:32 PT |
After installing KB5005566, installation of printers using Internet Printing Protocol (IPP) might not complete successfully. Devices which had connected to and installed the printer prior to the installation of KB5005566 are unaffected and print operations to that printer will succeed as usual. Note: IPP is not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations. Next steps: Microsoft is working on a resolution and targeting its release in a future update. Affected platforms:
| ||
September 2021
Apps might fail to open, close unexpectedly or become unresponsive | ||
| Status | Originating update | History | Resolved KB5006667 | OS Build 18363.1766 KB5005103 2021-08-26 | Resolved: 2021-10-12, 10:00 PT Opened: 2021-09-24, 11:00 PT |
After installing KB5005103 or a later update on devices using Microsoft Exploit Protection Export Address Filtering (EAF), you might have issues with some applications. You might be experiencing this issue if apps fail to open, fail to open files, or you might receive a white window when attempting to login. Affected platforms:
Resolution: This issue was resolved in KB5006667, released October 12, 2021. If you install an update released October 12, 2021 ( KB5006667) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before October 12, 2021, you can resolve this issue using KIR. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy (preferred) or setting a registry key according to the version of Windows you are using. Important Verify that you are using the correct Group Policy or registry key for your version of Windows. Group Policy (preferred):
For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Note Devices need to be restarted after configuring the special Group Policy or adding the registry key. Registry Key: 1, Open a Command Prompt window (cmd.exe) with elevated permissions. 2, Type the following command depending on which Windows version you are using and then press Enter. Windows Sever 2022: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 2801335948 /t REG_DWORD /d 0 /f Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 2767781516 /t REG_DWORD /d 0 /f Windows 10, version 1909: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 928713355 /t REG_DWORD /d 0 /f Windows 10, version 1809, Windows Server 2019: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 2371422858 /t REG_DWORD /d 0 /f 3, All version of Windows require a restart of the device for the registry key to take effect. Before restarting Windows 10, version 1909, Windows 10, version 1809 and Windows Server 2019, you will need to also run following command from elevated PowerShell prompt: Get-ScheduledTask -TaskName "ReconcileFeatures" | Start-ScheduledTask | ||
July 2021
Azure Virtual Desktops may not be able to update via Windows Server Update Services | ||
| Status | Originating update | History | Resolved KB5005566 | N/A | Resolved: 2021-09-14, 10:00 PT Opened: 2021-07-02, 12:40 PT |
We are investigating an issue where devices running Windows 10 Enterprise multi-session, version 1909 might not be able to download updates later than May 2021. This is observed in the Settings app under the Windows Update setting, which will display the message "You're up to date" even if no updates later than May 2021 have been installed. Workaround: There are 2 alternatives to resolve this issue. As the latest images from the Azure Marketplace will be up-to-date with all of the security updates, redeployment of images to existing devices will solve this issue. If redeployment is not an option, security updates can still be installed manually on these devices, via downloads from the Microsoft Update Catalog. For instructions, please see KB5004926 and review the Workaround section. Affected platforms:
Resolution: This issue was resolved in KB5005566. Reminder: As of May 11, 2021, the Home and Pro editions of Windows 10, version 1909 have reached end of servicing. Devices running these editions will no longer receive monthly security or quality updates and will need to update to a later version of Windows 10 to resolve this issue. | ||