Microsoft releases KB4522355 for Windows 10 version 1903

Martin Brinkmann
Oct 24, 2019
Updated • Oct 26, 2019
Windows, Windows 10
|
11

Microsoft released a new cumulative update for the current version of Windows 10, Windows 10 version 1903, on October 24, 2019.

The new update is a non-security update that is completely optional to install; all of its changes will also be included in the November 2019 Patch Tuesday update that Microsoft will release on November 12, 2019 to the public.

The update follows last week's updates that Microsoft released for earlier versions of Windows 10 and Windows 7 and Windows 8.1 as well as server variants.

KB4522355 for Windows 10 version 1903

KB4522355 windows 10 1903

KB4522355 is made available via Windows Update, Microsoft Update, Windows Server Update Services (WSUS), and as a direct download on Microsoft's Update Catalog website.

The update includes the following improvements and fixes:

  • Fixed an issue affecting Origin HTTP headers in Internet Explorer.
  • Fixed a Microsoft Narrator issue that prevented it from working in "certain touch mode scenarios". Fixed another Microsoft Narrator issue that had it stop working.
  • Fixed an issue that affected setting synchronization if "Continue experiences on this device" was set to disabled in the Group Policy.
  • Fixed an issue with assistive technology features.
  • Fixed the error message "OACClearArry: Cannot connect to Trace32 OLE Automation server. Error code: -2147483645." that appeared when opening apps after enabling NT Virtual DOS Machine and the legacy console mode.
  • Fixed a Magnifier issue that caused it to stop working (users had to restart to get it working again).
  • Updated time zone information for Fiji Islands, Australia and Norfolk Island.
  • Fixed an issue with the color command when setting the default Command Prompt window color.
  • Fixed a Microsoft Windows Search Indexer issue that caused it to "add or repair required access control lists without checking" if those exist.
  • Fixed an issue that had Win32 application controls fail to render correctly when started from logoff scripts using the "run shutdown scripts visible" policy.
  • Fixed an issue caused by too many font installations on a system that caused applications to stop responding.
  • Fixed a high CPU usage issue in the Desktop Window Manager that occurred when disconnected Remote Desktop Protocol sessions.
  • Fixed a scroll bar selection issue in Internet Explorer.
  • Fixed an issue that made the system go to Sleep after 2 minutes of inactivity even if the sleep timer was set to "never sleep".
  • Fixed an issue that prevented users from resizing windows.
  • Fixed an issue that caused Microsoft SharePoint filenames to appear incorrectly.
  • Fixed an issue that prevented the successful establishing of VPN connections.
  • Fixed a screen flickering or "slow to display" issue when showing application thumbnails on high DPI monitors.
  • Fixed a permission issue on a user's class Registry keys that could prevent users from "opening files, links, and applications".
  • Fixed a Photos app tile issue that made it appear larger than it should be.
  • Fixed an issue that made the system stop responding on the sign in screen.
  • Fixed a Windows Hello for Business issue that made it fail to show the default sign-in options.
  • Fixed a Windows Search option that caused it to close unexpected.
  • Fixed an issue that prevented the correct DHCP information from being retrieved.
  • Fixed a diagnostic data processing issue.
  • Fixed an opening issue that affected Internet Explorer.
  • Improved the reliability of UE-V AppMonitor.
  • Fixed an issue that caused Microsoft AppLocker to prevent applications from running or log false positives.
  • Fixed a netdom.exe issue.
  • Fixed an issue that caused Direct Access servers to use a large amount of non-paged pool memory.
  • Fixed an AppContainer firewall rules leak.
  • Fixed an issue that prevented the Windows Update Unified Write Filter servicing mode from working with Windows Server Update Services servers.
  • Fixed an issue that consumed all TCP dynamic ports.
  • Fixed an issue with NetQueryDisplayInformation API or the WinNT provider equivalent.
  • Fixed an issue that disrupted window ordering.
  • Improves access control list checks for Known Folders.
  • Fixed an issue with evaluating the compatibility status of the "Windows ecosystem".
  • Fixed an issue with Autopilot self-deploying mode.
  • Addressed an issue in which the pszTargetName parameter was set incorrectly in the InitializeSecurityContext() API.
  • Fixed an issue that caused certain core interface elements -- Start menu, Cortana Search, Tray icons, Microsoft Edge -- to stop responding after installing monthly updates.

