Windows 10 Insider Release Preview Channel (21H1)

Corrine

Corrine

Administrator,
Microsoft MVP,
Security Analyst
Staff member
Joined
Feb 22, 2012
Posts
12,391
Location
Upstate, NY
Releasing Windows 10 Build 19043.1147 (21H1) to Release Preview Channel

NOTE: Windows Insiders in the Beta Channel on 21H1 will not receive this update. We will be flighting Windows 11 Insider Preview builds to these Insiders soon!

This update includes the following improvements:
We fixed an issue with searchindexer. After you sign out, searchindexer continues to hold handles to the per user search database in the profile path, “C:\Users\username\AppData\Roaming\Microsoft\Search\Data\Applications\\”. As a result, searchindexer stops working and duplicate profile names are created.
We fixed an issue that prevents gaming services from opening certain games for desktop users.
We fixed an issue that prevents you from entering text using the Input Method Editor (IME). This might occur, for example, after startup if you have set the power options to shut down a laptop by closing its lid.
We changed the functionality for uploading new activity into Timeline. If you sync your activity history across your devices using your Microsoft account (MSA), you cannot upload new activity into the Timeline. You can still use Timeline and see your activity history (information about recent apps, websites, and files) on your local device. This does not affect Azure Active Directory (AAD) accounts. To view web history, Microsoft Edge and other browsers provide the option to view recent web activities. You can also view recently used files using Microsoft OneDrive and Microsoft Office.
We fixed an issue that might cause the File Explorer window to lose focus when you are mapping a network drive.
We fixed an issue that causes File Explorer to stop working after reaching 99% completion when you are deleting many files on a mapped network drive.
We fixed a timing issue in the Group Policy Registry Telemetry that causes Group Policy extension processing to fail.
We fixed an issue that repeatedly rebuilds the Windows Filtering Platform (WFP) filters. This issue occurs when a device is enrolled in a mobile device management (MDM) service and “MDMWinsOverGP” is set.
We fixed an issue with an MDM service that fails to correctly apply certain junk mail rules.
We fixed an issue that always reports the update build revision (UBR) as zero (0) on a device during enrollment to an MDM service.
We fixed an issue that causes the enrollment of the Elliptic Curve Digital Signature Algorithm (ECDSA) certificate to fail with the error, “0x80090027 NTE_INVALID_PARAMETER”. This issue occurs when the Trusted Platform Module (TPM) provider (the Microsoft Software Key Storage Provider) stores the key.
We fixed an issue with auditing events 4624 and 5142 that display the wrong event template when Dutch is the display language.
We fixed an issue that causes System Integrity to leak memory.
We fixed an issue that plays the sound for selecting something in a game loudly when you press the trigger button on a game controller.
We fixed an issue that prevents power plans and Game Mode from working as expected. This results in lower frame rates and reduced performance while gaming.
We fixed an issue in which “Network Internal Access” appears on the taskbar network icon on systems that access the internet from certain domains.
We fixed an issue in which the Network Connectivity Status Indicator (NCSI) fails to detect internet connectivity after you connect to a virtual private network (VPN).
We fixed an issue that causes printing to stop or prints the wrong output. This issue occurs when you print using a USB connection after updating to Windows 10, version 2004 or later.
We fixed a rare issue that might degrade performance in applications that call Gdiplus.dll!GdipMeasureString in a tight loop with a new font on each call. This issue occurs after installing Windows updates released on and after February 2021.
We fixed an issue that incorrectly routes some audio channels when streaming using certain fixed channel layouts.
We fixed an issue that always displays devices that RemoteFX USB redirects as “Remote Desktop Generic USB Device” instead of the actual device name.
We fixed an issue in which Set-RDSessionCollectionConfiguration does not set the camerastoredirect:s:value custom property.
We fixed a Local Security Authority Subsystem Service (LSASS) domain controller memory leak that is reported in Privileged Access Management (PAM) deployments.
We fixed an issue that prevents you from accessing a network drive that maps to a Distributed File System (DFS) root after you sign out.
We fixed an issue that prevents you from reconnecting to mapped network drives after you sign in and displays an access denied error. This issue occurs if you use the net use /deep option to create multiple drive mappings to different paths on the same encrypted file share.
We fixed an issue that prevents access to files on a Server Message Block (SMB) share when you enable Access Enabled Enumeration (ABE).
We fixed an issue that prevents the Windows Server service from starting if SrvComment is greater than 128 characters.
We fixed an issue in the Windows Network File System (NFS) client that might prevent you from renaming a file after mounting an NFS share. This issue occurs if you rename the file using File Explorer, but does not occur if you rename the file using command line.
We fixed an issue with an unhandled Open File dialog critical exception. As a result, Microsoft Foundation Class (MFC) applications might close unexpectedly.
We fixed an issue in which the Storage Sense page in Settings might incorrectly report the size of some storage devices that use the GUID Partition Table (GPT). The affected devices will incorrectly report in Storage Sense that the size is twice as large as the size reported in File Explorer. Note: This issue does not affect storage devices that use a master boot record (MBR).
Modify message
 
