Forum Discussion
Dev channel update to 81.0.381.0 is live
josh_bodner Unfortunately this new version is broken on my laptop... It opens full white, no UI elements. After a minute the UI is visible again, but no pages can be browsed, including internal pages like edge://settings, the browser always returns STATUS_ACCESS_VIOLATION error code.
I had to revert to the beta.
samuele2 In the absence of a Safe Mode option, try this:
Go to your Edge profile folder "User Data", rename it to anything else. The path is C:\Users\Your User Name\AppData\Local\Microsoft\Edge Dev. Start Edge Dev. This time it should not crash. Close it again. Rename the profile folder that was created by this successful startup to something else. Rename the original folder with your old profile back to the original name (User Data). Start the browser again. In case this still doesn't work, delete this folder and rename the recently created successful startup folder back to User Data and start Dev. You will have a brand new Edge, but you will have lost any customisations, Sync settings, Extensions, etc. You will have to recreate these.
Let me know if it works
Hi Dave. I tried the non-safe mode process you advised for @samuele2 and this made no difference. I confirmed Edge had no processes running, renamed the profile, ran Edge again and then nothing happened except for multiple processes starting in Task Manager. After a few minutes, I ended the processes and ran Edge again. This time it displayed the UI with an Edge closed unexpectedly dialog, still had white browser pages with "This page is having a problem". We can't even get into the Help -> about or Settings pages.
michaelgibson Thanks Michael, it was worth a shot. Put it down to experience 😊
Seeing the same issue. Dev (81.0.381.0) and Canary (81.0.387.0) is broken. Beta (79.0.309.60) works.
I'm also receiving STATUS_ACCESS_VIOLATION. From Event Viewer, I see the following:
Faulting application name: msedge.exe, version: 81.0.381.0, time stamp: 0x5e0eac60
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000001d7fe2
Faulting process id: 0x4630
Faulting application start time: 0x01d5c702a60d0ed2
Faulting application path: C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge.exe
Faulting module path: unknown
Report Id: 001aab9f-8642-4513-a4da-d6e0fcdc29bc
Faulting package full name:
Faulting package-relative application ID:C-los I too am experiencing this STATUS_ACCESS_VIOLATION error. When you roll back, are settings retained including collections?
- Spoiler
Steven Sanders wrote:I too am experiencing this STATUS_ACCESS_VIOLATION error. When you roll back, are settings retained including collections?
You can manually backup your collection.
all you have to do is copy this file and keep it in a safe location, then copy it back to the same place once you're done reinstalling your Edge browser.
it's an unencrypted .json file
located in: "\User Data\Default\Collections\collections.json"
to find the location of \User Data\
simply paste this into your browser address bar: edge://version/
and look for the "Profile path" parameter.
- Spoiler
C-los wrote:I'm also receiving STATUS_ACCESS_VIOLATION. From Event Viewer, I see the following:
Faulting application name: msedge.exe, version: 81.0.381.0, time stamp: 0x5e0eac60
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000001d7fe2
Faulting process id: 0x4630
Faulting application start time: 0x01d5c702a60d0ed2
Faulting application path: C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge.exe
Faulting module path: unknown
Report Id: 001aab9f-8642-4513-a4da-d6e0fcdc29bc
Faulting package full name:
Faulting package-relative application ID:HiC-los
It could be related to DEP, not 100% sure
You can try turning it off to see if it changes anything
https://www.minitool.com/data-recovery/dep-data-execution-prevention-windows-10.html
