C-7 here, trying to update from 2.3.8.139 to 2.3.8.140. It detects the update is available, downloads it, extracts it, then goes straight to âchecking for updatesâ and wonât break the cycle til the hub is rebooted. But then any attempt to update does the same thing again.
Good suggestion, but I tried that and the rollback to .138 was fine, then .140 does the same thing trying to install again. I think there might be something wacky with the package, even if you didn't have trouble with it.
You can use the diagnostic tool to "Download latest version" then use the Restore Previous.... button to install it (yes you can update with that button as well).
This will usually get you updated when the normal method gets stuck for whatever reason.
OK, that didn't work either. I do download latest version, it says it succeeded in downloading and to use restore previous version as you suggested. But when I look there, I only see 2.3.8.138 and 2.3.7.146
So it seems like the diagnostic tool also can't extract the .140 package ÂŻ_(ă)_/ÂŻ
I use Edge on Mac, and I was having corruption issues trying to create a local backup file (in prep for this update), but updating Edge fixed that... Maybe make sure your browser is updated and try again?
Yeah, this is what I'm wondering too. I don't know how to clear that though, it must be in the hub itself. I've tried full power cycles aside from the soft reboots I was doing as well, and that didn't help either.
You could try forcing it to download a bunch of older platforms and maybe that will clear it out. Use this endpoint and the number at the end is the major version, so 2.3.4 is 234 as shown.
Doing a reboot with a DB rebuild and a log purge has changed my results, but not much for the better. Now I see it download, verify, extract, and then give this âdownload failedâ message.