Error 1620: 193. Failure

BatchPatch Forums Home Forums BatchPatch Support Forum Error 1620: 193. Failure

  • This topic has 2 replies, 2 voices, and was last updated 5 years ago by Graceyin39.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #12164
    Graceyin39
    Participant

    Hi,

    I got the error below when I tried to download update.

    Tue-14:04:14> Windows Update: Error 1620: 193. Failure
    Tue-14:04:14> Windows Update: Failed to obtain result. Could not find file ‘\\Server01\C$\Program Files\BatchPatch\BatchPatchTempResult.log’.
    Tue-14:04:09> Windows Update: Executing BatchPatchRemoteAgent.exe…

    When I run psexec, I got error below.

    C:\Users\batchpatch>psexec \\Server01 IPCONFIG

    PsExec v2.11 – Execute processes remotely
    Copyright (C) 2001-2014 Mark Russinovich
    Sysinternals – http://www.sysinternals.com

    Could not start PSEXESVC service on Server01:
    %1 is not a valid Win32 application.

    I could access \\Server01\c$ and \\Server01\Admin$.

    What could the problem? Please advise!

    #12165
    doug
    Moderator

    In some cases this could be caused by antivirus or other security software running on the target computer and preventing psexesvc from starting. The link below explains a possible way to get around that.

    At the command prompt try using the -r switch like this and see if it works:
    C:\Users\batchpatch>psexec \\Server01 -r bpexesvc IPCONFIG

    Then try to enable the -r switch in BatchPatch per the instructions here:

    what-to-do-when-psexec-is-blocked-by-your-anti-virus-software

    If you still aren’t able to get psexec working with -r then next step would be try to disable all antivirus or similar security software running on the target, then test again.

    However, it could be that there is some other type of issue with the target computer or the psexec computer. Does the issue happen with all targets or only one? Try running psexec from a different source computer and see if results are different. Else try rebooting the target computer and trying again.

    If still no luck have a look at the possible resolutions explained at this link: error-1611-3-failure

    #12167
    Graceyin39
    Participant

    Hi Doug,

    Thank you for your reply. The issue is resolved. It is caused by our firewall settings.

    Thanks again!

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.