Microsoft Edge Windows Server 2019



  1. Edge Browser For Server 2016
-->

Find information on known issues and the status of the rollout for Windows 10, version 20H2 and Windows Server, version 20H2. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s).

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 19042.906 KB50-03-29: Resolved: 2021-03-29 17:01 PT. Dell only sells Windows installation media when ordered with a system. If you want to reinstall a Windows Server OS on your PowerEdge server, but you lost your original Windows Installation-DVD, you can download the matching ISO-file directly from Microsoft (after registration). Then we could delete Google Chrome in our environment, if Microsoft Edge will be supported on Server OS. In our Citrix environment we are still using Server 2008 R2, but we are getting ready to get on Server 2016 instead (hopefully Server 2019 if Citrix will support it soon). So I would like to see Microsoft Edge on those Server OS.

Windows
Windows 10, version 20H2 is available for users with devices running Windows 10, who manually seek to “Check for updates” via Windows Update. We have started 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 that are approaching end of service to update automatically to Windows 10, version 20H2. 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 We are slowly throttling up availability over the coming weeks to ensure a reliable download experience. As a result, the update may not be offered to you right away. For more details, see How to get the Windows 10 October 2020 Update.
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 >
Microsoft Edge Windows Server 2019

Known issues

This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

SummaryOriginating updateStatusLast 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 19042.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

Microsoft Edge Windows Server 2019

Microsoft Edge missing after using custom media/ISOs including March 29, 2021 updates

StatusOriginating updateHistory
ResolvedOS Build 19042.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:
  • Client: Windows 10, version 20H2; Windows 10, version 2004
  • Server: Windows Server, version 20H2; Windows Server, version 2004
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:
  1. Extract the cab from the msu via this command line (using the package for KB5000842 as an example): expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab <destination path>
  2. Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* <destination path>
  3. You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU.

December 2020

Automatic input of Furigana might not work as expected

StatusOriginating updateHistory
MitigatedN/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:
  • Client: Windows 10, version 20H2; Windows 10, version 2004
  • Server: Windows Server, version 20H2; Windows Server, version 2004
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

StatusOriginating updateHistory
ConfirmedN/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:
  • Client: Windows 10, version 20H2, Windows 10, version 2004
  • Server: Windows Server, version 20H2, Windows Server, version 2004
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

StatusOriginating updateHistory
ConfirmedN/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:
  • Client: Windows 10, version 20H2, Windows 10, version 2004
  • Server: Windows Server, version 20H2, Windows Server, version 2004
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.
Install edge browser server 2016Microsoft edge windows server 2019

Edge Browser For Server 2016