Skip to main content

New cumulative updates now available for Windows 10

Microsoft is pushing out another batch of cumulative updates for Windows 10 today. The October 2018 Update isn't included in today's release, but PCs on the April 2018 Update, Fall Creators Update, and Creators Update are all included. Here's a look at the release notes (opens in new tab) for each (via Neowin).

For the April 2018 Update, today's release pushed the build number up to 17134.556:

  • Addresses an issue in Microsoft Edge that fails to trigger the focusin event if the focus event listener of an element shifts focus to another element.
  • Addresses an issue that prevents sharing and timeline features and roaming settings from working for accounts that use Chinese, Japanese, and Korean languages.
  • Addresses an issue that may prevent some applications from displaying the Help (F1) window correctly.
  • Addresses an issue that causes power options to appear on the Windows security screen when the per user group policy to hide power options is set.
  • Addresses an issue that prevents links for certain compressed file formats from resolving.
  • Addresses an issue that causes BitLocker Network Unlock to fail on generation 2 virtual machines when it's used in a network that only supports IPv4.
  • Addresses a privacy issue with apps that obtain the BroadFileSystemAccess capability without a user's consent.
  • Addresses an issue in which WAM logging causes some applications such as Microsoft Office to stop working.
  • Addresses an issue that causes catalog signed scripts, including those shipped as part of Windows, to incorrectly generate a Windows Defender Application Control (WDAC) failure audit event.
  • Addresses an issue in which Windows Driver Frameworks causes high CPU utilization. As a result, the user-mode driver stops working when the device resumes from Hibernate (S4).
  • Addresses an issue that may cause a 30-second delay when deleting or renaming a link in a Distributed File System (DFS) Namespace. Additionally, renaming a folder may take 30 seconds when multiple users work in a group share simultaneously, and File Explorer stops responding.
  • Addresses an issue that prevents you from overwriting a file in a shared folder because of an Access Denied error when a filter driver is loaded.
  • Addresses an issue that may cause third-party applications to have difficulty authenticating hotspots.
  • Addresses an issue that may cause a blue screen to appear when a Thunderbolt storage device is attached.

The latest Fall Creators Update build, meanwhile, is 16299.936, and includes the following:

  • Addresses an issue in Microsoft Edge that fails to trigger the focusin event if the focus event listener of an element shifts focus to another element.
  • Addresses an issue that may prevent some applications from displaying the Help (F1) window correctly.
  • Addresses an issue that may cause an application to stop working when converting long Kana to Kanji using a combination of predictive and non-predictive input.
  • Addresses an issue in a multi-monitor configuration that causes a window to unexpectedly move to a different monitor when reconnecting to an existing user session.
  • Addresses an issue in which the desktop wallpaper image set by a group policy will not update if it has the same name as the previous image.
  • Addresses an issue that causes BitLocker Network Unlock to fail on generation 2 virtual machines when it's used in a network that only supports IPv4.
  • Addresses an issue that causes catalog signed scripts, including those shipped as part of Windows, to incorrectly generate a Windows Defender Application Control (WDAC) failure audit event.
  • Addresses an issue that causes Scheduled Tasks created in a disabled state to not run.
  • Addresses an issue that prevents you from overwriting a file in a shared folder because of an Access Denied error when a filter driver is loaded.
  • Addresses an issue that may cause third-party applications to have difficulty authenticating hotspots.
  • Addresses an issue that may cause a blue screen to appear when a Thunderbolt storage device is attached.
  • Addresses an issue that may display the error code "0x139" for the RNDISMP6!KeepAliveTimerHandler when connecting to a Remote Network Driver Interface Specification (RNDIS) device.

Finally, the Creators Update includes the following fixes with build 15063.1596:

  • Addresses an issue that causes downloads to fail because Mark of the Web (MOTW) was not supported at the download location.
  • Addresses an issue in Microsoft Edge that fails to trigger the focusin event if the focus event listener of an element shifts focus to another element.
  • Addresses an issue that may prevent some applications from displaying the Help (F1) window correctly.
  • Addresses an issue that causes BitLocker Network Unlock to fail on generation 2 virtual machines when it's used in a network that only supports IPv4.
  • Addresses an issue that causes catalog signed scripts, including those shipped as part of Windows, to incorrectly generate a Windows Defender Application Control (WDAC) failure audit event.
  • Addresses an issue that may cause a 30-second delay when deleting or renaming a link in a Distributed File System (DFS) Namespace. Additionally, renaming a folder may take 30 seconds when multiple users work in a group share simultaneously, and File Explorer stops responding.
  • Addresses an issue that prevents you from overwriting a file in a shared folder because of an Access Denied error when a filter driver is loaded.
  • Addresses an issue that may cause third-party applications to have difficulty authenticating hotspots.

Each update is available now via Windows Update.

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.

6 Comments
  • Anybody know when Microsoft will push the Oct 2018 update to computers that haven't received it yet? I'm reluctant to manually force it because I saw a recommendation saying to wait until it shows up in "Get Updates."
  • It can take several months for MSFT to solve the issues affecting a device such as yours. You are by no means alone. IMHO it is better to let MSFT resolve the issues so you don't have a bad experience. MSFT sometimes is dependent on an OEM to get the needed resolution done. It's up to you, of course.
  • When are they going to fix the transparency bug in command prompt??
  • When they will introduce a new notepad its so ugly right now.
  • Agree 😊 But it's probably from MS themselves
  • October 2018 update is a mess...