Patch Tuesday

Windows 10 update KB4041676 (build 15063.674) releases

Windows 10 gets a big October Patch Tuesday update with a slew of bugs and security fixes.

Windows 10 update KB4041676

Right on schedule Microsoft is now rolling out a Patch Tuesday update for devices running the Windows 10 Creators Update. In this quality update, the company is addressing a slew of bugs or security problems.

KB4041676 bumps the version number of Windows 10 to build 15063.674 and fixes problems with apps, Start menu, Windows Error Reporting, Internet Explorer, storage, and patches a number of security problems.

Alongside update KB4041676, the Windows 10 version 1607 is getting update KB4041691, version 1511 receives update KB4041689, and the initial version gets update KB4042895.

What’s new on Windows 10 build 15063.674

Microsoft has announced KB4041676 in its support site, and it’s referred as “October 10, 2017—KB4041676 (OS Build 15063.674)”. If you’re already running the Windows 10 Creators Update (version 1703) on your PC, this update will only address these issues:

  • Addressed issue where the Universal CRT caused the linker (link.exe) to stop working for large projects.
  • Fixed problem that prevents Windows Error Reporting from saving error reports in a temporary folder that is recreated with incorrect permissions. 
  • Addressed issue where some UWP and Centennial apps show a gray icon and display the error message “This app can’t open” on launch.
  • Addressed reliability issue that causes the AppReadiness service to stop working.
  • Fixed problem where applications that use the Silverlight map stack stop working.
  • Addressed issue where VSync prevents devices from entering Panel Self Refresh mode, which can lead to reduced battery life.
  • Fixed problem where user customizations (like pinned tiles) made to an enforced partial Start layout are lost when upgrading to Windows 10 1703.
  • Addressed issue where the MSMQ performance counter (MSMQ Queue) may not populate queue instances when the server hosts a clustered MSMQ role.
  • Fixed problem with the token broker where it was leaking a token that caused sessions to remain allocated after logoff.
  • Addressed issue where using AppLocker to block a Modern app fails. This issue occurs only with Modern apps that come pre-installed with Windows.
  • Fixed problem with form submissions in Internet Explorer.
  • Addressed issue where Personal Identity Verification (PIV) smart card PINs are not cached on a per-application basis.
  • Fixed problem where using the Cipher.exe /u tool to update Data Recovery Agent (DRA) encryption keys fails unless user certification encryption already exists on the machine.
  • Addressed issue with the rendering of a graphics element in Internet Explorer.
  • Fixed problem with the docking and undocking of Internet Explorer windows.
  • Addressed issue that prevents an element from receiving focus in Internet Explorer.
  • Fixed problem caused by a pop-up window in Internet Explorer.
  • Addressed issue where a Vendor API deleted data unexpectedly.
  • Fixed problem where using the Robocopy utility to copy a SharePoint document library, which is mounted as a drive letter, fails to copy files.
  • Addressed issue where MDM USB restrictions did not disable the USB port as expected.
  • Fixed problem where creating an iSCSI session on a new OS installation may result in the “Initiator instance does not exist” error when attempting to connect to a target.
  • Addressed issue where USBHUB.SYS randomly causes memory corruption that results in random system crashes that are extremely difficult to diagnose.
  • Fixed problem that affects the download of some games from the Microsoft Store during the pre-order phase. Download fails with the error code 0x80070005, and the device attempts to restart the download from the beginning.
  • Addressed issue where connecting to RDS applications published using Azure App Proxy fails. The error message is, “Your computer can’t connect to the Remote Desktop Gateway server. Contact your network administrator for assistance”. 
  • Fixed problem where the ServerSecurityDescriptor registry value does not migrate when you upgrade to Windows 10 1703. 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.
  • Security updates to Microsoft Windows Search Component, Windows kernel-mode drivers, Microsoft Graphics Component, Internet Explorer, Windows kernel, Microsoft Edge, Windows Authentication, Windows TPM, Device Guard, Windows Wireless Networking, Windows Storage and Filesystems, Microsoft Windows DNS, Microsoft Scripting Engine, Windows Server, Windows Subsystem for Linux, Microsoft JET Database Engine, and the Windows SMB Server.

How to download this Windows 10 update

Windows 10 build 15063.674 (KB4041676) for PCs and mobile devices is available immediately. The new update will download and install automatically, but you can always force the update from Settings > Update & security > Windows Update and clicking the Check for updates button.

For more details about the most recent Windows update, check out this list with release dates, KB and build numbers, and more.

You can download this update directly from Microsoft using these links:

Update 1 October 11, 2017: A number of users have been reporting problems after installing update KB4041676 and KB4041691, if your computer has been affected, you can try this workaround.

Update 2 October 11, 2017: It seems that it’s not an issue with the updates themselves. According to ZDNet, Microsoft mistakenly published the updates to Windows Server Update Services (WSUS) and System Center Configuration Manager both Cumulative and Delta updates that could be installed on devices at the same time were the root of the problem to business customers. Microsoft doesn’t make Delta updates to consumers, as such this issue shouldn’t affect regular users.

Update 3 October 13, 2017: Microsoft officially acknowledged that the October 10 quality update impacted some business users, and announces that the problem has now been corrected.