Edge and Chrome do not allow user to manually install an extension outside the Edge/Chrome Web Store by default. This article will introduce how to deploy a self-hosting Edge/Chrome extension to Microsoft Edge browser including allowing user to manually install an external extension and forcing an external extension to be installed silently in Edge.
I handled many Edge crash issues in my work. Most of them were caused by third-party modules where Edge failed to launch at the beginning. Some of them happened in both Edge and Chrome, some of them only happened in Edge. I have only seen one Edge/Chrome crash case which was caused by a bug of Blink (The rendering engine of Chromium). I am writing this article to summarize the actions to take to rule out an Edge crash issue that is caused by a third-party module.
This article lists some command-line flags I used to troubleshoot Edge/Chrome issues. I will keep updating this page as long as I support Microsoft Edge.
The Windows 10 version 20H2 release automatically includes the new Chromium-based Microsoft Edge browser instead of the legacy version of Edge. This article provides general information about Edge on Windows 10 version 20H2.
Symptom: Edge failed to start and browse any webpage, it always showed: "That's odd... something stopped working, so this page can't load." The detailed error message was: Unable to create content process", error code was: 0x8027025b. The root cause was: "ALL RESTRICTED APPLICATION PACKAGES" permission was missing on system folder:
C:\Windows\System32 and "S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681" permission was missing on
HKEY_LOCAL_MACHINE\Software. This article will show you how to fix this issue by adding back the right permissions.