Friedrich,

We are validating some patch downloads using wupdate.exe and have been getting a few anomalous issues.

1) Sometimes we get the 5060 "can't read manifest" error.

2) Sometimes we get the message that it can't find/download the patch installer, which implies it did find the manifest/INI since it displays the correct URL and patch executable name in the error message.

3) Other (most) times it all just works.

The most common denominator seems to be a delay when clicking on the 'next' button on the initial wupdate wizard, which would imply some sort of timeout, etc. Additionally, once it has failed once, it seems to work from that point on (manifest being cached on the network?).

Is there a way to set the wupdate timeout? Or do you have any other thoughts? I've checked all the 5060 threads, but the fact that it works most of the time would indicate that the basic settings are correct. No special MIME types, etc., just an INI and an EXE.

Finally, the manifest and download files are hosted at Amazon, so I don't have any access to server settings, etc.

Thanks,
Tom