Microsoft And Windows 10

Microsoft And Windows 10

3 PC hardware requirements may vary for games on Windows 10. DirectX Raytracing available with supported games, graphics chips, and requires Windows 10 April Update (or newer). 4 Files may be made available for offline use. Otherwise internet is required. Files Restore requires a Microsoft 365 subscription (sold separately). Hello RicardoSpeight, I'm John an Independent Advisor and a Microsoft user like you. I want to apologize if you encountered this issue. I understand you have a problem updating and retrieving Bluetooth drivers for Windows 10. Microsoft uses telemetry data from Windows 10 to identify security and reliability issues, to analyze and fix software problems, to help improve the quality of Windows and related services, and to.
Windows 10 And Microsoft Office
Microsoft Installation 10
Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents. Starting October 20, Microsoft is making the newest Windows 10 feature update available to mainstream users (not just Insider testers) who manually download it from a variety of channels.
-->Find information on known issues and the status of the rollout for Windows 10, version 20H2 and Windows Server, version 20H2. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s).
Windows 10, version 20H2 is available for users with devices running Windows 10, versions 1903 and higher who manually seek to 'Check for updates' via Windows Update. The recommended servicing status is Semi-Annual Channel.
Note We are slowly throttling up availability over the coming weeks to ensure a reliable download experience. As a result, the update may not be offered to you right away. For more details, see How to get the Windows 10 October 2020 Update.
Windows 10, version 20H2 is now available
 Find out how to get the update >What's new for IT pros
 Explore the latest features and servicing innovations in Windows 10, version 20H2 >
Known issuesThis table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

SummaryOriginating updateStatusLast updated
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-12-11 
17:12 PT
Stop error when plugging in a Thunderbolt NVMe SSD
Devices using Thunderbolt SSDs may receive a stop error 'DRIVER_VERIFIER_DMA_VIOLATION (e6)' when plugging an SSD in.
N/A 
Resolved
 KB45868532020-11-30 
14:00 PT
Automatic input of Furigana might not work as expected
In certain circumstances, the automatic Furigana input/conversion feature may not work as expected in apps.
N/A 
Mitigated
2020-12-10 
18:24 PT
Certificates may not be present after updating to a newer version of Windows 10
Devices in a managed environment using update management tools or ISO images might lose certificates when updating.
N/A 
Resolved
2020-12-11 
17:13 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 
Resolved
 KB45868532020-12-03 
14:18 PT
Domain controllers in your enterprise might encounter Kerberos authentication issues
Authentication and renewal issues for Kerberos ticket after installing updates released November 10, 2020.
OS Build 19042.630
 KB4586781
2020-11-10Resolved
 KB45944402020-11-19 
10:00 PT
You might receive an error when accessing the sign-in options or users MMC snap-in
You might receive the error, 'Your PC will automatically restart in one minute'
N/A 
Mitigated
2020-11-11 
18:11 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
Issue detailsDecember 2020Automatic input of Furigana might not work as expected
StatusOriginating updateHistory
MitigatedN/A 
Last updated: 2020-12-10, 06:24 PT
Opened: 2020-12-03, 12:29 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.
Workaround: To mitigate this issue, please follow the instructions in Revert to a previous version of an IME (Input Method Editor).
Affected platforms:
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.

November 2020Stop error when plugging in a Thunderbolt NVMe SSD
StatusOriginating updateHistory
Resolved
 KB4586853N/A 
Resolved: 2020-11-30, 02:00 PT
Opened: 2020-11-05, 07:01 PT
An incompatibility issue has been found with Windows 10, version 2004 or Windows 10, version 20H2 when using an Thunderbolt NVMe Solid State Disk (SSD). On affected devices, when plugging in a Thunderbolt NVMe SSD you might receive a stop error with a blue screen and 'DRIVER_VERIFIER_DMA_VIOLATION (e6) An illegal DMA operation was attempted by a driver being verified.' Affected Windows 10 devices will have at least one Thunderbolt port and any currently available version of the driver file stornvme.sys.
To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected drivers from being offered Windows 10, version 2004 or Windows 10, version 20H2. If your organization is using Update Compliance, the safeguard IDs is 29991611.
Affected platforms:
Client: Windows 10, version 20H2; Windows 10, version 2004
Resolution: This issue was resolved in KB4586853 and the safeguard hold has been removed as of December 11, 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 20H2 or Windows 10, version 2004 is offered. 

