Skip to main content

Microsoft rolls out new cumulative update for Windows 10 Anniversary Update PCs

Microsoft has quietly started rolling out another cumulative update for Windows 10 PCs still running the Anniversary Update. This latest update (via Neowin) comes just over a week after October's Patch Tuesday updates arrived for supported versions of Windows 10. There are no new features included, but the update does roll the build number up to 14393.1794 with a number of bug fixes across the board.

Here's a look at all of the fixes included (opens in new tab) in cumulative update KB4041688:

  • Addressed rare issue where fonts may be corrupted after the Out of Box Experience is completed. This issue occurs on images that have multiple language packs installed.
  • Addressed issue where downloading updates using express installation files may fail after installing OS Updates 14393.1670 through 14393.1770.
  • Addressed issue that causes an error when trying to access shares on a file server.
  • Addressed issue that prevents Windows Error Reporting from saving error reports in a temporary folder that is recreated with incorrect permissions. Instead, the temporary folder is inadvertently deleted.
  • Addressed issue where the MSMQ performance counter (MSMQ Queue) may not populate queue instances when the server hosts a clustered MSMQ role.
  • Addressed issue where restricting the RPC port of the Next Generation Credentials (Windows Hello) service causes the system to stop responding when logging on.
  • Addressed issue where Personal Identity Verification (PIV) smart card PINs are not cached on a per-application basis. This causes users to see the PIN prompt multiple times in a short time period. Normally, the PIN prompt onlys display once.
  • Improved M.2 NVMe SSD throughput when the queue size increases.
  • Addressed issue where running Event Tracing for Windows with Volsnap may result in error 0x50.
  • Addressed issue where using the Robocopy utility to copy a SharePoint document library, which is mounted as a drive letter, fails to copy files. However, in this scenario, Robocopy copies folders successfully.
  • Addressed issue where Miniports that make 64-bit DMA requests from a single 4 GB region may fail, preventing the system from booting.
  • Addressed issue where a disk losing communication with its S2D cluster may lead to a stale fault domain descriptor for the enclosure.
  • Addressed issue where, if an update to a pool config header occurs when it's performing a read function, a stop error may occur in a Windows Server 2016 Storage Spaces Directory (S2D) deployment.
  • Addressed issue to allow UEFI-based customers to pre-stage UEFI-based Gen 2 VMs to run Windows Setup automatically.
  • Addressed issue that intermittently misdirects AD Authority requests to the wrong Identity Provider because of incorrect caching behavior. This can affect authentication features like Multi-Factor Authentication.
  • Added the ability for AAD Connect Health to report AD FS server health with correct fidelity (using verbose auditing) on mixed WS2012R2 and WS2016 AD FS farms.
  • Addressed issue where the PowerShell cmdlet that raises the farm behavior level fails with a timeout during the upgrade from the 2012 R2 AD FS farm to AD FS 2016. The failure occurs because there are many relying party trusts.
  • Addressed issue where adding user rights to an RMS template causes the Active Directory RMS management console (mmc.exe) to stop working with an unexpected exception.
  • Addressed issue where AD FS causes authentication failures by modifying the WCT parameter value while federating the requests to another Security Token Server (STS).
  • Updated the SPN and UPN uniqueness feature to work within the forest root tree and across other trees in the forest. The updated NTDSAI.DLL won't allow a subtree to add an SPN or a UPN as a duplicate across the entire forest.
  • Addressed issue where the language bar stays open after closing a RemoteApp application, which prevents sessions from being disconnected.
  • Addressed issue where the working directory of RemoteApps on Server 2016 is set to %windir%\System32 regardless of the application's directory.
  • Addressed issue where USBHUB.SYS randomly causes memory corruption that results in random system crashes that are extremely difficult to diagnose.
  • Addressed issue where the ServerSecurityDescriptor registry value doesn't migrate when you upgrade to Windows 10 1607. As a result, users might not be able to add a printer using the Citrix Print Manager service. Additionally, they might not be able to print to a client redirected printer, a Citrix universal print driver, or a network printer driver using the Citrix universal print driver.
  • Addressed issue where policies are not pushed for servers that have an updated Instance ID. This occurs when synchronizing the removal of the old server resources with the notifications about NICs (port profile changes) from the host.

Microsoft also details a few known issues that are still included with this release, each of which you can check out in the full release notes (opens in new tab).

If you're still in the minority of users running the Anniversary Update on a PC, you should be able to grab these fixes via Windows Update now. You also might consider moving up to the recently released Fall Creators Update if possible because, while the Anniversary Update may still be officially supported, it will be the next version of Windows 10 to lose official support from Microsoft in the coming months.

Dan Thorp-Lancaster is the Editor in Chief for Windows Central. He began working with Windows Central as a news writer in 2014 and is obsessed with tech of all sorts. You can follow Dan on Twitter @DthorpL and Instagram @heyitsdtl. Got a hot tip? Send it to daniel.thorp-lancaster@futurenet.com.

8 Comments
  • at end they know the bug of usb drivers and hub usb. and printer stuck driver on network wifi maybe dont solved
  • Update to Creator's or Fall Creator's.
  • If you read the headline and the article it clearly states Anniversary Update!!
  • Why would anyone still be running the AU when there have been two upgrades since then?
  • Enterprise.
  • Because upgrades break things! Besides, Enterprise users aren't the only ones invested in having stable computers. It took months for Creators Update to settle down and even now it's sometimes flakey. CU focussed on style-over-substance. I'm a bleeding-edge type person yet even I patiently waited a month to upgrade to the CU. Why? Because my computers are largely used for work purposes. I can't afford to be fiddling with a computer to get it working. And, when the CU came along it really didn't offer much of substance. A few more settings. More continuation of Microsoft's existing pattern of snooping in all facets of our personal lives. PS I spent some time investigating what Microsoft recommends for its Windows 10 Education customers vis-a-vis privacy and it was eye-opening. Microsoft provides a much better and much less intrusive experience for Education customers than it does anyone else.  WHY CAN'T REGULAR PEOPLE GET PROTECTION FROM SNOOPING BY MICROSOFT? Out of the box Microsoft RECOMMENDS turning off Cortana and disabling Tips and Suggestions. Microsoft also provides the ability for educational institutions to use Bing ad free. Windows 10 Education also prevents Windows/Microsoft Store ads from appearing in your start menu. Anyway, I digress. I should switch to Google. At least there I have some control over what information is sent to Google when I browse, unlike Microsoft which simply sends everything to Microsoft.
  • Maybe they have tried but the creators update failed numerous times at 84% despite trying every fix/work around listed on the internet.  And then when the fall creators update the update failed multiple times at 83% so they gave up a second time on updating.  I have 5 computers 4 updated just fine but that last one will not update past AU for some reason.
  • If you're on W10 AU and you check for updates, then you'd be upgraded to the Fal update. Even my Enterprise W10 on my work SP3 got updated on day 1. If a business isn't at least on the first Creator Update, then that IT department needs to get with it. The world doesn't move at a snail's pace.