Apr 13 2019 01:39 PM
Apr 14 2019 06:11 AM
Apr 16 2019 10:57 PM
Apr 16 2019 11:02 PM
Apr 23 2019 05:47 AM
do you log in as "Administrator" ? change it
Apr 23 2019 01:30 PM
@vineydhiman Edge Classic cannot be launched with administrative privileges, period. Edge Chromium can be launched with administrative privileges, and that is dangerous, despite the warning.
Edge Chromium typically launches in Administrator mode because another program with administrative privileges (usually an e-mail program) contains a link that launches the browser with inherited privileges from the other program. The warning is a good thing (Chrome doesn't warn users, which is dangerous), but setting Edge Chromum up like Edge Classic so that it cannot be launched with administrative privileges would be a much, much better solution.
Edge Classic uses a distinct kernel, as I understand it, effectively sandboxing the browser. That is a basic, but important, security feature. I assume that making Edge Chromium similarly secure is on the development list. If it isn't, it should be.
Jun 13 2019 01:04 PM
This is an odd one. On my laptop I am an administrator. I never get that pop up. When I was building a laptop and installed Edge DEV and ran is as my Domain admin user I then get the message.
In both cases the user I am logging in with is a member of the local admin group. Not sure what the difference is.
Jun 13 2019 03:26 PM
I would like to know if your are still receiving this issue?
The top workarounds that are used:
Some accounts that are limited because of their Domain settings, should have more options when/if enterprise channel is released.
Thanks,
Frank
Jul 09 2019 09:15 AM
@vineydhiman I understand why the message pops up, however as I am debugging a website using Visual Studio (attached to IIS) I need the admin mode. Is there any way to disable the warning? It's irritating, although I could just use Chrome as the debugging browser... I'd rather not
Jul 09 2019 12:50 PM
Jul 22 2019 05:45 PM
Are you still receiving the Administrator Error?
You could try the enterprise Dev channel and see if you can change admin policy.
https://www.microsoftedgeinsider.com/en-us/enterprise
Thanks,
Frank