I’ve managed to successfully update my laptop using a tethered mobile connection and then manually copied over the missing files to my desktop PC (into the Download folder that the zwift updater had created). These are the main files that consistently fail to download, taken from the log file.
This is a workaround to complete the update but is far from ideal. I’m amazed that the updater appears to download each file individually in an uncompressed format.
It is consistent in that the majority of the files are downloaded successfully and always fails on the same files which is what led me to believe this could be an issue with the file repository. So far I’ve worked out that for me cdn . zwift . com is resolving to 4 load balanced cloud front servers. The IP addresses for these change periodically (which could explain perhaps how some people didn’t do anything apart from reboot or try and update at a different time).
I did attempt to manually download the missing files as the location details are all contained within the log file. However I’m unable to manually download files from the file server apart from the version XML file as the other files appear to require authentication to download (403 error).
I’m wondering if cloud front is closing the connection at some point during the download for some reason but I guess no one really cares. Unfortunate for anyone who isn’t technical and is faced with this issue as they will likely just not ride and/or stop their subscription.
For anyone else with the problem you will probably have to download (by running the installer) the missing files reported in the log file through another internet connection (perhaps on another PC) and then copy them across to your desktop if required like I did.
I don’t have any hard numbers at all and this is just conjecture from being on this forum for nearly two years but I believe the percentage of Zwifters who actually come on here is somewhere between 1 and 2 percent. None of the people I know personally come here and it is very rarely I encounter someone I’ve seen here during a Zwift event. It is not easy to find this place from the Zwift homepage, even when you need to.
So the few people you’re seeing complain about this is in reality a huge number when extended by percentage. Zwift should not be lulled into a sense of false complacency by the small number but be alarmed by the how many these few represent.
I too have had very few issues with Zwift or their monthly Bugdates and reading some of these tales of woe makes me very thankful for my good fortune.
I never said that it wasn’t a serious problem that Zwift should be addressing. But compare the number of people raising this download problem with those reporting in Crash after login (iOS and AppleTV) [November 2021] [1.19.0] (and the latter is only a problem for those who aren’t already logged in). So that one seems to be a much more consistent issue.
My point was that we’d be seeing it raised an awful lot more if files were consistently corrupted for the download. But that’s not to downplay the problem or to say that one problem is more serious than another.
Thanks @Wes. Any update on the flickering riders on ATV?
Riders relentlessly flickering in and out of visibility in large groups. Has been present since launch of pd3. Can’t be just my end as it’s a discussion point on every large event I join. Was hoping for a fix in this update as it’s bordering on being an eyesight issue or a headache. ATV and 300mbps bandwidth is usually a flawless experience. Can supply a video if you need to see impact.
Hmmm! Since the update my Apple Watch has been pairing without using the companion app. Before the up date I had to use the companion app and 40% to 50% of the time I had issues. I am using an Apple TV to run Zwift.
