-->
APPLIES TO: 2013 2016 2019 SharePoint in Microsoft 365
SharePoint Servers 2016 and 2019 supports several commonly used web browsers, such as Internet Explorer, Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge. However, certain web browsers can cause some SharePoint Servers 2016 or 2019 functionality to be downgraded, limited, or available only through alternative steps.
If you decide, as usual, to get the version of Edge that Microsoft designates as current, you will receive the following message when installing it under Windows Server 2019 Core: Microsoft Edge works best with the latest Windows Updates. Once you download updates and restart your device, rerun the installer. Download and deploy Microsoft Edge for business. Get the latest Microsoft Edge update for your business, school, or organization with multi-platform support in over 90 languages. The Windows platform downloads apply to all supported client and server releases of Windows. Learn more about supported Windows releases. Microsoft Seriously Beefs Up Security in Windows Server 2019. It looks like the latest version of Microsoft's venerable Windows Server operating system has upped its game in the security department. SharePoint Server 2016 supports the following versions: Internet Explorer and Microsoft Edge on Windows Phone 8.1 or later. Latest version of Chrome on Android 4.4 or later. Latest versions of Safari and Chrome on iOS 8 or later. For SharePoint Server 2019, Chrome or Safari on iOS10 or later.
As you plan your deployment of SharePoint Servers 2016 or 2019, we recommend that you review the browsers used in your organization to guarantee optimal performance with SharePoint Servers 2016 and 2019.
Key planning phase of browser support
Browser support is an important part of your SharePoint Servers 2016 or 2019 implementation. Before you install SharePoint Server, make sure that you know the browsers that SharePoint Server supports. The information in this article describes browser support in the following sections:
Browser support levels
Browser details
Browser support levels in SharePoint Server 2016
The following table summarizes the support levels of typically used web browsers.
| Browser | Supported | Not supported |
|---|---|---|
| Microsoft Edge (Chromium) | X | |
| Microsoft Edge (EdgeHTML - Legacy) | X | |
| Internet Explorer 11 | X | |
| Internet Explorer 10 | X | |
| Internet Explorer 9 | X | |
| Internet Explorer 8 | X | |
| Internet Explorer 7 | X | |
| Internet Explorer 6 | X | |
| Google Chrome (latest released version) | X | |
| Mozilla Firefox (latest released version plus immediate previous version) | X | |
| Apple Safari (latest released version) | X |
Browser support levels in SharePoint Server 2019
The following table summarizes the support levels of typically used web browsers.
| Browser | Supported | Not supported |
|---|---|---|
| Microsoft Edge (Chromium) | X | |
| Microsoft Edge (EdgeHTML - Legacy) | X | |
| Internet Explorer 11 | X | |
| Internet Explorer 10 | X | |
| Internet Explorer 9 | X | |
| Internet Explorer 8 | X | |
| Internet Explorer 7 | X | |
| Internet Explorer 6 | X | |
| Google Chrome (latest released version) | X | |
| Mozilla Firefox (latest released version plus immediate previous version) | X | |
| Apple Safari (latest released version) | X |
Browser details
Review the details of the web browser that you have or plan to use in your organization to make sure that the web browser works with SharePoint Server 2016 and 2019, and according to your business needs.
Internet Explorer and older functionality
Note
Some older SharePoint functionality that relies on NPAPI or ActiveX will not work on browsers other than Internet Explorer. You can work around each of these issues by using Internet Explorer to perform these tasks.
Using ActiveX controls in SharePoint Server
Some functionality in SharePoint Server requires ActiveX controls. This produces limitations on browsers which do not support ActiveX. Currently only 32-bit versions of Internet Explorer support this functionality. In SharePoint Server 2016, all other supported browsers, including Microsoft Edge and the Immersive mode of Internet Explorer 10 have the following limitations.
For SharePoint Server 2016 and 2019, browsers other than Internet Explorer 11 have the following limitations.
| Plugin name | DLL file name | What it does | Known limitations | |
| Digital Signature | Dsigctrl.dll, dsigres.dll | Digital signing takes place in both the InfoPath client and on the InfoPath Forms Services server. Make sure that the following conditions exist: Forms that are signed on the client can be verified on the server. Forms that are signed on the server can be verified on the client. | An inability to verify a form produces an error that states that the form cannot be signed. | |
| NameCtrl | Name.dll | Enables a webpage to display a contact card and presence status for people. Integrates through client-side APIs with Office client and Skype for Business client. | ||
| TaskLauncher | Nameext.dll | Used to export items in a task list to Project Server if Project client is installed on the client computer. | If software requirements are not met, an error message states that you need to install Project client. | |
| SpreadSheetLauncher | Owssupp.dll | Used to verify whether Excel is installed for Export to Excel feature. | If Excel is not installed, the user may be prompted to download the file 'query.iqy' which can then be opened in Excel. | |
| StssyncHandler | Owssupp.dll | Enables synchronization of lists of events and lists of contacts in SharePoint with a messaging application such as Outlook. Non-IE clients may have an additional prompt to open the calendar in Outlook. | ||
| ExportDatabase | Owssupp.dll | Enables a user to use an application such as Access to create or open a database that contains SharePoint list data. | To export a list, the client computer must have a SharePoint compatible application. | |
| OpenDocuments | Owssupp.dll | Starts Office client applications so that a user can create a or edit a document. Enables users to create documents that are based on a specified template, open documents as read-only, or open documents as read/write. | If a compatible Office application or browser is not installed on a client, an error message states that the feature requires a SharePoint compatible application and web browser. | |
| CopyCtl | Stsupld.dll | Enables a user to copy a document on a SharePoint site to one or more locations on a server. | In Firefox, Google Chrome, and immersive mode of Internet Explorer version 10, the copy progress dialog is not displayed. | |
| PPActiveX | PPSLAX.dll | Starts PowerPoint to open presentations from a slide library or publish individual slides to a slide library. | Does not work on Click-to-Run installations of Office and version of Office that run on Windows for ARM. | |
| BCSLauncher | BCSLaunch.dll | Starts the Visual Studio Tools for Office installer to install a Visual Studio Tools for Office package that has been generated on the server. |
Other functionality, such as Form settings in List settings only function with Internet Explorer.
Mobile browser support
SharePoint Server 2016 supports the following versions:
Internet Explorer and Microsoft Edge on Windows Phone 8.1 or later.
Latest version of Chrome on Android 4.4 or later.
Latest versions of Safari and Chrome on iOS 8 or later.
For SharePoint Server 2019, Chrome or Safari on iOS10 or later How to gent adobe pro full version for mac free.
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).
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 > |
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 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
Edge Browser For Server 2016
Microsoft Edge missing after using custom media/ISOs including March 29, 2021 updates | ||
| Status | Originating update | History |
| Resolved | OS 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:
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. | ||
Microsoft Edge Chromium Download Windows Server 2019
Install Ms Edge On Windows Server 2019
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. | ||