Windows 10 KB4458469, KB4457136, KB4457141 and KB4457127 updates

by Martin Brinkmann on September 21, 2018 in Windows - 15 comments

Microsoft released new cumulative updates for supported versions of the company's Windows 10 operating system on September 20, 2018.

The updates KB4458469, KB4457136, KB4457141 and KB4457127 address a huge number of issues in the Windows 10 versions 1803, 1709, 1703 and 1607.

Microsoft released the updates ten days after the release of Patch Tuesday updates for September 2018. The updates include "quality improvements" only; they don't introduce new features or fix security issues.

Microsoft plans to release the next feature version of Windows 10, Windows 10 version 1809 in the coming weeks.

Note: All updates include a Telemetry change

Addresses an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.

Here are the Support page links:

Windows 10 version 1803: KB4458469
Windows 10 version 1709: KB4457136
Windows 10 version 1703: KB4457141
Windows 10 version 1607: KB4457127

Microsoft Update Catalog links:

KB4458469

KB4458469 is a massive update the fixes a lot of issues. It is for Windows 10 version 1803 and includes the following fixes:

Fixed the cause for the prompt "You'll need a new app to open" when reloading websites on non-standard ports.
Fixed a download issue that caused downloads to fail.
Fixed a WebDAV downloads issue.
Fixed the FirstRunPage policy blocking the DefaultSearchProvider policy from working.
Address bar lost focus when new tabs are launched and "Allow web content on New Tab page" policy" was set to off.
Fixed a save password issue in Microsoft Edge that prevented the dialog to show.
Addressed a file previewer issue for HTML, MHT and EMail attachments in Outlook.
Internet Explorer would display security and certificate dialogs in the background
Use of EnableEUDC API could make application's become unresponsive.
The Spell Checker context menu would appear on the wrong monitor in multi-monitor environments.
Fixed an issue with Japanese characters in a remote desktop session (mstsc.exe).
Custom keyboard layouts would not work correctly under certain circumstances.
Fixed an issue with low-level mouse hooks.
Added User Configuration/Administrative Template/Control Panel/Settings Page Visibility
Fixed a Bluetooth pairing issue.
Various Universal CRT fixes.
Fixed a Windows Analytics issue.
The App-V client's scheduled task would not sync if the Device Guard lockdown policy was enabled.
Fixed an issue that would cause the Local Security Authority Subsystem Service (LSASS) process to stop working.
Delay in unlocking or singing in to a computer that was moved to a different network.
Fixed a sign-out issue on certain laptops that would prevent the sign-out process from completing.
Fixed an issue when enabling Bitlocker from a local admin account.
Fingerprint sensor could not be used to log in under certain circumstances.
Fixed a longer start-up issue that would cause systems to boot up to 60 seconds longer.
Fixed the error "Your PIN is no longer available due to a change to the security settings on this device" on Windows 10 S devices.
Fixed Direct Access connection issue.
Fixed the logging of negative events for drivers that are valid when Windows Defender Application Control runs in audit mode.
Third-party VPN interfaces would stop working.
Login process to a Remote Desktop Session Host Server would sometimes stop responding.
Printing to an open or existing file would sometimes fail when using Microsoft Print to PDF or XPS Document Writer.
Fixed daily tasks starting unexpectedly.
Fixed an issue that prevented subsequent tasks from running in the Task Scheduler.
Fixed another issue with repetitive tasks in the Task Scheduler.
Addressed an issue with tasks with indefinite durations starting immediately and not at the time specified.
Debugging of minimized UWP applications was prevented.
Fixed the cause for the error "The operation could not be completed because an unexpected host ID was encountered" with Visual Studio UWP Deployments.
Addressed an issue that ignored the MM_DONT_ZERO_ALLOCATION flag which led to performance issues and error 0x139.
Fixed the cause for the error "An Active Directory domain Controller (AD DC) for the domain %domain% could not be contacted" with NTLTEST, DCLOCATOR, or joining an Active Directory and SAMBA domain.
Fixed multiple pin prompts from being displayed for encrypted emails after the use cancels the first prompt.
Fixed Microsoft Help Viewer rendering HTML incorrectly if the .chm file is stored on a network location.
Lock screen displayed a solid color instead of an image before first sign in.
Microsoft Edge would stop working when printing PDF documents in a size 0 window.
Fixed another Microsoft Edge stops working issue when loading certain PDF documents.
Addresses an issue where GetSystemTime() may sometimes return an invalid value after using SetSystemTime() immediately before.
Fixed a "username hint field" empty issue.
Fixed an issue with the tile layout of the Start Menu after upgrading to Windows 10 version 1803.
Fixed an issue with the Japanese Calendar Era.
Background Apps Settings were lost under certain circumstances.
Fixed toast notifications not displaying issue.
Addresses an issue in which all Guest Virtual Machines running Unicast dual NIC NLB fail to respond to NLB requests after the Virtual Machines restart.
Fixed an issue with dual tunnel AlwaysOn VPN configurations to work correctly.

