If trying again (and downloading a new payload) after the issue is revealed magically solves the problem without the company admitting they pushed a fix, I’m a little bit dubious.
Maybe it was actually what they claimed about it being a corrupted update then? And considering the issue is still an active fire they're putting out, I'm l is give them the benefit of the doubt. They seem to be genuinely scrambling, so their comms are going to suffer. If, in a couple days, things haven't changed, then there's reason to question the intentionality of missing followup communication.
Also, if they pushed a fix that worked reliably, they'd be shouting that loud and clear as THE solution, not merely suggesting to try updating and to see if it might help.
Also, if they pushed a fix that worked reliably, they'd be shouting that loud and clear as THE solution, not merely suggesting to try updating and to see if it might help.