The number of browsers having the underlying Chromium Source code is constantly on the rise. And there are no complaints from the user either, as they are getting all the Chrome goodies but without limiting themselves to the resource-hungry Chrome browser.
However, there was always a concern looming around- if a significant issue gets into this source code, then all the browsers might get bugged at the same time. And this is what seems to be going on for a few months.
The complaints started pouring in from the Chrome users regarding the STATUS_ACCESS_VIOLATION error.
Then it was only a matter of time before other Chromium browsers joined in this list of affected browsers. Unfortunately, the Microsoft Edge chromium-browser soon became a part of this issue as well. Many users voiced their concern to the Microsoft Tech Community forum regarding this issue, but without much success.
However, there do exist a few workarounds that have been known to fix this Microsoft’s Edge STATUS_ACCESS_VIOLATION error. And this guide shall make you aware of just that. So without further ado, let’s get started.
Disable Renderer Code Integrity
Google recently enabled the Renderer Code Integrity, which was quickly adopted by other Chromium browsers as well. This integrity is responsible for two things- to verify all the codes that the webpage loads and allow only the signed ones to go ahead.
However, in some instances, it could raise a false positive and block the rendering of codes from a trustworthy site. So if you think that same is the case right now, then consider disabling Renderer Code Integrity.
Here are the steps to disable the renderer code integrity in the Edge browser:
- Select the Microsoft Edge’s desktop shortcut link.
- Right-click for the context menu and select Properties.
- Switch to the Shortcut tab, and add the below string at the end of the existing Target field:
- Your target field should now look something along the lines of:
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" – disable-features=RendererCodeIntegrity
- Click on and then .
- Launch the browser using this shortcut.
Now try loading the page you have an access violation issue. Disabling code integrity might have fixed the problem.
Alternatively, if you wish to carry out this task manually using Registry Editor, you can follow these steps:
- Launch Registry Editor in Windows OS,
- Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge location.
- Create a new DWORD (32-Bit) Value.
- Name the file RendererCodeIntegrityEnabled and assign it a 0 Value data.
- Hit on the command button to save.
Disabling Renderer Code Integrity could prove to be a little bit risky because you are turning off an important security feature. So while this feature is disabled, make sure you don’t visit any non-secure sites, such as those who are still following HTTP or the ones that don’t have a valid SSL Certificate.
Rename’s Edge Executable File
Some users could spell out success by assigning a random name to the Edge’s EXE file.
Here are the steps to locate and rename the MS Edge executable file:
- Launch File Explorer on your Windows PC and go to the below location:
C:\Program Files (x86)\Microsoft\Edge\Application
- Select the msedge.exe file.
- Right-click on the file and select Rename from the context menu.
- Rename something else, such as edge.exe, and save the changes.
Now launch Microsoft Edge using this EXE file and check if it fixes the STATUS_ACCESS_VIOLATION error
Switch to Edge Beta
Apart from the stable version that you might be currently using, Microsoft also runs a Beta build. BETA is mainly used for testing experimental features, but at the same time, it might not get bugged with issues that the stable build seems to go through.
In this regard, some users were able to rectify the STATUS_ACCESS_VIOLATION error after making a switch to Microsoft Edge’s Beta build. To try it out, download and install the Edge’s Beta Channel onto your Windows PC.
Launch Edge browser, sign in to your account (optional) and try accessing the page. See if it can fix the underlying issue.
If you are using a third-party extension that deals with scripts, you recommend that you disable them right away.
While extensions part of this domain allow you to add and modify web pages, they seem to be the root cause of this issue. So it would be best if you considered disabling them as of now.
- Launch Microsoft Edge computer browser.
- Click on the More for menu options.
- Select the Extensions menu from the list.
- Disable the toggle next to the extension that deals with scripts.
- Restart the Edge browser and see if this tweak worked out for you.
So it’s better to stay away from these extensions for quite some time until the patch is deployed in Edge chromium update.
Bottom Line: Edge Status Acess Violation
With that, we conclude the guide on how you could fix Microsoft Edge’s STATUS_ACCESS_VIOLATION error. We have shared four different methods, any one of which should work out in your favor.
For me, disabling the Renderer Code Integrity turned out to be the savior. However, since keeping it disabled could prove to be a risky bet, make sure to turn it back on as soon as you are done working with the concerned site.
On that note, we round off this tutorial. Do let us know in the comments section which method managed to fix the issue with Microsoft Edge. Also, please share if anything else you’ve tried and worked on improving the STATUS ACCESS VIOLATION issue.