Resolved issues in Windows 10, version 2004 and Windows Server, version 2004

See a list of known issues that have been resolved for Windows 10, version 2004 and Windows Server, version 2004 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
Stop error when plugging or unplugging a Thunderbolt dock
Devices using Thunderbolt docks may receive a stop error when plugging in or unplugging the dock

See details >
N/A

Resolved
KB4565503
July 14, 2020
06:15 PM PT
Issues using ImeMode property to control IME mode for individual text entry fields
Some IMEs for certain langauges might have issues using the ImeMode property with certain apps.

See details >
N/A

Resolved
KB4565503
July 14, 2020
10:00 AM PT
Local Security Authority Subsystem Service (lsass.exe) might fail on some devices
Affected devices might receive a critical system process error and the device might restart.

See details >
N/A

Resolved
KB4565503
July 14, 2020
10:00 AM PT
Errors or unexpected restarts for some devices using Always On, Always Connected
Devices with more than one Always On, Always Connected capable network adapter might have issues.

See details >
N/A

Resolved
KB4557957
June 09, 2020
10:00 AM PT
DISM might incorrectly report corruption is still present after repair
After running DISM /restorehealth, DISM might incorrectly indicate corruption is still present after repair.

See details >
N/A

Resolved
KB4557957
June 09, 2020
10:00 AM PT
Print spooler might error or close unexpectedly when attempting to print
Certain printers might be unable to print after taking updates released June 9, 2020.

See details >
OS Build 19041.329

June 09, 2020
KB4557957
Resolved
KB4567523
June 18, 2020
10:00 AM PT
No mouse input with apps and games using GameInput Redistributable
Affected apps and games using both GameInput Redistributable and Windows 10, version 2004 might lose mouse input.

See details >
N/A

Resolved
June 12, 2020
05:06 PM PT
Error when attempting to open any Microsoft Office application
You might receive the error: Windows cannot find "c:\program files\microsoft office\root\office16\winword.exe"

See details >
OS Build 19041.329

June 09, 2020
KB4557957
Resolved External
June 12, 2020
05:06 PM PT

Issue details

June 2020

DetailsOriginating updateStatusHistory
Local Security Authority Subsystem Service (lsass.exe) might fail on some devices
The Local Security Authority Subsystem Service file (lsass.exe) might fail on some devices with the error message, “A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status code c0000008. The machine must now be restarted."

Affected platforms:
  • Client: Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019
Resolution: This issue was resolved in KB4565503.

Back to top
N/A

Resolved
KB4565503
Resolved:
July 14, 2020
10:00 AM PT

Opened:
June 24, 2020
12:46 PM PT
Print spooler might error or close unexpectedly when attempting to print
After installing KB4557957, certain printers may be unable to print. Print spooler may error or close unexpectedly when attempting to print and no output will come from affected printer. You might also encounter issues with the apps you are attempting to print from. You might receive an error from the app or the app may close unexpectedly. Note This issue might also affect software-based printers, for example printing to PDF.

Affected platforms:
  • Client: Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1
  • Server: Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue was resolved in the out-of-band update KB4567523. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB4567523, 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 KB4567523 is not available from Windows Update and will not install automatically.

Back to top
OS Build 19041.329

June 09, 2020
KB4557957
Resolved
KB4567523
Resolved:
June 18, 2020
10:00 AM PT

Opened:
June 12, 2020
04:06 PM PT
Error when attempting to open any Microsoft Office application
We have received reports that some users are unable to open apps after installing KB4557957, especially Microsoft Office apps. Affected users might also receive an error, such as, 'Windows cannot find "c:\program files\microsoft office\root\office16\winword.exe" Make sure you typed the name correctly, and then try again.'

Affected platforms:
  • Client: Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1903
  • Server: Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1903
Resolution: This issue has been resolved by Avast. This issue only affected devices with certain versions of Avast or AVG applications and was addressed with an update to their respective products. For more information on this, please see Avast's forum post here. Note No update is needed for Windows or Microsoft Office to address this issue.

Back to top
OS Build 19041.329

June 09, 2020
KB4557957
Resolved External
Last updated:
June 12, 2020
05:06 PM PT

Opened:
June 12, 2020
04:18 PM PT

May 2020

