Resolved issues in Windows 10, version 21H2

See a list of known issues that have been resolved for Windows 10, version 21H2 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.


Resolved issues

SummaryOriginating updateStatusDate resolved
Outlook search might not locate recent emails
Searches on Outlook desktop app might fail when emails are stored locally in PST or OST files
OS Build 19041.1387
KB5007253
2021-11-22
Resolved
2022-01-19
15:56 PT
Certain IPSEC connections might fail
Some VPN clients using IPSEC or Layer 2 Tunneling Protocol (L2TP) might have issues connecting.
OS Build 19041.1466
KB5009543
2022-01-11
Resolved
KB5010793
2022-01-17
14:00 PT
The text cursor in some apps might move unexpectedly when using a Japanese IME
Text input using a Japanese IME might be entered out of order or the text cursor might move unexpectedly.
OS Build 19041.1387
KB5007253
2021-11-22
Resolved
2022-01-04
17:58 PT
Microsoft Installer might have issues updating or repairing apps
Affected apps might fail to open after an update or repair has been attempted.
N/A

Resolved
KB5007253
2021-11-22
14:00 PT
Connections to printers shared via print server might encounter errors
This issue is observed when print clients try to connect to a remote printer shared on a print server
N/A

Resolved
KB5007253
2021-11-22
14:00 PT

Issue details

January 2022

Outlook search might not locate recent emails

StatusOriginating updateHistory
ResolvedOS Build 19041.1387
KB5007253
2021-11-22
Resolved: 2022-01-19, 15:56 PT
Opened: 2022-01-19, 15:40 PT
After installing KB5007253 or later updates, recent emails might not appear in search results on Outlook desktop app. This issue is related to emails which have been stored locally in a PST or OST files. It might affect POP and IMAP accounts, as well as Microsoft Exchange and Microsoft 365 hosted accounts. If the default search in the Outlook app is set to server search, the issue will only affect the advanced search.
 
Workaround: To mitigate the issue, you can disable Windows Desktop Search which will cause Outlook to use its built-in search. For instructions, see Outlook Search not showing recent emails after Windows update KB5008212.

Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy (preferred). Important Verify that you are using the correct Group Policy for your version of Windows.

Group Policy:
Affected platforms:
  • Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 20H2; Windows Server, version 1809; Windows Server 2019

Certain IPSEC connections might fail

StatusOriginating updateHistory
Resolved KB5010793OS Build 19041.1466
KB5009543
2022-01-11
Resolved: 2022-01-17, 14:00 PT
Opened: 2022-01-13, 11:05 PT
After installing KB5009543, IP Security (IPSEC) connections which contain a Vendor ID might fail. VPN connections using Layer 2 Tunneling Protocol (L2TP) or IP security Internet Key Exchange (IPSEC IKE) might also be affected.

Workaround: To mitigate the issue for some VPNs, you can disable Vendor ID within the server-side settings. Note: Not all VPN servers have the option to disable Vendor ID from being used.

Resolution: This issue was resolved in the out-of-band update KB5010793. It is a cumulative update, so you do not need to apply any previous update before installing it. If you would like to install the update, you will need to Check for updates and select "Optional updates" and then select KB5010793. To get the standalone package for KB5010793, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB5010793 will not install automatically.

Affected platforms:
  • Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB
  • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server 2019; Windows Server 2016

The text cursor in some apps might move unexpectedly when using a Japanese IME

StatusOriginating updateHistory
ResolvedOS Build 19041.1387
KB5007253
2021-11-22
Resolved: 2022-01-04, 17:58 PT
Opened: 2022-01-04, 17:29 PT
After installing KB5007253, text input using a Japanese IME might be entered out of order or the text cursor might move unexpectedly in apps that use the multibyte character set (MBCS). This issue affects both the Microsoft Japanese IME and third-party Japanese IMEs.

Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy (preferred). Important Verify that you are using the correct Group Policy for your version of Windows.

Group Policy:
Affected platforms:
  • Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
  • Server: Windows Server 2022

November 2021

Microsoft Installer might have issues updating or repairing apps

StatusOriginating updateHistory
Resolved KB5007253N/A

Resolved: 2021-11-22, 14:00 PT
Opened: 2021-11-18, 10:34 PT
After installing or later updates, Microsoft Installer (MSI) might have issues repairing or updating apps. Apps that are known to be affected include some apps from Kaspersky. Affected apps might fail to open after an update or repair has been attempted.

Workaround: To mitigate this issue, you will need to uninstall the affected app, then install the latest version of the app.

Resolution: This issue was resolved in KB5007253. This update should prevent the issue from occurring again, but you might need to reinstall affected apps, if they will not open.

Affected platforms:
  • Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

October 2021

Connections to printers shared via print server might encounter errors

StatusOriginating updateHistory
Resolved KB5007253N/A

Resolved: 2021-11-22, 14:00 PT
Opened: 2021-10-29, 11:15 PT
Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server:
  • 0x000006e4 (RPC_S_CANNOT_SUPPORT)
  • 0x0000007c (ERROR_INVALID_LEVEL)
  • 0x00000709 (ERROR_INVALID_PRINTER_NAME)
Note: The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.
 
Workaround: You can take steps to workaround this issue on print servers that meet the following prerequisite:
 
  • Print clients must have installed a Windows update released on or after January 2021 before the print server has installed .
Ensure that network security and VPN solutions allow print clients to establish RPC over TCP connections to print server over the following port range:
  • Default start port: 49152
  • Default end port: 65535
  • Port Range: 16384 ports
Please refer to these articles for further guidance:
You also benefit from using client side rendering for print jobs. The 'Render print jobs on client computers' option is available from the printer's device Properties, and it is recommended that its checkbox is selected on the print server. Note this step will not help if clients have overwrites which prevent the server setting from taking effect.
 
Resolution: This issue was resolved in KB5007253.

Affected platforms:
  • Client: Windows 11, version 21H2; Windows 10, version 21H1; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2