Domain controllers in your enterprise might encounter Kerberos authentication issues
StatusOriginating updateHistory
Resolved
 KB4594440OS Build 19042.630
 KB4586781
2020-11-10Resolved: 2020-11-19, 10:00 PT
Opened: 2020-11-14, 01:39 PT
After installing KB4586781 on domain controllers (DCs) and read-only domain controllers (RODCs) in your environment, you might encounter Kerberos authentication issues. This is caused by an issue in how CVE-2020-17049 was addressed in these updates. As noted in CVE-2020-17049, there are three registry setting values for PerformTicketSignature to control it, but in the current implementation you might encounter different issues with each setting:
Setting the value to 0 might cause authentication issues when using S4U scenarios, such as scheduled tasks, clustering, and services for example line-of-business applications.
The default value setting of 1 might cause non-Windows clients authenticating to Windows Domains using Kerberos to experience authentication issues.
With setting 1, clients attempting to renew a Kerberos ticket that should be renewable on a DC updated with KB4586781 will fail to renew the Kerberos ticket if it was issued from a DC that has not installed an update released November 11, 2020 or any DC running Windows Server 2008 R2 SP1 or Windows Server 2008 SP2.
Going from 0 to 1 might also cause this issue since there can be outstanding Kerberos tickets that are marked renewable, but will not be renewed by updated DCs.
With the default value setting of 1, you might also have Cross realm referrals failures on Windows and non-Windows devices for Kerberos referral tickets passing through domain DCs that have not installed an update released November 11, 2020 or any DC running Windows Server 2008 R2 SP1 or Windows Server 2008 SP2. This issue might happen if domain environment is partially updated or contains at least one Windows Server 2008 R2 SP1 or Windows Server 2008 SP2.
Setting the value to 2 is intended for enforcement mode and will create issues in an environment where not all DCs are updated because it will explicitly reject certain types of non-compliant Kerberos tickets. It should also not be used at this time if your environment contains DCs running Windows Server 2008 R2 SP1 or Windows Server 2008 SP2.
Note This issue only affects Windows Servers, Windows 10 devices and applications in enterprise environments.
Affected platforms:
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 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue was resolved in the out-of-band update KB4594440. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB4594440, 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  KB4594440 is not available from Windows Update and will not install automatically.

You might receive an error when accessing the sign-in options or users MMC snap-in
StatusOriginating updateHistory
MitigatedN/A 
Last updated: 2020-11-11, 06:11 PT
Opened: 2020-11-05, 07:01 PT
After updating to Windows 10, version 20H2, you might receive the error in LSASS.exe with the text 'Your PC will automatically restart in one minute' when interacting with any dialog window that lists users, for example accessing the sign-in options settings app page or the users folder in the Local user and groups MMC snap-in. This issue only affects devices in which any of the local built-in accounts have been renamed, such as Administrator or Guest. You might also receive an error in the Application Event log with Event ID 1015 that LSASS.EXE failed with status code C0000374. C0000374 is related to heap corruption.
This issue is caused by duplicate built-in user accounts being created with the same security identifiers (SIDs) and relative identifiers (RIDs) during the update to Windows 10, version 20H2. SIDs and RIDs for built-in user accounts are well-known as documented here and must be unique on a given device.
To safeguard your update experience, we have applied a compatibility hold on these devices from installing or being offered Windows 10, version 2004 or Windows 10, version 20H2. If your organization is using Update Compliance, the safeguard ID is 30103339.
Workaround: For information on how to mitigate this issue, please see KB4592802. Note If you have already encountered this issue on your device, the uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you're updating to.
Affected platforms:
Client: Windows 10, version 20H2
Server: Windows Server, version 20H2
Next steps: We are working on a resolution and will provide an update in an upcoming release. In the coming weeks, we will also provide updated bundles and refreshed media to prevent the issue.
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.

