Advertisement

Windows 10 Build 18363.1474 is out for version 1909 in Preview

Microsoft today released a new Preview patch for Windows 10 version 1909. The update KB5000850 is available as an optional update, and can be installed from Settings manually. Before installing, keep in mind that this patch will remove the Microsoft Edge Legacy desktop application.

WIndows 10 1909 19h2 Banner

We would like to mention that consumer support for Windows 10 version 1909 will be ended in May. After May 11, 2021, the Home, Pro, Pro Education, Pro for Workstations editions of Windows 10 version 1909 and all editions of Windows Server, version 1909 will no longer receive security updates.

Advertisement

Here are the changes in KB5000850.

What's new in Windows 10 Build 18363.1474

  • Removes the Microsoft Edge Legacy desktop application that is out of support and installs the new Microsoft Edge. For more information, see New Microsoft Edge to replace Microsoft Edge Legacy with April’s Windows 10 Update Tuesday release

  • Addresses an issue with zoom that occurs when using Microsoft Edge IE Mode on devices that use multiple high-DPI monitors.
  • Allows administrators to use a Group Policy to enable extended keyboard shortcuts, including Ctrl+S, for users in Microsoft Edge IE Mode.
  • Addresses an issue that might cause a deadlock when a COM server delivers an event to multiple subscribers in parallel.
  • Addresses an issue with Japanese input that occurs after focus changes between boxes in Microsoft Edge Legacy.
  • Addresses issue that causes 16-bit apps that run on NT Virtual DOS Machine (NTVDM) to stop working when you open them.
  • Addresses an issue with USB 3.0 hubs. A device connected to the hub might stop working when you set the device to hibernate or restart the device.
  • Addresses an issue that prevents users from adjusting or turning off the touchpad because of administrative settings.
  • Addresses an issue that displays nothing or shows “Computing Filters” indefinitely when you filter File Explorer search results.
  • Updates the Volgograd, Russia time zone from UTC+4 to UTC+3.
  • Adds a new time zone, UTC+2:00 Juba, for the Republic of South Sudan.
  • Addresses an issue with the Windows Event Log Forwarding client, which returns the first matching certificate without checking private key permissions. With this update, the Windows Event Log Forwarding client selects the client’s certificate only if the Network Service has read permissions for the private key.
  • Addresses an issue that causes PowerShell-based monitors to stop working when you enable transcription on the systems.
  • Addresses an issue that stops BranchCache from working if you activate Windows using Cloud Solution Provider (CSP) license.
  • Addresses an issue that prevents App-V applications from opening and generates error 0xc0000225.
  • Addresses an issue in which some machines enrolled with a mobile device management (MDM) service fail to sync if the device manufacturer's name contains a reserved character.
  • Addresses an issue with using a configuration service provider (CSP) policy to configure a custom setting for Audit Other Logon/Logoff events. The custom setting fails to take effect.
  • Updates the Open Mobile Alliance (OMA) Device Management (DM) sync protocol by adding a check-in reason for requests from the client to the server. The check-in reason will allow the MDM service to make better decisions about sync sessions. With this change, the OMA-DM service must negotiate a protocol version of 4.0 with the Windows OMA-DM client.
  • Addresses an issue with credential roaming that occurs when Windows Hello for Business is enabled.
  • Addresses an issue that prevents users from using the Remote Desktop Protocol (RDP) to connect to a Windows Server 2019 device that is in Desktop Experience mode.
  • Addresses an issue that might prevent Hypervisor-Protected Code Integrity (HVCI) from being enabled when you configure it using a Group Policy.
  • Addresses an issue that causes multiple instances of appidcertstorecheck.exe to run on a system when AppLocker is enabled and the system is not on the internet.
  • Addresses an issue that causes a black screen or delays signing in to a Hybrid Azure Active Directory joined machine while the machine attempts to connect to login.microsoftonline.com.
  • Addresses an issue that prevents the Chromium-based Microsoft Edge from working. This issue occurs when Microsoft Edge is used in combination with Microsoft App-V and fonts are enabled inside the virtual environment.
  • Addresses possible race conditions that occur when the system calls NtOpenKeyEx(),which results in a stop error.
  • Addresses an issue with high memory usage when performing XSLT transforms using MSXLM6.
  • Addresses an issue that prevents Server Message Block 1 (SMB1) clients from accessing the SMB share after restarting the LanmanServer service.
  • Addresses an issue that might cause the cluster network interface to stop working for a short time. As a result, the network interface controller (NIC) is marked as failed. When the network is operational again, the system might not detect that the NIC is working and the NIC remains in a failed status.
  • Addresses an issue with signing in to a device that is in the current domain by using the default user profile of a device that is in a different, but trusted domain. The profile service of the current domain cannot retrieve the default user profile from the trusted domain and uses the local default user profile instead.
  • Addresses an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.
  • Addresses an issue that turns on Caps lock unexpectedly when using RemoteApp.
  • Addresses an issue with the svhost process that hosts the Microsoft-Windows-TerminalServices-LocalSessionManager. The svhost process consumes increasingly large amounts of memory because of a leak in COMMAND_ENTRY objects. Memory leaks might cause issues when signing in to an application or to the Remote Desktop. In extreme cases, the server might stop responding.

Support us

Winaero greatly relies on your support. You can help the site keep bringing you interesting and useful content and software by using these options:

If you like this article, please share it using the buttons below. It won't take a lot from you, but it will help us grow. Thanks for your support!

Advertisment

Author: Sergey Tkachenko

Sergey Tkachenko is a software developer who started Winaero back in 2011. On this blog, Sergey is writing about everything connected to Microsoft, Windows and popular software. Follow him on Telegram, Twitter, and YouTube.

One thought on “Windows 10 Build 18363.1474 is out for version 1909 in Preview”

  1. I came from revert H20 (microsoft suggested upgrade) to previous (19H) because was completely mess up my PC (see articles about H20) and this was needed a lot of work because nothing worked as expected in H20.

    I’m afraid to install this (KB5000850) update because I don’t want even more extra restrictions. I don’t want microsoft makes completely enforced decisions about everything: what exactly – and how exactly I need to use. For example, in H20 upgrade microsoft decided to remove, itself, a bunch of installed programs! (like Firefox, CCleaner, K-Lite Codec Pack, Notepad++, Viber, Vuse, and 23 more…! After this, many of programs needed to install again from scratch, included licenses, serials ect…)

    There’s anyone who has try this update?
    Should I install it?
    (of course, I don’t ever use Edge)

Leave a Reply

Your email address will not be published.

css.php
Using Telegram? Subscribe to the blog channel!
Hello. Add your message here.