Check for updates stuck at the "Attempting to initiate Windows Update

BatchPatch Forums Home Forums BatchPatch Support Forum Check for updates stuck at the "Attempting to initiate Windows Update

  • This topic has 3 replies, 2 voices, and was last updated 7 years ago by doug.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #8923
    thenew3
    Participant

    So for some unknown reason, batchpatch stopped working today. We were promoted to download the latest version so we downloaded the latest 2017.11.9.11.20 version but still would not run.

    We then found that for some odd reason psexec.exe would give an Access Denied when we tried to manually run it. So we downloaded the latest psexec (2.2) and replaced the older (2.11) and then psexec would now run.

    Doing a check for updates in batchpatch we get the following message

    Attempting to initiate Windows Update (Action: Search for updates: “SoftwareAndDrivers” | Server selection: Microsoft Update)…XX:XX:XX

    where XX:XX:XX is the hour:minute:second we initiated the process.

    It gets stuck at this phase and never completes the check.

    Tried this on two different PC and got same result.

    Any idea what’s going on? Thanks.

    #10345
    doug
    Moderator

    It sounds like something in your environment has changed. Access Denied generally means that there is a permissions issue. Please start by going through the troubleshooting guide step by step to help pinpoint where the issue is.

    #10347
    thenew3
    Participant

    We got around the permission issue. It was the anti malware blocking PSexec.exe We installed the latest psexec.exe (v2.2) and that issue went away.

    Now we are faced with the issue of update check never completing with

    Attempting to initiate Windows Update (Action: Search for updates: “SoftwareAndDrivers” | Server selection: Microsoft Update)…XX:XX:XX

    Using the latest batchpatch released today 2017.11.10.12.1 and psexec v2.2

    #10348
    doug
    Moderator

    It might be caused by your anti malware software blocking psexesvc.exe on the target computers. Try setting a custom name for this process under ‘Tools > Settings > Remote Execution > Use PsExec -r switch to specify remove service name’ You could use something like BatchPatchExeSvc.exe. This might be enough to bypass the anti malware app. If not then you could try whitelisting the exe files in the anti malware app.

    See also this posting, which explains the most common reason for getting stuck on “Attempting to initiate Windows Update”: https://batchpatch.com/batchpatch-stuck-attempting-to-initiate-windows-update

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