Fix ERROR_NO_TXF_METADATA (0X00001AA0) on Windows

You're seeing ERROR_NO_TXF_METADATA (0X00001AA0) and it's stopping whatever you're doing with a file or folder. I'm sorry—that messages is cryptic and frustrating. Let me walk you through the fix. The good news: you can usually fix it without losing data.

What this error actually means

Windows uses something called Transactional NTFS (TxF) to track file changes in a temporary metadata file. This error—error code 0X00001AA0—means that Windows expects to see that metadata, but can't find it. The file itself might be fine, but the transaction log that goes with it is missing or corrupted.

Step-by-step fix

Step 1: Run chkdsk to scan and repair

Press Windows Key + X and choose Terminal (Admin) or Command Prompt (Admin).
In the black window, type this command and press Enter:
```
chkdsk C: /f /r
```
Replace C: with the drive letter where the error appeared.
If it says the drive is in use, type Y and press Enter to schedule the check for next reboot.
Restart your computer. After restarting, Windows will run chkdsk before loading the desktop. Let it finish—it might take 30 minutes or more on a large drive.

After this step: Windows will show you a log of what it found and fixed. Look for lines about orphaned file records or corrupt metadata—that's the TxF metadata being repaired.

Step 2: Try to access the file again

Once chkdsk finishes and you're back at the desktop, try opening or moving the file that triggered the error. Most of the time, this is all you need. The chkdsk command rebuilds the missing metadata from the file's own remaining data.

Step 3: If the error still appears

Take ownership of the file or folder. Right-click the file, pick Properties, go to Security tab, click Advanced, then Change next to Owner. Type your username and click OK.
Copy the file to a different drive using Robocopy with metadata preservation:
```
robocopy "C:\sourcefolder" "D:\backupfolder" filename.txt /COPY:DAT
```
The /COPY:DAT flag copies Data, Attributes, and Timestamps—everything except the broken metadata.
Delete the original file after confirming the copy is good.

Why this fix works

Transactional NTFS was introduced in Windows Vista and is mostly used by older enterprise software (like SQL Server or Exchange) for safe file writes. The metadata is a tiny file that sits in the $Extend\$TxfLog folder on the volume. When that log gets corrupted—often from a power loss or a bad shutdown—Windows can't verify the transaction state. Chkdsk reads the drive at the NTFS level and reconstructs that metadata from the file's own data blocks. It's not perfect: if the file itself is also damaged, you might still have issues. But in most cases, the file is fine and just needs its metadata rebuilt.

Less common causes and fixes

Antivirus scanning during a transaction

Some antivirus tools lock files while scanning them, which can interfere with TxF operations. If chkdsk didn't help, try disabling real-time protection temporarily (just for testing). If the error goes away, add an exclusion for the affected folder in your AV software.

Corrupt $TxfLog folder

Rarely, the entire $TxfLog folder gets corrupted. You can't delete it from Windows Explorer (it's hidden and protected). Instead, run this command to check and repair the TxF logs specifically:

fsutil repair query C:

If it reports corruption, run:

fsutil repair initiate C: "C:\repair.log"

Then restart and run chkdsk again. This forces a deep scan of the volume's metadata structures.

Third-party disk tools

I've seen tools like PerfectDisk or Auslogics Disk Defrag cause this error if they interrupt a transaction. Uninstall any disk defragmenters or optimizers that run automatically, then repeat the chkdsk step.

How to prevent this error

Always shut down Windows properly. This is the #1 cause of TxF corruption. A power outage or hard shutdown leaves transactions open.
Use a UPS on your computer. A $50 UPS prevents most file system corruption from power failures.
Run chkdsk once a month as maintenance. Open an admin command prompt and type chkdsk /f C: (schedule it for next reboot). This catches small issues before they become big errors.
Update old software that uses TxF. SQL Server migrated away from TxF years ago. If you're running an old version that still relies on it, consider upgrading to avoid this error entirely.

One last thing: If none of this works, the file itself might be beyond repair. In that case, restore from backup. Don't try to copy the file without the metadata—that can make things worse.