Windows Insider Beta Channel Builds for 20H2 (Slow Ring)

Corrine

Corrine

Administrator,
Microsoft MVP,
Security Analyst
Staff member
Joined
Feb 22, 2012
Posts
12,393
Location
Upstate, NY
From Announcing Windows 10 Insider Preview Build 19042.330 (20H2)

Hello Windows Insiders, today we are announcing Windows 10 version 20H2 as the next feature update for Windows 10. The 20H2 feature update will be a scoped set of features and include the new Microsoft Edge based on Chromium. As part of today’s announcement, we’re also releasing 20H2 Build 19042.330 to the Beta Channel (Slow ring). This build includes the following fixes from KB4557957 as well as the new Microsoft Edge. After updating to today’s build, Microsoft Edge will be updated to the new Microsoft Edge based on Chromium.
Click to expand...
 
Windows Insider Preview Build 19042.388 (20H2) Released to Windows Insider in the Beta Channel: Announcing Windows 10 Insider Preview Build 19042.388 (20H2) | Windows Experience Blog.

The update includes a number of fixes including security updates to the following: Microsoft Scripting Engine, Windows App Platform and Frameworks, the Microsoft Store, Windows Graphics, Windows Input and Composition, Windows Media, Windows Shell, Windows Fundamentals, Windows Management, Windows Kernel, Windows Hybrid Cloud Networking, Windows Storage and Filesystems, Windows Update Stack, Windows MSXML, Windows File Server and Clustering, Windows Remote Desktop, Internet Explorer, Microsoft Edge Legacy, and the Microsoft JET Database Engine.
 
Windows Insider Preview Build 19042.421 (20H2) Released to Beta Channel: Announcing Windows 10 Insider Preview Build 19042.421 (20H2) | Windows Experience Blog.

New features include a refresh of the Start menu, ALT + TAB between apps and sites with Microsoft Edge, improving pinned sites in Microsoft Edge, improvements in the notifications experience. continuation of bringing capabilities from Control Panel forward into Settings and more, including changes and fixes.
 
Corrine said:
ALT + TAB between apps and sites with Microsoft Edge
Click to expand...

And from what I understand, the Edge function will be the default for ALT+TAB, so if you're someone who actually still uses it to switch between running applications under Windows, you'll need to tweak it back to that function.

This will end up being a big deal in the blind and visually-impaired user community where ALT+TABBING between running applications has been standard operating procedure for decades.
 
britechguy said:
And from what I understand, the Edge function will be the default for ALT+TAB, so if you're someone who actually still uses it to switch between running applications under Windows, you'll need to tweak it back to that function.

This will end up being a big deal in the blind and visually-impaired user community where ALT+TABBING between running applications has been standard operating procedure for decades.
Click to expand...
I can't decide whether I'm imagining it, but I think IE used to let you alt+tab between open tabs, although I can't remember if it was default or not.
 
Note that the addition to Microsoft Edge specifically includes "apps" in the wording. Thus, with the shortcut addition to Microsoft Edge, ALT + TAB will now work with both applications as well as websites open on the browser. To test, I had Edge open with four tabs and two apps open. With ALT + TAB, each website and each app was displayed and I could tab between them, stopping on either the website or app of my choice.
 
Windows Insider Preview Build 19042-487 (20H2) Released to Beta Channel: Announcing Windows 10 Insider Preview Build 19042.487 (20H2) | Windows Insider Blog.

The update is a non-security update, KB4571744, with a very long list of fixed issues as well as quality improvements. In addition, 20H2 has been released to commercial customers in the Beta Channel and Release Preview Channel for pre-release validation as indicated in Windows 10, version 20H2 available for commercial pre-release validation
 
Windows Insider Preview Build 19042.508 (20H2) Released to Beta Channel: Announcing Windows 10 Insider Preview Build 19042.508 (20H2) | Windows Insider Blog.