October 2020Certificates may not be present after updating to a newer version of Windows 10
StatusOriginating updateHistory
ResolvedN/A 
Resolved: 2020-12-11, 05:13 PT
Opened: 2020-10-30, 05:16 PT
System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later and then proceed to update to a later version of Windows 10 from media or an installation source which does not have an LCU released October 13, 2020 or later integrated. This primarily happens when managed devices are updated using outdated bundles or media through an update management tool such as Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager. This might also happen when using outdated physical media or ISO images that do not have the latest updates integrated. 
Note Devices using Windows Update for Business or that connect directly to Windows Update are not impacted. Any device connecting to Windows Update should always receive the latest versions of the feature update, including the latest LCU, without any extra steps. 
Workaround: If you have already encountered this issue on your device, you can mitigate it within the uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you're updating to. You will then need to update to the later version of Windows 10 after the issue is resolved in your environment. Note Within the uninstall window, you can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You must make this change before the default uninstall window has lapsed. For more information, see DISM operating system uninstall command-line options. 
Affected platforms:
Client: Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1903
Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1903
Resolution: This issue is now resolved when using the latest feature update bundles and refreshed media. Feature update bundles released November 9, 2020 or later will resolve this issue when deploying via Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. Refreshed media was released December 3, 2020 on Visual Studio Subscriptions (VSS, formerly MSDN Subscriptions) and December 7, 2020 on Volume Licensing Service Center (VLSC). For information on verifying you're using the refreshed media, see How to address feature update refreshes in your environment. If you are using or creating custom media, you will need to include an update released October 13, 2020 or later.
Windows 10 And Microsoft Office
August 2020Issues when using Microsoft IME for Japanese or Chinese languages
StatusOriginating updateHistory
Resolved
 KB4586853N/A 
Resolved: 2020-12-03, 02:18 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. For a list of specific issues, see KB4564002.
Affected platforms:
Client: Windows 10, version 20H2, Windows 10, version 2004
Server: Windows Server, version 20H2, Windows Server, version 2004
Resolution: All IME issues listed in KB4564002 were resolved in KB4586853.

May 2020Errors or issues during or after updating devices with certain Conexant audio drivers
StatusOriginating updateHistory
InvestigatingN/A 
Last updated: 2020-12-11, 05:12 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 for safeguard IDs 25702617 and 25702660, 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.
Resolution: This issue was resolved for safeguard IDs 25702662 and 25702673. The safeguard hold has been removed for these safeguard IDs as of December 11, 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 or Windows 10, version 20H2 is offered. 

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.

 -->Windows 10 Home and Pro follows the Modern Lifecycle Policy.
This applies to the following editions: Home, Pro, Pro Education, Pro for Workstations
Important
Microsoft will continue to support at least one Windows 10 Semi-Annual Channel until October 14, 2025.
Support DatesListingStart DateRetirement Date
Windows 10 Home and Pro07/29/201510/14/2025
ReleasesVersionStart DateEnd Date
Version 20H210/20/202005/10/2022
Version 200405/27/202012/14/2021
Version 190911/12/201905/11/2021
Version 190305/21/201912/08/2020
Version 180911/13/201811/10/2020
Version 180310/17/201711/12/2019
Version 170910/17/201704/09/2019
Version 170304/05/201710/09/2018
Version 160708/02/201604/10/2018
Version 151111/10/201510/10/2017
Version 150707/29/201505/09/2017
LinksNote
Pro for Workstations first released with Version 1709.
Note

Listing	Start Date	Retirement Date
Windows 10 Home and Pro	07/29/2015	10/14/2025

Version	Start Date	End Date
Version 20H2	10/20/2020	05/10/2022
Version 2004	05/27/2020	12/14/2021
Version 1909	11/12/2019	05/11/2021
Version 1903	05/21/2019	12/08/2020
Version 1809	11/13/2018	11/10/2020
Version 1803	10/17/2017	11/12/2019
Version 1709	10/17/2017	04/09/2019
Version 1703	04/05/2017	10/09/2018
Version 1607	08/02/2016	04/10/2018
Version 1511	11/10/2015	10/10/2017
Version 1507	07/29/2015	05/09/2017

Unless deferred, subsequent Windows 10 Semi-Annual Channel feature updates may be installed prior to the listed end of Mainstream Support date.
EditionsMicrosoft Installation 10Home
Pro
Pro Education
Pro for Workstations

