The exit code in this case is not coming from BatchPatch. Rather, BatchPatch is passing through the exit code that was returned by wusa.exe on the target or by the target OS. I can’t find 1396 in any lists of wusa.exe exit codes, so there is a pretty good chance (not a guarantee) that it’s just a standard Windows system error code. If that’s true then in this case it would mean
ERROR_WRONG_TARGET_NAME
1396 (0x574)
The target account name is incorrect.
This error would normally occur due to a logon failure on the target computer, and so it seems like it’s probably not coming from wusa but rather from Windows during the attempt to connect. To confirm that this is actually what’s happening, try a different command:
‘Actions > Execute remote process/command’ and then try to execute just a simple IPCONFIG command as a test. If this fails with the same error, then we can be pretty confident that the error info above is accurate and that there is a logon issue. The link below explains some ways that you might be able to resolve that logon issue.
One possible quick workaround might be to use IP address instead of host name.
More possible workarounds/solutions here:
https://social.technet.microsoft.com/Forums/windows/en-US/d760ee38-5b98-4982-91d0-e5c9c3fe45a5/logon-failure-the-target-account-name-is-incorrect?forum=w7itpronetworking