Sometimes you want to work uninterrupted on a server and you definitely do not want to start notepad elevated in order to edit your stuff. There are of course many ways to do this, but I find myself using the following routine.
- Start an elevated CMD – Right click CMD and run as administrator.
- Run the following command: tskill explorer & explorer
To do this more automated you could save the command into a batch file on the desktop. And then when you need an elevated desktop you just right click the batch file and choose “run as administrator”.
You can now verify that explorer is running elevated by going into task manager and adding the “Elevated column”. (Right click on an existing column and choose “Select Columns”
This is of course not a best practice.
Best practice would be to elevate every application you need as you need it. For example when you need to edit the hosts file under c:\windows\system32\drivers\etc the best practice would be to start an elevated notepad to edit it.
When you run my command you will be able to browse to hosts file and choose edit directly without the need of elevating notepad first.
Hope you liked this tip. 🙂
Oh god, finally, something that almost works!
For some reason, other tricks don’t seem to work for me on 1511 (build 10586.589).
If I run the command when an Explorer process is already running, obviously it stays that way (limited); merely another process/window with elevated rights will be added
If I run it when all Explorer processes are killed already, the new process will start as limited.
What this does for me is launch a single Explorer INSTANCE as elevated. This means:
– Other Explorer calls will still be limited
– The Main/root Explorer process is still limited
…so this is only good for getting one elevated window where you then have to manually navigate to where you want to go, but everything else will still result in limited windows for me.
What might be the source of that problem?