Windows 10, version 2004 and Windows Server, version 2004

Find information on known issues and the status of the rollout for Windows 10, version 2004 and Windows Server, version 2004. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). Want the latest Windows release health updates? Follow @WindowsUpdate on Twitter.

Current status as of July 22, 2020
Windows 10, version 2004 is available for users with devices running Windows 10, versions 1903 and 1909, who manually seek to “Check for updates” via Windows Update. We are now starting a new phase in our rollout. Using the machine learning-based (ML-based) training we have done so far, we are increasing the number of devices selected to update automatically to Windows 10, version 2004 that are approaching end of service. We will continue to train our machine learning through all phases to intelligently rollout new versions of Windows 10 and deliver a smooth update experience. The recommended servicing status is Semi-Annual Channel.
Windows 10, version 2004 is now available Windows 10, version 2004 is now available
Find out how to get the update >
What’s new for IT pros What’s new for IT pros
Explore the latest features and and servicing innovations in Windows 10 >
Wondering how to deploy feature updates remotely? Wondering how to deploy feature updates remotely?
Get tips and best practices >

Known issues

This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

SummaryOriginating updateStatusLast updated
Variable refresh rate not working as expected on devices with Intel iGPU
Enabling VRR on affected devices will not enable the VRR for games using Direct X 9.

See details >
N/A

Resolved
KB4568831
July 31, 2020
10:00 AM PT
Issue with older drivers for Nvidia display adapters (GPU)
You might have issues if you are using an Nvidia display adapter (GPU) and drivers with a version below 358.00.

See details >
N/A

Mitigated External
August 06, 2020
02:13 PM PT
Issues updating or starting up devices when aksfridge.sys or aksdf.sys is present
Devices with apps or drivers using certain versions of aksfridge.sys or aksdf.sys might have issues updating or starting

See details >
N/A

Investigating
August 06, 2020
02:13 PM PT
Errors or issues during or after updating devices with Conexant ISST audio drivers
Devices with affected Conexant ISST audio drivers might receive an error or have issues with Windows 10, version 2004.

See details >
N/A

Investigating
August 06, 2020
02:14 PM PT
Difficulty connecting to more than one Bluetooth device
Windows 10 devices with certain Realtek drivers might be unable to connect to more than one Bluetooth device.

See details >
N/A

Resolved
KB4568831
July 31, 2020
10:00 AM PT
Errors or issues during or after updating devices with certain Conexant audio drivers
Devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen.

See details >
N/A

Investigating
August 06, 2020
02:13 PM PT
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 16, 2020
05:07 PM PT
Outlook closes unexpectedly or you might receive an error when attempting to open
An example of an error you might receive is, "Outlook couldn't start last time."

See details >
OS Build 19041.388

July 14, 2020
KB4565503
Resolved
July 15, 2020
03:43 PM PT
Dragging with the mouse in some apps might cause issues for some IME users
Users of the Microsoft IME for Chinese and Japanese might receive an error or the app might stop responding or close.

See details >
N/A

Investigating
July 14, 2020
10:19 AM 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

Issue details

July 2020

DetailsOriginating updateStatusHistory
Outlook closes unexpectedly or you might receive an error when attempting to open
Microsoft Outlook might close unexpectedly or you might receive an error when attempting to open the app. An example of an error you might receive is, "Outlook couldn't start last time. Safe mode could help you troubleshoot the problem, but some features might not be available in this mode. Do you want to start in Safe Mode?" You might also see an event in the Event Viewer, as listed in the article linked below.

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 2015 LTSB; Windows 8.1; Windows 7 SP1
Workaround: As an alternative, on your Windows 10 device you can use the Office365 on the web (OWA), also known as webmail. Outlook mobile is also unaffected. There is no workaround for this issue for the Outlook app on Windows 10 until the resolution is deployed to your device. We do not recommend using the command to revert to an earlier version.

Resolution: This Outlook issue has been resolved and will be deployed automatically to your device. This issue was not related to any update for Windows and no update for Windows is needed. We expect this issue to be completely resolved for all affected users by July 15, 2020 at 3:30 PM PST (10:30 PM UTC). You may also need to attempt to open Outlook a few times before it will be fully refreshed and open as expected. For more information, please see the support article, Active Investigation into Outlook Crashing on Launch and this twitter thread.

Back to top
OS Build 19041.388

July 14, 2020
KB4565503
Resolved
Resolved:
July 15, 2020
03:43 PM PT

Opened:
July 15, 2020
03:22 PM PT
Dragging with the mouse in some apps might cause issues for some IME users
Users of the Microsoft IME for Chinese and Japanese in some apps such as Microsoft Excel, might receive an error or the app might stop responding or close when attempting to drag with the mouse.

Affected platforms:
  • Client: Windows 10, version 2004
  • Server: Windows Server, version 2004
Next steps: For more information and workaround steps, please see KB4564002.

Back to top
N/A

Investigating
Last updated:
July 14, 2020
10:19 AM PT

Opened:
July 14, 2020
09:06 AM PT

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

May 2020

