OneDrive Ghost/Orphaned Files – Metadata Corruption Escalation Request

NPLGlitcherPatcher 350 Reputation points
2026-06-17T10:59:31.1033333+00:00

Hello,

In my OneDrive folder, there are several files that are completely inaccessible. They appear in the cloud but cannot be opened, downloaded, or deleted. These items behave like ghost/orphaned files — ownerless and unauthorized.

I have already tried all client-side resets (cloud sync reset, MS 365 reset, unlink/reinstall, cache clear), but none of them worked. The issue is clearly server-side metadata corruption.

Neither the SharePoint technical support team nor the OneDrive application support team could resolve this. They confirmed that the problem requires escalation.

This problem has been ongoing for years, and I urgently need a resolution.

**
Please escalate this case to the OneDrive backend engineering team for metadata repair or account-level purge.**

Thank you,

[Moderator note: Personally Identifiable Information removed].

Microsoft 365 and Office | OneDrive | For business | Windows
0 comments No comments

Answer accepted by question author
Anonymous
2026-06-17T13:01:13.47+00:00

Hi @MovelessMove-0585

Thank you for your detailed explanation of the issue. I completely understand how frustrating it must be, especially since this has been ongoing for such a long time and has already gone through multiple troubleshooting attempts. 

As a forum moderator, I want to clarify that I don’t have the ability to directly escalate cases to backend engineering team or initiate actions such as metadata repair or account-level purge. Escalations of this nature can only be performed by the official Microsoft support engineers who are actively handling your case and have already collected the necessary diagnostic logs from your environment. 

Since your issue has been confirmed as requiring escalation, the best course of action would be: 

  • Continue working with the assigned support engineer handling your ticket 
  • Request them to formally escalate the case internally to the appropriate backend or engineering team, based on the logs and investigation they have already gathered 

If your case is currently inactive or has stalled, you may also consider reopening it or creating a new support request through the Microsoft 365 admin center to ensure it is routed correctly and followed up. 

I truly appreciate your patience on this, and I agree that your scenario warrants deeper backend investigation. 

Thank you again for your time and understanding. I really appreciate your patience, and I’m here to help. Looking forward to your response!     


Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread 

Was this answer helpful?

2 people found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.