Windows 10 Edge can’t be opened using the built-in administrator account


With the release of Windows 10 today, many are spinning up VMs and loading the new workstation on test boxes to take a look at the final build version.  If you are like me, one of the first things I wanted to test drive was the final release build of the Edge browswer.  Quickly however, I ran into an issue (security feature) out of the box with the built-in administrator account attempting to launch Edge.  I received the error Microsoft Edge can’t be opened using the Built-in Administrator account.  Sign in with a different account and try again.

edge_admin1a-300x82 Windows 10 Edge can't be opened using the built-in administrator account


Microsoft has went the direction of making the Edge browser a true app now and additional security is in place much like the Internet Explorer Enhanced Security that we have grown to love and hate.

In order to get around this message in your test environment and be able to use your Built-in Administrator account to navigate Edge, follow the following steps to get up and running.

  • Navigate to your local security policy on your Windows 10 workstation – You can do this by typing secpol.msc at a search/run/command prompt.
  • Under Local Policies/Security Options navigate to “User Account Control Admin Approval Mode for the Built-in Administrator account
  • Set the policy to Enabled

edge_admin1-300x81 Windows 10 Edge can't be opened using the built-in administrator account
edge_admin2-249x300 Windows 10 Edge can't be opened using the built-in administrator account


***Updated for Windows 10 Home Users***

For Windows 10 Home users, the local security policy editor doesn’t exist.  However, most of the policy changes that can be made using the policy editor can also be made using the registry.  I have not tested this on a Windows 10 Home system, however, changing this registry key should be the equivalent to enabling the policy above – See the UAC registry guide from Microsoft  Navigate to the following registry key:


  • Create a DWORD value if it doesn’t already exist called FilterAdministratorToken
  • Set the value to 1

Next we need to navigate to the registry and make an additional change:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\UIPI\
  • Change the Default string key to 0x00000001(1)

edge_admin3-300x88 Windows 10 Edge can't be opened using the built-in administrator account
edge_admin4-300x189 Windows 10 Edge can't be opened using the built-in administrator account

Also, in addition to the above, make sure your User Account Control Setting is set to the third level from the bottom.  To get to UAC, go to your Windows 10 search and type uac.  It should come up as “Change User Account Control Settings“.

win10uac01-300x222 Windows 10 Edge can't be opened using the built-in administrator account


Finally, restart Windows and then you will be able to enjoy Edge under your Built-in Administrator account.


  • Ralphster

    Hello and thanks for the guide! Would you happen to have a workaround for Windows 10 Home which is lacking secpol.msc

    • Ralphster,

      I haven’t tested this as of yet as I don’t have a copy of Windows 10 Home, however, the post has been updated with how to enable the value the policy editor is enabling by way of the registry instead. Let me know your findings.

      • Ralphster

        Hi, I can confirm that your windows 10 home instructions worked! For reference on my installation the FilterAdministratorToken DWORD value already existed but with the value set to 0 by default. Thank you very much!

      • disqus_0am4a3o17z

        It did not work for me 🙁

  • thankachan_smith

    Yeah.It worked!!. Thanks you very much Brandon 🙂

  • confed2001

    ScumSoft….what a bunch of F’ing A-Holes!!!!!

  • juan

    Hello. Whan security problems can cause this?

  • jayinatlanta

    Thanks a ton. Edge is a vital piece of the OS, so disallowing Edge for the built-in admin was blocking new accounts from being added. When I followed your registry instructions to the letter on this corrupted Win 10 Home installation, I was able to add the correct Microsoft account back with no problems.

  • H B Bergman

    Hello. I did not work for me. Windows 10 Home. Registry Keys
    change is simple. Check and rechecked. Reinstalled Apps through PowerShell and
    rechecked registry key and still no go. I do not know what to try next.

  • Ph Ahmed

    sorry but It didn’t work with my windows 10 version (Microsoft Windows [Version 10.0.10240])

  • Dan Stevenson

    Thanks for the detailed instructions but it seems to me like Microsoft’s logic is flawed going by their own description of the Admin Approval Mode setting:

    Enabled. The built-in Administrator account uses Admin Approval Mode. By default, any operation that requires elevation of privilege will prompt the user to approve the operation.

    Disabled. (Default) The built-in Administrator account runs all applications with full administrative privilege.

    If this is set to disabled it should allow me to run ALL programs AND apps under the built in administrator account. When I set it to enabled it did indeed allow me to run the Edge browser and the store app but it broke my network login script. I have a script that pushes out Windows system policies when users log into our CentOS server and after enabling Admin Approval Mode all the commands in my script were failing with access denied errors. I had to set Admin Approval Mode back to disabled and just forget about trying to run Edge or use the store app.

  • The Brain™

    Works for me! (Home user)

  • Jonathan FONG

    that’s great, thanks

  • Rudolph

    This worked.. I upgraded to 1151 and had permission problems after using reset file permissions.

  • Fix

    windows 10 home 1511. Registry keys work. thanks mate

  • Rafael Souza

    I did that, but didnt work

  • Greg Gum

    Worked for me on Windows Server 2016 Tech Preview 4.

  • Todd Dillard

    Not working for me. How ridiculous is it anyway that they make a change and you not only have to go figure out what the heck happened, you have such a whacked process for fixing it. Stupid.

  • DCM

    Didn’t work. Win 10 Home

    • Hamura Otsutsuki32

      my comment is for home version

  • Hamura Otsutsuki32

    Hey guys found the correct fix for this problem. On windows 10 there is no secpol.msc; hit the windows button and type “uac”. Then make sure the slider is at the third level from the bottom. This will indeed fix it. Don’t know how these people haven’t realised this is different from windows 8 and 8.1. Let me know if this helps.

    • Hamura, thank you for your comment. As mentioned I didn’t have access to Windows 10 Home edition for testing. I have added the UAC setting as part of the resolution. Thanks again.

      • Hamura Otsutsuki32


    • rata

      your are right on the money.thank you very much

      • Hamura Otsutsuki32

        No worries

        • Alexander Borisov

          I just want to hug you, im in a busy environment and this has been annoying me the whole day. Why couldn’t anyone just say “there is no secpol.msc” but instead give this stupidly complicated work around every time. Saved my lazy ass 😀 Im hating Server 2016 because of this

          • Hamura Otsutsuki32

            glad i could heelp.

  • Angelo Coelho

    And if I need to have UAC off and the first suggestion doesn’t work I’m shit out of luck? Freaking ridiculous

  • Perumal Raja Narayanasamy

    Thanks. Working for me. My Version is Windows 10 updated from Windows 8. Guys, try simply 🙂

  • Paul

    This worked for me, but I had to combine to two solutions. Firstly I am running Windows 10 Pro, and for me, after running secpol.msc, this did not fix the problem. So I continued down the resolution and found that the second registry entry was not set to 1. Then I found that I also had to run the UAC tools and set the slider as described.
    This sort out the problem.