KB4089848 Available for Windows 10 Version 1709 Fall Creators Update

After releasing its normal Patch Tuesday update for Windows 10 Fall Creators Update, Microsoft is back with a new patch that includes even more fixes.

Microsoft is rolling out another new cumulative update — KB4089848 — for Windows 10 Fall Creators Update (version 1709). The company already rolled out cumulative update KB4088776 for Windows 10 earlier this month as part of it regular Path Tuesday. But today’s new update comes with even more fixes and bumps your build number up to 16299.334. Here is a look at what’s been fixed and changed in this latest update.

Windows 10 Fall Creators Update Build 16299.334

There are no new features with this update, but here an extensive list of improvements and new fixes the patch contains:

  • Addresses issue with a GDI handle leak in the Windows Ribbon control.
  • Addresses issue where users can’t select OK after entering credentials in command line on Windows Server version 1709.
  • Addresses issues where Bluetooth devices fail to receive data after a restart.
  • Addresses issue where, during BitLocker decryption or encryption of a drive, files protected with the Encrypting File System (EFS) may become corrupted.
  • Addresses issue where the server may occasionally encounter an error during file transfer. The error is “Stop D1 in tcpip!TcpSegmentTcbSend”.
  • Addresses issue where an iSCSI RESET might trigger a cluster failover.
  • Addresses issue in MPIO where pass-through SCSI requests might lead to a stop error if the disk is pending removal.
  • Addresses issue where processing of group policies may fail, and policies may be removed as a result. This occurs if the length of the Windows Defender Firewall policy rule exceeds 260 characters.
  • Addresses issue caused by a new privilege in Windows Server 2016 and Windows 10 version 1709 named “Obtain an impersonation token for another user in the same session”. When applied using Group Policy to those computers, gpresult /h fails to generate reporting data for any setting configured by the Security Configuration Engine (SCE) extension. The error message is “Requested value ‘SeDelegateSessionUserImpersonatePrivilege’ was not found”. The Group Policy Management Console fails to show the privilege in the Settings tab for a GPO where the setting has been configured.
  • Addresses issue where errors may occur when accessing WebDAV files or folders on a SharePoint site if the file or folder name contains multibyte characters.
  • Addresses issue where the Remote Desktop License report gets corrupted when it exceeds the 4 KB size limit.
  • Addresses issue where an Azure point-to-site VPN connection that uses IKEv2 may fail when the user’s device contains a large number of trusted root certificates.
  • Addresses rendering issue in Microsoft Edge for PDF documents with backgrounds created using various third-party publishing tools.
  • Addresses issue where a media platform stops responding when changing cameras rapidly on a device.
  • Addresses issue where a media platform stops responding, which affects media playback in Microsoft Edge, Internet Explorer, and Microsoft PowerPoint.
  • Addresses issue with spatial audio when used in connection to Dolby Atmos for Headphones.
  • Addresses issue where a credential prompt that requires administrative privileges appears when a standard user account performs the first logon to a Windows 10 device that has been deployed using Windows Autopilot.
  • Addresses issue where tiles in the Start menu aren’t preserved when upgrading from Windows 10 version 1607 to Windows 10 version 1709.
  • Addresses issue with Spell Check and custom dictionaries.
  • Addresses issue with the press and hold feature when using a pen in Tablet mode.
  • Addresses issue with editing web password fields using a touch keyboard.
  • Addresses issue where some Bluetooth card readers don’t work after a restart.

Of course, you should get this latest update automatically via Windows Update within the next couple of days, but if you like to stay on top of the situation, head to Settings > Update & Security > Windows Update and check for updates. Or, you can certainly download and install the standalone version for x86, x64, and Server. After you restart your system, hit Start and type: winver and hit Enter. You will see your build has been bumped up to 16299.334.

Winver build 16299-334

After you install today’s update, let us know how things are going with your system. Also, make sure to check out our Windows 10 Forums for more discussions on all things Microsoft and troubleshooting advice.



  1. Laura

    March 23, 2018 at 4:10 pm

    Since my computer said it was up to date but I found no evidence of the above update, I tried the stand-alone updater but was told it was not for my computer (Windows 10 Pro x86.)

  2. Al

    March 25, 2018 at 3:46 pm

    I installed this update, then rebooted and got the “black screen with mouse cursor” thing. Rolling back didn’t cure it, so I think my computer is hosed, be careful,

Leave a Reply

Your email address will not be published. Required fields are marked *


To Top