The google support offered a work around below: I wanted to let you know that I checked this out with our dedicated team and they explained to me that they are aware of this behavior with Drive for Desktop as it seems to be a known issue however, they are currently working on a solution and they expect the issue to be resolved with the new version of Drive for Desktop (version 50). I contacted googel support and the google suppor told me that If users in your org are having the similiar issues recently, the below info might be relavent Some of our users in our org started reporting the same issue since July 16, 2021.