Microsoft lists no known issues at this point. We recommend that the update is not installed at this point unless one of the issues is experienced.

Now you: did you install the update?

Summary
Microsoft releases KB4522355 for Windows 10 version 1903
Article Name
Microsoft releases KB4522355 for Windows 10 version 1903
Description
Microsoft released a new cumulative update for the current version of Windows 10, Windows 10 version 1903, on October 24, 2019.
Author
Publisher
Ghacks Technology News
Logo
Advertisement

Tutorials & Tips


Previous Post: «
Next Post: «

Comments

  1. EP said on November 8, 2019 at 12:52 am
    Reply

    Hi Martin.

    It appears that the KB4522355 update fixes the “broken or disappearing” update deferral option as noted by this recent Computerworld.com article by Woody:

    https://www.computerworld.com/article/3452525/disappearing-windows-update-deferral-pane-suddenly-reappears.html

  2. Cinikal said on October 26, 2019 at 10:31 am
    Reply

    Does anyone know what will happen to all the tablets with 16gb hard drives, are they just kicked to the curb?

  3. Dave said on October 25, 2019 at 4:56 pm
    Reply

    I have to wonder, do these issues effect my use of my PC or M$’s?

  4. Turbo_Toes said on October 25, 2019 at 11:47 am
    Reply

    This new patch DOES NOT FIX my particular issue on 1903. If I sysprep with this patch or the previous patch KB4517389 I get Default Apps crash (x18) when the computer comes back up.
    Not ideal. If I block this patch and the KB4517389 and create the image, the patch installs fine.. It just means that the user has to sit through this monster before staging.
    Well Annoying Microsoft, sort that SH** OUT MAN..

  5. chesscanoe said on October 25, 2019 at 4:20 am
    Reply

    WU not only installed optional KB4522355, but .NET cumulative update KB4519573 as well. Autopilot KB4523786 was also installed on my installed Microsoft Windows [Version 10.0.18362.449] x64 Home laptop even though tenforums.com says it is never offered in my environment. Nothing seems broken so far with 5 hours of use.

    1. chesscanoe said on October 26, 2019 at 1:17 am
      Reply

      Per https://www.computerworld.com/article/3448576/microsoft-pushes-then-yanks-rogue-kinda-security-patch-kb-4523786-ostensibly-for-autopilot.html I uninstalled KB4523786. It took not one but two restarts before Check History was correct.

  6. pHROZEN gHOST said on October 25, 2019 at 12:27 am
    Reply

    Big question is, what will it break?

    1. stefann said on October 25, 2019 at 2:40 pm
      Reply

      Windows 10 ???

  7. Bobby Phoenix said on October 24, 2019 at 10:54 pm
    Reply

    My bad. I didn’t get this one. It was KB4517389. All three running 1903, but only one got that update.

  8. Bobby Phoenix said on October 24, 2019 at 10:52 pm
    Reply

    Funny you say it was released today. I got it on one of my three machines on Tuesday. I kept checking on the other two then, and yesterday, but it never showed. I wonder why I got it early. Maybe a beta tester? LOL

    1. pHROZEN gHOST said on October 25, 2019 at 12:31 am
      Reply

      That one machine may be on the Windows Insider Program (i.e. you are a free beta test team member).

      One of my 3 PCs was using Zonealarm +av (the others were on Win Def). When I switched to Win Def, I noticed that I was also on the insider program. So I had to fix a couple of registry settings to nix that.

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.