The updates for Windows 10 version 1709, 1703, and 1607 share most of their fixes with 1803 but fewer issues are fixed.

Here is the list of updates not found in 1803.

KB4457136

Fixed Microsoft Narrator from accessing the content of Windows Security dialogs displayed by low integrity level processes.
Installation of encrypted .appx packages was prevented under certain circumstances.
Fixed error "STATUS_LOGON_FAILURE" when using smart cards to log in to Remote Desktop Servers.
Fixed an issue that caused logging to a Remote Desktop Session Host Server to stop responding.
Addressed a Service Control Manager (SCM) and Netlogon stop working issue.

KB4457141

The EnterpriseAssignedAccess policy on mobile devices could not be used to configure certain pages.

KB4457127

Fixed an issue that prevented the correct changes to folder content to show on some Network Attached Storage (NAS) configurations.
Fixed log file corruption issue for Microsoft-Windows-Kerberos-Key-Distribution-Center source and Event IDs 4933, 4928, and 4937.
Addressed DNS Server returning an error to queries.
Addressed a time sync issue when using Windows Server 2016 and guest Service Host.
Addresses an issue that prevents the lastLogonTimestamp attribute of new Active Directory users from updating
Addresses several Active Directory Domain Services issues.
Addresses an issue where a DirSync client never finishes syncing when using a search filter that contains a linked attribute.
Addressed several Windows Server Backups issue (fail to restore or when backing up).
Fixed creation of a Client Access Point taking a long time due to firewall blocking access to child domain controllers.
Fixed memory leak in Cluster Health Service.
Fixed access error when accessing NFS Shares.
Addresses an issue where opening Explorer view on a SharePoint server site using TMG proxy fails.
Addresses an issue that may cause a system to stop working when you mount an NFS drive using the command line with the option -u -p.
Addresses an issue that may cause setup to fail during OEM-OOBE implementation if French or Spanish language setting is selected on the Hyper-V host.
Fixed report date "unknown" issue in Remote Desktop License Manager.

Closing Words

Should you install these updates? Unless you are affected by a described issue in a major way, it is recommended that you wait with the installation. Updates are designed to fix issues but they sometimes introduce issues of their own. If you do want to proceed with the installation right away make sure you create a system backup before you do.

Addresses an issue that may cause setup to fail during OEM-OOBE implementation if French or Spanish language setting is selected on the Hyper-V host. : Did you install these updates?

Summary

Article Name

Windows 10 KB4458469, KB4457136, KB4457141 and KB4457127 updates

Description

Microsoft released new cumulative updates for supported versions of the company's Windows 10 operating system on September 20, 2018.

Author

Martin Brinkmann

Publisher

Ghacks Technology News

Logo

Comments

alex said on September 21, 2018 at 10:20 am
in all my oc’s with windows 10 1803 Home this update is not available
burn notice said on September 21, 2018 at 11:33 am
Tor Browser 8.0 sends OS+kernel+TOTAL_PING_COUNT in update queries to Mozilla
– Tails 3.9, which ships with TB 8.0, is also affected.
######
User report:[1]
https://blog.torproject.org/comment/277375#comment-277375
Sanitize the add-on blocklist update URL
https://trac.torproject.org/projects/tor/ticket/16931
related, old, closed ticket (unresolved):
TBB-Firefox sends OS+kernel in update queries to Mozilla
https://trac.torproject.org/projects/tor/ticket/6734
[1]: “TBB-Firefox sends Linux kernel version in extensions blocklist update queries to Mozilla. 6 years old ticket closed https://trac.torproject.org/projects/tor/ticket/6734 without fix this privacy issue.
From Ubuntu 18.04.1 LiveCD
/v1/blocklist/3/%7Bec8030f7-c20a-464f-9b0e-13a3a9e97384%7D/60.2.0/Firefox/20180204030101/Linux_x86_64-gcc3/en-US/release/Linux 4.15.0-29-generic (GTK 3.22.30 libpulse 11.1.0)/default/default/1/1/new/”
“about:config
extensions.blocklist.url”
“Also it send TOTAL_PING_COUNT to tell mozilla how many days you use TBB.”
######
1. ULBoom said on September 21, 2018 at 6:55 pm
  Tor 8.0 is messed up. It also adopts your windows title bar colors. What else is it doing?
  Use 7.5.6 and disable the update feature in:
  Tor Browser\Browser\update-settings.exe
  by changing the only line in it to: ACCEPTED_MAR_CHANNEL_IDS=0
  The update onion in the browser will flash, but no big deal; it won’t auto update any more.
  1. Peterc said on September 22, 2018 at 4:52 am
    @ULBoom:
    You meant to type “update-settings.ini” (not.exe), but it was obvious once you were in the folder. Still, at first I half freaked out! (How do I edit an EXE file?).
    I kept a separate install of Tor Browser 7.5.6 going, both because I like my legacy extensions and because I wanted to give time for problems with Tor Browser 8 to shake out … and it looks like there were some.
    Anyway, thanks for the tip!