This security update includes the following quality improvements:
  • We fixed an issue with a possible elevation of privilege in windowmanagement.dll.
  • We fixed a security vulnerability issue with user proxies and HTTP-based intranet servers. After installing this update, HTTP-based intranet servers cannot leverage a user proxy by default to detect updates. Scans using these servers will fail if the clients do not have a configured system proxy. If you must leverage a user proxy, you must configure the behavior using the Windows Update policy “Allow user proxy to be used as a fallback if detection using system proxy fails.” This change does not affect customers who secure their Windows Server Update Services (WSUS) servers with the Transport Layer Security (TLS) or Secure Sockets Layer (SSL) protocols. For more information, see Ensuring clients stay secure, changes to scans against Windows Server Update Service (WSUS) servers.
  • Security updates to Windows App Platform and Frameworks, Microsoft Graphics Component, Windows Input and Composition, Windows Media, Windows Shell, Windows Cloud Infrastructure, Windows Fundamentals, Windows Management, Windows Kernel, Windows Virtualization, Windows Storage and Filesystems, and the Microsoft JET Database Engine.
 
Windows Insider Build 19042.572 (KB4579311) Released to Beta and Release Preview Rings: Announcing Windows 10 Insider Preview Build 19042.572 (20H2) | Windows Insider Blog.

The update includes today's security updates as well as the following fixes:
  • We fixed an issue with a possible elevation of privilege in win32k.
  • We fixed an issue with the Group Policy service that might recursively delete critical files in alphabetic order from %systemroot%\systm32. This issue occurs when a policy has been configured to delete cached profiles. These file deletions might cause stop error “0x5A (CRITICAL_SERVICE_FAILED)” boot failures.
  • We fixed an issue with creating null ports using the user interface.
  • Security updates to Windows App Platform and Frameworks, Microsoft Graphics Component, Windows Media, Windows Fundamentals, Windows Authentication, Windows Virtualization, and Windows Kernel.
 
