Windows 10, version 1903 and Windows Server, version 1903
- 10 minutes to read
Find information on known issues and the status of the rollout for Windows 10, version 1903 and Windows Server, version 1903. 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 November 9, 2020: On December 8, 2020, all editions of Windows 10, version 1903 and Windows 10 Server, version 1903 will reach end of service. After that date, devices running these versions of Windows will no longer receive monthly security and quality updates. To keep you protected and productive, we will soon begin updating devices running Windows 10, version 1903 to Windows 10, version 1909. This update will install like a monthly update, resulting in a far faster update experience. 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 more information on end of service dates for currently supported versions of Windows 10, see the Microsoft Lifecycle Policy search tool. |
Known issues
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.
Issue details
November 2020
Domain controllers in your enterprise might encounter Kerberos authentication issues | ||
| Status | Originating update | History | Resolved KB4594443 | OS Build 18362.1198 KB4586786 2020-11-10 | 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. | ||
October 2020
Certificates may not be present after updating to a newer version of Windows 10 | ||
| Status | Originating update | History | Mitigated | OS Build 18362.1110 KB4577062 2020-09-16 | Last updated: 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.
Next steps: Windows 10, version 1903 and Windows Server, version 1903 will reach end of service on December 8, 2020 and will no longer receive monthly security and quality updates after that date. We recommend you update the devices in your environment to a later version of Windows 10 or Windows Server, which have this issue resolved. 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. | ||
June 2020
Local Security Authority Subsystem Service (lsass.exe) might fail on some devices | ||
| Status | Originating update | History | Resolved KB4565483 | OS Build 18362.836 KB4556799 2020-05-12 | Resolved: 2020-07-14, 10:00 PT Opened: 2020-06-24, 12:46 PT |
The Local Security Authority Subsystem Service file (lsass.exe) might fail on some devices immediately after login with the error message in system event log Wininit event 1015 is logged with the text, “A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status code c0000008. The machine must now be restarted." c0000008 is an invalid handle error related to Credential Manager (VaultSvc) Service.
Resolution: This issue was resolved in KB4565483. | ||
February 2020
“Reset this PC” feature might fail | ||
| Status | Originating update | History | Mitigated | N/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”.
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:
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 | ||
| Status | Originating update | History | Mitigated | N/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.
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.
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. | ||
0 thoughts to “Downloading windows 10 1903”