Jump to content

The Windows 10 May 2020 Update still has a whole bunch of known issues


Karlston

Recommended Posts

The Windows 10 May 2020 Update still has a whole bunch of known issues

1589115291_w10may2020update_story.jpg

 

Today, Microsoft released the Windows 10 May 2020 Update, also known as version 2004. It's actually been in testing with Windows Insiders for 15 months, with the RTM build being released in December, and serviced ever since. There are a few reasons that it's been in testing for so long, but one of them is because Microsoft changed the way it delivers feature updates. Version 1909 was nothing more than an enablement package. For all intents and purposes, it was just a serviced version of 1903.

 

But version 2004 is rolling in as a full Windows 10 build, and these seem to be coming yearly at this point, since 20H2 is also going to be an enablement package. And since this is such a major update, that means lots of things are changing, and there are still a bunch of known issues, despite being tested and serviced for so long.

 

Here's the full list of things that are still broken:

  • 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.
  • 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.
  • 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.
  • 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.
  • Variable refresh rate not working as expected on devices with Intel iGPU
    Enabling VRR on affected devices will not enable the VRR for most games, especially games using Direct X 9.
  • 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
  • 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.
  • No mouse input with apps and games using GameInput Redistributable
    Affected apps and games using both GameInput Redistributable and Windows 10, version 2004 might lose mouse input.
  • 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
  • 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.

A lot of these are pretty significant. There are Bluetooth connectivity issues if you've got more than one device connected, such as a mouse and a keyboard. If you use a Thunderbolt dock, that's an issue too. Also, be aware if you've got an older Nvidia GPU, as that could run into some issues as well.

 

All of these issues list "investigating" as the status, so it's unclear when they will be fixed. For many of these issues, there's a compatibility hold in place for those that will be affected, so those users won't be offered this update.

 

 

Source: The Windows 10 May 2020 Update still has a whole bunch of known issues (Neowin)

Link to comment
Share on other sites


  • Replies 5
  • Views 1.4k
  • Created
  • Last Reply
BimBamSmash

Ah, miracles of modern tech project management, where games are sold at full-price while development has barley reached the alpha stage, and mandatory operating system updates are rolled out with a list of several eyebrow-raising known-issues. This is the much lauded Agile and Scrum framework in full display for you folks.

Link to comment
Share on other sites


This new issue for the May 2020 Update was added on May 28:

 

Quote

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
 
Next steps: We are working on a resolution and estimate a solution will be available in mid-June.

 

at least MS finally acknowledged the problem with the DISM tool for 2004

Link to comment
Share on other sites


Microsoft acknowledges several issues in the latest update

 

Windows 10 May 2020 Update is now live for users who want to manually download it, and in addition to lots of new features and improvements, it also comes with a series of known issues that everyone should have in mind when planning to update.

 

While you can check all issues that have already been acknowledged by Microsoft in the box embedded at the end of the article, there are several others that you should be aware of, simply because they are causing Blue Screen of Death errors.

 

As you probably know already, a BSOD is the worst thing that could happen on a Windows device, as it’s a fatal crash that requires a full reboot to recover.

 

The following known issues could cause a BSOD once Windows 10 May 2020 Update is installed on a device:

  • Errors or issues during or after updating devices with certain Conexant audio drivers
  • Stop error when plugging or unplugging a Thunderbolt dock
  • Issue with older drivers for Nvidia display adapters (GPU)

 

Upgrade blocks in place

 

More information on the NVIDIA issue in Windows 10 May 2020 Update is available here.

 

The Conexant audio driver bug, on the other hand, is encountered after the update to version 2004 and could lead to a Blue Screen of Death.

 

“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,” Microsoft says.

 

As for the Thunderbolt problem, Microsoft says it’s triggered when a Thunderbolt dock is used on a device with Kernel DMA Protection enabled and Windows Hypervisor Platform disabled.

 

In all cases, Microsoft has already put an upgrade block in place, which means that devices that might be potentially affected won’t get the May 2020 Update via Windows Update.

 

Source

 

Link to comment
Share on other sites


Similar topics merged.

 

(The three issues mentioned are included in the OP's list)

Link to comment
Share on other sites


zanderthunder
On 5/28/2020 at 4:08 AM, Karlston said:

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.

Surface devices such as Surface Laptop 3 and Surface Pro 7 are affected with this issue. Not sure for other Surface devices though.

Link to comment
Share on other sites


Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...