Releasing Windows 10 Build 19043.1149 (21H1) to Release Preview Channel

NOTE: Windows Insiders in the Beta Channel on 21H1 will not receive this update. We will be flighting Windows 11 Insider Preview builds to these Insiders soon!

This update includes the following change in addition to all the improvements listed as part of Build 19043.1147:

  • We added a new policy that creates generic strings and removes branding-specific terms, such as “Windows” or “PC”, for IoT Enterprise editions. For example, we changed “computer” to “device”. Instead of “Getting Windows ready,” we changed that to “Getting things ready” and so on. These generic strings are displayed on a user’s screen when an update is in progress.
 
Releasing Windows 10 Build 19043.1200 (21H1) to Release Preview Channel

This Build is only for those Insiders who are on Windows 10, version 21H1 and includes the following improvements:

  • We fixed an issue that prevents users from tracking Distributed Component Object Model (DCOM) activation failures.
  • We fixed a threading issue that might cause the Windows Remote Management (WinRM) service to stop working when it is under a high load.
  • We fixed an issue that causes the Windows Management Instrumentation (WMI) provider host process to stop working. This occurs because of an unhandled access violation that occurs when using the Desired State Configuration (DSC).
  • We fixed an issue that causes file migration between Distributed File System (DFS) paths that are stored on different volumes to fail. This issue occurs when you implement the migration using PowerShell scripts that use the Move-Item command.
  • We fixed an issue that prevents you from writing to a WMI repository after a low memory condition occurs.
  • We fixed an issue that resets the brightness for standard dynamic range (SDR) content on high-dynamic range (HDR) monitors. This occurs after you restart the system or reconnect to the system remotely.
  • We fixed an issue that might cause an external monitor to display a black screen after Hibernation. This issue might occur when the external monitor connects to a docking station using a certain hardware interface.
  • We fixed a memory leak that occurs when you use nested classes within VBScript.
  • We fixed an issue that prevents you from typing any words in the username box during the out-of-box experience (OOBE) process. This issue occurs when you use the Chinese Input Method Editor (IME).
  • We fixed an issue that causes applications that use a shim to stop working. This issue occurs on devices that do not have edgegdi.dll installed. The error message is, “The code execution cannot proceed because edgegdi.dll was not found”.
  • We fixed an issue that might prevent you from minimizing an application that uses unthemed windows.
  • We fixed an issue that might cause your device to stop working during a touch input gesture. This issue occurs if you bring more fingers into contact with the touchpad or screen during the middle of the gesture.
  • We fixed an issue with resizing images that might produce flickering and residual line artifacts.
  • We fixed an issue with copying and pasting a text box into Office 365 apps. The IME prevents you from inserting text into the text box.
  • We fixed an issue that prevents USB audio headsets from working on laptops that support USB audio offload. This issue occurs if you installed third-party audio drivers on the laptops.
  • We fixed an issue that prevents Code Integrity rules from working correctly when specifying Package Family Name rules in a Code Integrity policy. This issue occurs because of the incorrect handling of case-sensitive names.
  • We fixed an issue that prevents the ShellHWDetection service from starting on a Privileged Access Workstation (PAW) device and prevents you from managing BitLocker drive encryption.
  • We fixed an issue in Windows Defender Exploit Protection that prevents some Microsoft Office applications from working on machines that have certain processors.
  • We fixed an issue that causes the IME toolbar to appear even when the Remote App is closed.
  • We fixed an issue that might occur when you configure the policy, “Delete user profiles older than a specified number of days on system restart”. If a user has been signed in for longer than the time specified in the policy, the device might unexpectedly delete profiles at startup.
  • We fixed an issue with the Microsoft OneDrive sync setting “Always keep on this device”. The setting is unexpectedly reset to “Known folders only” after you install Windows updates.
  • We fixed an issue that provides the wrong Furigana result when a user cancels the Japanese reconversion.
  • We fixed a rare condition that prevents Bluetooth headsets from connecting using the Advanced Audio Distribution Profile (A2DP) for music playback and causes the headsets to only work for voice calls.
  • We added the “Target Product Version” policy. With this, administrators can specify the Windows product they want devices to migrate to or remain on (for example, Windows 10 or Windows 11).
  • We increased the default number of entries in the local security authority (LSA) Lookup Cache to improve lookup performance in high lookup volume scenarios.
  • We fixed an issue that might create duplicate built-in local accounts, such as administrator or guest account, during an in-place upgrade. This issue occurs if you previously renamed those accounts. As a result, the Local Users and Groups MMC snap-in (msc) appears blank with no accounts after the upgrade. This update removes the duplicate accounts from the local Security Account Manager (SAM) database on the affected machines. If the system detected and removed duplicate accounts, it logs a Directory-Services-SAM event, with ID 16986, in the System event log.
  • We fixed a stop error 0x1E in srv2!Smb2CheckAndInvalidateCCFFile.
  • We fixed an issue that might cause transfer validations to fail with the error, “HRESULT E_FAIL has been returned from a call to a COM component”. This issue occurs when you use Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012 as sources.
  • We fixed an issue that might cause a system to stop working after a deduplication filter detects damage in a reparse point. This issue occurs because of deduplication driver changes introduced in a previous update.
  • We fixed an issue with using the robocopy command with the backup option (/B) to fix data loss. This issue occurs when the source location contains tiered Azure File Sync files or tiered Cloud Files.
  • We stopped running queries against OneSettings APIs from the obsolete Storage Health feature.
  • We enabled over 1400 new mobile device management (MDM) policies. With them, you can configure policies that Group Policies also support. These new MDM policies include administrative template (ADMX) policies, such as App Compat, Event Forwarding, Servicing, and Task Scheduler. Starting in September 2021, you can use the Microsoft Endpoint Manager (MEM) Settings Catalog to configure these new MDM policies.
 
