Google has opened an investigation to determine the cause of a problem Drive that automatically deletes files from folders stored in the cloud without notice of personal and business accounts since May this year.

A user shared on the Google Drive Help page that his storage unit “returned to as-is in May 2023,” that is, it only showed the documents, photos, and videos that were stored at the time.

More specifically, this person indicated that because files are not deleted manuallydid not appear in the drive’s trash, so they would have been permanently removed from the Drive details Europe Press.

When this user learned of this error, he contacted Google support in South Korea, who provided him with a Drive recovery tool, although its implementation proved unsuccessful. “Nothing has changed,” said this user, identified as Yeonjoong.

After attempting to restore a folder, this user reported the issue to Google Support in the United States recommended that you contact local experts to correct the recorded error.

On this forum, other users – including those with commercial Google Drive accounts – reported the same problem, pointing out that all files in their storage space had been automatically deleted, as is the case with the one identified as Antonio Vohl, who caused that Google has disclaimed any responsibility for removing these files.

Nicco Coraccio, another patient, claimed to have had the same problem and reached a point where all your files have stopped syncing for some reason, but that Google Drive continued to function normally. Similarly, other users reported losing their files with the storage platform update.

Initially, Google’s Photos & Drive employee, identified on this forum as PeteranDi, acknowledged that the company did not have access to user accounts. With this, he recommended filing a new complaint with the company’s support team.

Now Google has recognized the error, according to a support message shared by another user, confirming that more customers have been affected by this error. “It is being investigated by our product engineers and we are also awaiting a root cause analysis on how to resolve the issue.“, can be read in this comment, which does not specify what might be causing the issue or how many users are affected by this error. (JO)