September 16, 2020—KB4577062 (OS Builds 18362.1110 and 18363.1110) Preview
Applies To
Windows 10, version 1903, all editions Windows Server version 1903 Windows 10, version 1909, all editions Windows Server version 1909Tanggal Rilis:
16/09/2020
Versi:
1903-OS Build 18362.1110 and 1909-OS Build 18363.18363.1110
IMPORTANT Starting in July 2020, we will resume non-security releases for Windows 10 and Windows Server, version 1809 and later. There is no change to the cumulative monthly security updates (also referred to as the "B" release or Update Tuesday release). For more information, see the blog post Resuming optional Windows 10 and Windows Server non-security monthly updates.
IMPORTANT Starting in July 2020, all Windows Updates will disable the RemoteFX vGPU feature because of a security vulnerability. For more information about the vulnerability, seeCVE-2020-1036 and KB4570006. After you install this update, attempts to start virtual machines (VM) that have RemoteFX vGPU enabled will fail, and messages such as the following will appear:
If you re-enable RemoteFX vGPU, a message similar to the following will appear:
-
“The virtual machine cannot be started because all the RemoteFX-capable GPUs are disabled in Hyper-V Manager.”
-
“The virtual machine cannot be started because the server has insufficient GPU resources.”
-
"We no longer support the RemoteFX 3D video adapter. If you are still using this adapter, you may become vulnerable to security risk. Learn more (https://go.microsoft.com/fwlink/?linkid=2131976)”
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
-
Adds a notification to Internet Explorer 11 that informs users about the end of support for Adobe Flash in December 2020. For more information, see KB4581051.
-
Updates an issue that causes certain apps to go into an unwanted repair cycle. As a result, a user cannot use that app during that time.
-
Updates an issue that might display 4K high dynamic range (HDR) content darker than expected when you configure certain non-HDR systems for HDR Streaming.
-
Updates an issue to reduce the likelihood of missing fonts.
-
Updates an issue that causes a device to stop responding after you have been using a pen for several hours.
-
Reduces distortions and aberrations in Windows Mixed Reality head-mounted displays (HMD).
-
Updates an issue on some dual graphics processing unit (GPU) devices that prevent connections to a Miracast receiver.
-
Updates an issue in the user experience (UX) that prevents you from connecting or reconnecting to a Miracast receiver.
Improvements and fixes
This non-security update includes quality improvements. Key changes include:
-
This build includes all the improvements from Windows 10, version 1903.
-
No additional issues were documented for this release.
This non-security update includes quality improvements. Key changes include:
-
Adds a notification to Internet Explorer 11 that informs users about the end of support for Adobe Flash in December 2020. For more information, see KB4581051.
-
Addresses an issue with Microsoft Edge IE Mode that occurs when you enable Configure enhanced hang detection for Internet Explorer mode in Microsoft Edge.
-
Addresses an issue that causes certain apps to go into an unwanted repair cycle. As a result, a user cannot use that app during that time.
-
Addresses an issue that, in certain scenarios, causes applications to stop working if they are created using Visual Basic for Applications (VBA). The error is, “Class not registered” error.
-
Addresses an issue that might display an empty black screen when a device is connecting to a Windows Virtual Desktop (WVD) machine.
-
Addresses an issue that might display 4K high dynamic range (HDR) content darker than expected when you configure certain non-HDR systems for HDR Streaming.
-
Addresses an issue that causes a stop error when the initialization of the graphics adapter fails.
-
Addresses an issue to reduce the likelihood of missing fonts.
-
Addresses an issue that causes a device to stop responding after you have been using a pen for several hours.
-
Addresses an issue that fails to recognize the first East Asian language character typed into a Microsoft Foundation Class Library (MFC) DataGrid.
-
Addresses an issue in which selecting I forgot my Pin from Settings>Accounts>Sign-in options fails in a Windows Hello for Business On-Premise deployment.
-
Addresses an issue that causes File Explorer to close unexpectedly when you use a Ribbon shell extension under specific circumstances.
-
Addresses an issue that affects default application associations during certain upgrade scenarios. This might cause numerous toast notifications to appear when you first sign in after the upgrade.
-
Addresses an issue that generates a "No features to install" message when you add a feature, even if you provide administrative credentials.
-
Addresses an issue that causes a stop error when using Microsoft Surface Slim Pen on certain editions of Microsoft Surface Pro X or Microsoft Surface Laptop 3.
-
Updates 2021 time zone information for Fiji.
-
Addresses stop error 0xC2 in usbccgp.sys.
-
Addresses an issue that causes random line breaks when you redirect PowerShell console error output.
-
Addresses an issue with creating HTML reports using tracerpt.
-
Allows the DeviceHealthMonitoring Cloud Service Plan (CSP) to run on Windows 10 Business and Windows 10 Pro editions.
-
Addresses an issue that prevents the content under HKLM\Software\Cryptography from being carried over during Windows feature updates.
-
Addresses an issue that displays an error that states that a smart card PIN change was not successful even though the PIN change was successful.
-
Addresses an issue that might create duplicate Foreign Security Principal directory objects for Authenticated and Interactive users in the domain partition. As a result, the original directory objects have “CNF” added to their names and are mangled. This issue occurs when you promote a new domain controller using the CriticalReplicationOnly flag.
-
Addresses an issue that prevents you from enabling BitLocker after installing the Server Core App Compatibility Feature on Demand (FOD).
-
Addresses an issue that causes an access violation in lsass.exe when a process is started using the runas command in some circumstances.
-
Addresses an issue in which Windows Defender Application Control enforces package family name rules that should be audit only.
-
Addresses an issue, which occurs after an update, that causes devices that have the Dynamic Root of Trust for Measurement (DRTM) enabled to unexpectedly reset when hibernating.
-
Updates the configuration of Windows Hello Face recognition to work well with 940nm wavelength cameras.
-
Reduces distortions and aberrations in Windows Mixed Reality head-mounted displays (HMD).
-
Ensures that new Windows Mixed Reality HMDs meet minimum specification requirements and default to a 90Hz refresh rate.
-
Addresses an issue that causes a stop error on a Hyper-V host when a virtual machine (VM) issues a specific Small Computer System Interface (SCSI) command.
-
Addresses an issue that prevents Always On VPN (AOVPN) from automatically reconnecting when resuming from Sleep or Hibernate.
-
Adds an Azure Active Directory (AAD) Device Token that is sent to Windows Update (WU) as part of each WU scan. WU can use this token to query for membership in groups that have an AAD Device ID.
-
Addresses an issue that fails to log events 5136 for group membership changes in certain scenarios. This occurs when you use the “Permissive Modify” control; for example, the Active Directory (AD) PowerShell modules use this control.
-
Addresses an issue with the Microsoft Cluster Shared Volumes File Systems (CSVFS) driver that prevents Win32 API access to SQL Server Filestream data. This occurs when the data is stored on a Cluster Shared Volume in a SQL Server failover cluster instance, which is on an Azure VM.
-
Addresses an issue that causes a deadlock when Offline Files are enabled. As a result, CscEnpDereferenceEntryInternal holds parent and child locks.
-
Addresses an issue that causes deduplication jobs to fail with stop error 0x50 when you call HsmpRecallFreeCachedExtents().
-
Addresses an issue that causes applications stop working when they use Microsoft’s Remote Desktop sharing APIs. The breakpoint exception code is 0x80000003.
-
Removes the HTTP call to www.microsoft.com that the Remote Desktop Client (mstsc.exe) makes at sign out when using a Remote Desktop Gateway.
-
Adds support for certain new Windows Mixed Reality motion controllers.
-
Addresses an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.
-
Addresses an issue with setting the “Restrict delegation of credentials to remote servers” Group Policy with the “Restrict Credential Delegation” mode on the RDP client. As a result, the Terminal Server service tries to use “Require Remote Credential Guard” mode first and will only use “Require Restricted Admin” if the server does not support “Require Remote Credential Guard".
-
Addresses an issue that causes an application to flicker or stop responding when sharing the application using Microsoft Teams.
-
Addresses an issue on some dual graphics processing unit (GPU) devices that prevent connections to a Miracast receiver.
-
Addresses an issue in the user experience (UX) that prevents you from connecting or reconnecting to a Miracast receiver.
-
Changes BitLocker behavior by preventing you from using BitLocker on file systems that are on an active master boot record (MBR) drive. When you attempt to use BitLocker on active MBR drives, you might see the following:
-
“ERROR: The volume X: could not be opened by BitLocker. This may be because the volume does not exist, or because it is not a valid BitLocker volume.”
-
“The drive cannot be encrypted because it contains system boot information……”
Additionally, the BitLocker encryption command will be missing from the context menu in File Explorer.
-
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 |
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. |
This issue is resolved in KB4579919. |
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. |
This issue is resolved in KB4592449. |
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 (KB4576751) 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) |
No |
You can import this update into WSUS manually. See the Microsoft Update Catalog for instructions. |
File information
For a list of the files that are provided in this update, download the file information for cumulative update 4577062.
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.