Releasing Windows 10 Build 19043.1263 (21H1) to Release Preview Channel

Fixes:
  • We fixed an issue that changes the device’s current UI language. This occurs during an unattended out-of-box experience (OOBE) language pack installation scenario on a desktop.
  • We fixed an issue that causes the system time to be incorrect by one hour after a daylight saving time (DST) change.
  • We fixed an issue that causes the Server Manager application to disappear after you use it to remove Hyper-V features on Windows Server 2022.
  • We fixed an issue with parsing time formats in event logs. This issue occurs when you exclude milliseconds.
  • We fixed an issue that causes the DnsCache service to increase the CPU usage to 100% utilization. As a result, the device stops responding.
  • We provided administrators the option to reset the zoom to the default for HTML dialogs in Microsoft Edge Internet Explorer mode.
  • We fixed an issue that stops calls to the Windows Image Acquisition (WIA) minidriver for Windows Portable Devices (WPD) devices that you access using WIAMgr.
  • We fixed an issue that causes applications, such as Microsoft Outlook, to suddenly stop responding during normal use. This occurs if the application created and removed UI elements on a background thread that is no longer receiving messages.
  • We fixed an issue with the Microsoft Outlook Add-in that prevents you from providing input after you select Reply.
  • We fixed an issue that fails to keep the NumLock state after a Fast Startup restart.
  • We fixed an issue with sharing a screen using Microsoft Teams. Protected content, such as a digital rights management (DRM) email, appears black for the presenter, but appears transparent for everyone else.
  • We fixed an issue that might prevent drawing on the screen using Windows Context::UpdateRgnFromRects from working.
  • We fixed an issue that might cause distortion in the audio that Cortana and other voice assistants capture.
  • We removed the limitation of 25 maximum Traffic Selectors in the Windows native Internet Key Exchange (IKE) client and server.
  • We fixed an issue that fails to display the smart card PIN dialog when you are connected to a virtual private network (VPN). This issue occurs after upgrading to Windows 10, version 2004.
  • We fixed an issue that causes a memory leak in lsass.exe when the pTokenPrivileges buffer is not released.
  • We fixed an issue with a non-paged pool (NPP) leak from the UxSF pool tag. This leak occurs when lsass.exe stops processing asynchronous Security Support Provider Interface (SSPI) calls.
  • We fixed an issue that prevents the xhunter1.sys driver from loading. As a result, some games cannot run when you enable Hypervisor-Protected Code Integrity (HVCI).
  • We fixed an issue that causes Windows to stop working if you deploy a Code Integrity policy without user mode rules.
  • We improved the performance of MsSense.exe in environments with User Datagram Protocol (UDP) applications that require high amounts of bandwidth.
  • We fixed an input method editor (IME) mode instability in the RemoteApp scenario. You must install this update on the Remote Desktop server and Remote Desktop client.
  • We fixed an issue that causes blurry News and interests icons when you use certain screen resolutions.
  • We fixed a paged pool memory leak of the registry keys for the Virtual Desktop ID that occurs in explorer.exe.
  • We fixed an issue that causes LogonUI.exe to stop working because Direct Manipulation fails to start.
  • We fixed an issue that causes News and interests to appear in the context menu even when you have disabled it on a device.
  • We fixed an issue that causes the configuration for multiple artifact DB support across datacenters to fail for Security Assertion Markup Language (SAML) artifacts.
  • We fixed an issue that causes the LsaLookupSids() function to fail. This occurs when there are security identifiers (SID) for users that no longer exist in a group that contains cross-domain trusted users.
  • We fixed an issue that fails to apply the post_logout_redirect_uri= parameter when you use an External Claims Provider.
  • We fixed an issue with a deadlock in the WebDav redirector that occurs when it attempts to read a file from the local TfsStore. As a result, the system stops responding.
  • We fixed an issue that causes a stop error after a restart.
  • We fixed an issue with Enterprise Mode Site List redirection from Internet Explorer 11 to Microsoft Edge. In certain circumstances, the redirection opens a site in multiple tabs in Microsoft Edge.
  • We removed a hyperlink that might cause the Input app to stop working when you first enter fuzzy pinyin content.
  • We fixed an activation issue for the Input application.
  • We fixed an issue that causes apps to lose focus when the taskbar is not at the bottom of the screen.
  • We fixed an issue that always reports the update build revision (UBR) as zero (0) on a device during enrollment to mobile device management (MDM) service.
  • We fixed an issue with PropertyGet in JScript9.dll.
  • We implemented a Group Policy for the registry key below:
    • Key: HKLM\Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint
    • Value: RestrictDriverInstallationToAdministrators
 