DetailsOriginating updateStatusHistory
Variable refresh rate not working as expected on devices with Intel iGPU
Intel and Microsoft have found incompatibility issues when using a monitor with Variable refresh rate (VRR) plugged into an Intel integrated graphics processing unit (iGPU) display adapter and Windows 10, version 2004 (the Windows 10 May 2020 Update). Enabling VRR on affected devices will not enable the VRR for games using Direct X 9.

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. If your organization is using Update Compliance, the safeguard ID is 26251417.

Affected platforms:
  • Client: Windows 10, version 2004
Resolution: This issue was resolved in KB4568831. The safeguard hold is estimated to be removed in mid-August.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until the safeguard is removed.

Back to top
N/A

Resolved
KB4568831
Resolved:
July 31, 2020
10:00 AM PT

Opened:
May 27, 2020
12:13 AM PT
Issue with older drivers for Nvidia display adapters (GPU)
Nvidia and Microsoft have found incompatibility issues with certain versions of Nvidia display adapter drivers and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Nvidia display driver versions might receive a stop error with a blue screen or other issues during or after installing the update to Windows 10, version 2004. The affected drivers are any version lower than 358.00.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Nvidia display drivers drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard ID is 24803238.

Affected platforms:
  • Client: Windows 10, version 2004
  • Server: Windows Server, version 2004
Workaround: To mitigate this issue, you will need to check with your device manufacturer (OEM) to see if an updated driver is available and install it.

Next steps: Microsoft is working on a resolution and estimate a solution will be available in mid-August.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until the safeguard is removed.

Back to top
N/A

Mitigated External
Last updated:
August 06, 2020
02:13 PM PT

Opened:
May 27, 2020
12:09 AM PT
Issues updating or starting up devices when aksfridge.sys or aksdf.sys is present
An incompatibility issue was found with apps or drivers using certain versions of aksfridge.sys or aksdf.sys and Windows 10, version 2004 (the Windows 10 May 2020 Update). When an affected version of aksfridge.sys or aksdf.sys is present, Windows 10, version 2004 might fail to install or might fail to start after updating. Affected file versions are up to 1.8.0.* for aksfridge.sys or up to 1.51.* for aksdf.sys.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with an affected version of aksfridge.sys from being offered Windows 10, version 2004 or Windows Server, version 2004. If your organization is using Update Compliance, the safeguard ID is 24858586.

Affected platforms:
  • Client: Windows 10, version 2004
  • Server: Windows Server, version 2004
Next steps: Microsoft is working on a resolution and estimate a solution will be available in mid-August.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until the safeguard is removed.

Back to top
N/A

Investigating
Last updated:
August 06, 2020
02:13 PM PT

Opened:
May 27, 2020
12:09 AM PT
Errors or issues during or after updating devices with Conexant ISST audio drivers
Synaptics and Microsoft have found incompatibility issues with certain versions of drivers for Conexant ISST audio driver and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Conexant ISST audio driver might receive an error or experience issues while installing the update or after the device has updated. The affected driver will be named Conexant ISST Audio or Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and have file name uci64a96.dll through uci64a231.dll and a file version lower than 7.231.3.0.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Conexant or Synaptics audio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard ID is 25178825.

Affected platforms:
  • Client: Windows 10, version 2004
  • Server: Windows Server, version 2004
Workaround: To mitigate this issue, you will need to check with your device manufacturer (OEM) to see if an updated driver is available and install it.

Next steps: Microsoft and Synaptics are working on a resolution and will provide an update in an upcoming release.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top
N/A

Investigating
Last updated:
August 06, 2020
02:14 PM PT

Opened:
May 27, 2020
12:22 AM PT
Difficulty connecting to more than one Bluetooth device
Realtek and Microsoft have found incompatibility issues with certain versions of drivers for Realtek Bluetooth radios and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Realtek Bluetooth radio drivers might be unable to connect or pair with more than one Bluetooth device at a time after updating.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Realtek Bluetooth radio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard ID is 25692458.

Affected platforms:
  • Client: Windows 10, version 2004
  • Server: Windows Server, version 2004
Resolution: This issue was resolved in KB4568831. The safeguard hold is estimated to be removed in mid-August.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until the safeguard is removed.

Back to top
N/A

Resolved
KB4568831
Resolved:
July 31, 2020
10:00 AM PT

Opened:
May 27, 2020
12:22 AM PT
Errors or issues during or after updating devices with certain Conexant audio drivers
Synaptics and Microsoft have found incompatibility issues with certain versions of drivers for Conexant or Synaptics audio devices and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen during or after updating to Windows 10, version 2004. The affected driver will be named Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and have versions 8.65.47.53​, 8.65.56.51​, or 8.66.0.0 through 8.66.89.00 for chdrt64.sys or chdrt32.sys.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Conexant or Synaptics audio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated. If your organization is using Update Compliance, the safeguard IDs are 25702617, 25702660, 25702662, and 25702673.

Affected platforms:
  • Client: Windows 10, version 2004
  • Server: Windows Server, version 2004
Next steps: Microsoft and Synaptics are working on a resolution and will provide an update in an upcoming release.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top
N/A

Investigating
Last updated:
August 06, 2020
02:13 PM PT

Opened:
May 27, 2020
12:20 AM PT
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 and the safeguard hold has been removed as of July 16, 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. 

Back to top
N/A

Resolved
KB4565503
Resolved:
July 16, 2020
05:07 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