Exit Code: 1385

[doug]

On January 11 the v2.21 version of PsExec was released, but it contained a few bugs. The next day v2.30 was released, but it still contained a couple of bugs. And then two days later v2.32 was released, but it still contains one issue, which is that when specifying alternate credentials you will end up with exit code 1385, if your remote execution context is set to anything other than SYSTEM. In BatchPatch if you go to ‘Tools > Settings > Remote Execution’ if you change the ‘Remote Execution Context’ setting from ‘Elevated token’ to SYSTEM, you will not get the 1385 error anymore. For the very large majority of actions/scripts/commands, SYSTEM will be successful in places where ‘Elevated token’ would have previously been successful. We also expect that Microsoft will release another update in the coming days to resolve this 1385 issue.

[doug]

OK so where things have been left is that PsExec v2.32, which is the current/new release, will work the same as previous versions of PsExec, when using SYSTEM remote execution context. However, when using ‘Elevated token’ in conjunction with alternate credentials in PsExec v2.32, you also have to now additionally use the -i (interactive) switch. In the next release of BP we will add this option as well.

Microsoft appears to be considering this change intentional, and not due to a bug after all. It’s unclear at this time if they will be making any additional changes in the near future, but all signs point to this being where things will be left, at least for now. It does not appear that they plan to release an update to replace v2.32 any time in the very near future.

[jeffallen]

I ran into exit code 1385 the other day, and this article helped me. Thank you.

When I encountered the error, I changed from Elevated token to SYSTEM and that fixed it. PSEXEC is now at version 2.43. If I had instead simply updated PSEXEC to current, would you say that would have resolved the problem as well? Are there any other reasons why I should update PSEXEC from 2.34 to V2.43?

[doug]

I’m not certain if I understand exactly what you’re saying. In my posting above in Jan 2021 I reference v2.32 because that was the latest version at the time. But now it’s Jan 2025 and PsExec is up to v2.43. Generally, it’s usually a good idea to use the latest version, but if things are working fine for you on v2.34, I’m not aware of any specific reason why you should feel compelled to go to v2.43 aside from just it being the most recent one.

[Author]

Posts