Share via

OneDrive web instance (https://onedrive.live.com) not showing any files

Anonymous
2024-06-08T22:01:14+00:00

Hi,

My OneDrive stopped working very suddenly about three days ago. At first, it seemed like just the sync had broken, as all my local folders and files were showing red Xs. I went through the guides on the Microsoft site and the community, all to no avail, including resetting and uninstalling OneDrive completely. However, when I eventually logged onto the server-side instance at https://onedrive.live.com, my files weren't visible either, proving it wasn't a client-side issue at all.

For some reason, I can't upload any images here, but the error I'm getting in the "My Files" section of OneDrive is:

"This item might not exist or is no longer available. This item might have been deleted, expired, or you might not have permission to view it. Contact the owner of this item for more information. RETRY Correlation ID: 4cbf30a1-b07e-8000-f14f-ec0d992b3cc2"

If I try to search for specific files using the search bar, they do appear in the search results. However, when I try to download any of them, a zip file is created with text files as follows:

1)

  • File name: OneDrive_1.txt
  • Contents:

Sorry, there was a problem downloading this file from OneDrive. Please try again. https://onedrive.live.com/?id=53C8E7CADAC3AE31%21s9218cd9b621f4dc49a2c403ac0924da8&action=Download

3)

Clicking any of the links will return the same error in red above as will checking the recycling bin or clicking the "Restore Your OneDrive" button.

Any ideas?

Microsoft 365 and Office | OneDrive | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2024-06-10T20:59:13+00:00

    Out of the blue, this started working again today.

    I changed nothing which leads me to believe there was some temporay server-side issue which was suddenly resolved.

    Was this answer helpful?

    0 comments No comments