There was a known issue where Symantec would cause Chrome and Edge to crash with error code: STATUS_INVALID_IMAGE_HASH, details can be found at: Google Chrome/Microsoft Edge Chromium version 78.0.x and 79.0.x error "Aw, Snap! Something went wrong while displaying this webpage." when using Endpoint Protection, disabling Renderer code integrity was a workaround. ![]() Renderer code integrity is enabled by default, but in some case it may cause Edge to crash. disable-features RendererCodeIntegrity msedge.exe -disable-features=RendererCodeIntegrity -winhttp-proxy-resolver command line switch.Instructs Edge/Chrome to use the system libraries for one narrow part of proxy resolution: evaluating a given PAC script or auto detecting WPAD. Elevated Browsing (As Administrator) for more details. If this feature is disabled (-do-not-de-elevate), Edge will show a warning to help users recognize the unexpected situation: Microsoft Edge will attempt to silently deelevate and relaunch itself when launched as an Administrator, running at Medium IL instead of High. This command-line flag overrides the User Data Directory, see User Data Directory for more details. user-data-dir msedge.exe -user-data-dir=c:\temp\NewEdgeUser ![]() ![]() I will keep updating this page as long as I support Microsoft Edge. This article lists some command-line flags I used to troubleshoot Edge/Chrome issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |