asked on Using runas.exe on win10 is different to former OS' - why?
Experts,
I hope you realize that this, though it is just a technical detail, has an impact on how we can/cannot use certain things, for example administrative tools, on windows 10.
Steps to reproduce:
On Windows 10 (here: v1511)
1 start notepad elevated entering different credentials (via right click or via runas.exe)
2 use the open dialogue to navigate to c:
3 rightclick a folder and select properties. You'll see an error message on windows 10: "the properties for this item are not available"
Why is that?
I hope you realize that this, though it is just a technical detail, has an impact on how we can/cannot use certain things, for example administrative tools, on windows 10.
Steps to reproduce:
On Windows 10 (here: v1511)
1 start notepad elevated entering different credentials (via right click or via runas.exe)
2 use the open dialogue to navigate to c:
3 rightclick a folder and select properties. You'll see an error message on windows 10: "the properties for this item are not available"
Why is that?
Windows 10
Last Comment
McKnife
ASKER
You don't?
Well I have it on a clean installation.
Let me guess: you are running as admin? Then it works. But if you run as restricted user, then the problem shows.
Well I have it on a clean installation.
Let me guess: you are running as admin? Then it works. But if you run as restricted user, then the problem shows.
You mean you go from a restricted to an admin user?
ASKER
Correct.
Confirmed. Going from restricted to unrestricted you seem not to be able to switch the Explorer privileges. But you can use the Open File explorer correctly. I was able to navigate thru the paths without issues, just couldn't open the properties.
If you do the same with e.g. cmd, then start an Explorer from there, you see you do not have changed privileges (i.e. cannot navigate to other users folders, for example). Explorer has "some issues" with switching users, that is no news. It might help to allow to start Explorer windows in a separate process instead of respawning the one for the GUI (in Folder and Search Options) - didn't try that.
If you do the same with e.g. cmd, then start an Explorer from there, you see you do not have changed privileges (i.e. cannot navigate to other users folders, for example). Explorer has "some issues" with switching users, that is no news. It might help to allow to start Explorer windows in a separate process instead of respawning the one for the GUI (in Folder and Search Options) - didn't try that.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Solved. It's a bug and MS will fix it. Workaround until the fix arrives: rename the runas entry at HKEY_LOCAL_MACHINE\SOFTWAR
See discussion at https://social.technet.microsoft.com/Forums/en-US/8a6211f5-7819-4ab9-b475-ced9ab878cf2/using-runasexe-on-win10-behaves-differently-compared-to-former-os?forum=win10itprosecurity
See discussion at https://social.technet.microsoft.com/Forums/en-US/8a6211f5-7819-4ab9-b475-ced9ab878cf2/using-runasexe-on-win10-behaves-differently-compared-to-former-os?forum=win10itprosecurity
Note that even with elevated privileges you do not have access to all folders by default.