Setool 1 1204 descargar whatsapp

Windows 10, version 2004 and Windows Server, version 2004

  • 8 minutes to read

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 February 3, 2021
Windows 10, version 2004 is designated for broad deployment. The recommended servicing status is Semi-Annual Channel.

Known issues

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

Issue details

May 2021

A high-pitched noise might be heard when using 5.1 audio with certain settings

statusOriginating updateHistory
MitigatedOS Build 19041.906
KB5000842
2021-03-29
Last updated: 2021-05-14, 14:48 PT
Opened: 2021-05-13, 7:35 pm PT
After installing KB5000842 or later updates, 5.1 Dolby Digital audio may play containing a high-pitched noise or squeak in certain apps when using certain audio devices and Windows settings. grade This issue does not occur when stereo is used.
Workaround: To mitigate this issue, you can try one or more of the following:
  • Streaming the video or audio in a web browser or different app, instead of the app affected by this issue.
  • Enable Spatial sound settings by right clicking or long pressing on the volume icon in the notification area, selecting Spatial sound (off) and selecting any of the available options.
  • Client: Windows 10, version 20H2; Windows 10, version 2004
Next steps: We are working on a resolution and will provide an update in an upcoming release.

Security updates released May 11, 2021 might not offer in managed environments

statusOriginating updateHistory
ResolvedOS Build 19041.985
KB5003173
2021-05-11
Resolved: 2021-05-11, 7:01 PM PT
Opened: 2021-05-11, 14:58 PT
When checking for updates within Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager and managed devices that connect to these servers, KB5003173 might not be available or offered. Note: This might also affect Security Only and Internet Explorer Cumulative Rollups, on platforms that receive these types of updates.
  • Client: Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue is now resolved on the service side and updates should be available. Note: If you initiate a synchronization cycle and are still not being offered the updates, please check again soon. There might be slight delay as it propagates to all servers in all regions.

April 2021

Lower than expected performance in games

statusOriginating updateHistory
ResolvedOS Build 19041.906
KB5000842
2021-03-29
Resolved: 2021-04-27, 3:48 pm PT
Opened: 2021-04-23, 18:04 PT
A small subset of users have reported lower than expected performance in games after installing KB5000842 or later updates. Most users affected by this issue are running games full screen or borderless windowed modes and using two or more monitors.
  • Client: Windows 10, version 20H2; Windows 10, version 2004
  • Server: Windows Server, version 20H2; Windows Server, version 2004
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 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. gradeDevices need to be restarted after configuring the special group policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview.

December 2020

Automatic input of Furigana might not work as expected

statusOriginating updateHistory
MitigatedN / A

Last updated: 2020-12-10, 18:24 PT
Opened: 2020-12-03, 12:29 PM PT
When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allow the input of Furigana characters, you might not get the correct Furigana characters and might need to enter them manually. Note for developers: Affected apps are using the ImmGetCompositionString function.
  • Client: Windows 10, version 20H2; Windows 10, version 2004
  • Server: Windows Server, version 20H2; Windows Server, version 2004
Next steps: We are working on a resolution and will provide an update in an upcoming release.

May 2020

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

statusOriginating updateHistory
ResolvedN / A

Resolved: 2021-05-07, 13:29 PT
Opened: 2020-05-27, 00: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 HD Audio Driver under Sound, video and game controllers in Device Manager and have versions8.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.
  • Client: Windows 10, version 20H2, Windows 10, version 2004
  • Server: Windows Server, version 20H2, Windows Server, version 2004
Resolution:The safeguard hold with safeguard IDs 25702617, 25702660, 25702662, and 25702673 has been removed for all devices as of May 7, 2021, including devices with affected drivers. If updated drivers are not available for your device and you are offered Windows 10, version 2004 or Windows 10, version 20H2, a small number of devices might roll back to the previous version of Windows 10 when attempting to update. If this occurs, you should attempt to update to Windows 10, version 2004 or Windows 10, version 20H2 again.
Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to a later version of Windows 10 is offered.

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

statusOriginating updateHistory
ResolvedN / A

Resolved: 2021-05-07, 13:29 PT
Opened: 2020-05-27, 00: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 ESST audio orConexant HD Audio Driver under Sound, video and game controllers in Device Manager and have file name uci64a96.dll through uci64a231.dll and a file version of 7.231.3.0 or lower.
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.
  • Client: Windows 10, version 20H2, Windows 10, version 2004
  • Server: Windows Server, version 20H2, Windows Server, version 2004
Resolution:The safeguard hold with safeguard ID 25178825 has been removed for all devices as of May 7, 2021, including devices with affected drivers. If updated drivers are not available for your device and you are offered Windows 10, version 2004 or Windows 10, version 20H2, a small number of devices might roll back to the previous version of Windows 10 when attempting to update. If this occurs, you should attempt to update to Windows 10, version 2004 or Windows 10, version 20H2 again.
Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to a later version of Windows 10 is offered.