How to make Win10 Pro act more like Enterprise when disabling UAC?

Page 1 of 2 12 LastLast

  1. Posts : 20
    XP, 7, 10
       #1

    How to make Win10 Pro act more like Enterprise when disabling UAC?


    Windows 7 Pro & Enterprise were very closely related, however, with Windows 10 Microsoft are clearly separating the two and suspect Home & Pro may merger at some point.

    Disabling UAC in Windows Pro used to run applications like Command Prompt as an elevated user automatically but this is no longer the case. Obviously I can create shortcuts and tick ''Run as administrator' but I'd ideally like that to be on the application itself. Now when I do 'WIN+R' > type: CMD it brings up a non elevated Command Prompt.

    Have Microsoft defaulted user permissions somewhere or is there something fundamentally different in the UAC mechanism. When I compare say CMD.exe on Enterprise & Pro the permissions are identical. Is there something deep in the registry?
    Any tricks would be appreciated.

    P.S. - Please don't turn this into a 'but you shouldn't disable UAC' discussion. Start another thread if it pains you to discuss the wherefores and whys.
      My Computer

  2. xTL's Avatar
    xTL
    Posts : 388
    Windows 10 Pro 64-Bit (1809) 17763.379
       #2

    Hi AGTDenton,

    As far as i know Ms has not changed the defaulted user permissions, as long as ur in a admin acc.

    What windows 10 version are you on ?

    Are you on a local account or a Ms signed in acc ?
      My Computer


  3. Posts : 20
    XP, 7, 10
    Thread Starter
       #3

    Hi xTL

    On both Pro & Enterprise I am using locally created Admin accounts, no online or Domain accounts.

    Using Win10 Enterprise with UAC disabled, if I run CMD or Powershell it is immediately elevated to Administrator level. (The same as W7 Pro)
    However, if I run CMD from Windows 10 Pro with UAC disabled it is not elevated to Administrator level. I still have to right click 'run as administrator' or create a shortcut with 'Run as Administrator' ticked.

    You will know if CMD is elevated to Administrator as the command prompt window title will display 'Administrator: Command Prompt'. If it is not elevated to administrator level the window title simply shows 'Command Prompt'.

    Many Thanks
      My Computer

  4. xTL's Avatar
    xTL
    Posts : 388
    Windows 10 Pro 64-Bit (1809) 17763.379
       #4

    AGTDenton said:
    Hi xTL

    On both Pro & Enterprise I am using locally created Admin accounts, no online or Domain accounts.

    Using Win10 Enterprise with UAC disabled, if I run CMD or Powershell it is immediately elevated to Administrator level. (The same as W7 Pro)
    However, if I run CMD from Windows 10 Pro with UAC disabled it is not elevated to Administrator level. I still have to right click 'run as administrator' or create a shortcut with 'Run as Administrator' ticked.

    You will know if CMD is elevated to Administrator as the command prompt window title will display 'Administrator: Command Prompt'. If it is not elevated to administrator level the window title simply shows 'Command Prompt'.

    Many Thanks
    Okey so it's basically only win10 pro that gives you the headache?
    Please check here Run as Administrator in Windows 10 | Windows 10 Tutorials
    and try option 9

    Let me know if the problem still occur after :)
      My Computer


  5. Posts : 20
    XP, 7, 10
    Thread Starter
       #5

    Hi xTL

    Thanks, yes both of those work.
    UAC is doing something different between the versions of Windows 10 Pro & Enterprise.
    It seems with W10 Pro Microsoft are forcing an additional step to elevate applications to administrator level (despite being an admin). Whereas in W10 Enterprise they are not forcing the additional step and admin users are elevated by default on any application with UAC disabled. Like it was with W7 Pro.

    I'm trying to eliminate the need to create shortcuts, change the compatibility or perform a right click action.
    Something we've not been required to do since W2000.

    Many Thanks
      My Computer

  6. xTL's Avatar
    xTL
    Posts : 388
    Windows 10 Pro 64-Bit (1809) 17763.379
       #6

    You just want it to work straight out of the box so to speak i get it :)

    Can i ask, if you create a new local account on ur win10 pro pc and disable UAC, then signout, signin, open up cmd,
    Does CMD with admin rights work right away, or does same issue occur ?
    Could your local profile have been damaged somehow?
      My Computer


  7. Posts : 20
    XP, 7, 10
    Thread Starter
       #7

    xTL said:
    You just want it to work straight out of the box so to speak i get it :)

    Can i ask, if you create a new local account on ur win10 pro pc and disable UAC, then signout, signin, open up cmd,
    Does CMD with admin rights work right away, or does same issue occur ?
    Could your local profile have been damaged somehow?
    I have this problem with all PCs with W10 Pro on. With my home computers its less of an issue but in the environment I'm dealing with at work it is very annoying but not a showstopper. Obviously I should point out I'm using CMD/Powershell as an example to simplify things, the elevation issue isn't restricted to those apps.
    Are you running Windows 10 Pro? Do you have Pro N or K?
    Do you not experience the same thing running CMD with UAC disabled?

    Thanks.
      My Computer

  8. xTL's Avatar
    xTL
    Posts : 388
    Windows 10 Pro 64-Bit (1809) 17763.379
       #8

    AGTDenton said:
    I have this problem with all PCs with W10 Pro on. With my home computers its less of an issue but in the environment I'm dealing with at work it is very annoying but not a showstopper. Obviously I should point out I'm using CMD/Powershell as an example to simplify things, the elevation issue isn't restricted to those apps.
    Are you running Windows 10 Pro? Do you have Pro N or K?
    Do you not experience the same thing running CMD with UAC disabled?

    Thanks.
    I am running Windows 10 Pro 64-Bit ( 1809 ) OS Build: 17763.1
    I use a local account, UAC disabled, i do not get these issue.

    Yeah i understood that it wasn't restricted just to cmd :)
    Would be easier to find a solution if i could recreate this issue on my VM.
    But suggestions that is located here have you tried em ?
      My Computer


  9. Posts : 20
    XP, 7, 10
    Thread Starter
       #9

    Very interesting that you dont have the issue, you've given me a couple of thoughts. I use a localised version of the Windows 10 installer. English (UK). I'm wondering if there is an issue with that. Did you install a localised version of W10 or the US edition?
    When I go to work tomorrow I will check those policies.
    Thanks again.
      My Computer

  10. xTL's Avatar
    xTL
    Posts : 388
    Windows 10 Pro 64-Bit (1809) 17763.379
       #10

    AGTDenton said:
    Very interesting that you dont have the issue, you've given me a couple of thoughts. I use a localised version of the Windows 10 installer. English (UK). I'm wondering if there is an issue with that. Did you install a localised version of W10 or the US edition?
    When I go to work tomorrow I will check those policies.
    Thanks again.
    That is a great question
    I do belive i used Windows 10 64-bit US version.
    I would check if i still had my .iso :)
    I do know that my .iso is from around ~feb 2018, because that is when i installed my current Win10 OS.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:10.
Find Us




Windows 10 Forums