|
|
|
|
|
by Bjartr
1428 days ago
|
|
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. |
|