Checking for updates for Windows 10 on 2019
Upcoming fixes

Windows 10 update KB5007253 outs for versions 21H2, 21H1 (preview)

Windows 10 build 19044.1379 and build 19044.1379 are now available as previews with upcoming fixes and improvements.

  • Microsoft releases update KB5007253 for Windows 10 21H2 and 21H1.
  • The update is a non-security update that bumps the version number to build 19044.1379 (19044.1381).
  • Update KB5007253 fixes a slew of problems and brings several improvements.

Shortly after the official launch of the Windows 10 November 2021 Update (version 21H2), Microsoft has begun testing the next cumulative for versions 21H2 and 21H1. The update includes a slew of fixes and improvements, and it’s currently available in the Release Preview Channel.

The update KB5007253 bumps the version number to build 19044.1379 (19044.1381 – see notes below) for both the November 2021 Update and the May 2021 Update, and according to the official notes, it fixes problems with Windows Search, adds a new (–cd) argument to specify a Windows or Linux path on WSL, addresses networking issues, problems with Encrypted File System (EFS), BitLocker, and more.

Update KB5007253 fixes and changes

These are the fixes and improvements available with the latest update preview of Windows 10:

  • Addressed an issue that affects the opening of the SearchFilterHost.exe process.
  • Fixed a problem 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.
  • Addressed 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).
  • Fixed a problem that fails to apply machine Group Policy objects automatically at startup or in the background to devices on a domain that has 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.
  • Addressed an issue that fails to provide an event description for the System Center – Operations Manager.
  • Fixed a problem that incorrectly renders some variable fonts.
  • Addressed 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.
  • Fixed a problem 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.
  • Addressed an issue that affects predictive pre-rendering in Microsoft Edge Internet Explorer mode.
  • Fixed a problem that causes Internet Explorer to stop working.
  • Addressed an issue that causes Internet Explorer to stop working when using the Input Method Editor (IME) to insert elements.
  • Fixed a problem that causes the Settings page to unexpectedly close after you uninstall a font.
  • Addressed 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.
  • Fixed a problem that turns off screen capture and recording functionalities on the Windows Game Bar because of a service failure.
  • Addressed an issue that might cause the return value of GetCommandLineA() to be lowercase in some developer scenarios.
  • Fixed a problem 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”.
  • Addressed 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”.
  • Fixed a problem 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.
  • Addressed an issue that sometimes prevents Quick Assist users from using full-screen view after they start a remote assistance session.
  • Fixed a problem 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.
  • Addressed an issue that causes the syncing of desktop settings to fail when you use the built-in User Experience Virtualization (UE-V) template.
  • Fixed a problem that prevents Failover Clustering from updating Domain Name Server (DNS) records.
  • Fixed a problem that prevents your device from starting up, and it becomes unresponsive because of licensing API calls. 

Download November 2021 update for Windows 10

These updates are available immediately, and they will download and install automatically through the Release Preview Channel. However, you can always force the update from Settings Update & Security > Windows Update, click the Check for updates button, and use the option to install the optional update.

Update November 18, 2021: Microsoft is re-releasing the update KB5007253 for Windows 10 21H2 and 21H1 as build 19044.1381 for version 21H2 and build 19044.1381 for version 21H1 in the Release Preview Channel. The update includes everything listed above, and a new fix for an issue that might affect devices that use Windows Hello for Business and are joined to Azure Active Directory (AD).