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 20H2 is now available Windows 10, version 20H2 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 servicing innovations in Windows 10, version 20H2 >

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
When installing incorrectly formatted third-party drivers, you might receive an error
You might receive, “Windows can’t verify the publisher of this driver software” or other errors.
OS Build 19041.572
KB4579311
2020-10-13
Resolved
2020-10-20
10:06 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.
N/A

Investigating
2020-10-20
10:06 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.
N/A

Investigating
2020-10-20
10:06 PT
Issues when using Microsoft IME for Japanese or Chinese languages
Users of the Microsoft IME for Japanese or Chinese languages might have issues.
N/A

Mitigated
2020-10-20
10:06 PT
Certain WWAN LTE modems might not be able to connect after waking from sleep
Affected WWAN LTE modems might show no internet and be unable to connect.
N/A

Resolved
KB4577063
2020-10-01
10:00 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.
N/A

Resolved
KB4571744
2020-09-03
14:00 PT

Issue details

October 2020

When installing incorrectly formatted third-party drivers, you might receive an error

StatusOriginating updateHistory
ResolvedOS Build 19041.572
KB4579311
2020-10-13
Resolved: 2020-10-20, 10:06 PT
Opened: 2020-10-13, 09:37 PT
When installing a third-party driver, you might receive the error, “Windows can’t verify the publisher of this driver software”. You may also see the error “No signature was present in the subject” when attempting to view the signature properties using Windows Explorer.

This issue occurs when one or more of the following is present in a driver package:
  • an improperly formatted catalog file is identified during validation by Windows. Starting with this release, Windows will require the validity of DER encoded PKCS#7 content in catalog files. Catalogs files must be signed per section 11.6 of describing DER-encoding for SET OF members in X.690.
  • a driver catalog file extension is not one of the supported extensions.
Affected platforms:
  • Client: Windows 10, version 20H2, 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 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1
  • Server: Windows Server, version 20H2, 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
Next steps: If this happens you should contact the driver vendor or device manufacturer (OEM) and ask them for an updated driver to correct the issue.

August 2020

Issues when using Microsoft IME for Japanese or Chinese languages

StatusOriginating updateHistory
MitigatedN/A

Last updated: 2020-10-20, 10:06 PT
Opened: 2020-08-31, 12:12 PT
Users of the Microsoft IME for Japanese or Chinese languages might experience issues when attempting various tasks. Input may have issues, you may receive unexpected results or you may be unable to enter text.

Affected platforms:
  • Client: Windows 10, version 20H2, Windows 10, version 2004
  • Server: Windows Server, version 20H2, Windows Server, version 2004
Next steps: For more information on issues, workaround steps and currently resolved issues, please see KB4564002.

Certain WWAN LTE modems might not be able to connect after waking from sleep

StatusOriginating updateHistory
Resolved
KB4577063
N/A

Resolved: 2020-10-01, 10:00 PT
Opened: 2020-08-31, 11:42 PT
After waking from sleep or hibernation, certain WWAN LTE modems might show no internet in the Network Connectivity Status Indicator (NCSI) in the notification area and might be unable to connect to the internet.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected WWAN LTE modems drivers installed from being offered Windows 10, version 2004 until the issue has been resolved. If your organization is using Update Compliance, the safeguard ID is 28428232.

Workaround: To mitigate this issue if you are already on Windows 10, version 2004, you can enable then disable Airplane mode. To do this, you can select the Start button, type airplane mode and select it. In the settings dialog, toggle Airplane mode on then off again. You should now be able to connect as expected.

Affected platforms:
  • Client: Windows 10, version 2004
Resolution: This issue was resolved in KB4577063 and the safeguard hold has been removed as of October 15, 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. 

July 2020

Dragging with the mouse in some apps might cause issues for some IME users

StatusOriginating updateHistory
Resolved
KB4571744
N/A

Resolved: 2020-09-03, 02:00 PT
Opened: 2020-07-14, 09:06 PT
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
Resolution: This issue was resolved in KB4571744. If you are experiencing other IME issues, please see KB4564002 for information on symptoms, workaround steps and currently resolved issues.

May 2020

Errors or issues during or after updating devices with certain Conexant audio drivers

StatusOriginating updateHistory
InvestigatingN/A

Last updated: 2020-10-20, 10:06 PT
Opened: 2020-05-27, 12:20 PT
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 20H2, Windows 10, version 2004
  • Server: Windows Server, version 20H2, 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.

Errors or issues during or after updating devices with Conexant ISST audio drivers

StatusOriginating updateHistory
InvestigatingN/A

Last updated: 2020-10-20, 10:06 PT
Opened: 2020-05-27, 12:22 PT
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 20H2, Windows 10, version 2004
  • Server: Windows Server, version 20H2, 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.