19041 is possibly Version 2004 and Edge Chromium is one week away! Microsoft released Windows 10 version 2004, also known as the May 2020 Update. The new feature update for Microsoft's Windows operating system is available for systems running Windows 10 version 1903 or 1909 only via Windows Update, and only if users click on the 'check for updates' button to search for the new version manually. The new Microsoft Edge will add a shortcut to the desktop. If the current version of Microsoft Edge already has a shortcut, it will be replaced. By default, most protocols that Microsoft Edge handles will be migrated to the new Microsoft Edge. The current version of Microsoft Edge will be hidden from UX surfaces in the OS.
-->Find information on known issues and the status of the rollout for Windows 10, version 2004 and Windows Server, version 2004. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). Want the latest Windows release health updates? Follow @WindowsUpdate on Twitter.
Windows 10, version 2004 is designated for broad deployment. The recommended servicing status is Semi-Annual Channel. |
| 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 issues
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| Microsoft Edge missing after using custom media/ISOs including March 29, 2021 updates Microsoft Edge missing when installing Windows from custom media/ISOs using updates released March 25, 2021 or later. | OS Build 19041.906 KB5000842 2021-03-29 | Resolved | 2021-03-29 17:01 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 | Confirmed | 2021-01-22 13:43 PT |
| 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 | Confirmed | 2021-01-05 17:37 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 |
Issue details
March 2021
Windows 10 2004 Edge Version
Microsoft Edge missing after using custom media/ISOs including March 29, 2021 updates | ||
| Status | Originating update | History |
| Resolved | OS Build 19041.906 KB5000842 2021-03-29 | Resolved: 2021-03-29, 17:01 PT Opened: 2021-03-29, 16:15 PT |
Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone Servicing Stack Update (SSU) released March 29, 2021 or later. Note Devices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the Servicing Stack Update (SSU) and latest cumulative update (LCU) without any extra steps. Workaround: If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge from here. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business Affected platforms:
Resolution: This issue is resolved. To avoid this issue, be sure to first slipstream the Servicing Stack Update (SSU) released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the latest cumulative update (LCU). To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the using SSU:
| ||
December 2020
Automatic input of Furigana might not work as expected | ||
| Status | Originating update | History |
| Mitigated | N/A | Last updated: 2020-12-10, 18: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:
Next steps: We are working on a resolution and will provide an update in an upcoming release. | ||
May 2020
Errors or issues during or after updating devices with Conexant ISST audio drivers | ||
| Status | Originating update | History |
| Confirmed | N/A | Last updated: 2021-01-22, 13:43 PT Opened: 2020-05-27, 00: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 of 7.231.3.0 or lower. 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:
Workaround: To mitigate the safeguard, you might need to check with your device manufacturer (OEM) to see if an updated driver is available and install it. If updated drivers are not available for your device and you are offered Windows 10, version 2004 or Windows 10, version 20H2, a small number of devices might roll back to the previous version of Windows 10 when attempting to update. If this occurs, you should attempt to update to Windows 10, version 2004 or Windows 10, version 20H2 again. Next steps: Microsoft and Synaptics are working on a resolution and will provide an update in an upcoming release. As of January 14, 2021, we are adjusting this safeguard to allow certain devices with the affected driver to update to Windows 10, version 2004 or Windows 10, version 20H2. 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. | ||
Errors or issues during or after updating devices with certain Conexant audio drivers | ||
| Status | Originating update | History |
| Confirmed | N/A | Last updated: 2021-01-05, 17:37 PT Opened: 2020-05-27, 00: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:
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. | ||
Microsoft has recently re-released Windows update KB4576754 to offer support for Windows 10 version 2004, or May 2020 Update, essentially forcing the new Edge browser on its latest desktop operating system release.
Windows 10 version 2004 was officially launched in late May, and since then, devices across the world have been receiving it in stages. The rollout still continues today, as general availability is yet to be reached, despite the fact that Microsoft is expected to complete another feature update as soon as this month.
Windows 10 version 20H2 should be completed in September, while the rollout for production devices should kick off in October or November.
If you think you’ve heard of update KB4576754 before, you’re not wrong. This is a rather infamous update that pushes the new Chromium-powered Microsoft Edge on Windows 10 devices, replacing the legacy version of the browser, as well as its files and browsing data.
Novation usb devices driver. Borncity first report about KB4576754 being re-released earlier this month when the update landed on the first devices running Windows 10 version 2004. The rollout most likely happens gradually, as I still haven’t received the update on my laptop running the May update.
According to the official KB page, the latest revision to this update was released on August 31, and now KB4576754 is aimed at Windows 10 version 1809 and newer, with version 2004 included too.
“Microsoft has released a new Chromium-based version of Microsoft Edge. This new version provides best in class compatibility with extensions and websites. Additionally, this new version provides great support for the latest rendering capabilities, modern web applications, and powerful developer tools across all supported OS platforms,” Microsoft explains.
Windows 10 2004 Edge Chromium
Once the update is installed and Microsoft Edge legacy is replaced with its Chromium-based sibling, you should see the new browser launching after a system reboot to provide you with the first-run welcome screen.
“The First Run Experience (FRE) will auto-launch the first time that a device restarts after the new Microsoft Edge is installed. This does not occur on devices joined to a Domain, Active Directory, Azure AD or on Windows 10 Enterprise and Surface Hub Editions,” Microsoft explains.
What you need to know is that the Chromium version of Edge replaces pretty much everything that is linked with the legacy browser, thus making the transition as smooth as it can be. The browsing history, the bookmarks, the shortcuts, and the desktop icons, everything is moved to the new browser, so there’s a chance that many might not even notice that a new browser was installed on the devices.
Needless to say, many have complained that Microsoft is forcing the new browser on their devices. The company, however, provides users with a blocker toolkit that can be installed to prevent this update from being offered on Windows Update.
Leaving aside all the criticism that Microsoft has been forced to deal with lately due to this update, the new Microsoft Edge browser is actually worth a try.
The application comes with a feature lineup that’s obviously similar to the one of Google Chrome, but at the same time, it also bundles additional tools that remind of the legacy version of Edge. Needless to say, it also comes with support for Microsoft accounts, and you can configure sync features to have data like the passwords and the bookmarks roaming across devices, with Android support also offered.
Windows 10 2004 Remove Edge
Going forward, it’s pretty clear that this Chromium version of Edge is the chosen one for Windows 10, so sooner or later, the legacy version of the browser should just get the ax and go away from Windows. No ETA has been provided, however, as to when the switch is supposed to happen.