chesscanoe said on September 21, 2018 at 1:04 pm
After researching the good documentation Microsoft provided on 2018-09-20, I used WU to install KB4458469 that day, as I am in favor of installing Quality updates and Security updates, and much less interested in Feature updates. No problems were observed so far for me.
lehnerus2000 said on September 21, 2018 at 1:21 pm
“The updates KB4458469, KB4457136, KB4457141 and KB4457127 address a huge number of issues in the Windows 10 versions 1803, 1709, 1703 and 1607.”
I bet they do nothing to fix the real issues with W10.
John Doe 101 said on September 21, 2018 at 4:37 pm
Hey, still waiting for 1809, no needs for Updates, i got NO good Results when doing Updates,…only doing new Upgrades to keep mee System and PC running flawlessly.
1809 will be released in October, i guess?
Matthew said on September 21, 2018 at 7:23 pm
This isn’t the first time I see your recommending people not to update their software, so I now feel obliged to fill you in on how you’re wrong.
The idea that someone should only update if they were facing issues is just not true at all. The vast majority of people will update their software without any issues, this time and always.
There’s really no need to be poisoning people’s minds by telling them to steer clear of software updates.
1. Martin Brinkmann said on September 21, 2018 at 8:17 pm
  There is no need to rush this update. I’m not saying that you should never upgrade. With this particular update, it makes no difference if you wait until the next Patch Tuesday unless you are affected by one or multiple of the issues described.
  1. ilev said on September 22, 2018 at 7:36 am
    The question is why has Microsoft issued this update out of the blue ? It doesn’t fix some 0-day security bug or any thing important. People don’t have to stop their work 4 times in a month on Microsoft’s whim. Once in a month is more than enough. Once in 3 months is much better.
2. Dave said on September 24, 2018 at 5:09 am
  Delaying updates long enough for everyone to test them first is always sound advice.
finngran said on September 22, 2018 at 2:37 am
the kb4458469 won’t update, keeps showing error and when downloaded from windows catalogue keeps searching for installed updates for ever
Peterc said on September 22, 2018 at 5:14 am
Good LORD, that’s a long and heterogeneous list of bugs! My dad, who’s on the Enterprise Semi-Annual Channel, was forcibly upgraded from 1709 to 1803 last weekend. He’s getting pretty old, and I’m afraid if I go through the entire list with him to ask if he’s been affected by any, he might lapse into a coma!
Dave said on September 24, 2018 at 4:58 am
@Martin
What about all the other tiny updates happening in the background?
Every single windows app wants to connect to the internet on it’s own and update constantly.
I use WFC and have “Secure Rules” enabled so this fails and causes my PC to get stuck trying to update apps in the backround. I disable the secure rules and let them all update then I can go look at the rules list and see all the new ones that were added. Every single app gets it’s own rule.
This makes me uncomfortable having every single app allowed to connect on it’s own instead of them all being updated by WU. Especially because no one is saying what exactly these little updates or for.
chesscanoe said on September 27, 2018 at 6:26 am
On Windows 10 x64 Home at 17134.319, WU offered KB4458469 (and probably KB4456655 by install observation). The 1803 is now at 17134.320 .
https://support.microsoft.com/en-us/help/4458469/windows-10-update-kb4458469
My new tab page in Chrome Version 70.0.3538.35 (Official Build) beta (64-bit) is now blank white instead of using the long available Google Arts and Culture extension. Chrome More Tools – Extension shows it as still turned on.