UPDATE 9/10: Cumulative Update KB4515384 Windows 10 v1903 build 18362.356 Sept. 10

July 9, 2019 - KB4507453 (OS Build 18362.239)

Applies to: Windows 10 version 1903, Windows Server version 1903

---

Note Follow @WindowsUpdate to find out when new content is published to the release information dashboard.

Note This release also contains updates for Microsoft HoloLens (OS Build 18362.1024) released July 9, 2019. Microsoft will release an update directly to the Windows Update Client to improve Windows Update reliability on Microsoft HoloLens that have not updated to this most recent OS Build.

For more information about the various types of Windows updates, such as critical, security, driver, service packs, etc., please see the following article.

July 19, 2019 - IMPORTANT: Beginning with the July 2019 updates, Active Directory domain controllers will intentionally block unconstrained delegation across forest, external, and quarantined trusts. Authentication requests for services that use unconstrained delegation over the listed trust types will fail when you request new tickets. Administrators should reconfigure the affected services to use resource-based constrained delegation. For more information, see KB4494025.

Highlights

• Updates an issue with a tilted world some Mixed Reality users may see after connecting their headsets.
• Updates the visual quality issues some users may have when using Windows Mixed Reality (WMR) headsets with Steam®VR content.
• Updates an issue with BitLocker encryption recovery mode.
• Updates to improve security when using Internet Explorer, Microsoft Edge, wireless technologies, and Microsoft Office products.

Improvements and fixes

This update includes quality improvements. Key changes include:

• Addresses an issue that may cause BitLocker to go into recovery mode if BitLocker is being provisioned at the same time as updates are being installed.
• Addresses an issue that may cause Mixed Reality users to see a tilted world after connecting their headsets.
• Addresses visual quality issues some users may have seen with Windows Mixed Reality (WMR) headsets and Steam®VR content.
• Security updates to Windows Wireless Networking, Microsoft Scripting Engine, Windows Server, Windows Storage and Filesystems, Windows Kernel, Microsoft HoloLens, Internet Explorer, Windows Input and Composition, Windows Virtualization, Windows App Platform and Frameworks, Microsoft Graphics Component, Microsoft Edge, and Windows Cryptography.

If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.

For more information about the resolved security vulnerabilities, please refer to the Security Update Guide.

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
Windows Sandbox may fail to start with "ERROR_FILE_NOT_FOUND (0x80070002)" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.	Microsoft is working on a resolution and will provide an update in an upcoming release.
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” on devices where the diagnostic data level is manually configured to the non-default setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”. This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with or without device tunnel. This does not affect manual only VPN profiles or connections.	To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings. Set the value for the following group policy settings: Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full) Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection Setting: AllowTelemetry Type: REG_DWORD Value: 1, 2 or 3 Note If the Remote Access Connection Manager service is not running after setting the Group Policy or registry key, you will need to manually start the service or restart the device. We are working on a resolution and estimate a solution will be available in late July.
After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected. Note Users who have already migrated from Window-Eyes to Freedom Scientific's other screen reader, JAWS, should not be affected by this issue.	We are working on a resolution and will provide an update in an upcoming release.
[ADDED 7/10] Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM) may fail to start with the error "Status: 0xc0000001, Info: A required device isn't connected or can't be accessed" after installing this update on a WDS server.	For mitigation instructions, see KB4512816. We are working on a resolution and will provide an update in an upcoming release.
[ADDED 7/26] Devices connected to a domain that is configured to use MIT Kerberos realms may not start up or may continue to restart after installation of this update. Devices that are domain controllers or domain members are both affected. If you are not sure if your device is affected, contact your administrator. Advanced users can check if this registry key exists HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\MitRealms or for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos.	At this time, we suggest that devices in an affected environment do not install this update. We are working on a resolution and estimate a solution will be available in mid-August.

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 and applying Microsoft security fixes. For more information, see Servicing stack updates.

If you are using Windows Update, the latest SSU (KB4509096) 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 and Microsoft Update	Yes	None. This update will be downloaded and installed automatically from Windows 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 synchronize with WSUS if you configure Products and Classifications as follows: Product: Windows 10, version 1903 and later Classification: Security Updates

File information

For a list of the files that are provided in this update, download the file information for cumulative update 4507453.

Source: https://support.microsoft.com/en-us/help/4507453

Direct download links for KB4507453 MSU file from Microsoft Update Catalog:

Download KB4507453 MSU for Windows 10 v1903 32-bit (x86) - 98.4 MB

Download KB4507453 MSU for Windows 10 v1903 64-bit (x64) - 222.4 MB

   Tip

How to Find Windows 10 Version Number

How to Find Windows 10 Build Number

Known issues for Windows 10 May 2019 Update version 1903

Posted By: Brink
09 Jul 2019