New Windows 10 cumulative update rolls out to Anniversary Update PCs

Outside of its standard Patch Tuesday schedule, Microsoft recently started rolling out an additional cumulative update for Windows 10 PCs still running the Anniversary Update (1607) (via Neowin). Coming two weeks after November's round of Patch Tuesday updates, this build doesn't contain anything in the way of new features. However, the update does roll the build number up to 14393.1914 and includes a variety of bug fixes and improvements.

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

  • Addressed issue where screen tearing and scrambled content appear in applications when a computer is connected to three or more USB 3.0 display devices. This occurs when you change the content on one or more of the connected display devices.
  • Addressed issue where a service fails to start when two or more services are using the same built-in account (such as NetworkService or LocalService). When this issue occurs, the failing service reports the error, "The service did not start due to a logon failure", or, "A specified logon session does not exist. It may already have been terminated."
  • Addressed issue where scheduled tasks with stored credentials fail to run when Credential Guard is enabled. The task fails and reports event ID 104 with the following message: "Task Scheduler failed to log on '\Test' . Failure occurred in 'LogonUserExEx' . User Action: Ensure the credentials for the task are correctly specified. Additional Data: Error Value: 2147943726. 2147943726 : ERROR_LOGON_FAILURE (The user name or password is incorrect)."
  • Addressed issue where, during BitLocker decryption or encryption of a drive, files protected with the Encrypting File System (EFS) may become corrupted.
  • Addressed issue where opening Microsoft Office files from a file server that has Windows Information Protection enabled fails with the error, "Sorry we couldn't open document xxxx".
  • Addressed issue where a Storage Spaces Direct (S2D) drive that is failing or being removed from a node is incorrectly reported as healthy in admin tools. These tools include Get-Physical Disk, Server Manager, and Failover Cluster Manager.
  • Addressed issue where a repair job could be suspended indefinitely after re-adding a node to an S2D cluster.
  • Addressed issue where an incomplete Storage Spaces repair could lead to faulty metadata causing future repairs to stop working.
  • Addressed issue in the Network Flyout where closing the sign-in dialog unexpectedly (e.g., clicking outside the window) prevents additional sign-in dialogs from appearing when the user tries to connect to the same network.
  • Addressed a token leak in services.exe that occurs after applying MS16-111/KB3175027. This results in a kernel session object leak that degrades system performance over time. This especially affects Terminal Server implementations, where more user logons typically occur.
  • Addressed an AppProxy issue that could prevent mobile devices from connecting to a network.
  • Addressed issue where the Remote Desktop clipboard redirection policy doesn't take effect if reconnecting to an existing session and the policy has changed between the initial connection and reconnecting to the session.
  • Addressed issue where in a non-English language environment, the OEM OOBE process cannot finish when building a failover cluster. This process fails with the error message, "No integration component with the given name could be found."
  • Improved performance when querying the file system formats of Direct-Access Storage Devices.
  • Addressed issue associated with the clustering health policy for handling unresponsive clustered drives. By default, drives are retired for unresponsive conditions. The frequency of unresponsive reset remediation is too aggressive.
  • Addressed issue in the Network Flyout where closing the sign-in dialog unexpectedly (e.g., clicking outside the window) prevents further sign-in dialogs from appearing when the user tries to connect to the same network.
  • Improved performance when launching applications that use Virtual Disk Service to manage volumes.
  • Addressed issue that impacted some Epson SIDM (Dot Matrix) and TM (POS) printers, which were failing to print on x86 and x64-based systems. This issue affects KB4048953.

Microsoft also says there are a couple of known issues still included in this build, a list of which you can find in the full release notes (opens in new tab).

If you're still one of the few running the Anniversary Update on a PC, you should be able to grab these fixes via Windows Update now. It's also worth considering a move up to the Fall Creators Update if possible because, while the Anniversary Update is still supported, it will be the next major Windows 10 release to lose support from Microsoft in the coming months.

Dan Thorp-Lancaster

Dan Thorp-Lancaster is the former Editor-in-Chief of Windows Central. He began working with Windows Central, Android Central, and iMore as a news writer in 2014 and is obsessed with tech of all sorts. You can follow Dan on Twitter @DthorpL and Instagram @heyitsdtl

  • Microsoft Surface Book 2 is awesome.
  • What does this have to do with the AU on PC?
  • How is it possible that a pc has updates on the old version of the OS? Like i'm on CU and I have paused the windows update cause I don't want to get FCU, cause its horrible and has nothing interesting in it anyway. But if i unpause the wu, then i will get FCU, not cumulative updates to CU. Can someone explain?
  • You can delay feature updates (like Creators Update) and only receive bug fixes and security updates.
  • i got kmode exception not handled after the usual windows update required restart windows, now stuck at boot loop, atom bay trail z3740 tablet, windows update doesn't update this tablet to newer version of windows 10 Creators Update and Fall Creators Update, so i just let it be stuck at older version of windows 10 Anniversary Update.
  • i can confirm KB4051033 is the cause of the BSOD kmode exception not handled after some testing, after uninstall KB4051033 the BSOD is gone. i can only go into windows 10 by select Disable Early Launch Anti-Malware Protection at Advanced startup , Troubleshoot , Startup Settings , the whole Advanced startup work with touchscreen, but only the Startup Settings page doesn't work with touchscreen, have to press number keys or function keys, there is no On-Screen Keyboard there, since this is a tablet, have to plug in a keyboard each times to do it. disableelamdrivers at bcdedit doesn't work too, so have to do it manually each time when have to. since windows 10 support Fast Startup, BSOD only happen during boot after Windows Restart, doesn't happen after turn on from cold boot, sleep, hibernate, shutdown. using wushowhide.diagcab right now to block KB4051033 auto install again after uninstall.