KB4089848

[Clintlgm]

March 22, 2018 - KB4089848 (OS Build 16299.334)

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4089848

Might help out some people still having issue with the last one.

 

[Saltgrass]

With all these recent updates, I wonder is Microsoft is preparing systems for a new build upgrade...

 

[Tim Locke]

It is due in April I think. I wonder how confident they are? Will it roll out slowly or just be there on next patch Tuesday.

 

[Grizzly]

It is coming down on two of my laptops. Seems like one laptop is hanging at 98% download while the other is already installing at 22%

WOW ! ! ! !

from starting the update through restart and re login 26 minutes. That was the fastest Update so far...

 

[Clintlgm]

With all these recent updates, I wonder is Microsoft is preparing systems for a new build upgrade...

Seems likely to me, we know SCU is coming in April

 

[davehc]

With all these recent updates, I wonder is Microsoft is preparing systems for a new build upgrade...

Inevitably coming in April. But, I think this one was to correct some issues with AMDs only. No updates forthcoming for my Intels - yet!
The update link (First post) is a little confusing. I had a look at the description for the X64 - Third down in the list -although it said X64, only referred to X86
Architecture: AMD64 , X86
Classification: Updates
Supported products: Windows 10
Supported languages: all
Going deeper:, it replaced 7 earlier update back to KB4090913

 

[JAY B.]

No sign of it yet !???

This is what I found about this KB

KB4089848, changelog

• 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.

I’ll wait for it !

Bye

 

[Clintlgm]

Inevitably coming in April. But, I think this one was to correct some issues with AMDs only. No updates forthcoming for my Intels - yet!
The update link (First post) is a little confusing. I had a look at the description for the X64 - Third down in the list -although it said X64, only referred to X86
Architecture: AMD64 , X86
Classification: Updates
Supported products: Windows 10
Supported languages: all
Going deeper:, it replaced 7 earlier update back to KB4090913

Not exactly what you're saying here that it only refers to AMD X86, this installed on all 3 of my 64bit pro machines without issues. I prefer to manually download and install over allowing WU to screw up my units while I'm not prepared or paying attention.

 

[Trouble]

No updates forthcoming for my Intels - yet!

Checked for it yesterday on two machines.
Both running Windows 10 Pro 64bit latest version.
One machine got this update the other didn't
The only glaring difference between the two.....
The AMD machine got the update.
The Intel machine never saw it.

 

[davehc]

Something screwy here (surprise - not)
For the heck of it, I download and installed 9848 (AMD it says. ) All went perfectly.

 

[Trouble]

For the heck of it, I download

By that..... can we assume that you got it from the update catalog rather than by just running the normal Windows Update manually?
I just re-checked the update utility on my intel machine and it still is not showing up as available through there.

 

[Clintlgm]

Same here 3 units 64bit Pro

 

[davehc]

By that..... can we assume that you got it from the update catalog rather than by just running the normal Windows Update manually?
I just re-checked the update utility on my intel machine and it still is not showing up as available through there.

Yes. From the catalogue.

 

[Trouble]

OK.... I think I'll just wait and see if it ever actually shows up on my update, but...
As of a few seconds ago....

 

[Comp Cmndo]

My 1 AMD machine said "Up-to-Date". 2 more computers said the same, Had to do manually with download from Windows Update Catalog. 3 Intel machines did it from Windows Update. 2 of the 3 are identical old Pentium Dual Core, 1 is CoreI3 Ivy Bridge.

 

[Grizzly]

All my Intel's got this update, none of my AMD's though but then, they can't run Win10 anyway...

 

[Bighorn]

My AMDs and Intels are getting it but I have noticed those with Build 16299.214 had to first be updated to Build 16299.309 first.

 

[Comp Cmndo]

My AMDs and Intels are getting it but I have noticed those with Build 16299.214 had to first be updated to Build 16299.309 first.

Updates are cumulative not consecutive.

 

[Bighorn]

Updates are cumulative not consecutive.

That's why I posted what transpired/actually happened with a few computers I was updating.