Hi Quinn I'm aware that there should be no limit on the file count. I observed the described behavior with completely different sets of files. Also on Windows 7 and Windows 10. Using SysInternals Process Monitor on the target machine shows that the 65. file (C:\Windows\PAExec_Move64.dat) (C:\\Windows\\PAExec_Move64.dat) cannot be created for whatever reason (Error code NAME_NOT_FOUND). If I use the -lo option I do not get any new information: <code> Connecting to 192.168.1.123... Starting PAExec service on 192.168.1.123... Copying 65 files remotely... PAExec returning exit code -8 </code> Maybe you give it a try yourself?

Hi Quinn I'm aware that there should be no limit on the file count. I observed the described behavior with completely different sets of files. files. Also on Windows 7 and Windows 10. Using SysInternals Process Monitor on the target machine shows that the 65. file (C:\Windows\PAExec_Move64.dat) cannot be created for whatever reason. reason (Error code NAME_NOT_FOUND). If I use the -lo option I do not get any new information: <code> Connecting to 192.168.1.123... Starting PAExec service on 192.168.1.123... Copying 65 files remotely... PAExec returning exit code -8 </code></code> Maybe you give it a try yourself?

Hi Quinn I'm aware that there should be no limit on the file count. I observed the described behavior with completely different sets of files. Using SysInternals Process Monitor shows that the 65. file cannot be created for whatever reason. If I use the -lo option I do not get any new information: <code> Connecting to 192.168.1.123... Starting PAExec service on 192.168.1.123... Copying 65 files remotely... PAExec returning exit code -8 </code>