Gone with Windows 7 : RunAs for Explorer

By apexwm, 29 August, 2011 15:03

One of the most useful support tools for Windows XP that we've used over the years, is the ability to run Windows Explorer as an administrator account, while having a restricted user logged in. This allows an administrator to perform Explorer-related tasks while leaving the end user logged in.

This is accomplished by using the command "runas /user:administrator explorer.exe". It is a great tool and we almost use it daily on XP computers.

But, with Windows 7, suddenly this no longer works. Running Explorer with RunAs, simply opens a new instance of Explorer as the currently logged in user. Back when we started migrating users from XP to 7, we searched and searched for the solution for Windows 7 that works like XP. But, even today, none has been found. The workaround? To use Switch User and log in to the PC as an administrator account, and run Explorer. But, the drawback is when trying to switch back to the regular user that is logged in, their password needs to be typed in. This is counterproductive if the user is not at their desk while the admin is troubleshooting.

So, with enhanced "security features" in Windows 7, some features have completely disappeared. I'm guessing there are some 3rd party solutions available, but we normally try to avoid these due to adding costs and other issues into the mix.

Talkback

There are many things gone in Explorer after XP. See the full list here: http://en.wikipedia.org/wiki/List_of_features_removed_in_Windows_Vista and http://en.wikipedia.org/wiki/List_of_features_removed_in_Windows_7 . The Explorer team didn't do a good enough job with Vista and 7 and they aren't with Windows 8 either by refusing to fix all these bugs and omissions.

As for RunAs, you can use Sysinternals' ShellRunAs to bring the exact functionality back. ShellRunAs can also be registered in the context menu.
anonymuos 30 August, 2011 18:04
Report offensive content Reply

See if Win7 Explorer will behave the way you want it to after launching it inside a standard user login session. Use the Windows key, or point and click if you must, to open the Start menu. Type char string explorer.exe into the Search box. Ignoring the results, use keyboard combination Ctrl + Shift + Enter to run any program with administrator privileges. Enter your admin credentials into the UAC dialog. Test this instance of Explorer to your heart's content. Oops! Apparently apexwm is correct, because a check of Task Mgr. (Ctrl + Shift + Esc) showed the process running as a standard user regardless of the attempt to elevate! By contrast, a quick check likewise after launching Notepad worked. Oh well. I guess the Command shell will have to do, but elevating the Command Processor just to browse the file system seems like a bit of overkill. And although hardly ideal (impossibly so for searching), don't forget that Explorer's address bar can be used to reveal normally concealed folders, but only if you type the correct path, a la the command line!
Apachegila 30 August, 2011 22:58
Report offensive content Reply

The Command line, in Windows, Surely Not!

Command line is the main reason given by Windows Fanboi's to try and put people off using Linux, as well as the obsolete idea that you have to write your own drivers from Scratch.
djflunk 31 August, 2011 13:45
Report offensive content Reply

anonymuos :

Thanks for pointing out the Sysinternals solution. I believe we have seen that one before. The point with all of this, is that Microsoft continues to rip out core functionality from the operating system, with no direct solution other than relying on a 3rd party.
apexwm 31 August, 2011 15:18
Edit Delete Report offensive content Reply