This page is having a problem, Error code: STATUS_INVALID_IMAGE_HASH

Anonymous
2020-07-15T21:11:04+00:00

Split from this thread.

I am having the same issue except nothing happens when I click on settings.  I get this screen (attached) and nothing else.  So frustrating, I just want to get my work down and after this updated last night I'm stuck.  I need to use Edge, not Chrome.  Please help.

Microsoft Edge | Browser crashes or stops working | Windows 10

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes
Answer accepted by question author
  1. Anonymous
    2020-07-15T21:10:13+00:00

    This is a well-known issue on some systems resulting from a change in security measures within Chromium. Eric Lawrence, a senior PM on the Edge team, has explained it in detail in a blog post, where he also explains how to deal with it. See here:

    https://textslashplain.com/2019/09/27/aw-snap-every-tab-crashes/

    tl;dr

    Security software (e.g. anti-virus) is the most likely cause. of this error. Update any third-party security software you have to the latest version.

    0 comments No comments

5 additional answers

Sort by: Most helpful
  1. Anonymous
    2020-07-17T22:18:04+00:00

    I appreciate your help, however I did as suggested and temporarily launched Edge without the sandbox feature, but I still got the same window as shown above.  I then "searched for the culprit" by using chrome://conflicts#R and saw only two things that were not signed by MS or Google, and those were Symantec and Critrix.  Neither of which had a single "R" in the process type, they had "BR", just as all of the other process types.  Because it listed Citrix and Symantec, I made sure that Citrix was not running and I verified that Symantec is updated, restarted the computer and tried to open the browser again, and I STILL received the same message as in the screen shot above.  I then went on to the next option listed and checked the event log.  I found a lot of events with the 3033 ID but the instructions don't tell you want to do with that knowledge, it just moves on to... "Optional: Use Enterprise Policy to disable the new protection", which is way over my ability (unless you have an easy way to do that) as it starts with "IT Administrators can disable the new protection" using the RendererCodeIntegrity policy for Chrome and Edge.  It says I should "outreach my software vendor responsible for the problematic applications and request that they update them." Seriously? The way I see it, my old version of Edge and my current Chrome worked/work fine so this is not something I should have to go to Citrix or Symantec about (if they are indeed the problem).  Lastly, the final option was "other possible causes" and talks about an "obscure bug" but doesn't offer any way to overcome the issue, if that is the issue. 

    I'm really very angry about this.  I'm teleworking due to Covid and I need Edge (the old Edge) to run, I use GO Virtual/Citrix and it works best from Edge.  I was able to get the new Edge to open by selecting compatibility mode, but I have to do it every time, EVERY TIME I open Edge, surely this isn't how it's going to be from now on. 

    Ugh, fed up!  Thinking about all my friends that swear by their Mac systems.  :-/

    I've had to do so much homework searching through forums to find a way to fix this and I keep seeing that people are not getting the problem solved. 

    So so so angry (and I'm not generally an angry person).

    0 comments No comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Anonymous
    2020-07-18T08:17:14+00:00

    I found a lot of events with the 3033 ID but the instructions don't tell you want to do with that knowledge, 

    What is the name and version of the Symantec and Citrix applications you have installed?

    Please check those ID 3033 events again. If you select one in the upper pane, the Details pane will tell you which DLL file it was that was trying to insinuate itself into the browser. Look particularly for events dated both before and after you updated the Symantec software. 

    You could take the risky course of disabling this layer of protection, but only until you've tracked down the specific cause and eliminated it. If you want to do this, say so and I'll post instructions. 

    Thinking about all my friends that swear by their Mac systems.  :-/

    Macs have a similar system, so it's not unlikely that Mac users would face similar problems in similar situations.

    [I've been trying to think of an analogy to explain what's happening.  This is the best I could come up with, using a topical theme:

    Imagine a hospital intensive care unit. In the midst of an epidemic, the hospital's owners decide to impose a new mandatory safety measure to prevent infection: everyone - doctors, nurses, porters, cleaning and maintenance staff - seeking to enter the unit has to have been health-tested and carry a special badge issued by the owners to say so.

    Maintenance of specialist equipment is contracted out to another company. Along comes an older engineer from the contractor to check the equipment. He has been tested, but his employer hasn't issued him with one of the new badges. When he tries to enter the ICU, klaxons blare and the doors are locked shut.

    The engineer poses no risk (because he's clean);  the problem only arises because the contractor failed to follow the hospital's instructions about getting badged and the fail-safe protection measures kick in.

    Hospital owners - Microsoft

    Hospital - Edge

    ICU - browser renderer

    Contractor - Symantec

    Engineer - Old Symantec DLL

    Badge - Microsoft certificate

    I clearly have too much time on my hands ...]

    0 comments No comments
  4. Anonymous
    2020-07-18T11:17:45+00:00

    You could take the risky course of disabling this layer of protection, but only until you've tracked down the specific cause and eliminated it. If you want to do this, say so and I'll post instructions. 

    I'll post them anyway, in case anyone wants to try this at their own risk:

    1. Close down all Edge windows.
    2. Copy the black line:

    reg add HKLM\SOFTWARE\Policies\Microsoft\Edge /v RendererCodeIntegrityEnabled /t REG_DWORD /d 0 3. Press Windows key + R to open a Run box, type cmd into the box and press Ctrl-Shift-Enter to open an administrator command window. Give UAC permission when asked. 4. Press Ctrl-V to paste into the window and press Enter.

    You should see The operation completed successfully. 5. Close the command window, launch Edge and test.

    To reverse the change, do exactly the same again, but at step 2 use this black line:

    reg add HKLM\SOFTWARE\Policies\Microsoft\Edge /v RendererCodeIntegrityEnabled /t REG_DWORD /d 1


    You will be asked whether you want to override. Type y to say Yes.

    0 comments No comments