Releasing Windows 10 Build 19043.1319 (21H1) to Release Preview Channel

Fixes:
  • We fixed an issue that prevents you from accessing the pre-provisioning page during the out-of-box experience (OOBE). This issue occurs when the credentials page for signing in to Azure Active Directory appears, and you press the Windows key five times.
  • We added a feature that facilitates certain cross-browser data transfers.
  • We fixed an issue with Assigned Access kiosks that are configured with Microsoft Edge as a kiosk application. These kiosks might sometimes fail to restart Microsoft Edge if users close the browser window.
  • We fixed an issue in which the use of App-V intermittently causes black screens to appear when signing in on the credentials page.
  • We fixed an issue that might prevent subtitles from displaying for certain video apps and streaming video sites.
  • We fixed an issue that prevents Windows 10 virtual private network (VPN) users from connecting to Windows Server 2019 Routing and Remote Access service (RRAS) servers.
  • We fixed an issue that prevents Software-Defined Networking (SDN) virtual machines from working when you configure the Generic Routing Encapsulation (GRE) VPN bandwidth limitation.
  • We fixed a Primary Refresh Token (PRT) update issue that occurs when VPN users sign in using Windows Hello for Business when the VPN connection is offline. Users receive unexpected authentication prompts for online resources that are configured for user sign-in frequency (SIF) in Azure Active Directory-Conditional Access.
  • We fixed an issue that causes Windows to go into BitLocker recovery after a servicing update.
  • We fixed an issue that might cause Kerberos.dll to stop working within the Local Security Authority Subsystem Service (LSASS). This occurs when LSASS processes simultaneous Service for User (S4U) user-to-user (U2U) requests for the same client user.
  • We fixed an issue in Code Integrity that might cause a memory leak.
  • We enhanced Microsoft Defender for Endpoint’s ability to identify and intercept ransomware and advanced attacks.
  • We fixed an issue in the OOBE that might cause Windows AutoPilot provisioning to fail.
  • We fixed an issue that prevents Kana input mode users from inserting a question mark (?) using the Shift-0 key combination.
  • We fixed an issue that sometimes causes the lock screen to appear black if you enable slideshow.
  • We fixed a reliability issue with LogonUI.exe, which affects the rendering of the network status text on the credentials screen.
  • We fixed an issue that causes Server Message Block (SMB) Query Directory Requests to fail when the buffer size is large.
  • We fixed a memory leak issue in lsass.exe on domain controllers in the forest root domain that occurs when you have multiple forests and multiple domains in each forest. The SID-Name mapping functions leak memory when a request comes from another domain in the forest and crosses forest boundaries.
  • We fixed an issue with the virtual machine (VM) Load Balancing feature, which ignores a site’s fault domain.
 
