2011-01-25, 01:16 PM
2011-01-25, 01:24 PM
Ok install psexec from the PSTools zip. Then go into cmd and type:
Then close explorer using task manager. And type "explorer.exe" into your psexec cmd.
Psexec.exe -i -s cmd.exe
Then close explorer using task manager. And type "explorer.exe" into your psexec cmd.
2011-01-25, 02:33 PM
Thanks, now that command worked. I am System
2011-01-25, 06:43 PM
Thats a very very bad way to do it Killing the explorer process can have harmful affects on your computer.
This is so much simpler:
Now your "Administrator" account is always on the Welcome Screen or Classic Logon Screen
What Windoze really needs is a proper sudo!
This is so much simpler:
- Go into safe mode as described in my previous post (by using F8 when you restart your computer)
- Launch Registry Editor. (start->run --> regedit)
- Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList in the Registry Editor.
- Double-click the Administrator key in the right pane.
- If the Administrator key doesn’t exist, right-click on the above tree in the pane, choose New, DWORD Value, name it Administrator and press Enter
- Type 1 in the “Value data” box, and press Enter
- Close regedit
- Reboot
Now your "Administrator" account is always on the Welcome Screen or Classic Logon Screen
What Windoze really needs is a proper sudo!
2011-01-25, 08:53 PM
(2011-01-25, 06:43 PM)Dylan M. Wrote: [ -> ]Thats a very very bad way to do it Killing the explorer process can have harmful affects on your computer.How so? To my knowledge it causes no problems. It only stops the displaying of folders and files on the screen. When started back up again, it is perfectly fine.
TBH, running under the system account or even a superuser administrator is far more dangerous
2011-01-25, 09:38 PM
So if a virus enters while i am in System it would have access to any file and registry then?
2011-01-25, 09:56 PM
Yea, but if you run as an administrator you're at rusk anyway. Just run explorer as system, and do only what you need or better, just run regedit from your psexec cmd by typing "regedit"
2011-01-27, 06:47 PM
Just to ask...will this theoretically work on an Account that has limited privileges on Windows XP?
2011-01-27, 08:19 PM
(2011-01-25, 08:53 PM)Tom K. Wrote: [ -> ]How so? To my knowledge it causes no problems. It only stops the displaying of folders and files on the screen. When started back up again, it is perfectly fine.
TBH, running under the system account or even a superuser administrator is far more dangerous
It also affects any file copy/move operations and a few other things. Killing processes is always risky. Using psexec to run commands is fine, but killing off a process to re-run it is risky. All I'm saying. Besides, you don't STAY logged in as Admin. You "switch user" log into Admin, do what you need to, LOG OUT, and relog back into your normal user session. Thats what quick user switching is for. You should never use the Admin account for everyday tasks, but it is annoying to require "safe mode" to see it. Hence the above registry hack.
(2011-01-27, 06:47 PM)dikidera Wrote: [ -> ]Just to ask...will this theoretically work on an Account that has limited privileges on Windows XP?
What do you mean theoretically work? As in can a limited account use psexec?
http://technet.microsoft.com/en-us/sysin...s/bb897553
And for the dangerous side of psexec:
http://www.windowsecurity.com/articles/P...an-Do.html
2011-01-28, 02:08 AM
Wait what? I thought you could access the admin account by running
net user Administrator active:yes
??
net user Administrator active:yes
??