[bweddell]

I’ve tried to do a batchpatch deployment of individual .msu files and also show this error. I’m using the same domain account that has domain admin privs in the domain. I can test connectivity \\servername\c$ and ability to creates files and directories from the server I’m running batchpatch from to computers I want to deploy to.

I’ve also read that exit code 5 comes from wusa directly (confirmed by running psexec in a command prompt).

In my case I am running Windows 10 with batchpatch 2020.9.25.16.33.

From other things I’ve seen on the Internet, this is by design since wusa isn’t allowed to perform remote execution. Is that correct?

If it is, what is the suggested mitigation from the batchpatch perspective since a deployment prefaces the command with wusa?

Although I’ve not tested it, I assume that may be a combination of (in batchpatch) to copy file/folder followed up by Execute remote process/command.

[Author]

Posts