Software⏱️ 3 min read📅 2026-06-15

How to Fix: psexec could not start psexec service on <server>. Error in the remote procedure call was cancelled

Psexec error on Win2012 server: Error in the remote procedure call was cancelled.

Quick Answer: Try using the correct syntax for psexec, such as \ -u -p cmd.exe, and ensure that the Active Directory user is properly configured.

📋 Table of Contents

  1. ⚠️ Common Causes
  2. 🔧 Proven Troubleshooting Steps
  3. ✨ Wrapping Up

The 'psexec could not start psexec service on ' error occurs when attempting to execute commands remotely using PsExec on a Windows Server 2012 machine. This issue affects users who try to run commands with PsExec but fail due to a service cancellation error.

This problem can be frustrating, especially for IT professionals who rely heavily on PsExec for remote command execution. However, by following the steps outlined below, you should be able to resolve this issue and successfully execute commands remotely.

⚠️ Common Causes

  • The primary cause of this error is that the PSEXESVC service is not running or is not configured correctly on the target server. This can happen due to various reasons such as a misconfigured registry entry, a missing dependency, or a corrupted service file.
  • Another possible reason for this error is that the credentials provided to PsExec are invalid or do not have the necessary permissions to access the target machine.

🔧 Proven Troubleshooting Steps

Configuring PSEXESVC Service

  1. Step 1: Step 1: Ensure that the PSEXESVC service is installed and running on the target server. You can check this by opening the Services console (Windows + R, type 'services.msc' and press Enter), finding the PSEXESVC service, and verifying its status.
  2. Step 2: Step 2: If the service is not running, you need to start it manually. Right-click the PSEXESVC service in the Services console, select 'Start', and then wait for a few seconds to ensure that the service has started successfully.
  3. Step 3: Step 3: Verify that the registry entry related to PSEXESVC is correct. The key should be located at HKEY_LOCAL_MACHINE\Services tservice tpsexesvc, and it should have a 'Start' value of '2' (Automatic). If this key does not exist or has incorrect settings, you need to create or modify it manually.

Verifying Credentials

  1. Step 1: Step 1: Check the credentials provided in PsExec. Ensure that the username and password are correct and have the necessary permissions to access the target machine.
  2. Step 2: Step 2: If you're using an Active Directory user account, verify that the account has the required permissions and is not locked out or disabled.

✨ Wrapping Up

By following these steps, you should be able to resolve the 'psexec could not start psexec service on ' error and successfully execute commands remotely using PsExec. If you're still experiencing issues, it may be helpful to consult with a Windows Server administrator or seek additional support from Microsoft or Sysinternals.

Did this fix your problem?

If not, try searching for specific error codes.

🔍 Search Error Database

❓ Frequently Asked Questions

🛠️ Related Fixes

How to Fix: Pc crashes shortly after launching game (rainbow

Fix Pc crashes shortly after launching game (rainbow six siege). Compl

How to Fix: Installing an APK on a locked down phone

Installing an APK on a locked down phone: Try using a rooted device, e

How to Fix: New PC build- no signal and no clue

Fix New PC build- no signal and no clue. Complete troubleshooting guid