The error 0x8007112a (Mismatch between the tag specified in the request and the tag present in the reparse point) occurs when people attempt to move or delete a folder on Windows 7, Windows 8.1, and Windows 10.
In most cases, it turned out that this problem was caused by a folder permission issue. In this case, you will be able to fix the issue by running the File & Folder Troubleshooter or the Shared Folders troubleshooter (if applicable).
An app conflict or a bad update can also be responsible for this problem. If you’re unsure of the culprit, one universal fix is to use the System Restore utility to revert your computer back to a healthy state.
However, the problem can also be caused by a series of corrupted system files. If this scenario is applicable, you should start by deploying DISM and SFC scans and see if they manage to fix the issue automatically. In more serious instances, you might need to go for a complete Windows component reset procedure (clean install or repair install).
Method 1: Running the File & Folder Troubleshooter
If you’re encountering this issue with a shared folder or a sub-folder of OneDrive (or similar cloud service), you are probably dealing with a permission issue that prevents you from moving content around your PC.
In case this scenario sounds like it could be applicable, you should attempt to run the File & Folder troubleshooter and the Shared folders troubleshooter (if you’re on Windows 10).
These two troubleshooting utilities contain a selection of automated repair strategies that might just end up fixing the 0x8007112a error code. If a problem that’s already covered by a repair strategy is found, the utility will automatically attempt to repair it.
If you want this method a try, follow the instructions below:
- Access the download page of the Windows File & Folder troubleshooter and click on the download button to download the utility.
Note: This utility is compatible with Windows 10, Windows 7, and Windows 8.1.
- Once the .diagCab file is successfully downloaded, double-click on it and click Yes at the User Account Control (UAC) to grant administrative privileges.
- Once you’re inside the first screen of the File and Folder Troubleshooter, click on the Advanced hyperlink and check the box associated with Apply repairs automatically. Then, click Next to initiate a scan with troubleshooter.
- After the initial scan is complete, check the boxes associated with the type of problems that you’re currently occurring.
Note: Users that have fixed the 0x8007112a using this troubleshooter have checked the boxes associated with Problems with deleting files and folders and Renaming or moving files and folders.
- Wait until the operation is complete, then see if the troubleshooter managed to find and fix any issues. If it did, reboot your machine and see if the problem is fixed at the next computer startup.
- If the issue is still persisting and you’re seeing this problem with a shared folder on Windows 10, follow the next steps below to run the Shared Folders troubleshooter.
Note: In case you’re not seeing the error on Windows 10, move directly to Method 2.
- Press Windows key + R to open up a Run dialog box. Next, type ‘ms-settings:troubleshoot’ inside the text box and press Enter to open the Troubleshooting tab of the Settings app.
- Once you’re inside the Troubleshooting tab, move over to the right-hand section, scroll down to the Find and Fix other problems section, then expand the Shared folders menu before clicking on Run the troubleshooter.
- Wait until the initial scan is complete, then paste the network location of the folder you’re encountering the 0x8007112a error with and press Next to start the troubleshooting investigation.
- Once the investigation is completed, follow the on-screen prompts to apply the recommended fix, then restart your computer & network to see if the problem is now fixed.
If you followed the instructions above and you’re still seeing the 0x8007112a error or this particular scenario was not applicable, move down to the next potential fix below.
Method 2: Performing DISM and SFC scans
If none of the troubleshooters above have allowed you to fix the issue, it’s possible that the folder issue you’re currently dealing with is rooted in some kind of system file corruption.
In this case, you should be able to fix the issue by using a couple of built-in utilities capable of replacing corrupted operating system files with healthy equivalents – DISM (Deployment Image Servicing and Management) and SFC (System File Checker) are two consolidated utilities that might get the job done for you.
Since their modus operandi is different, we recommend that you run both scans in quick succession to maximize your chances of fixing the 0x8007112a error.
If you’re determined to try this fix, deploy an SFC scan and wait for the operation to complete. Keep in mind that this utility doesn’t require an internet connection – It relies on a locally stored archive that it will use to swap out corrupted Windows files with healthy equivalents.
Note: Once you start this operation, it’s not recommended that you close it prematurely or restart/shut down your computer while it’s still in progress. Doing so might leave your system exposed to additional logical errors.
Once this operation is completed, restart your computer conventionally and wait for the next startup to complete. After your PC boots back up, initiate a DISM scan and wait for the operation to complete.
But before doing so, keep in mind that DISM is heavily reliant on a Windows Update sub-component, so a stable Internet connection is required in order to allow DISM to replace corrupted instances with healthy files.
Once the second scan is completed, restart your computer and see if the error is fixed.
In case you’re still seeing the 0x8007112a error when you attempt to delete or move a folder in File Explorer, move down to the next potential fix below.
Method 3: Using System Restore
If you noticed that the problem only started to appear after a certain app installation/update or after Windows update installed a new OS build, you might be dealing with a software conflict or a badly installed driver.
In situations like this where the culprit is not clear, the best course of action is to use the System Restore utility to restore your machine state back to when it was functioning properly.
Note: Keep in mind that System Restore is configured by default to create new restore snapshots at important system events. This includes app updates, installation of Windows Updates, AV scans, etc.
If you plan on using System Restore to revert your computer state back when the 0x8007112a error was not occurring, use this step-by-step guide on using System Restore.
If you already tired using System Restore to no effect, move down to the final potential fix below.
Method 4: Resetting every OS component
if none of the potential fixes above have worked for you, it’s possible that you’re dealing with some type of system file corruption that simply cannot be resolved conventionally.
If this scenario is applicable and none of the potential fixes above have worked for you, the only viable fix left for you is to reset every relevant Windows component in order to eliminate any persisting type of corruption. When it comes to doing this, you really only have two ways forward:
- Performing a Clean install – This is the easier option since you can deploy it without a compatible installation media. It will reset the components of your window installation alright, but unless you had your data backed up, be prepared for total data loss.
- Repair install – If you’re looking for the focused approach, this is it. This procedure is also known as an ‘in-place repair’ and will reset every OS component without touching the rest of your files. This means that you get to keep your apps, games, and personal media if they are currently stored on the OS drive.