Forum Discussion
Dev channel update to 81.0.381.0 is live
josh_bodner Edge was working great until this last update. I use it here at work. However now it will not work at all. I can't get any pages to open, not even the settings page. The error I get is "This page is having a problem" STATUS_ACCESS_VIOLATION. I have uninstalled, rebooted, reinstalled....Nothing. Tried running with elevated rights with the same result. (using on Win10 Enterprise, 1809)
Dale_Wrobel
Hi Dale,
Update your Win10 to 1909 then, try again with Dev & see what results you have. There was another similar instance, recently and they were ok after I had suggested they bring the OS up to current. Anxious to have a progress report from you soon on this.
Cheers,
Drew
- michaelgibsonJan 10, 2020Copper Contributor
Drew1903 I can confirm we have multiple instance of this breaking immediately after the latest release and we are all on 1909.
- Drew1903Jan 10, 2020Silver ContributorI get that, Michael. Just pointing out that the behavior is not hitting everyone. That, too, is good info for the Team.
Cheers,
Drew
Sent from Windows Mobile- HotCakeXJan 10, 2020MVPSpoiler
Drew1903 wrote:
Just pointing out that the behavior is not hitting everyone. That, too, is good info for the Team.To be honest, I don't see how it's useful/helpful to say you don't have a problem.
in this thread alone, you've said more than 3 times that you don't have a bug or problem, right after someone says they have a problem or bug.
it feels like when we say we are experiencing a problem. we are lying.
imagine if everyone came here and said they don't have problem.
so like:
"person1: I don't have problem.
person2: I don't have problem.
person 3: I don't have problem.
.
.
"
soon the thread would be filled with hundreds of posts that are just not doing anything.
the default expected thing is that everyone has no problem and so they work with their browser or software normally, but when there is a problem, it should be mentioned and we all help to fix it.
Sent from Android mobile
- HotCakeXJan 09, 2020MVPSpoiler
Drew1903 wrote:Update your Win10 to 1909 then, try again with Dev & see what results you have. There was another similar instance, recently and they were ok after I had suggested they bring the OS up to current. Anxious to have a progress report from you soon on this.
Windows 10 1903 still has a Long way to go before it is no longer supported. the only version of Windows people better upgrade from is Windows 7..
- HotCakeXJan 09, 2020MVPSo clearly not Windows 10 related..
- Dale_WrobelJan 09, 2020Copper ContributorWe are not able to upgrade to that version of windows 10 in our environment yet. The highest I could go is 1903.
- Drew1903Jan 09, 2020Silver Contributor
Dale_Wrobel
Ok, understood.
Cheers,
Drew - Dale_WrobelJan 09, 2020Copper ContributorWell, my test machine is 1903 and it has the same issue. Something else is going on here.
- Drew1903Jan 09, 2020Silver Contributor
Dale_Wrobel
Oh, yes, indeed there is. Firewalls of some sort, maybe? But, suddenly with this Build is the odd part. Maybe, Josh will have a helpful thought.
Cheers,
Drew