Manage the P4 Server Windows service

When you install P4 Server on Windows, the installer:

  • Installs the P4 Server executable.

  • Registers the server as a Windows service.

  • Configures the service to start automatically when Windows starts.

In normal operation, you manage the server through this Windows service. You do not usually start or stop the server by running an executable manually.

Understanding p4s.exe and p4d.exe

You may notice both of the following files in the server installation directory:

  • p4s.exe - This is the Windows service version.

  • p4d.exe - This is the command‑line server executable

Both p4s.exe and p4d.exe are the same server program. The only difference is how they are started:

File

How it is used

When to use it

p4s.exe

Runs as a Windows service.

Normal, recommended operation.

p4d.exe

Run manually from a command prompt.

Advanced or temporary use only.

In summary:

  • Most administrators should always use the Windows service (p4s.exe).

  • Running p4d.exe manually is not recommended for day‑to‑day operation.

  • Never run p4d.exe manually while the Windows service is running. Doing so could result in:

    • Port conflicts.

    • Database corruption.

    • Unpredictable server behavior.

Service account and file ownership

By default, the P4 Server Windows service runs under the LocalSystem account.

This means:

  • The service account owns the P4ROOT directory.

  • The service can fully access the server’s database and archive files.

For most installations, no changes are required.

You typically only need to change the service account if you:

  • Store P4ROOT on a network drive.

  • Need the server to access external resources under a specific user account.

  • Have strict Windows security or backup requirements.

If you change the service account, ensure that account has:

  • Read and write access to P4ROOT.

  • Access to required registry keys.

What's next

To learn more on how else you can manage the P4 Server as a Windows service, see: