Microsoft releases Windows 10 builds 17134.915, 16299.1296 - here's what's new

One week ago, it was Patch Tuesday, the day that Microsoft released cumulative updates for all supported versions of Windows. That's not where the story ends though, because the company frequently releases additional updates throughout the month.

Some of those updates are arriving today, as new cumulative updates are available for Windows 10 versions 1803, 1709, 1703, and 1607. These updates, however, are optional. That means that you can pull them down through Windows Update if you choose to, but they won't install automatically.

If you're on the Windows 10 April 2018 Update, or version 1803, you're going to get KB4507466, which brings the build number to 17134.915. You can manually download it here, and it has the following highlights:

  • Updates an issue that prevents a device from recognizing a Microsoft account until you sign out and sign in again.

  • Updates an issue that affects applications that manage files, folders, and device settings.

  • Improves compatibility with the Window-Eyes screen reader application.

  • Updates an issue to keep your App permissions settings when resetting your device.

Here's what got fixed:

  • Addresses a performance issue that may occur on some websites that use WebAssembly.
  • Addresses an issue that may prevent the personal identification number (PIN) prompt from appearing when authenticating in Internet Explorer.

  • Updates time zone information for Brazil.

  • Addresses an issue that fails to bypass automatic sign in (Autologon) when you press and hold the Shift key during startup.

  • Addresses an issue that prevents the Windows Event Log service from processing notifications that the log is full. This causes issues with some Event Log behaviors such as archiving the log when it reaches a maximum file size and you’ve configured the "Archive the log when full, do not overwrite events" setting. Additionally, the Local Security Authority (LSA) cannot handle CrashOnAuditFail scenarios when the Security Log is full, and events cannot be written.

  • Addresses an issue that prevents a system from recognizing a Microsoft account or Azure Active Directory account until the user signs out and signs in again.

  • Addresses an issue that may prevent the Netlogon service from establishing a secure channel and reports the error, “0xC000007A – ERROR_PROC_NOT_FOUND.”

  • Addresses an issue that fails to update the PIN policy (minimum length, required digits and special characters, etc.) for Windows Hello for Business when a PIN already exists on the machine.

  • Addresses an issue that may sometimes cause systems that have Trusted Platform Module (TPM) devices to stop working.

  • Addresses an issue that may cause authentication to fail when using Windows Hello for Business on a server running Windows Server 2016 with the Server Core option installed.

  • Addresses an issue that causes a device to stop working because of a race condition between stream tear down and sync root disconnect.

  • Addresses an issue that causes applications that use windows.storage.dll to stop working and displays ExceptionCode c0000005 (Access violation) when the process closes.

  • Reinforces the Certificate Revocation List (CRL) on Internet Key Exchange version 2 (IKEv2) machines for certificate-based virtual private network (VPN) connections, such as Device Tunnel, in an Always On VPN deployment.

  • Improves performance for Server Message Block (SMB) clients that have directories that contain more than 500,000 files.

  • Addresses an issue that prevents Microsoft Application Virtualization (App-V) scripting from working if you run it when you’re not connected to a domain controller (DC). App-V scripting also fails when you run it in an environment that only contains Microsoft Azure Active Directory.

  • Addresses an issue with opening or using the Window-Eyes screen reader application that may result in an error and prevent some features from functioning as expected.

  • Addresses an issue that may fail to keep App permissions settings when you select Keep my files after selecting Reset this PC.

  • Addresses an issue that may cause a cluster node to lose membership in a cluster and cause all its workloads to fail over. This issue may occur when a cluster node creates a Live Dump.

There are also a few known issues to be aware of:

Symptom Workaround
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.

Do one of the following:

  • Perform the operation from a process that has administrator privilege.
  • Perform the operation from a node that doesn’t have CSV ownership.
Microsoft is working on a resolution and will provide an update in an upcoming release.
We are investigating reports that a small number of devices may startup to a black screen during the first logon after installing updates.

To mitigate this issue, press Ctrl+Alt+Delete, then select the Power button in the lower right corner of the screen and select Restart. Your device should now restart normally.

We are 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.


For those that are on the Windows 10 Fall Creators Update, or version 1709, you'll get KB4507465, which brings the build number to 16299.1296. It's worth noting that this version, as well as version 1703, is only supported for Enterprise and Education SKUs. You can manually download it here, and it contains the following highlights:

  • Updates an issue that affects applications that manage files, folders, and device settings.

  • Improves compatibility with the Window-Eyes screen reader application.

Here's what got fixed:

  • Addresses a performance issue that may occur on some websites that use WebAssembly.
  • Updates time zone information for Brazil.

  • Addresses an issue that may prevent the personal identification number (PIN) prompt from appearing when authenticating in Internet Explorer.

  • Addresses an issue that may prevent the Netlogon service from establishing a secure channel and reports the error, “0xC000007A – ERROR_PROC_NOT_FOUND.”

  • Reinforces the Certificate Revocation List (CRL) on Internet Key Exchange version 2 (IKEv2) machines for certificate-based virtual private network (VPN) connections, such as Device Tunnel, in an Always On VPN deployment.

  • Addresses an error in the New Technology File System (NTFS).

  • Addresses an issue that causes applications that use windows.storage.dll to stop working and displays ExceptionCode c0000005 (Access violation) when the process closes.

  • Addresses an issue that prevents Microsoft Application Virtualization (App-V) scripting from working if you run it when you’re not connected to a domain controller (DC). App-V scripting also fails when you run it in an environment that only contains Microsoft Azure Active Directory.

  • Addresses an issue with opening or using the Window-Eyes screen reader application that may result in an error and prevent some features from functioning as expected.

  • Addresses an issue that may cause a cluster node to lose membership in a cluster and cause all its workloads to fail over. This issue may occur when a cluster node creates a Live Dump.

