Windows 10 KB4458469, KB4457136, KB4457141 and KB4457127 updates

Martin Brinkmann
Sep 21, 2018
Windows, Windows 10

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:

Microsoft Update Catalog links:


KB4458469 windows 10 update

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.


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


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


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

Windows 10 KB4458469, KB4457136, KB4457141 and KB4457127 updates
Article Name
Windows 10 KB4458469, KB4457136, KB4457141 and KB4457127 updates
Microsoft released new cumulative updates for supported versions of the company's Windows 10 operating system on September 20, 2018.
Ghacks Technology News

Tutorials & Tips

Previous Post: «
Next Post: «


  1. Dan Donx said on January 15, 2023 at 10:29 am

    What mental age of reader are you targeting with the first sentence? 10?

    Why not write an article on how to *avoid* upgrading from W10 to W11. Analogous to those like me who avoided upgrading from 7 to 10 for as long as possible.

    If your paymaster Microsoft permits it, of course.

  2. Dexter said on January 15, 2023 at 11:14 am

    5. Rufus
    6. Ventoy

    PS. I hate reading these “SEO optimized” articles.

    1. cdr said on January 15, 2023 at 3:32 pm

      I used Rufus to create an installer for a 6th gen intel i5 that had MBR. It upgraded using Setup. No issues except for Win 11 always prompting me to replace my local account. Still using Win 10 Pro on all my other PCs to avoid the bullying.

  3. sv said on January 15, 2023 at 6:40 pm

    bit pointless to upgrade for the sake of upgrading as you never know when you’ll get locked out because ms might suddenly not provide updates to unsupported systems.

    ps…. time travelling?
    written. Jan 15, 2023
    Updated • Jan 13, 2023

    1. Martin Brinkmann said on January 16, 2023 at 5:49 am

      This happens when you schedule a post in WordPress and update it before setting the publication date.

  4. Anonymous said on January 16, 2023 at 8:24 am

    Anyone willing to downgrade to this awful OS must like inflicting themselves with harm.

  5. basingstoke said on January 16, 2023 at 11:18 am

    I have become convinced now that anybody who has no qualms with using Windows 11/10 must fit into one of the following brackets:

    1) Too young to remember a time before W10 and W11 (doesn’t know better)

    2) Wants to play the latest games on their PC above anything else (or deeply needs some software which already dropped W7 support)

    3) Doesn’t know too much about how computers work, worried that they’d be absolutely lost and in trouble without the “”latest security””

    4) Microsoft apologist that tries to justify that the latest “features” and “changes” are actually a good thing, that improve Windows

    5) Uses their computer to do a bare minimum of like 3 different things, browse web, check emails, etc, so really doesn’t fuss

    Obviously that doesn’t cover everyone, there’s also the category that:

    6) Actually liked W7 more than 10, and held out as long as possible before switching, begrudgingly uses 10 now

    Have I missed any group off this list?

    1. Heinz Strunk said on September 19, 2023 at 3:57 pm

      You have missed in this group just about any professional user that uses business software like CAD programs or ERP Programs which are 99% of all professional users from this list.

      Linux doesn’t help anyone who is not a linux kid and apple is just a fancy facebook machine.

  6. ilev said on August 24, 2023 at 7:34 pm

    Microsoft has removed KB5029351 update

    1. EP said on August 24, 2023 at 9:21 pm

      only from windows update though
      KB5029351 is still available from the ms update catalog site

  7. Anonymous said on August 24, 2023 at 11:05 pm

    1. This update is labaled as PREVIEW if it causes issues to unintelligent people, then they shouldn’t have allowed Preview updates ot install.

    2. I have installed it in a 11 years old computer, and no problems at all.

    3. Making a big drama over a bluescreen for an updated labeled as preview is ridiculous.

    This is probably another BS internet drama where people ran programs and scripts that modified the registry until they broke Windows, just for removing stuff that they weren’t even using just for the sake of it.
    Maybe people should stop playing geeks and actually either use Windows 10 or Windows 11, but don’t try to modify things just for the sake of it.

    Sometimes removing or stopping things (like defender is a perfect example) only need intelligence, not scripts or 3rd party programs that might mess with windows.

  8. john said on August 24, 2023 at 11:17 pm

    Windows 11 was a pointless release, it was just created because some of the Windows team wanted to boost sales with some sort of new and improved Windows 10. Instead, Microsoft cannot support one version well let alone two.

    1. John G. said on August 25, 2023 at 12:08 pm

      Windows 11 is the worst ugly shame by Microsoft ever. They should release with every new W11 version a complete free version of Starallback inside just to make this sh** OS functionally again.

  9. EP said on August 25, 2023 at 3:10 pm

    motherboard maker MSI has recently released a statement regarding the “unsupported processor” blue screen error for their boards using Intel 600/700 series chipsets & to avoid the KB5029351 Win11 update:–UNSUPPORTED-PROCESSOR–Error-Message-of-Windows-11-Update-KB5029351-Preview-142215

  10. EP said on August 29, 2023 at 7:32 pm

    check out the following recent articles:

    Neowin – Microsoft puts little blame on its Windows update after UNSUPPORTED PROCESSOR BSOD bug:

    BleepingComputer – Microsoft blames ‘unsupported processor’ blue screens on OEM vendors:

  11. Leonard Britvolli said on August 30, 2023 at 10:33 pm

    While there may be changes or updates to the Windows 10 Store for Business and Education in the future, it is premature to conclude that it will be discontinued based solely on rumors.

  12. sembrador said on September 5, 2023 at 9:32 pm

    My advice, I left win 15 years ago. Now I’m a happy linux user (linuxmint) but there is Centos, Fedora, Ubuntu depending on your needs.

  13. EP said on September 6, 2023 at 11:55 am

    motherboard maker MSI has recently released new BIOS/firmware updates for their Intel 600 & 700 series motherboards to fix the “UNSUPPORTED_PROCESSOR” problem (Sept. 6):–UNSUPPORTED-PROCESSOR–caused-BSOD-on-MSI-s-Intel-700-and-600-Series-Motherboards-142277

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.