Forum Discussion
josh_bodner
Microsoft
MicrosoftDev channel update to 81.0.381.0 is live
Welcome to the new year! Today we’re releasing build 81.0.381.0 to the Dev Channel, which as you can see is the first new build from major version 81. We haven’t been completely asleep during the h...
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.
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.
Steven Sanders I wasnt able to rollback
Steven Sanders I am also getting Error code: STATUS_ACCESS_VIOLATION
This is on dev and canary. Beta works ok. My Edge Dev was working fine last night until 10:30 EST.
Also tried reinstalling dev, but no dice 😞
k1ck3rtw I am also seeing Error code: STATUS_ACCESS_VIOLATION, after the upgrade.
Beta version works perfectly.
- 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
HotCakeX I tried turning off DEP following the instructions in the links you provided. It did not fix the issues I am seeing. Thanks for the response and information,
David Hurst wrote:HotCakeX I tried turning off DEP following the instructions in the links you provided. It did not fix the issues I am seeing. Thanks for the response and information,
Yw, well hope we don't have to wait for the next week for this problem to get fixed