Releasing Windows 10 Build 19044.1379 / 19043.1379 to Release Preview Channel

Build 19044.1379 is for Insiders on 21H2 and Build 19044.1379 is for Insides on 21H1 (KB5007253).

Fixes:
  • We fixed an issue that affects the opening of the SearchFilterHost.exe process.
  • We fixed an issue that causes searchindexer.exe to keep handles to the per user search database in the path below after you sign out: “C:\Users\username\AppData\Roaming\Microsoft\Search\Data\Applications\\” As a result, searchindexer.exe stops working and duplicate profile names are created.
  • We added support for the cancellation of daylight savings time for the Republic of Fiji for 2021.
  • We fixed an issue that prevents the enrollment status page (ESP) from displaying the error message or remediation options after a failure.
  • We added the –cd argument to wsl.exe to specify a Windows or Linux path as a starting directory for Windows Subsystem for Linux (WSL).
  • We fixed an issue that fails to apply machine Group Policy objects automatically at startup or in the background to devices on a domain that have certain processors.
  • We added the option to configure an Internet Protocol version 4 (IPv4) maximum transmission unit (MTU) that is less than 576 bytes on an interface.
  • We fixed an issue that fails to provide an event description for the System Center – Operations Manager.
  • We fixed an issue that incorrectly renders some variable fonts.
  • We fixed an issue that might cause the 32-bit version of Microsoft Excel to stop working on devices that have certain processors when you export to PDF.
  • We fixed an issue that displays glyphs at the wrong angle when you use the Meiryo UI font and other vertical fonts. These fonts are frequently used in Japan, China, or other countries in Asia.
  • We enabled onunload events to create pop-up windows in Microsoft Edge Internet Explorer mode.
  • We fixed an issue that affects predictive pre-rendering in Microsoft Edge Internet Explorer mode.
  • We fixed an issue that causes Internet Explorer to stop working.
  • We fixed an issue that causes Internet Explorer to stop working when using the Input Method Editor (IME) to insert elements.
  • We fixed an issue that causes the Settings page to unexpectedly close after you uninstall a font.
  • We fixed an issue that affects the UI for renaming files when using folder view in File Explorer. The UI fails to properly handle inline composition when using the new Japanese IME.
  • We fixed a memory leak in ctfmon.exe that occurs when you switch between different edit clients.
  • We fixed a known issue that causes error codes 0x000006e4, 0x0000007c, or 0x00000709 when connecting to a remote printer that is shared on a Windows print server.
  • We fixed an issue that turns off screen capture and recording functionalities on the Windows Game Bar because of a service failure.
  • We fixed an issue that might cause the return value of GetCommandLineA() to be lowercase in some developer scenarios.
  • We fixed an issue that might cause the decryption of a file that is on a remote server to fail. This issue occurs when using the Encrypted File System (EFS) on the remote server and the error message is, “ERROR_DECRYPTION_FAILED”.
  • We fixed an issue that prevents you from enabling BitLocker on a thinly provisioned virtual machine (VM). The error is “A device attached to the system is not functioning” and the system logs, “STATUS_UNSUCCESSFUL”.
  • We fixed an issue that causes Windows Defender Application Control to incorrectly compare two file version numbers.
  • We enabled credentials for Azure Active Directory (Azure AD) Active Directory Federation Services (ADFS) users in Quick Assist.
  • We fixed an issue that sometimes prevents Quick Assist users from using full screen view after they start a remote assistance session.
  • We fixed an issue that prevents the applications that you use often from appearing on the Start menu and prevents you from configuring them to appear on the Start menu using a Group Policy.
  • We fixed an issue that causes the syncing of desktop settings to fail when you use the built-in User Experience Virtualization (UE-V) template.
  • We fixed an issue that prevents Failover Clustering from updating Domain Name Server (DNS) records.
  • We fixed an issue that prevents your device from starting up, and it becomes unresponsive because of licensing API calls.
 
Releasing Windows 10 Build 19044.1381 / 19043.1381 to Release Preview Channel

Build 19044.1381 is for Insiders on 21H2 and Build 19044.1381 is for Insiders on 21H1 (KB5007253).

In addition to the fixes from the previous build, this release includes the following fix:
  • We fixed an issue that might affect devices that use Windows Hello for Business and are joined to Azure Active Directory (AD). These devices might experience issues when they access on-premises resources, such as file shares or websites.
 

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

Back
Top