A more complete and thorough solution
“There is a mismatch between the tag specified in the request and the tag present in the reparse point”, is the full error message you get after clicking on a folder with a corrupted reparse point.
Sometimes you just can’t delete a file or directory, but let’s not focus on the details of the problem, just the solution. Suffice it to say its usually a file corruption issue; though occasionally it’s caused by too long of a file path structure or reserved name conflict due to some kind of POSIX hell.
Update Note: OneNote appears to do this often after deleting large numbers of small files on SSD drives. Wish I knew why.
I just ran into such a problem trying to delete a folder from OneDrive and it’s sub-folders. It would not give me an error and would not remove the folder in my Windows 10 workstation. Not until I navigated down to the bottom directory and tried to delete the specific sub folder did I obtain the error above. Undeterred, I tried to delete it from the command line with rm and got this, “rm: cannot remove ‘src’: Input/output error”.
So I set the dirty bit to run chkdsk /f /r on the reboot, but it wouldn’t really run it. It would go through the motions, but you can’t chkdsk on a nearly 1 TB volume in 14 seconds. I tried about all of the chkdsk variations, but couldn’t achieve a real scan and couldn’t delete the folder. Strange, but to be resolved later (Bad NvME drive). I suspect that I’m not the only one who’s had this problem.
Update: Why CHKDSK wouldn’t run? ADATA SSD drives do not work with AMD onboard Raid 0 and probably variations similar to this. Use Samsung SSD.
Some Boot Options
I’ve been using Active Boot for more than 15 years so I opted to boot to a USB drive with raid drivers installed. This allowed me to run a full on chkdsk with “chkdsk f: /scan /perf /F”. Problem solved and the folder was able to be deleted. Now to figure out why the native OS couldn’t run chkdsk. The results will look something like this if there is a reparse error involved.
The type of the file system is NTFS. Stage 1: Examining basic file system structure ... Deleting corrupt attribute record (0xC0, "") from file record segment 0x1A97CB. Deleting corrupt attribute record (0xC0, "") from file record segment 0x1F65EC. Deleting corrupt attribute record (0xC0, "") from file record segment 0x22735D. 2488832 file records processed. File verification completed. 22125 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... Correcting reparse point file record segment 1A97CB. Correcting reparse point file record segment 1F65EC. Correcting reparse point file record segment 22735D. Deleting an index entry from index $R of file 1A. Deleting an index entry from index $R of file 1A. Deleting an index entry from index $R of file 1A. 712194 reparse records processed. 3043510 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 712194 reparse records processed. Stage 3: Examining security descriptors ... Security descriptor verification completed. 277340 data files processed. CHKDSK is verifying Usn Journal... Usn Journal verification completed. Windows has made corrections to the file system. No further action is required.