Microsoft – Microsoft releases new 20H2 construct for Home windows Insiders within the Beta and Launch Preview channels » OnMSFT.com

Home windows Insiders within the Beta and Launch Preview channels can obtain at present a brand new patch for the Home windows 10 October 2020 Replace (20H2). That is the cumulative replace construct 19042.662 (KB4586853), which brings a protracted checklist of fixes associated to the contact keyboard, the Xbox Sport Bar, USB 3.Zero hubs, and extra.

You could find the complete checklist of high quality fixes included on this construct beneath:

• We up to date Web Explorer’s About dialog to make use of the usual fashionable dialog.
• We mounted a problem that causes Narrator to cease responding after you unlock a tool if Narrator was in use earlier than you locked the gadget.
• We mounted a problem that fails to show the native account teams within the localized language even after you deploy the language pack.
• We mounted a problem that forestalls a consumer from discovering sure Microsoft Xbox consoles on a Home windows gadget.
• We mounted a problem that shows a black display screen to Home windows Digital Desktop (WVD) customers once they try to register.
• We mounted a problem with a sure COM API that causes a reminiscence leak.
• We mounted a problem that fails to show the Microsoft Xbox Sport Bar app controls on supported screens. This problem happens in sure Microsoft DirectX® 9.0 (DX9) video games which are working with Variable Refresh Fee enabled on these screens.
• We mounted a problem that forestalls the contact keyboard from opening in Common Home windows Platform (UWP) apps when USB gadgets are related.
• We mounted a problem with USB 3.Zero hubs. A tool related to the hub may cease working whenever you set the gadget to hibernate or restart the gadget.
• We mounted a problem that crops the contact keyboard whenever you use a Distant Desktop Connection on a tool that has a distinct display screen decision.
• We mounted a problem with extreme community visitors that happens whenever you use the Open File dialog field in File Explorer and browse to a shared folder that has the Earlier Model function out there.
• We mounted a problem that causes the ImmGetCompositionString() operate to return the full-width Hiragana when utilizing the Microsoft Enter Technique Editor (IME) for Japanese as an alternative of returning the half-width Katakana.
• We mounted a problem that forestalls Soar checklist gadgets from functioning. This happens whenever you create them utilizing the Home windows Runtime (WinRT) Home windows.UI.StartScreen API for desktop purposes which are packaged within the MSIX format.
• We mounted a problem that forestalls purposes from receiving the Shift and Ctrl keystroke occasions when the Bopomofo, Changjie, or Fast Enter Technique Editors (IME) are in use.
• We mounted a problem that randomly modifications the enter focus of edit controls when utilizing the Japanese IME or the Chinese language Conventional IME.
• We mounted a problem that forestalls you from signing in on sure servers. This happens whenever you allow a Group Coverage that forces the beginning of a pc session to be interactive.
• We mounted a problem that fails to set the desktop wallpaper as configured by a GPO whenever you specify the native background as a stable colour.
• We mounted a problem with the Microsoft Pinyin IME that unexpectedly dismisses the candidate pane whenever you sort sure phrases.
• We mounted a problem that fails to ship the Shift keyup occasion to an utility whenever you use the Japanese IME.
• We mounted a problem that renders Kaomoji incorrectly on the emoji panel.
• We mounted a problem that makes the contact keyboard unstable within the Mail app.
• We mounted a problem that enters sudden characters, corresponding to half-width Hiragana, whenever you sort a password whereas the IME is in Kana enter mode.
• We mounted a problem which may fail to pair sure MIDI gadgets that join utilizing Bluetooth Low Vitality (LE).
• We mounted a runtime error that causes Visible Primary 6.0 (VB6) to cease working when duplicate home windows messages are despatched to WindowProc().
• We mounted a problem that generates a 0x57 error when the wecutil ss /c: command is used to replace an Occasion Forwarding subscription.
• We mounted a problem that causes purposes to fail once they name the LookupAccountSid() API. This happens after migrating accounts to a brand new area whose title is shorter than the title of the earlier area.
• We mounted a problem wherein loading a Code Integrity Coverage causes PowerShell to leak a considerable amount of reminiscence.
• We mounted a problem that causes a system to cease working throughout startup. This happens when the CrashOnAuditFail coverage is ready to 1 and command-line argument auditing is turned on.
• We mounted a problem that causes the Microsoft Administration Console (MMC) Group Coverage utility to cease working when you’re enhancing the Group Coverage Safety settings. The error message is, “MMC cannot initialize the snap-in.”
• We mounted a problem that fails to free a system’s non-paged pool and requires a restart of the system. This happens when working 32-bit purposes with the Federal Data Processing Normal (FIPS) mode enabled.
• We mounted a problem which may forestall updates from putting in and generates an “E_UNEXPECTED” error.
• We mounted a problem that causes the “I forgot my Pin” performance on the lock display screen to fail. This failure happens if the consumer has signed in utilizing a username and password and the DontDisplayLastUserName or HideFastUserSwitching coverage settings are enabled.
• We mounted a problem that forestalls entry to Azure Energetic Listing (AD) utilizing the Google Chrome browser due to a Conditional Entry coverage error.
• We improved the visible high quality of Home windows Blended Actuality headsets that run in decrease decision mode.
• We prolonged Microsoft Defender for Endpoint assist to new areas.
• We enabled a brand new {Hardware}-enforced Stack Safety function known as shadow stacks on supported {hardware}. This replace permits purposes to decide in to user-mode shadow stack safety, which helps harden backward-edge control-flow integrity and prevents return-oriented programming-based assaults.
• We mounted a problem within the Microsoft Distant Process Name (RPC) runtime that causes the Distributed File System Replication (DFSR) service to cease responding. This problem generates log occasions for DFS Replication (5014), RPC (1726), and no reconnection (5004) for a default timeout of 24 hours with no replication.
• We added the contact keyboard to the allowed apps checklist, and it now works in multi-app assigned entry mode.
• We mounted a problem that forestalls the PDF24 app, model 9.1.1, from opening .txt recordsdata.
• We mounted a problem which may trigger a non-paged pool reminiscence leak in some eventualities.
• We mounted a problem that permits an app that has been blocked from hydrating recordsdata to proceed hydrating recordsdata in some circumstances.
• We mounted a problem which may trigger a reminiscence leak in bindflt.sys when copying recordsdata in a container state of affairs.
• We mounted a problem with Energetic Listing Certificates Companies (AD CS) that fails to submit Certificates Transparency (CT) logs when they’re enabled.
• We mounted a problem wherein cluster validation exams inside switches that aren’t for cluster use and re-communication.
• We mounted a problem that causes cease error 0x27 whenever you try to register to a tool that’s not in a website utilizing credentials for a tool that’s within the area.
• We mounted a problem that causes a tool to repeatedly restart after putting in an app.
• We mounted points with Kerberos authentication associated to the PerformTicketSignature registry subkey value in CVE-2020-17049, which was part of the November 10, 2020 Home windows replace. The next points may happen on writable and read-only area controllers (DC):
  • Kerberos service tickets and ticket-granting tickets (TGT) won’t renew for non-Home windows Kerberos purchasers when PerformTicketSignature is ready to 1 (the default).
  • Service for Consumer (S4U) eventualities, corresponding to scheduled duties, clustering, and providers for line-of-business purposes, may fail for all purchasers when PerformTicketSignature is ready to 0.
  • S4UProxy delegation fails throughout ticket referral in cross-domain eventualities if DCs in intermediate domains are inconsistently up to date and PerformTicketSignature is ready to 1.

In case you missed it, the Home windows Insider group announced last week that as a result of Thanksgiving vacation, there wouldn’t be a brand new Dev Channel flight this week. We hope the group might be again to enterprise subsequent week, and hopefully with a construct that brings greater than the standard bug fixes.

Share This Publish: