When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works.

Windows 10 for PCs build 14393.1613 is now available - here's what's fixed

Patch Tuesday was only eight days ago, and despite the fact that it's been little over a week since Microsoft released updates for every supported version of Windows, there's another one available. This one is for those running the Windows 10 Anniversary Update, and build 14393.1613 is only for PCs.

The cumulative update, KB4034661, contains a wide range of fixes:

  • This package contains d3dcompiler_47.dll; for more information, read the blog post, HLSL, FXC, and D3DCompile.

  • Addressed issue where a black screen appears when launching an application on Citrix XenApp that was deployed from Windows Server 2016. For more details, read CTX225819.

  • Addressed issue where the User Account Control (UAC) prompt sometimes appears hidden under other opened windows.

  • Addressed issue in the event collector data that caused data corruption with % symbols in the user logon events (ID 4624) from other Domain Controllers (DCs).

  • Addressed issue where the PowerShell command Add-HgsAttestationTpmHost fails to find the Endorsement Key Certificate for a system even though the certificate exists.

  • Addressed issue where, in some cases, an Encrypted Hard Drive device would not automatically unlock at system startup.

  • Addressed issue where the AppLocker rules wizard crashes when selecting accounts.

  • Addressed issue where third-party directory structures caused Disk Cleanup to render a boot drive inaccessible.

  • Addressed issue where unsynchronized access in NtfsQueryLinksInfo led to a system crash.

  • Addressed issue where an extremely high number of I/O flushes might lead to an error.

  • Addressed a reliability issue that occurs when a user gives the wrong input to the smart card pin prompt.

  • Addressed issue by increasing the time out window when starting Docker for Windows to avoid 0x5b4 errors.

  • Addressed issue with Azure Multi Factor Authentication (MFA) when an ADFX server is configured to use an HTTP Proxy.

  • Addressed issue where the calling IP address is not logged by 411 events in the Security Event log of ADFS 4.0 and Windows Server 2016 RS1 ADFS servers. This issue occurs even after enabling Success Audits and Failure Audits.

  • Addressed issue where a computer account loses its domain membership with the error 1789, “The trust relationship between this workstation and the primary domain failed.” The same problem happens internally when a user password cannot be changed with error 0xc0000206, “The size of the buffer is invalid for the specified operation.”

  • Addressed issue where, after a planned restart of the primary server, storage replication doesn't automatically resume as expected. Also, Storage Replication service randomly fails after restart.

  • Addressed issue where using a GPO logon script to map a network drive fails if the user disconnects from the network and restarts. When the user logs in again, the mapped drive is not available. This issue occurs even though the logon script has the persistence flag set to TRUE.

  • Addressed issue where after uninstalling SMBv1, if you set the SPN validation level to 2, when you access a UNC share remotely (e.g., \\\C$), the request will fail with STATUS_ACCESS_DENIED.

  • Addressed issue where the Remote Desktop client cannot connect or disconnects intermittently when trying to connect using the RD Gateway.

  • Addressed issue where presenting an expired or revoked certificate to the ADFS Proxy server does not return an error to the user.

Interestingly, there are three known issues, which is quite a bit for something that's going out to Production. Here's what's still broken:

Symptom Workaround
“Update History” does not list previously installed updates.

As an alternative, to see which quality updates have been applied, navigate to the inventory by going to Control Panel -> Programs -> “View Installed Updates”

Microsoft is investigating this issue and will provide an update as soon as possible.
Updates that were previously hidden may be offered after installing this update.

Updates that were previously hidden can be hidden again.

Microsoft is investigating this issue and will provide an update as soon as possible.

WSUS servers will exhibit increased CPU, memory, and network utilization when Windows Update clients perform their first scan after installing KB4034658. Microsoft is investigating this issue and will provide an update as soon as possible.


These three issues are currently listed in the release notes for last week's build 14393.1593; however, they weren't there when the update was published. If you want to install KB4034661 manually, you can find it in the Microsoft Update Catalog here.

Report a problem with article
Next Article

The SteelSeries Apex M750 keyboard debuts with visual cues for Discord notifications

Previous Article

Xbox One Insider Preview build 16262 is now available in the Alpha ring - here's what's new

Join the conversation!

Login or Sign Up to read and post a comment.

5 Comments - Add comment