This month’s patch Tuesday brings an update for the Windows 10 May 2019 Update (1903) version of Windows 10. The update is KB4512508 and takes the build number to 18362.267 and includes security fixes for Internet Explorer, Edge, Bluetooth and networking:
This security update includes quality improvements. Key changes include:
Security updates to Windows App Platform and Frameworks, Windows Storage and Filesystems, Microsoft Scripting Engine, Windows Input and Composition, Windows Wireless Networking, Windows Cryptography, Windows Datacenter Networking, Windows Virtualization, Windows Storage and Filesystems, the Microsoft JET Database Engine, Windows Linux, Windows Kernel, Windows Server, Windows MSXML, Internet Explorer, and Microsoft Edge.
There are still some know issues with the update but they are minor:
|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.|
|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.
|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 late August.|