What's new for Windows 10, version 1909 and Windows 10, version 1903 release notes
Windows 10, versions 1903 and 1909 share a common core operating system and an identical set of system files. As a result, the new features in Windows 10, version 1909 were included in the recent monthly quality update for Windows 10, version 1903 (released October 8, 2019), but are currently in a dormant state. These new features will remain dormant until they are turned on using an enablement package, which is a small, quick-to-install “master switch” that simply activates the Windows 10, version 1909 features.
To reflect this change, the release notes for Windows 10, version 1903 and Windows 10, version 1909 will share an update history page. Each release page will contain a list of addressed issues for both 1903 and 1909 versions. Note that the 1909 version will always contain the fixes for 1903; however, 1903 will not contain the fixes for 1909. This page will provide you with the build numbers for both 1909 and 1903 versions so that it will be easier for support to assist you if you encounter issues.
For more details about the enablement package and how to get the feature update, see the Windows 10, version 1909 delivery options blog.
For more information about the various types of Windows updates, such as critical, security, driver, service packs, and so on, please see the following article.
Note Follow @WindowsUpdate to find out when new content is published to the release information dashboard.
Highlights
- Updates an issue that prevents the speech platform application from opening for several minutes in a high noise environment.
- Updates an issue that reduces the image quality in the Windows Mixed Reality (WMR) home environment.
- Updates an issue that might prevent ActiveX content from loading.
- Improves the battery performance during Modern Standby mode.
- Updates an issue that causes Microsoft Narrator to stop working when a user session is longer than 30 minutes.
- Addresses an issue that adds an unwanted keyboard layout as the default after an upgrade even if you have already removed it.
- Updates an issue that prevents the Windows Search box from rendering properly.
- Updates an issue that prevents the printer settings user interface from displaying properly.
- Updates an issue that prevents some applications from printing to network printers.
Improvements and fixes
If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.
Windows Update Improvements
Microsoft has released an update directly to the Windows Update client to improve reliability. Any device running Windows 10 configured to receive updates automatically from Windows Update, including Enterprise and Pro editions, will be offered the latest Windows 10 feature update based on device compatibility and Windows Update for Business deferral policy. This doesn't apply to long-term servicing editions.
Known issues in this update
Symptom | Workaround |
Devices using a manual or auto-configured proxy, especially with a virtual private network (VPN), might show limited or no internet connection status in the Network Connectivity Status Indicator (NCSI) in the notification area. This might happen when connected to or disconnected from a VPN or after changing the state between the two. Devices with this issue might also have issues reaching the internet using applications that use WinHTTP or WinInet. Examples of apps that might be affected on devices in this state include, but are not limited to, Microsoft Teams, Microsoft Office, Microsoft Office 365, Microsoft Outlook, Internet Explorer 11, and some versions of Microsoft Edge. | This issue is resolved in KB4554364. |
Because of a bug, some customers who purchase a Windows 10 Pro Education device, may receive a genuine edition of Windows 10 Education. Windows 10 editions for education customers, Windows 10 Pro Education builds on the commercial version of Windows 10 Pro, and Windows 10 Education builds on Windows 10 Enterprise. This bug is not expected to introduce any negative experiences for customers. More information: Compare Windows 10 editions | A resolution for this issue will be released in a future servicing update that will prevent customers from entering this state. |
After installing this update on a Windows 10 device with a wireless wide area network (WWAN) LTE modem, reaching the internet might not be possible. However, the Network Connectivity Status Indicator (NCSI) in the notification area might still indicate that you are connected to the internet. | This issue is resolved in KB4559004. |
How to get this update
Before installing this update
Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system before installing the latest cumulative update (LCU). SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU. For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.
If you are using Windows Update, the latest SSU (KB4538674) will be offered to you automatically. To get the standalone package for the latest SSU, search for it in the Microsoft Update Catalog.
Install this update
Release Channel | Available | Next Step |
Windows Update or Microsoft Update | Yes | Go to Settings > Update & Security > Windows Update. In the Optional updates available area, you’ll find the link to download and install the update. |
Microsoft Update Catalog | Yes | To get the standalone package for this update, go to the Microsoft Update Catalog website. |
Windows Server Update Services (WSUS) | Yes | This update will automatically sync with WSUS if you configure Products and Classifications as follows: Product: Windows 10, version 1903 and later Classification: Updates |
File information
For a list of the files that are provided in this update, download the file information for cumulative update 4535996.
Note Some files erroneously have “Not applicable” in the “File version” column of the CSV file. This might lead to false positives or false negatives when using some third-party scan detection tools to validate the build.