aakkam22/windowsUpdateLoopFix

Broken download link for Windows Update Agent v7.6

mahatma-panda opened this issue · 4 comments

bitsadmin /transfer wua http://download.windowsupdate.com/windowsupdate/redist/standalone/7.6.7600.320/windowsupdateagent-7.6-x86.exe "%systemdrive%\packages\wua.exe" >nul

This link appears to be broken. The script hangs on this line since the link is dead.

There is an archive of the link from archive.org at the following URL: https://web.archive.org/web/20220206050819/http://download.windowsupdate.com/windowsupdate/redist/standalone/7.6.7600.320/windowsupdateagent-7.6-x64.exe

I did not verify the authenticity of the archive.org file.

Hi @mahatma-panda, the link seems to "work for me". Could you try again ?
Thanks, bye 🙇


EDIT : Maybe related to #6.

@mahatma-panda Link works for me if inserted in web browser, but I will investigate to see if I can reproduce the issue. Thanks

I tried the link (not the script) from a different machine and it worked fine. I have no idea what happened. I'll troubleshoot some more on the affected machine.

Is there currently a way to have the script run on the existing files instead of deleting them and re-downloading them? Example: I download the three files on my own, place them in the C:/packages directory, then have the script execute the remainder of the steps to install the three files.

I am back at this again.

I am digging a bit further into this. Two things:

  1. It appears that for some reason, WindowsUpdateAgent will not download through CMD. (I am able to download it through chrome.)
  2. The error being thrown by BITSADMIN does not appear to be handled correctly by the script. It appears to hang indefinitely on "Downloading Windows Update Agent v7.6..."

Below is the output when I run the following command in an admin cmd:
bitsadmin /transfer wua http://download.windowsupdate.com/windowsupdate/redist/standalone/7.6.7600.320/windowsupdateagent-7.6-x86.exe "%systemdrive%\packages\wua.exe"

image

Is there anything obvious that I'm missing? I'm sure there is something silly preventing CMD from completing this download that I'm not understanding...