DetailsOriginating updateStatusHistory
Stop error when plugging or unplugging a Thunderbolt dock
Intel and Microsoft have found incompatibility issues when Windows 10, version 2004 (the Windows 10 May 2020 Update) is used with certain settings and a Thunderbolt dock. On affected devices, you might receive a stop error with a blue screen when plugging or unplugging a Thunderbolt dock. Affected Windows 10 devices will have at least one Thunderbolt port, have Kernel DMA Protection enabled and Windows Hypervisor Platform disabled. To verify your Kernel DMA Protection settings, please see How to check if Kernel DMA Protection is enabled. To verify your Windows Hypervisor Platform settings, select Start, type turn windows features on or off and select it. When the Windows Features dialog opens, find the setting for Windows Hypervisor Platform. If it is note checked, then Windows Hypervisor Platform is disabled.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected drivers or firmware from being offered Windows 10, version 2004.

Affected platforms:
  • Client: Windows 10, version 2004
Resolution: This issue was resolved in KB4565503. The safeguard hold is estimated to be removed in the coming days.

Back to top
N/A

Resolved
KB4565503
Resolved:
July 14, 2020
06:15 PM PT

Opened:
May 27, 2020
12:18 AM PT
Issues using ImeMode property to control IME mode for individual text entry fields
Some apps utilize the ImeMode property to control the IME (Input Method Editor) mode for individual text entry fields to increase typing efficiency. Some IMEs in Windows 10, version 2004 (the May 2020 Update) might have issues using the ImeMode property with certain apps. For example, the input mode will not switch automatically to Full-width Katakana mode, Full-width Alphanumeric mode, or Full-width Hiragana mode.

Affected platforms:
  • Client: Windows 10, version 2004
  • Server: Windows Server, version 2004
Resolution: This issue was resolved in KB4565503.

Back to top
N/A

Resolved
KB4565503
Resolved:
July 14, 2020
10:00 AM PT

Opened:
May 27, 2020
12:18 AM PT
Errors or unexpected restarts for some devices using Always On, Always Connected
Some devices using the Always On, Always Connected feature might have compatibility issues with Windows 10, version 2004 (the Windows 10 May 2020 Update). Affected devices will have more than one Always On, Always Connected capable network adapter, such as the Microsoft Surface Pro 7 and Microsoft Surface Laptop 3, and might receive errors or unexpected shutdown or restart.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected drivers or firmware from being offered Windows 10, version 2004.

Affected platforms:
  • Client: Windows 10, version 2004
Resolution: This issue was resolved in KB4557957 and the safeguard hold has been removed as of June 29, 2020. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 2004 is offered. 

Text last updated: July 8, 2020

Back to top
N/A

Resolved
KB4557957
Resolved:
June 09, 2020
10:00 AM PT

Opened:
May 27, 2020
12:11 AM PT
DISM might incorrectly report corruption is still present after repair
After using the Deployment Image Servicing and Management (DISM.exe) command /restorehealth to detect and correct system corruption, you might receive a report from the tool that corruption is still present. This can occur even when it has been repaired. An example for using the /restorehealth command is: DISM.exe /Online /Cleanup-image /Restorehealth

Affected platforms:
  • Client: Windows 10, version 2004
  • Server: Windows Server, version 2004
Workaround: If you receive reports that there is still corruption, subsequent scans should indicate the true state of the corruption. You can verify that DISM has fixed it by rerunning the same command or by using the /ScanHealth command. An example using the /ScanHealth command is: DISM.exe /Online /Cleanup-Image /ScanHealth

Resolution: This issue was resolved in KB4557957.

Back to top
N/A

Resolved
KB4557957
Resolved:
June 09, 2020
10:00 AM PT

Opened:
May 28, 2020
03:02 PM PT
No mouse input with apps and games using GameInput Redistributable
An incompatibility issue was found with some apps and games using GameInput Redistributable and Windows 10, version 2004 (the Windows 10 May 2020 Update). Affected apps or games might lose mouse input. Note GameInput Redistributable might be bundle with apps and games and might be silently installed during the installation of that app or game.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with GameInput Redistributable from being offered Windows 10, version 2004.

Affected platforms:
  • Client: Windows 10, version 2004
Resolution: After further investigation, we have found that this issue does not affect any version of GameInput Redistributable in use. The safeguard hold has been removed. Please note, it can take up to 48 hours before the update to Windows 10, version 2004 (the Windows 10 May 2020 Update).

Back to top
N/A

Resolved
Resolved:
June 12, 2020
05:06 PM PT

Opened:
May 27, 2020
12:11 AM PT