Remotely Restart the FileWave Windows Client Service with PsExec

Use Microsoft PsExec to restart the FileWaveWinClient service on a remote Windows device when the Client is not responding through normal FileWave commands. Common cases include a stopped or stuck service, a manual restart required during troubleshooting, or a configuration change that specifically requires the service to restart. Use normal FileWave commands first; do not treat a service restart as a routine fix for an unidentified problem.

Before you start

• Download PsExec from Microsoft Sysinternals.
• Use an account with local administrator rights on the target device.
• Confirm that your Windows firewall, admin shares, and organization security controls permit approved remote administration.
• Do not put an administrator password in the command line. The example uses the current administrator context. If an alternate account is required, add -u DOMAIN\User and omit the -p option entirely so PsExec prompts for the password without displaying it on the command line.

Open a remote shell

From an elevated Command Prompt in the PsTools folder, replace computername with the target Windows device:

psexec64 \\computername -h cmd

If your download contains PsExec.exe instead of PsExec64.exe, use that executable name. Type exit when you are finished with the remote shell.

Restart the FileWave Client service

First query the service, request the stop, and query it again:

sc.exe query FileWaveWinClient
sc.exe stop FileWaveWinClient
sc.exe query FileWaveWinClient

Continue only when STATE reports STOPPED. If the service reports STOP_PENDING, wait and run the query again. Do not force-kill the service from this procedure.

After the service is stopped, start it and confirm its state:

sc.exe start FileWaveWinClient
sc.exe query FileWaveWinClient

The final query should report a RUNNING state. Exit the remote shell, confirm that the device checks in to FileWave again, and review the Client log if it does not.

If the service does not restart

• If PsExec returns Access is denied, verify the account’s rights and the remote-administration prerequisites before retrying.
• If security software blocks PsExec, use your organization’s approved remote-management tool instead of weakening endpoint protection.
• Review C:\ProgramData\FileWave\fwclient\fwcld.log for the service error.
• Use sc.exe qc FileWaveWinClient to inspect the configured service start type and binary path. Do not change them unless troubleshooting has identified a specific configuration problem.

Related Content

• PsExec as a Helper in Troubleshooting
• Using PowerShell to Remotely Check the Windows FileWave Client Status
• Microsoft: sc.exe query