Windows Server 2016/2019: systemsettingsadminflows.exe error

In Windows 2016/2019 server, when you have enrolled the server in a domain, and log in as domain admin, and you try to add an extra UI language, you will see the following:

 

c:\Windows\system32\systemsettingsadminflows.exe
Windows cannot access the specified device, path or file. You may not have the appropriate permissions to access the item

This can be fixed with changing the following:

Start –> Run

“secpol.msc” – ENTER

After this, log out, and in again, and give it another try 🙂

 

Links: https://docs.microsoft.com/da-dk/windows/security/threat-protection/security-policy-settings/user-account-control-admin-approval-mode-for-the-built-in-administrator-account

26 Comments

  1. HAIDER SHAHZAD

    thanks for the solution, it work like a charm.

    Reply
    1. Martin (Post author)

      Thanks for your feedback 🙂

      Reply
    2. ANTONIO SANTOS

      Thank you.
      Work for me 🙂

      Reply
      1. Martin (Post author)

        Glad to hear 🙂

        Regards Martin

        Reply
    3. Luis Antonio Sánchez

      It worked for me

      Reply
  2. Steve

    Thanks very much Martin.
    This worked perfectly for me (with Windows Server Standard 2019)

    Cheers

    Reply
  3. Steven Quina

    Thanks, worked for me!

    Reply
  4. Øyvind Hvidsten

    Works perfectly on Server 2019 as well

    Reply
    1. Martin (Post author)

      Thanks for sharing 🙂

      Reply
  5. Sjunkie

    if I enable this, I cannot access my administrative tools anymore.. and it keeps resetting the permissions on them after a reboot

    Reply
    1. Martin (Post author)

      Have you enabled or disabled UAC? It should be enabled.

      Reply
  6. Klaus

    Thanks it works 🙂

    Reply
    1. Martin (Post author)

      Glad to hear 🙂

      Reply
  7. Mattias

    Thank you.

    Reply
  8. Sevy

    Thx m8. You’re a life saver.

    Sevy

    Reply
    1. Martin (Post author)

      Thanks 😉

      Reply
  9. Marek

    Thanks very much Martin.
    This worked perfectly for me (with Windows Server Standard 2019 after upgrade from 2012)

    Cheers

    Reply
    1. Martin (Post author)

      Glad to hear – thanks 🙂

      Reply
  10. Matz Höög

    Work like a charm! Thanks!

    Reply
    1. Martin (Post author)

      Thanks 🙂

      Reply
  11. sami

    …and enable UAC 🙂

    Reply
    1. Martin (Post author)

      🙂

      Reply
  12. Eric F

    I was trying to install OpenSSH and getting this error but this did the trick! Thank you!!

    Reply
  13. Flou

    Thanks for the tips, it wored like a charm for me

    Reply
  14. Christian Weiten

    Thank you so much!

    Reply
  15. MAS

    Hey,

    Thank you so much for the post. I was struggling for days to find the solution.

    Reply

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close