error 0x80071129 the tag present in the reparse point buffer is invalid

Anonymous
2021-01-04T06:14:19+00:00

I get this error when selecting the option always keep this folder on this device.  Anyone know how to fix?

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

20 answers

Sort by: Most helpful
  1. Anonymous
    2021-01-04T07:03:50+00:00

    Hi HaoSun,

    I'm Nik, an independent advisor here to assist you with this.

    As per the issue description and error message screenshot, I would like to suggest to you:

    1.Follow the steps and command from here "How to Fix "tag present in the reparse point buffer is invalid" OneDrive Error":

    https://www.youtube.com/watch?v=SMd2s1Em42Q&amp...

    1. Reset OneDrive app as described in the following article and check the outcome:

    https://support.microsoft.com/en-us/office/rese...

    Disclaimer:

    Note: Link shared in this conversation is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

    Regards

    Nik

    Was this answer helpful?

    100+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-04-08T13:20:58+00:00

    Chkdsk works to fix this. However, this issue keeps constantly popping up for us. For all users across all our Windows devices and we can't keep wasting 30 minutes of our users time (and our support's) each week because their disk has to be scanned. 

    This issue has existed for us for years. Google search shows this issue back in 2015. Will it ever get fixed by Microsoft?

    Was this answer helpful?

    70+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-04-21T14:34:04+00:00

    chkdsk /r /f does work but this happens all the time and it's insanely frustrating. We need our IT support to run a offline chkdsk for the user which takes upwards of 30 minutes. This wastes everyone's time and is a weekly occurrence for us. 

    And Microsoft as usual never fixes any of this. This bug has been going on for years, still no progress and only solution from Microsoft is run chkdsk each time this happens (no matter how often that is).

    Was this answer helpful?

    50+ people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-02-04T03:42:12+00:00

    This (chkdsk /r /f) as in the video above solved my reparse buffer issue with an inaccessible OneDrive Folder.

    Was this answer helpful?

    50+ people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2021-05-23T19:01:22+00:00

    We now perform a "chkdsk c: /scan" daily (sometimes more than one a day) on all client systems using OneDrive. We are suffering chronic file system corruption (reparse errors) on those systems, which results in many strange problems for our users. To make matters worse, when the "chkdsk c: /scan" detects a reparse error, it appears to have a bug with its online repair code, so rather than fixing the problem right there and then, chkdsk instead simply blows up! At least chkdsk marks the drive's file system as dirty (that is, the file system needs to be structurally checked at the next boot) before it crashed. The check it performs at the next boot is a "/f" type, so it typically takes less than 5 minutes to complete (as opposed to the much more time consuming "/r" type); however, it does mean making the user reboot in the middle of their day to fix the corruption.

    As we can no longer count on healthy file systems for our business clients that make use of Microsoft OneDrive, we are transitioning off of the Microsoft 365 platform--and Windows--entirely. An operating system and cloud service that can't maintain the integrity of client data is absolutely useless and of no value. In fact, persisting with its use when you are aware that it is chronically corrupting data is irresponsible for our own data, and our duty to our client's data.

    Microsoft seems to have made no attempt to address this problem in any meaningful way. Instead, it just keeps advising users to do a "chkdsk" to fix it each time it occurs. However, because the symptoms a damaged file system cause are so varied, our users don't know when to do the "chkdsk". Instead, they suffer with bizarre problems--sometimes for days! Microsoft's lack of action to correct the cause of the chronic reparse errors for so long just makes clear how little attention it pays to small business and other users of Microsoft 365 products.

    I believe this marks the final chapter in Microsoft's role as a partner to small businesses. It's time to move on to greener pastures.

    Was this answer helpful?

    40+ people found this answer helpful.
    0 comments No comments