What is “The tag present in the reparse point buffer is invalid” error
The tag present in the reparse point buffer is invalid or error 0x80071129 is a kind of message a user may receive while trying to use Microsoft OneDrive. This error often occurs when the On-Demand OneDrive feature is on. While this functionality unlocks an easier path to managing files, it sometimes leads to facing problems in the form of such errors. As a rule, the most likely reason for this is some disk corruption that prevents OneDrive from backing up junction files. Alternatively, it can otherwise be a OneDrive fault related to cache or even an internal Windows bug that can be solved only through updating. Whatever it is, we recommend you try each of the three methods presented below to resolve the OneDrive “The tag present in the reparse point buffer is invalid” error.
Download Windows Repair Tool
There are special repair utilities for Windows, that can solve problems related to registry corruption, file system malfunction, Windows drivers instability. We recommend you to use Advanced System Repair Pro to fix OneDrive “The tag present in the reparse point buffer is invalid” error in Windows 11 or Windows 10.
1. Run the CHKDSK command
This solution will most likely resolve the issue. We should though warn you that despite the effectiveness of this method, it might not be able to solve the issue forever. Many users reported that have to enter this command multiple times to get a temporary room for OneDrive usage. Even so, we recommend you try this method and see how it goes on your system. Here are the step-by-step guidelines below:
- Open Command Prompt by typing
cmdinto the searching loop next to the Start Menu button.
- Right-click on Command Prompt and choose Run as administrator.
- Type in this command
chkdsk C: /f /rand press Enter.
- If necessary, replace C: with your actual hard drive letter.
- In case Windows tells you that this volume is already being used, then type
Yand press Enter.
- Then, close the console and restart your computer. The scan process will start during restart, so wait until it finally ends.
2. Reset OneDrive inside cache folder
In this consecutive method, we are going to clear redundant cache files of OneDrive. Such files may be able to cause some jams in proper OneDrive operation. Thus, we recommend you follow these steps to clear it. Do not worry, this will not affect your OneDrive data in any negative way.
- Open Command Prompt the same way we did it above.
- Copy-paste this command
%localappdata%\Microsoft\OneDrive\onedrive.exe /resetand press Enter.
- Once done, close the console and try to perform that same algorithm of action that was causing the error to appear.
3. Make sure your system is up-to-date
Some error victims say the issue has evolved into a chronic cycle, repeatedly showing itself upon each regular OneDrive usage. While this can be temporarily solved using the methods above, it is less likely the error can be permanently banned without Microsoft’s help. We advise you to check your system for new updates. It is possible that developers will roll out some update that fixes minor bugs causing such OneDrive failures. Here is an instruction on how to check for updates and install them, if any.
- Right-click on the Start Menu button at the bottom taskbar of your desktop and choose Settings..
- Navigate to Windows Update and click Check for updates.
- Wait until Windows finds new updates and install them. If new updates were already pending, you can install them immediately without searching for them.
These several solutions should be enough to make the “The tag present in the reparse point buffer is invalid” message vanish away. As mentioned in the concluding method of our guide, it is less likely that you will be able to get rid of the error forever. You can try reinstalling your system or OneDrive itself, however, we do not think it will serve you the desired help. The best-case scenario remains to be repeating the fixes that worked each time the issue occurs while waiting until Microsoft sorts out the internal bug with an update.