Windows Insider Build 19042-608 (20H2) ((KB4580364) released to Windows Insider in the Release Preview and Beta Channel Rings: Announcing Windows 10 Insider Preview Build 19042.608 (20H2) | Windows Insider Blog.

Initially the build is going to Insiders in the Release Preview Ring and later to those in the Beta Channel.

This update includes the following fixes and improvements:
  • Earlier this year we introduced Meet Now in Skype. Meet Now makes it easy to connect with anyone in as little as two clicks for free and each call can last up to 24 hours. Today, we’re excited to share that we will be extending this capability in Windows 10 by bringing Meet Now right to the taskbar. In the coming weeks, you will be able to easily set up a video call and reach friends and family in an instant by clicking the Meet Now icon in the taskbar notification area. No sign ups or downloads needed.
  • We fixed an issue with using Group Policy Preferences to configure the homepage in Internet Explorer.
  • We gave administrators the ability to use a Group Policy to enable Save Target As for users in Microsoft Edge IE Mode.
  • We fixed an issue with untrusted URL navigations from Internet Explorer 11 by opening them in Microsoft Defender Application Guard using Microsoft Edge.
  • We fixed an issue that occurs when using the full suite of developer tools in Microsoft Edge for remote debugging on a Windows 10 device.
  • We fixed an issue that displays nothing on the screen for five minutes or more during the Remote Desktop Protocol (RDP) session.
  • We fixed an issue that prevents certain Windows Virtual Desktop (WVD) users from searching for files using File Explorer.
  • We fixed an issue that causes a device to stop responding after you have been using a pen for several hours.
  • We fixed an issue that causes an application to stop responding temporarily, which causes extra z-order operations that affect the Topmost property of a window.
  • We fixed an issue that might cause DDE apps to stop working.
  • We fixed an issue that causes the ImmGetCompositionString() function to return the full-width Hiragana when using the Microsoft Input Method Editor (IME) for Japanese instead of returning the half-width Katakana.
  • We fixed an issue that occurs when you first sign in to an account or unlock an existing user session using Remote Desktop Services (RDS). If you enter an incorrect password, the current keyboard layout changes unexpectedly to the system default keyboard layout. This keyboard layout change might cause additional attempts to sign in to fail or lead to account lockouts in domains with low account lockout thresholds.
  • We fixed an issue that displays the incorrect CPU frequency for certain processors.
  • We fixed a performance issue that occurs when PowerShell reads the registry to check if the ScriptBlockLogging registry key is in the registry.
  • We fixed an issue that randomly changes the time offset of the time format returned by the command exe OS Get localdatetime/ value.
  • We fixed an issue that prevents Microsoft User Experience Virtualization (UE-V) from assigning the Microsoft Outlook Signatures.
  • We fixed an issue that prevents Hybrid Azure Active Directory joined devices from updating portal information when a device name or Windows version changes.
  • We fixed an issue that might prevent the Smart Cards for Windows service from starting.
  • We added a new Microsoft Event Tracing for Windows (ETW) provider named “Microsoft-Antimalware-UacScan”. This ETW provider reports the details of the context for
  • each User Account Control (UAC) request in the ETW provider manifest.
  • We fixed an issue with virtual private network (VPN) connections that use Secured Password (EAP-MSCHAP v2) for authentication and have enabled the “Automatically use my Windows logon user name and password” property. When you connect to this type of VPN, an authentication dialog box incorrectly prompts for your credentials.
  • We now display Recovery Partitions in the diskpart utility.
  • We fixed an issue that causes stop error 0xd1 in sys. This issue occurs when moving certain arrays from one cluster node to another.
  • We fixed an issue that causes the IAutomaticUpdatesResults::get_LastInstallationSuccessDate method to return 1601/01/01 when there are no active updates.
  • We added support for the Transport Layer Security (TLS) 1.1 and 1.2 protocols when connecting to SQL Server using the data providers in Windows Defender Application Control (WDAC).
  • We fixed an issue with SQL Server that might cause performance issues if you configure a Linked Server provider to load out-of-process.
  • We fixed an issue that might degrade Windows performance and prevent the LanmanServer service from starting when third-party software uses LanmanServer custom file system controls (FSCTL).
  • We fixed an issue with deduplication that causes long wait times on Resilient File System (ReFS) Cluster Shared Volumes (CSV).
  • We fixed an issue that might prevent some applications from behaving correctly. This occurs when you publish them as Remote Application Integrated Locally (RAIL) applications using Remote Desktop Services (RDS) and change the docking for an AppBar
  • We fixed an issue with a deadlock in the Transmission Control Protocol/Internet Protocol (TCPIP) driver that causes the operating system to stop working or stop responding.
  • We fixed an issue that causes the Routing and Remote Access Service (RRAS) to stop responding for new connections. However, RRAS continues working for existing connections.
  • We fixed an issue that causes the RRAS administrator Microsoft Management Console (MMC) to stop responding randomly when you are performing administrative tasks or at startup.
  • We fixed an issue with starting Windows Subsystem for Linux 2 (WSL2) on ARM64 devices that occurs after installing KB4579311.

Modify message
 
Windows Insider Preview Build 19042.662 Released to the Beta and Preview Builds (20H2): Announcing Windows 10 Insider Preview Build 19042.662 (20H2) | Windows Insider Blog.

Included in the update is the following long list of fixes and improvements:

  • We updated Internet Explorer’s About dialog to use the standard modern dialog.
  • We fixed an issue that causes Narrator to stop responding after you unlock a device if Narrator was in use before you locked the device.
  • We fixed an issue that fails to display the local account groups in the localized language even after you deploy the language pack.
  • We fixed an issue that prevents a user from finding certain Microsoft Xbox consoles on a Windows device.
  • We fixed an issue that displays a black screen to Windows Virtual Desktop (WVD) users when they attempt to sign in.
  • We fixed an issue with a certain COM API that causes a memory leak.
  • We fixed an issue that fails to display the Microsoft Xbox Game Bar app controls on supported monitors. This issue occurs in certain Microsoft DirectX® 9.0 (DX9) games that are running with Variable Refresh Rate enabled on these monitors.
  • We fixed an issue that prevents the touch keyboard from opening in Universal Windows Platform (UWP) apps when USB devices are connected.
  • We fixed 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.
  • We fixed an issue that crops the touch keyboard when you use a Remote Desktop Connection on a device that has a different screen resolution.
  • We fixed an issue with excessive network traffic that occurs when you use the Open File dialog box in File Explorer and browse to a shared folder that has the Previous Version feature available.
  • We fixed an issue that causes the ImmGetCompositionString() function to return the full-width Hiragana when using the Microsoft Input Method Editor (IME) for Japanese instead of returning the half-width Katakana.
  • We fixed an issue that prevents Jump list items from functioning. This occurs when you create them using the Windows Runtime (WinRT) Windows.UI.StartScreen API for desktop applications that are packaged in the MSIX format.
  • We fixed an issue that prevents applications from receiving the Shift and Ctrl keystroke events when the Bopomofo, Changjie, or Quick Input Method Editors (IME) are in use.
  • We fixed an issue that randomly changes the input focus of edit controls when using the Japanese IME or the Chinese Traditional IME.
  • We fixed an issue that prevents you from signing in on certain servers. This occurs when you enable a Group Policy that forces the start of a computer session to be interactive.
  • We fixed an issue that fails to set the desktop wallpaper as configured by a GPO when you specify the local background as a solid color.
  • We fixed an issue with the Microsoft Pinyin IME that unexpectedly dismisses the candidate pane when you type certain phrases.
  • We fixed an issue that fails to send the Shift keyup event to an application when you use the Japanese IME.
  • We fixed an issue that renders Kaomoji incorrectly on the emoji panel.
  • We fixed an issue that makes the touch keyboard unstable in the Mail app.
  • We fixed an issue that enters unexpected characters, such as half-width Hiragana, when you type a password while the IME is in Kana input mode.
  • We fixed an issue that might fail to pair certain MIDI devices that connect using Bluetooth Low Energy (LE).
  • We fixed a runtime error that causes Visual Basic 6.0 (VB6) to stop working when duplicate windows messages are sent to WindowProc().
  • We fixed an issue that generates a 0x57 error when the wecutil ss /c: command is used to update an Event Forwarding subscription.
  • We fixed an issue that causes applications to fail when they call the LookupAccountSid() API. This occurs after migrating accounts to a new domain whose name is shorter than the name of the previous domain.
  • We fixed an issue in which loading a Code Integrity Policy causes PowerShell to leak a large amount of memory.
  • We fixed an issue that causes a system to stop working during startup. This occurs when the CrashOnAuditFail policy is set to 1 and command-line argument auditing is turned on.
  • We fixed an issue that causes the Microsoft Management Console (MMC) Group Policy application to stop working when you are editing the Group Policy Security settings. The error message is, “MMC cannot initialize the snap-in.”
  • We fixed an issue that fails to free a system’s non-paged pool and requires a restart of the system. This occurs when running 32-bit applications with the Federal Information Processing Standard (FIPS) mode enabled.
  • We fixed an issue that might prevent updates from installing and generates an “E_UNEXPECTED” error.
  • We fixed an issue that causes the “I forgot my Pin” functionality on the lock screen to fail. This failure occurs if the user has signed in using a username and password and the DontDisplayLastUserName or HideFastUserSwitching policy settings are enabled.
  • We fixed an issue that prevents access to Azure Active Directory (AD) using the Google Chrome browser because of a Conditional Access policy error.
  • We improved the visual quality of Windows Mixed Reality headsets that run in lower resolution mode.
  • We extended Microsoft Defender for Endpoint support to new regions.
  • We enabled a new Hardware-enforced Stack Protection feature called shadow stacks on supported hardware. This update allows applications to opt in to user-mode shadow stack protection, which helps harden backward-edge control-flow integrity and prevents return-oriented programming-based attacks.
  • We fixed an issue in the Microsoft Remote Procedure Call (RPC) runtime that causes the Distributed File System Replication (DFSR) service to stop responding. This issue generates log events for DFS Replication (5014), RPC (1726), and no reconnection (5004) for a default timeout of 24 hours with no replication.
  • We added the touch keyboard to the allowed apps list, and it now works in multi-app assigned access mode.
  • We fixed an issue that prevents the PDF24 app, version 9.1.1, from opening .txt files.
  • We fixed an issue that might cause a non-paged pool memory leak in some scenarios.
  • We fixed an issue that allows an app that has been blocked from hydrating files to continue hydrating files in some cases.
  • We fixed an issue that might cause a memory leak in bindflt.sys when copying files in a container scenario.
  • We fixed an issue with Active Directory Certificate Services (AD CS) that fails to submit Certificate Transparency (CT) logs when they are enabled.
  • We fixed an issue in which cluster validation tests internal switches that are not for cluster use and re-communication.
  • We fixed an issue that causes stop error 0x27 when you attempt to sign in to a device that is not in a domain using credentials for a device that is in the domain.
  • We fixed an issue that causes a device to continually restart after installing an app.
  • We fixed issues with Kerberos authentication related to the PerformTicketSignature registry subkey value in CVE-2020-17049, which was a part of the November 10, 2020 Windows update. The following issues might occur on writable and read-only domain controllers (DC):
    • Kerberos service tickets and ticket-granting tickets (TGT) might not renew for non-Windows Kerberos clients when PerformTicketSignature is set to 1 (the default).
    • Service for User (S4U) scenarios, such as scheduled tasks, clustering, and services for line-of-business applications, might fail for all clients when PerformTicketSignature is set to 0.
    • S4UProxy delegation fails during ticket referral in cross-domain scenarios if DCs in intermediate domains are inconsistently updated and PerformTicketSignature is set to 1.
 
Windows Insider Preview Build 19042.685 Released to the Beta and Preview Builds (20H2): Announcing Windows 10 Insider Preview Build 19042.685 (20H2).

This security update includes quality improvements. Key changes include:
  • We fixed a security vulnerability by preventing applications that run as a SYSTEM account from printing to “FILE:” ports. To address this issue in the future, make sure your applications or services run as a specific user or service account.
  • Security updates to Microsoft Edge Legacy, the Microsoft Graphics Component, Windows Media, Windows Fundamentals, and Windows Virtualization.
 
Windows Insider Preview Build 19042.746 Released to the Beta and Preview Builds (20H2): Releasing Windows 10 Build 19042.746 (20H2) to Beta and Release Preview Channels | Windows Insider Blog.

This security update includes quality improvements. Key changes include:
  • We fixed a security vulnerability issue with HTTPS-based intranet servers. After installing this update, HTTPS-based intranet servers cannot, by default, use a user proxy to detect updates. Scans using these servers will fail if you have not configured a system proxy on the clients. If you must use a user proxy, you must configure the behavior using the policy “Allow user proxy to be used as a fallback if detection using system proxy fails.” To ensure the highest levels of security, also use Windows Server Update Services (WSUS) Transport Layer Security (TLS) certificate pinning on all devices. This change does not affect customers who are using HTTP WSUS servers. For more information, see Changes to scans, improved security for Windows devices.
  • Addresses a security bypass vulnerability that exists in the way the Printer Remote Procedure Call (RPC) binding handles authentication for the remote Winspool interface. For more information, see KB4599464.
  • Security updates to Windows App Platform and Frameworks, Windows Media, Windows Fundamentals, Windows Cryptography, Windows Virtualization, Windows Peripherals, and Windows Hybrid Storage Services.
 
Windows Insider Build 19042.782 (20H2) (KB4598291) Released to Beta and Release Preview Channels: Releasing Windows 10 Build 19042.782 (20H2) to Beta and Release Preview Channels | Windows Insider Blog.

This update includes the following fixes and improvements:
  • We updated the default values for the following Internet Explorer registry keys:
    • svcKBFWLink = “ ” (empty string)
    • svcKBNumber = “ ” (empty string)
    • svcUpdateVersion = 11.0.1000.
In addition, these values will no longer be updated automatically.
  • We enabled administrators to disable standalone Internet Explorer using a Group Policy while continuing to use Microsoft Edge’s IE Mode.
  • We enabled you to configure certain policies that support Microsoft Edge IE Mode using mobile device management (MDM).
  • We fixed an issue in the Universal C Run-time Library (UCRT) that causes printf() to incorrectly round floating point values.
  • We fixed an issue that displays a User Account Control (UAC) dialog box unexpectedly when you turn on speech recognition.
  • We fixed an issue that fails to notify the target application when you select the Copy link command on the Share menu.
  • We fixed an issue that causes the 64-bit fmod() and remainder() functions to damage the Floating Point Unit (FPU) stack.
  • We fixed an issue that causes a stop error or causes a device to stop responding when you play a game in full-screen or tablet mode.
  • We fixed an issue with using Ctrl+Caps Lock and Alt+Caps Lock to switch to Hiragana or Katakana mode respectively after upgrading to Windows 10, version 2004.
  • We fixed an issue that prevents you from opening a document that is on the Windows desktop and generates the error, “The directory name is invalid.” This issue occurs after changing the desktop location in the Location tab of the Desktop Properties dialog box (File Explorer -> This PC -> Desktop).
  • We fixed an issue that creates duplicate cloud provider folders in the File Explorer navigation pane.
  • We fixed an issue that occurs when the Mandatory Profile check box is selected when you copy a user profile.
  • We fixed an issue that might cause the Alt+Tab order to change unexpectedly and cause you to switch to the wrong window.
  • We fixed an issue that prevents ImmGetCompositionString() from returning the white space for furigana when using the Japanese Input Method Editor (IME).
  • We fixed an issue with some special key combinations used in DaYi, Yi, and Array IMEs that might cause an application to stop working.
  • We fixed an issue that displays a blank lock screen after a device wakes up from Hibernate.
  • We corrected historical daylight savings time (DST) information for the Palestinian Authority.
  • We added support for serial number control using the registry.
  • We fixed an issue that incorrectly deactivates some Windows 10 Education devices after upgrading to Windows 10, version 2004.
  • We fixed an issue that causes the upload of diagnostic logs to a management service, such as Microsoft Intune, to fail. The failure occurs because of a network time-out on a slow network.
  • We displayed a notification to a user when an administrator signs in to an MDM service, such as Microsoft Intune, to find the location of a managed device.
  • We fixed an issue that prevents users from using their smart card credentials when the user hint is the domain credential name (domain\username).
  • We fixed an issue in which using local Service for User (S4U) affects Data Protection API (DPAPI) credential keys and causes users to sign out unexpectedly.
  • We fixed an issue that causes the silent mode deployment of BitLocker to fail with the error 0x80310001. This issue occurs when deploying BitLocker encryption to Hybrid Azure Active Directory (Azure AD) joined devices.
  • We fixed an issue that might cause a black screen to appear or delay signing in to Hybrid Azure Active Directory joined machines. Additionally, there is no access to login.microsoftonline.com.
  • We fixed an issue that might cause systems that use BitLocker to stop working with the error 0x120 (BITLOCKER_FATAL_ERROR).
  • We fixed an issue that causes a device to stop working when deploying Microsoft Endpoint Configuration Manager if AppLocker is enabled on the device.
  • We fixed an issue that cause the LSASS.exe process to leak memory on a server that is under a heavy authentication load when Kerberos Armoring (Flexible Authentication Secure Tunneling (FAST)) is enabled.
  • We fixed an issue that causes LSASS.exe to stop working because of a race condition that results in a double free error in Schannel. The exception code is c0000374, and the Event Log displays Schannel event 36888, fatal error code 20, and error state 960. This issue occurs after installing Windows updates from September 2020 and later.
  • We fixed a memory leak issue that occurs when you authenticate a client certificate on servers that are configured as domain controllers.
  • We fixed an issue with Virtual Interrupt Notification Assert (VINA) interrupts.
  • We fixed an issue with HTTP caching that interferes with kiosk mode that targets Azure AD groups.
  • We fixed an issue that occurs when a Volume Shadow Copy Service (VSS) snapshot triggers on virtual machines (VM) that contain Resilient File System (ReFS) volumes. The triggered VSS snapshot fails with a time-out and prevents access to the ReFS volume for 30 minutes.
  • We fixed an issue that incorrectly logs Extensible Storage Engine Technology (ESENT) event 642 in the Application Event Log.
  • We fixed an issue with Administrative Template settings you configure using a Group Policy Object (GPO). When you change the value of the policy settings to NOT CONFIGURED, the system fails to remove the previous settings. This issue is most noticeable with roaming user profiles.
  • We fixed an issue that might cause a deadlock in Windows Virtual Desktop when a user disconnects before a driver fully loads
  • We fixed an issue that fails to show Extract all on the shortcut menu when you right-click an online-only ZIP file.
  • We updated the process for enrolling in online speech recognition. If you are already enrolled, you will see a message that asks you to review the new settings. If you choose not to contribute your speech data for human review, you can still use online speech recognition. The new settings contain one button to turn on online speech recognition and another button that turns on the collection of your voice clips. If you turn on the collection of your voice clips, you can turn it off at any time using the same button in the new settings page.
  • We fixed an issue that prevents the Start menu, Cortana, and tiles pinned to the Taskbar from opening. This issue occurs when an administrator copies an existing profile that has the Mandatory Profile check box selected.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top