So basically it's ready for release ?
Current status as of July 22, 2020
Windows 10, version 2004 is available for users with devices running Windows 10, versions 1903 and 1909, who manually seek to “Check for updates” via Windows Update. We are now starting a new phase in our rollout. Using the machine learning-based (ML-based) training we have done so far, we are increasing the number of devices selected to update automatically to Windows 10, version 2004 that are approaching end of service. We will continue to train our machine learning through all phases to intelligently rollout new versions of Windows 10 and deliver a smooth update experience. The recommended servicing status is Semi-Annual Channel.
Note follow @WindowsUpdate on Twitter to find out when new content is published to the release information dashboard.
Unexpected one-minute startup of Outlook if UE-V is enabled | Microsoft Support
Issue with some Storage Spaces configurations after updating to Windows 10, version 2004 and Windows Server, version 2004 | Microsoft Support
Workaround and recovery steps for issue with some Parity Storage Spaces after updating to Windows 10, version 2004 and Windows Server, version 2004 | Microsoft Support
Issues using OneDrive Files On-Demand on some devices after updating to Windows 10, version 2004 | Microsoft Support
Known issues
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.
Summary Originating update Status Last updated 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.OS Build 19041.488
KB4571744
2020-09-03Resolved
KB45868532020-11-30
14:00 PTErrors 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 Confirmed 2021-01-05
17:37 PTErrors 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 Confirmed 2021-01-05
17:37 PTAutomatic 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
Resolved issues
Summary Originating update Status Date resolved 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.OS Build 19041.488
KB4571744
2020-09-03Resolved
KB45868532020-11-30
14:00 PTIssues 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-11-30
14:00 PTDomain 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 19041.630
KB4586781
2020-11-10Resolved
KB45944402020-11-19
10:00 PTCertificates 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.OS Build 19041.546
KB4577063
2020-10-01Resolved 2020-11-17
14:11 PTLocal Security Authority Subsystem Service (lsass.exe) might fail on some devices
Affected devices might receive a critical system process error and the device might restart.N/A Resolved
KB45655032020-07-14
10:00 PTWhen installing incorrectly formatted third-party drivers, you might receive an error
You might receive, “Windows can’t verify the publisher of this driver software” or other errors.OS Build 19041.572
KB4579311
2020-10-13Resolved 2020-10-20
10:06 PTCertain WWAN LTE modems might not be able to connect after waking from sleep
Affected WWAN LTE modems might show no internet and be unable to connect.N/A Resolved
KB45770632020-10-01
10:00 PTDragging with the mouse in some apps might cause issues for some IME users
Users of the Microsoft IME for Chinese and Japanese might receive an error or the app might stop responding or close.N/A Resolved
KB45717442020-09-03
14:00 PTIssue 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.N/A Resolved
KB45688312020-07-31
10:00 PTIssues 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 startingN/A Resolved
KB45688312020-07-31
10:00 PTDifficulty 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.N/A Resolved
KB45688312020-07-31
10:00 PTVariable refresh rate not working as expected on devices with Intel iGPU
Enabling VRR on affected devices will not enable the VRR for games using Direct X 9.N/A Resolved
KB45688312020-07-31
10:00 PTStop error when plugging or unplugging a Thunderbolt dock
Devices using Thunderbolt docks may receive a stop error when plugging in or unplugging the dockN/A Resolved
KB45655032020-11-30
14:00 PTOutlook closes unexpectedly or you might receive an error when attempting to open
An example of an error you might receive is, "Outlook couldn't start last time."OS Build 19041.388
KB4565503
2020-07-14Resolved 2020-07-15
15:43 PTIssues 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.N/A Resolved
KB45655032020-07-14
10:00 PT
Source:
- Known issues in Windows 10, version 2004 and Windows Server, version 2004
- Resolved issues in Windows 10, version 2004 and Windows Server, version 2004
See also:
I totally disagree with the assumption that there aren't any issues.
There are well documented issues regarding ESENT errors. I also see on many machines. The VSS issue was catalogued by design and was never fixed and this is what also will happen with the ESENT issues and the Defrag issue. There are a lot more problems then those that I mention. The worst is that most of the time it's users like us that with trial and error eventually find a fix for these issues and document a work around. Why doesn't MS just quick fix those well documented errors and then we can move on ?
I'm worried too. They say that the new Windows will be a completely new version and that, therefore, it will erase outdated programs, as well as so many other programs that would not be compatible. How is it that Microsoft takes so many freedoms in matters that are not their own?How is it that to "update" you have to throw Windows out the window?Can we wait a few months to update?Are there solutions to not update in the short term?