[Update, July 31]: fixed several issues including Nvidia GPU driver and Intel iGPU issues via KB4568831 (will be delivered to everyone next week)
[Update, July 15]: lsass.exe and ImeMode issues resolved via KB4565503.
[Update, June 18]: Printing issue resolved via KB4567523.
[Update, June 16]: added more issues / solved (one by Avast); printing problem will be solved soon.
[Update, June 9]: one issue was addressed by Patch Tuesday updates for version 2004 in June.
Originally published May 28
Microsoft released the Windows 10 May 2020 Update, version 2004, after more than a year of internal and insider testing. While the latest builds of Windows 10 version 2004 did not show any major bugs, the Windows maker has now released a fairly long list of known issues plaguing the latest version of the operating system.
Because of these issues, Microsoft is putting compatibility watch on Windows 10 devices that may be affected by these bugs. The company also recommended that you do not manually install the update using the Update Now button or the Media Creation Tool until the problem with your specific machine is resolved.
Here is the complete list of known issues with Windows 10 version 2004 (and their current status) recognized by Microsoft
|1||DISM may be falsely reporting that corruption is still present after repair: |
After using the / restorehealth Deployment Image Servicing and Management (DISM.exe) command to detect and correct system corruption, you may receive a notification from the tool that corruption is still present. This can happen even when it has been repaired. An example for using the / restorehealth command is: DISM.exe / Online / Cleanup-image / Restorehealth
|2||Variable refresh rate does not work as expected on devices with Intel iGPU: |
Intel and Microsoft have identified incompatibilities when using a Variable Refresh Rate (VRR) monitor connected to an Intel Integrated Graphics Processing Unit (iGPU) display adapter and Windows 10, version 2004 (the Windows 10 May 2020 Update). Enabling VRR on affected devices will not enable the VRR for games using Direct X 9.
|3||Difficulty connecting to more than one Bluetooth device: |
Realtek and Microsoft have found incompatibility issues with certain versions of drivers for Realtek Bluetooth radios and Windows 10, version 2004 (the Windows 10 May 2020 update). Windows 10 devices with affected Realtek Bluetooth radio drivers may not be able to connect or pair with more than one Bluetooth device at a time after updating.
|4||Errors or problems 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 (Windows 10 May 2020 Update). Windows 10 devices with the affected Conexant ISST audio driver may receive an error or experience problems installing the update or after the device is updated. The affected driver will be named Conexant ISST Audio or Conexant HDAudio Driver under Sound, Video and Game Controllers in Device Manager and will have the file name uci64a96.dll through uci64a231.dll and a file version lower than 184.108.40.206.
|5||Errors or problems 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 (Windows 10 May 2020 Update). Windows 10 devices with affected Conexant or Synaptics audio drivers may receive a blue screen stop error during or after updating to Windows 10, version 2004. The affected driver is named Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and versions have 220.127.116.11, 18.104.22.168 or 22.214.171.124 through 8.66.89.00 for chdrt64.sys or chdrt32.sys.
|6||Problems using the ImeMode property to manage IME mode for individual text input fields:|
Some apps use the ImeMode property to manage IME (Input Method Editor) mode for individual text input fields to increase typing efficiency. Some IMEs in Windows 10 version 2004 (the May 2020 update) may have problems using the ImeMode property with certain apps. For example, the input mode does not automatically switch to Kanji or Hiragana.
|7||Stop error when connecting or disconnecting a Thunderbolt dock:|
Intel and Microsoft have found incompatibility issues when using Windows 10 version 2004 (Windows 10 May 2020 Update) with certain settings and a Thunderbolt dock. On affected devices, you may receive a blue screen stop error when you connect or disconnect a Thunderbolt dock. Affected Windows 10 devices have at least one Thunderbolt port, have Kernel DMA Protection enabled, and Windows Hypervisor Platform is disabled. To check if your Kernel DMA Protection settings are, go to How to check if Kernel DMA Protection is enabled. To check your Windows Hypervisor Platform settings, select Start, type Enable or disable Windows features and select it. Find the setting for Windows Hypervisor Platform when the Windows Features dialog box opens. If checked, Windows Hypervisor platform is disabled.
|8||Errors or unexpected restarts for some devices using Always On, Always Connected:|
Some devices that use the Always On, Always Connected feature may have compatibility issues with Windows 10, version 2004 (Windows 10 May 2020 Update). Affected devices have more than one Always On, Always Connected compatible network adapter, such as the Microsoft Surface Pro 7 and Microsoft Surface Laptop 3, and can receive errors or shutdown or restart unexpectedly.
|9||No mouse input on apps and games with GameInput Redistributable:|
An incompatibility issue has been found with some apps and games with GameInput Redistributable and Windows 10 version 2004 (Windows 10 May 2020 Update). Affected apps or games can lose mouse input. Note GameInput Redistributable may be a bundle of apps and games and may install silently during the installation of that app or game.
|10||Problems updating or booting devices when aksfridge.sys or aksdf.sys is present:|
An incompatibility issue has been found with apps or drivers using certain versions of aksfridge.sys or aksdf.sys and Windows 10 version 2004 (Windows 10 May 2020 Update). When an affected version of aksfridge.sys or aksdf.sys is present, Windows 10, version 2004 may fail to install or start after updating. Affected file versions are up to 1.8.0. * For aksfridge.sys or up to 1.51. * For aksdf.sys.
|11||Older Nvidia display adapter (GPU) drivers issue:|
Nvidia and Microsoft have found incompatibility issues with certain versions of the Nvidia display adapter drivers and Windows 10 version 2004 (Windows 10 May 2020 Update). Windows 10 devices with affected Nvidia display driver versions may experience a blue screen stop error or other issues during or after installing the update to Windows 10, version 2004. The affected drivers are any version lower than 358.00.
Workaround: To resolve this issue, contact your device (OEM) manufacturer to see if an updated driver is available and install it.
Next steps: Microsoft and Nvidia are working on a fix and will update in an upcoming release.
Note We recommend that you do not attempt to update manually using the Update Now button or the Media Creation Tool until this issue is resolved.
|12||Error opening a Microsoft Office application|
We have received reports that some users are unable to open apps after installing KB4557957, especially Microsoft Office apps. Affected users may also receive an error message, such as’ Windows cannot find ‘c: program files microsoft office root office16 winword.exe’. Make sure you typed the name correctly and try again. “
|Solved by Avast|
|13||Print Spooler may experience an error or close unexpectedly when you try to print|
Some printers may not be able to print after installing KB4557957. Print Spooler may display an error or close unexpectedly when you try to print, and no output from the affected printer. You may also experience problems with the apps you’re trying to print with. You may receive an error from the app or the app closes unexpectedly. Note This problem can also affect software-based printers, such as printing to PDF.
|14||Subsystem Service Local Security Authority (lsass.exe) may fail on some devices|
The Local Security Authority Subsystem Service file (lsass.exe) may fail on some devices with the error message “A critical system process, C: WINDOWS system32 lsass.exe, failed with status code c0000008. The machine should now be restarted. “
|15||Dragging the mouse in some apps can cause problems for some IME users |
Microsoft IME Chinese and Japanese users in some apps, such as Microsoft Excel, may receive an error or the app becomes unresponsive or closes when trying to drag the mouse.
It is unclear why Microsoft had to wait until after the launch release this list of known issues and why they could not be addressed when Windows 10 version 2004 was tested. Since the list is already live, it can’t be due to customer complaints either, as it’s too early to start that process. We can only hope that that process won’t bring more bugs in the just released Windows 10 May 2020 update.
Windows 10 version 2004 is the first update to be released under the new direction of Panos Panay. Many hoped that this would finally end the era of buggy updates for Windows 10. While users are sure to criticize this list of known issues, it must be admitted that the company is at least honest about it (after all, the bar is low ) and don’t wait for users to go through the annoyingly tiring updating process and then report the issues. Hopefully the solutions will come through OEMs or next month’s cumulative update.
As always, we recommend waiting a few months before moving on to a new version of the operating system. For those who want to have 100% confidence in a new version, it is better to stick to the latest released version (November 2019 update in this case) rather than the latest version. But if you are a fan of Windows 10, you can choose to install Windows 10 version 2004 manually. Again, Microsoft recommended that you don’t if the above list of known issues affects your device.
* solved by June 9 cumulative update.
** up to and including June PT update; resolved by the June 18 out-of-band update.
*** resolved through July 14 cumulative update.
**** resolved through July 31 KB4568831 (currently in preview)