latguide.blogg.se - Uninstall microsoft edge windows 10 20h2

UNINSTALL MICROSOFT EDGE WINDOWS 10 20H2 HOW TO
UNINSTALL MICROSOFT EDGE WINDOWS 10 20H2 UPDATE
UNINSTALL MICROSOFT EDGE WINDOWS 10 20H2 FOR WINDOWS 10

Launch Internet Explorer, click Tools, Internet Options.

Method 2: Disable third-party browser extensions in Internet Explorer HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Edge\IEToEdgeĭata : 0 (Never), or 1 (Incompatible sites only), or 2 (Always) The following key is where the above setting is stored: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Edge\IEToEdge You can also configure this in the registry. Set “Let Internet Explorer open sites in Microsoft Edge” to “Never.” Or, launch the URL edge://settings/defaultbrowser from the address bar. Start Microsoft Edge, open Settings, and select the “Default browser” tab. Follow one of these methods: Method 1: Microsoft Edge Settings There are several methods to stop Internet Explorer from redirecting you to Edge. Disable Auto redirection of unsupported sites to Edge

UNINSTALL MICROSOFT EDGE WINDOWS 10 20H2 HOW TO

This article explains how to disable the automatic redirection of unsupported sites in Internet Explorer to Microsoft Edge Chromium. The dialog also allows the user to import the browsing data, cookies, bookmarks, preferences, etc., from IE to Microsoft Edge. On redirection to Microsoft Edge, the user is shown why the website is being redirected. Microsoft also maintains a compatibility list of websites for this purpose. To make this switch possible, Edge installs a Browser Helper Object (BHO) that hooks into Internet Explorer. Starting with Microsoft Edge version 84, Microsoft Edge supports this new capability that automatically redirects users from Internet Explorer. When the Internet Explorer user visits an unsupported website (e.g., Facebook, Internet Archive, etc.), the user may get a message stating the website is incompatible with Internet Explorer. In the case where you would want to adjust the whitelist defined in the script, for various reasons, use the sample script below for AppX provisioning packages that will be removed by default when running this script using the embedded list.Many modern websites have designs that are incompatible with Internet Explorer. Manually validate what will be removed by the script

UNINSTALL MICROSOFT EDGE WINDOWS 10 20H2 UPDATE

Create a PowerShell Script object, point towards the script and ensure it’s running in a 64-bit process in the System context, similar to the following configuration: What’s removed from the device after running this scriptĪs for built-in appx provisioning packages, here’s the list of apps that will be removed:Īnd for the Feature on Demand V2 packages, these will be removed:Īs always, you can update the $WhiteListOnDemand and $WhiteListedApps variables to include more apps, ensuring they’re kept on the device, or of course remove entries from both if you think the already added apps does not fit in your environment.

UNINSTALL MICROSOFT EDGE WINDOWS 10 20H2 FOR WINDOWS 10

Remove Built-in apps for Windows 10 version 1903 – MSEndpointMgrĪs for Windows Autopilot and Intune, I’ve not written any posts as of yet, however the instructions are extremely simply. Remove Built-in apps when creating a Windows 10 reference image – MSEndpointMgr ConfigMgr, see the following posts for implementation guidance: Notepad|MSPaint|PowerShell.ISE|ShellComponentsĪs for using the script when creating a reference image for e.g.

Windows 10 version 20H2: Added to the white list, but also extended the Feature on Demand V2 white list to include the following packages:.

Windows 10 version 2004 (20H1): Added Microsoft.VCLibs.140.00 to the white list.

I’ve made the script available on our GitHub repository along with all the other scripts that we’ve shared, and it’s available on the following URL: This script also works for when provisioning new devices using Windows Autopilot for devices to be managed with Microsoft Intune. Recently however, Windows Autopilot has increased in popularity. Originally, this method was developed for when creating a reference image here, as shown in the blog post below. Up until now though, I’ve been behind on keeping it up-to-date, but rest assured, here’s the latest version that now supports Windows 10 version 20H2 and below. During this time, I’ve attempted to keep my script updated after each new release of Windows 10. Over the years, the community has provided several solutions on how to accomplish this including myself. Since the release of Windows 10, it has been common for organization to try and reduce the footprint of built-in apps (or default apps) in their reference images, or even during bare-metal deployment.