Some of our external clients are reporting that the updater process isn't working for them. I just did a support session with one of them and it worked for some of the computers in the office, but not all of them. We tried one of the computers where it wasn't working:
1) The download (about 60 mb) was very slow. This appears to be on their end.
2) In the case I witnessed, it got to about 40% done, then jumped to the MD5 check and reported that the file was corrupt.
3) If I used Internet Explorer to download the msi update directly, it would download (just as slowly) but complete. I could then perform the update manually.
I didn't see the failure actually occur (I was looking away when it went from 40% to showing the "corrupt" dialog), but it seems like the download may be timing out. Is there a way to tell the updater to be more patient before it fails? We're getting several clients that are reporting this, so it's becoming an issue for us.
FOLLOW US
Get the latest news in Application Packaging