PAExec v1.21 fails to copy file to remote machine when PsExec succeeds, why?

Hi.

Thank you very much for PAExec.

Local Machine:
Windows 7 Enterprise 64-bit SP1
Joined to a domain
Logged in as domain user "domain\firstname.lastname"

Remote Machine (IP Address = 192.168.0.201):
Windows 7 Enterprise 32-bit
Joined to a workgroup
UAC Disabled
Administrator is logged into the desktop

Elevated command prompt command line:
paexec.exe /AcceptEula \\192.168.0.201 -u 192.168.0.201\Administrator -p password -c "C:\path to\file.exe"

Output:
PAExec v1.21 - Execute Programs Remotely
Copyright (c) 2012-2013 Power Admin LLC
www.poweradmin.com/PAExec

Connecting to 192.168.0.201...
Starting PAExec service on 192.168.0.201...
Copying C:\path to\file.exe remotely...

PAExec returning exit code -8

I noticed that during the time "Starting PAExec service on 192.168.0.201..." is displayed, a new file was created on the remote machine, C:WindowsPAExec-18408-LOCALMACHINE.exe for example, where LOCALMACHINE is the machine name of where PAExec was run.
After PAExec fails, that exe no longer exists but the following new file remains on the remote machine: C:WindowsPAExec_Move0.dat

The contents of PAExec_Move0.dat is the same as "c:path tofile.exe" but it just has a different name.

I ran ProcMon on the remote machine and noticed that the remote PAExec process is trying to call CreateFile on "C:path tofile.exe" but fails with PATH NOT FOUND.

Using PsExec with the same command line works as expected.

However, when I run the following command, it works:
paexec.exe /AcceptEula \\192.168.0.201 -u 192.168.0.201\Administrator -p password -c -csrc "C:\path to\file.exe" file.exe

I did not expect to have to:

1. pass the -csrc paramter; this should be the default when specifying -c
   
2. pass the name of the exe again; this should be the default
   

Thank you very much.