Summary	Originating update	Status	Last updated
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-12-11 17:12 PT
Stop error when plugging in a Thunderbolt NVMe SSD Devices using Thunderbolt SSDs may receive a stop error 'DRIVER_VERIFIER_DMA_VIOLATION (e6)' when plugging an SSD in.	N/A	Resolved KB4586853	2020-11-30 14:00 PT
Automatic input of Furigana might not work as expected In certain circumstances, the automatic Furigana input/conversion feature may not work as expected in apps.	N/A	Mitigated	2020-12-10 18:24 PT
Certificates may not be present after updating to a newer version of Windows 10 Devices in a managed environment using update management tools or ISO images might lose certificates when updating.	N/A	Resolved	2020-12-11 17:13 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	Resolved KB4586853	2020-12-03 14:18 PT
Domain controllers in your enterprise might encounter Kerberos authentication issues Authentication and renewal issues for Kerberos ticket after installing updates released November 10, 2020.	OS Build 19042.630 KB4586781 2020-11-10	Resolved KB4594440	2020-11-19 10:00 PT
You might receive an error when accessing the sign-in options or users MMC snap-in You might receive the error, 'Your PC will automatically restart in one minute'	N/A	Mitigated	2020-11-11 18:11 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

Automatic input of Furigana might not work as expected
Status	Originating update	History
Mitigated	N/A	Last updated: 2020-12-10, 06:24 PT Opened: 2020-12-03, 12:29 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. Workaround: To mitigate this issue, please follow the instructions in Revert to a previous version of an IME (Input Method Editor). Affected platforms: 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.

Stop error when plugging in a Thunderbolt NVMe SSD
Status	Originating update	History
Resolved KB4586853	N/A	Resolved: 2020-11-30, 02:00 PT Opened: 2020-11-05, 07:01 PT
An incompatibility issue has been found with Windows 10, version 2004 or Windows 10, version 20H2 when using an Thunderbolt NVMe Solid State Disk (SSD). On affected devices, when plugging in a Thunderbolt NVMe SSD you might receive a stop error with a blue screen and 'DRIVER_VERIFIER_DMA_VIOLATION (e6) An illegal DMA operation was attempted by a driver being verified.' Affected Windows 10 devices will have at least one Thunderbolt port and any currently available version of the driver file stornvme.sys. To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected drivers from being offered Windows 10, version 2004 or Windows 10, version 20H2. If your organization is using Update Compliance, the safeguard IDs is 29991611. Affected platforms: Client: Windows 10, version 20H2; Windows 10, version 2004 Resolution: This issue was resolved in KB4586853 and the safeguard hold has been removed as of December 11, 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 20H2 or Windows 10, version 2004 is offered.

Domain controllers in your enterprise might encounter Kerberos authentication issues
Status	Originating update	History
Resolved KB4594440	OS Build 19042.630 KB4586781 2020-11-10	Resolved: 2020-11-19, 10:00 PT Opened: 2020-11-14, 01:39 PT
After installing KB4586781 on domain controllers (DCs) and read-only domain controllers (RODCs) in your environment, you might encounter Kerberos authentication issues. This is caused by an issue in how CVE-2020-17049 was addressed in these updates. As noted in CVE-2020-17049, there are three registry setting values for PerformTicketSignature to control it, but in the current implementation you might encounter different issues with each setting: Setting the value to 0 might cause authentication issues when using S4U scenarios, such as scheduled tasks, clustering, and services for example line-of-business applications. The default value setting of 1 might cause non-Windows clients authenticating to Windows Domains using Kerberos to experience authentication issues. With setting 1, clients attempting to renew a Kerberos ticket that should be renewable on a DC updated with KB4586781 will fail to renew the Kerberos ticket if it was issued from a DC that has not installed an update released November 11, 2020 or any DC running Windows Server 2008 R2 SP1 or Windows Server 2008 SP2. Going from 0 to 1 might also cause this issue since there can be outstanding Kerberos tickets that are marked renewable, but will not be renewed by updated DCs. With the default value setting of 1, you might also have Cross realm referrals failures on Windows and non-Windows devices for Kerberos referral tickets passing through domain DCs that have not installed an update released November 11, 2020 or any DC running Windows Server 2008 R2 SP1 or Windows Server 2008 SP2. This issue might happen if domain environment is partially updated or contains at least one Windows Server 2008 R2 SP1 or Windows Server 2008 SP2. Setting the value to 2 is intended for enforcement mode and will create issues in an environment where not all DCs are updated because it will explicitly reject certain types of non-compliant Kerberos tickets. It should also not be used at this time if your environment contains DCs running Windows Server 2008 R2 SP1 or Windows Server 2008 SP2. Note This issue only affects Windows Servers, Windows 10 devices and applications in enterprise environments. Affected platforms: 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 2016; Windows Server 2012 R2; Windows Server 2012 Resolution: This issue was resolved in the out-of-band update KB4594440. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB4594440, 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 KB4594440 is not available from Windows Update and will not install automatically.

