The likely cause of this is that psexesvc is not running successfully on the target. Normally psexec creates the psexesvc service on the target computer, but this is likely failing in your case. It might be that there is antivirus or other similar blocking in place.
I would start by trying the following setting in BatchPatch:
Tools > Settings > Remote Execution > Use PsExec -r switch to specify remote service name
This setting allows you to modify the remote service name that is used by psexec from ‘psexesvc’ to ‘BatchPatchExeSvc’ or any other custom name of your choice. In the case where anti-virus or other security related software is blocking the remote service from running, changing the name of the remote service with this setting can often work to bypass the restriction for some of those applications without having to add psexesvc to a whitelist.
I would also suggest reviewing these postings:
1611-5-error-on-sccm-distribution-points
windows-update-error-1611-5-failure