This update contains only the first and third known issues as the update listed above.

For those on the Windows 10 Creators Update, or version 1703, you'll get KB4507467, bringing the build number to 15063.1955. You can manually download it here, and it contains the following highlights:

  • Updates an issue that affects applications that manage files, folders, and device settings.

  • Improves compatibility with the Window-Eyes screen reader application.

Here's what got fixed:

  • Addresses an issue that may prevent the personal identification number (PIN) prompt from appearing when authenticating in Internet Explorer.
  • Updates time zone information for Brazil.

  • Addresses an issue that may prevent the Netlogon service from establishing a secure channel and reports the error, “0xC000007A – ERROR_PROC_NOT_FOUND.”

  • Addresses an issue that causes applications that use windows.storage.dll to stop working and displays ExceptionCode c0000005 (Access violation) when the process closes.

  • Addresses an issue that prevents Microsoft Application Virtualization (App-V) scripting from working if you run it when you’re not connected to a domain controller (DC). App-V scripting also fails when you run it in an environment that only contains Microsoft Azure Active Directory.

  • Addresses an issue with opening or using the Window-Eyes screen reader application that may result in an error and prevent some features from functioning as expected.

  • Addresses an issue that may cause a cluster node to lose membership in a cluster and cause all its workloads to fail over. This issue may occur when a cluster node creates a Live Dump.

This one only has one known issue, the first one on the above list.

Finally, those on the Windows 10 Anniversary Update, or version 1607, will get KB4507459, bringing the build number to 14393.3115. This is only for LTSC and Windows Server 2016 customers. You can manually download it here, and it contains the following highlights:

  • Addresses an issue that may prevent the personal identification number (PIN) prompt from appearing when authenticating in Internet Explorer.

  • Addresses an issue with leaking Windows notification sockets that causes Windows to run out of ports.

  • Updates time zone information for Brazil.

  • Addresses an issue that displays the Power button on the Ctrl+Alt+Del screen when the "User Configuration\Administrative Templates\Start Menu and Taskbar\Remove and prevent access to the Shut Down, Restart, Sleep, and Hibernate commands" policy is enabled.

  • Addresses an issue that fails to bypass automatic sign in (Autologon) when you press and hold the Shift key during startup.

  • Addresses an issue that may prevent the Netlogon service from establishing a secure channel and reports the error, “0xC000007A – ERROR_PROC_NOT_FOUND.”

  • Addresses an issue that causes Windows Defender Application Control to generate too many events related to dynamic code generation.

  • Addresses an issue that causes applications that use windows.storage.dll to stop working and displays ExceptionCode c0000005 (Access violation) when the process closes.

  • Addresses an issue that causes the Storage Spaces Direct (S2D) pool to lose Pool Quorum and prevents access to the S2D volumes if you restart one of the S2D cluster nodes.

  • Addresses an issue in Microsoft Remote Desktop Web Access (RDWeb) that allows user passwords to be updated even if there is a "Confirm New Password" field error.

  • Addresses an issue that may cause a Remote Desktop Server to stop responding when someone who is using drive redirection disconnects.

  • Addresses an issue that may prevent some applications from running as expected on clients of Active Directory Federation Services 2016 (AD FS 2016) after installing KB4493473 on the server. Applications that may exhibit this behavior use an IFRAME during non-interactive authentication requests and receive X-Frame Options set to DENY.

  • Addresses an issue that prevents Microsoft Application Virtualization (App-V) scripting from working if you run it when you’re not connected to a domain controller (DC). App-V scripting also fails when you run it in an environment that only contains Microsoft Azure Active Directory.

  • Addresses an issue with opening or using the Window-Eyes screen reader application that may result in an error and prevent some features from functioning as expected.

  • Addresses an issue that may cause a cluster node to lose membership in a cluster and cause all its workloads to fail over. This issue may occur when a cluster node creates a Live Dump.

This one has several known issues:

Symptom Workaround

For hosts managed by System Center Virtual Machine Manager (SCVMM), SCVMM cannot enumerate and manage logical switches deployed on the host after installing the update.

Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.
  1. Run mofcomp on the following mof files on the affected host:
    1. Scvmmswitchportsettings.mof
    2. VMMDHCPSvr.mof
  2. Follow the best practices while patching to avoid a stop error in vfpext.sys in an SDN v2 environment (NC managed hosts).
After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.

Set the domain default "Minimum Password Length" policy to less than or equal to 14 characters.

Microsoft is working on a resolution and will provide an update in an upcoming release.

Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.

Do one of the following:

  • Perform the operation from a process that has administrator privilege.
  • Perform the operation from a node that doesn’t have CSV ownership.
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.


As mentioned earlier, you can still get these updates through Windows Update, but they will not be installed automatically.

Report a problem with article
1554612401_may2019u3
Next Article

Microsoft is starting to auto-update Windows 10 1803 users to 1903

1478118961_microsoft-slack
Previous Article

Slack CEO doesn't see Teams as a threat

0 Comments - Add comment

Advertisement