question

MikeDiack-1747 avatar image
1 Vote"
MikeDiack-1747 asked MrBike edited

Is Psexec 2.30 buggy - I cannot use it to get a SYSTEM prompt any more? (2.20 is fine)

I think the newly released Psexec 2.30 has a bug. On Windows 7/10 (but not XP), whenever I now try to run: psexec -i -s cmd.exe to get a SYSTEM command prompt, I see: "No process is on the other end of the pipe." This occurs even if I delete the old psexesvc.exe Psexec 2.20 is fine.

windows-sysinternals-pstools
· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I am also having this issue. This is something I have come to depend on. Hope it gets fixed.. Guess I will revert to 2.20..

1 Vote 1 ·

Do you know where can I find the 2.20 version or any other older version of Psexec?

1 Vote 1 ·

Do you know where can I find the 2.20 version or any other older version of Psexec?

1 Vote 1 ·

No but asking co-workers if they might have a previous version... My googlefu seems weak today and I could not find it.. You would think they would keep a previous version available on this site until current version is rock solid.

I have tried this on 2.45 and 2.46 and it has the same issue. Very irritating. I have also tried all of the suggestions of killing the service and restarting computer nothing has corrected this issue.

1 Vote 1 ·
pcbl avatar image
2 Votes"
pcbl answered

I am facing issues with 2.3 when I use the -h flag. With 2.2 worked fine! Since yesterday update of the package this issue came up...

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

EricHuggins-6855 avatar image
1 Vote"
EricHuggins-6855 answered

I just had the same problem with 2.3.
Fortunately had a copy of 2.2 handy.
Deleted psexecsvc using powershell and then ran 2.2.
Works find now.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

PaulT-5039 avatar image
1 Vote"
PaulT-5039 answered

I was finally able to get this (psexec.exe -i -s cmd.exe to work by opening the services app on windows 10 as an admin and stopping the service, PSExeSVC. I then tried this psexec.exe -i -s cmd.exe and it worked. Sorry I could not be more help.

In my post above I was trying to stop the service using PSKill so I am guessing there was an issue with that so I finally had the idea to stop the service by opening the services app as admin and stopping it. Yeah, should have done that from the beginning..

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

foxmsft avatar image
1 Vote"
foxmsft answered MikeDiack-1747 commented

For interactive sessions the -i flag (with no session number) is now necessary.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

That maybe so, but I've always used -i with it as you describe, but the initial release of 2.30 didn't do it anyway.

In any case there are still a number of other bugs with 2.30.

0 Votes 0 ·
VafinSergei-5701 avatar image
0 Votes"
VafinSergei-5701 answered MrBike edited

I got "access denied error" with the version 2.30. With the version 2.2 it worked fine.

The previous version of pstool 2.45 (with psexec 2.2) can be downloaded from https://www.computerbild.de/?dl=1&dlcid=WjgzVUUuVFpGLlAsTShTLVY5IihbPEZVSi5PKEgsMyhDLFA8RihQWkYuUFFNKFQxVjs2NUY9JiVaPCIoWwouOjNVRC1QJEMtMzBELDM0Si5KR2AKYAo%3D

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

The link to pstools 2.45 doesn't work for me?

1 Vote 1 ·

if you search a bit on that website you'll find it
https://www.computerbild.de/suche/?q=pstool%202.45

however, initially had an issue with 2.2 as well: "Error establishing communication with PsExec service on DEEPTHOUGHT:
The network path was not found."

solution: admin$ also on local host needs to be accessible.
check that name resolution for the hostname is working, server service is running and file and printer sharing is not disabled on the network adapter


0 Votes 0 ·