Just-Released Windows 10 v20H2 Inherits Some Bugs from v2004

Submit

Since the release of Windows 10 May 2020 Update, version 2004 earlier this year, Microsoft has chosen to be more upfront about what issues to expect from a new feature update. While this helps in reducing dread over the new update, it also makes users question why would the company not remove these issues before the public release.

In the case of Windows 10 October 2020 Update, it seems like version 20H2 is inheriting the issues of version 2004 that are yet to be resolved.

PS5 3rd-Party Games Outperforming XSX, Microsoft Vows to “Resolve the Issues” With Devs

Here is the current list of Windows 10 October 2020 Update known issues

1- When installing incorrectly formatted third-party drivers, you might receive an error (Tagged as Resolved)

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.

Microsoft has recommended users to contact the driver vendor or device manufacturer (OEM) and ask them for an updated driver to correct the issue.

2- Errors or issues during or after updating devices with certain Conexant audio drivers (Tagged as Investigating)

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.

This issue is coming from version 2004. The Windows maker said that it has applied a compatibility hold on Windows 10 devices with affected Conexant or Synaptics audio drivers. Microsoft added that it's working with Synaptics "on a resolution and will provide an update in an upcoming release."

3- Errors or issues during or after updating devices with Conexant ISST audio drivers (Tagged as Investigating)

Xbox TV App May Come Within Next Year Says Spencer, Cloud-Console Hybrid Model the Future

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.

Similar to above issue, currently causing a safeguard hold for affected devices.

4- Issues when using Microsoft IME for Japanese or Chinese languages (Tagged as Mitigated)

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.

Workaround steps are shared in this support document.

Updated list of Windows 10 version 20H2 known issues

1Issues when using Microsoft IME for Japanese or Chinese languages
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.
Mitigated
2Errors 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.
Investigating
3Errors 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.
Investigating
4When installing incorrectly formatted third-party drivers, you might receive an error
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.
Resolved
5Certificates may not be present after updating to a newer version of Windows 10
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.
Investigating
6You might receive an error when accessing the sign-in options or users MMC snap-in
After upgrading 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.
Mitigated
7Stop error when plugging in a Thunderbolt NVMe SSD
Intel and Microsoft have found incompatibility issues when Windows 10, version 2004 or Windows 10, version 20H2 are used a 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.
Investigating
8Domain controllers in your enterprise might encounter Kerberos authentication issues
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.
Investigating

- In this stream

Submit