Fix 0x8007016A & 0x80071129 Windows File Errors

Not long ago, I encountered a frustrating issue after disconnecting an old OneDrive account from my PC. I was left with a persistent folder that refused to budge, displaying the annoying error message 0x8007016A The cloud provider is not running. Every time I attempted a standard fix, it swiftly escalated to the infamous 0x80071129 The tag present in the reparse point buffer is invalid.

It became clear that these locked files still bore corrupted reparse point tags—the low-level metadata indicating a file serves as a placeholder in the cloud. Since my OneDrive account was disconnected, my system lacked any active “cloud provider” to sanction the deletion, resulting in the error. After much trial and error, I created a video to assist others, like YOU. Here’s a detailed guide on how I resolved these errors.

Step 1: Repair the Filesystem Using CHKDSK

Initially, I opted for a fundamental repair, as the corruption appeared to lie within the filesystem.

1. Launch an elevated Command Prompt (or PowerShell Admin).
2. Execute the complete disk check command: chkdsk C: /f /r
   • I specified C: as that was where my locked OneDrive folder resided.
3. Restart your computer to permit the scan to run.

Though the disk check uncovered and repaired some issues, I regrettably found that upon rebooting and attempting to delete the troublesome folder, the error remained.

Step 2: Try the PowerShell Brute Force Approach

Next, I decided to try a more aggressive command-line deletion via PowerShell, hoping to bypass the folder’s restrictions.

1. Open PowerShell as an administrator.
2. Utilise the Remove-Item cmdlet with the following parameters:
   
   Remove-Item -Path "C:\Path\To\My Locked Folder" -Recurse -Force
   • The Recurse parameter deletes all subfolders.
   • The Force parameter overrides prompts and restrictions.

Although this method is effective for numerous typical file deletion dilemmas, in my case, the command encountered failure due to the severe reparse point corruption, which PowerShell couldn’t override.

Step 3: The Ultimate Resolution for 0x8007016A or 0x80071129 Using Robocopy /MIR

This prompted me to employ the ultimate command-line solution: Robocopy. Known for its robust file operations, it offers a feature capable of forcefully mirroring the directory structure.

1. I switched to a standard Command Prompt (Admin).
2. Created a temporary, empty directory on my C: drive with: mkdir C:\TempEmptyFolder
3. Executed the command that does the trick. This command mirrors the source folder (my empty C:\TempEmptyFolder) onto the destination (my troublesome OneDrive folder): robocopy C:\TempEmptyFolder "C:\Path\To\My Locked Folder" /MIR

While chkdsk and Remove-Item acts as great initial steps, the robocopy /MIR solution was the definitive fix for my stubborn, cloud-locked files. If you find yourself grappling with this issue, I strongly recommend following the steps outlined in the video.