Author: Aditza
Subject: psexec v2.11 broken for local system
Posted: 02 September 2014 at 6:19am
i am used to using the command
psexec -sdi cmd.exe
to launch a local command shell with local system account privileges on the local machine when i need to run regedit and other debugging tools directly with local system privileges, however, sometime between v2.00 and v2.11 this behavior has been broken horribly.
i tested with v1.98 AND with v2.0.. they work fine, however v2.11 seems broken. The screenshot below is from the v1.98 vs v2.11 test. (v2.0 works too, behaves as v1.98 so not including it here).
What's going on? Why is the new psexec trying to reach out over the network for a command that is supposed to be run locally?
has the syntax been changed and i need to use other parameters? (but the help for psexec v2.11 doesn't look any different when telling me what the -s -d -i parameters do... )
![]()
Edited by Aditza - 9 minutes ago at 6:28am
Subject: psexec v2.11 broken for local system
Posted: 02 September 2014 at 6:19am
i am used to using the command
psexec -sdi cmd.exe
to launch a local command shell with local system account privileges on the local machine when i need to run regedit and other debugging tools directly with local system privileges, however, sometime between v2.00 and v2.11 this behavior has been broken horribly.
i tested with v1.98 AND with v2.0.. they work fine, however v2.11 seems broken. The screenshot below is from the v1.98 vs v2.11 test. (v2.0 works too, behaves as v1.98 so not including it here).
What's going on? Why is the new psexec trying to reach out over the network for a command that is supposed to be run locally?
has the syntax been changed and i need to use other parameters? (but the help for psexec v2.11 doesn't look any different when telling me what the -s -d -i parameters do... )
Edited by Aditza - 9 minutes ago at 6:28am