My guess is that engineering resources have been focused on the upcoming new version of drive, and are ignoring difficult bugs with the current version.
I could understand that in a smaller company, but seems poor at Google scale. OTOH, that scale also means they don't care about losing a few customers over something like this.
The issue is, Google is trying to make serious inroads into enterprise with Cloud/GSuite. This almost certainly costs Google more in reputation among that crowd than it would to fix it or just offer a refund.
This shouldn't happen. There's things called End-of-Life and End-of-Service. EOS usually happens a least a year out. Google should still be servicing previous versions.
I could understand that in a smaller company, but seems poor at Google scale. OTOH, that scale also means they don't care about losing a few customers over something like this.