You might receive an error when accessing the sign-in options or users MMC snap-in
Status	Originating update	History
Mitigated	N/A	Last updated: 2020-11-11, 06:11 PT Opened: 2020-11-05, 07:01 PT
After updating to Windows 10, version 20H2, you might receive the error in LSASS.exe with the text 'Your PC will automatically restart in one minute' when interacting with any dialog window that lists users, for example accessing the sign-in options settings app page or the users folder in the Local user and groups MMC snap-in. This issue only affects devices in which any of the local built-in accounts have been renamed, such as Administrator or Guest. You might also receive an error in the Application Event log with Event ID 1015 that LSASS.EXE failed with status code C0000374. C0000374 is related to heap corruption. This issue is caused by duplicate built-in user accounts being created with the same security identifiers (SIDs) and relative identifiers (RIDs) during the update to Windows 10, version 20H2. SIDs and RIDs for built-in user accounts are well-known as documented here and must be unique on a given device. To safeguard your update experience, we have applied a compatibility hold on these devices from installing or being offered Windows 10, version 2004 or Windows 10, version 20H2. If your organization is using Update Compliance, the safeguard ID is 30103339. Workaround: For information on how to mitigate this issue, please see KB4592802. Note If you have already encountered this issue on your device, the uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you're updating to. Affected platforms: Client: Windows 10, version 20H2 Server: Windows Server, version 20H2 Next steps: We are working on a resolution and will provide an update in an upcoming release. In the coming weeks, we will also provide updated bundles and refreshed media to prevent the issue. 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.

Certificates may not be present after updating to a newer version of Windows 10
Status	Originating update	History
Resolved	N/A	Resolved: 2020-12-11, 05:13 PT Opened: 2020-10-30, 05:16 PT
System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later and then proceed to update to a later version of Windows 10 from media or an installation source which does not have an LCU released October 13, 2020 or later integrated. This primarily happens when managed devices are updated using outdated bundles or media through an update management tool such as Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager. This might also happen when using outdated physical media or ISO images that do not have the latest updates integrated. Note Devices using Windows Update for Business or that connect directly to Windows Update are not impacted. Any device connecting to Windows Update should always receive the latest versions of the feature update, including the latest LCU, without any extra steps. Workaround: If you have already encountered this issue on your device, you can mitigate it within the uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you're updating to. You will then need to update to the later version of Windows 10 after the issue is resolved in your environment. Note Within the uninstall window, you can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You must make this change before the default uninstall window has lapsed. For more information, see DISM operating system uninstall command-line options. Affected platforms: Client: Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1903 Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1903 Resolution: This issue is now resolved when using the latest feature update bundles and refreshed media. Feature update bundles released November 9, 2020 or later will resolve this issue when deploying via Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. Refreshed media was released December 3, 2020 on Visual Studio Subscriptions (VSS, formerly MSDN Subscriptions) and December 7, 2020 on Volume Licensing Service Center (VLSC). For information on verifying you're using the refreshed media, see How to address feature update refreshes in your environment. If you are using or creating custom media, you will need to include an update released October 13, 2020 or later.

Issues when using Microsoft IME for Japanese or Chinese languages
Status	Originating update	History
Resolved KB4586853	N/A	Resolved: 2020-12-03, 02:18 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. For a list of specific issues, see KB4564002. Affected platforms: Client: Windows 10, version 20H2, Windows 10, version 2004 Server: Windows Server, version 20H2, Windows Server, version 2004 Resolution: All IME issues listed in KB4564002 were resolved in KB4586853.

Errors or issues during or after updating devices with certain Conexant audio drivers
Status	Originating update	History
Investigating	N/A	Last updated: 2020-12-11, 05:12 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 for safeguard IDs 25702617 and 25702660, 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. Resolution: This issue was resolved for safeguard IDs 25702662 and 25702673. The safeguard hold has been removed for these safeguard IDs as of December 11, 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 or Windows 10, version 20H2 is offered.