Windows Service Error 3, "The system cannot find the path specified" when starting a service

Error 3 when starting a service means the folder in the service's binary path does not exist. The file itself may be fine, but the directory Windows was told to look in is gone.

The fix, in order

  1. Check the binary path. Run sc qc followed by the service name in an admin Command Prompt and read the BINARY_PATH_NAME line.
  2. Check whether the folder in that path exists. If the folder was deleted or renamed, the service cannot start until the path is fixed.
  3. Check the drive letter. A path that points at a drive that changed letter, or a network drive that is not connected, gives error 3 even when the folder exists somewhere else.
  4. Reinstall the program that provides the service. A clean install recreates the folder structure and writes the correct path.
  5. Check environment variables in the path. A service path that uses a variable like %ProgramFiles% fails if that variable was changed or removed. Compare it with the same variable on a working PC.
  6. Run sfc /scannow in an admin Command Prompt if the missing folder belongs to Windows.

If it still happens

If the folder exists but the error continues, look for a typo in the path, a trailing backslash problem, or a permission issue on the folder. A folder that exists but cannot be opened by the service account can report the same code.

Common questions

What is the difference between error 2 and error 3 for a service? Error 2 means the folder exists but the file inside it is missing. Error 3 means the folder itself is missing, so Windows never got far enough to look for the file.

Can a changed drive letter cause error 3? Yes. If the service path points at D:\Programs and that drive is now E:, the path does not exist. Restoring the original drive letter or reinstalling the program fixes it.

Related errors

Windows Service Error 2 · Windows Service Error 87 · Windows Update Error 0x80070003

Was this helpful?