Fix ERROR_QUOTA_LIST_INCONSISTENT (0x0000026D) Fast

Yeah, that ERROR_QUOTA_LIST_INCONSISTENT 0x0000026D is a real pain. It usually pops up when you're trying to enable or view disk quotas on a drive, and Windows just throws its hands up. I had a client last month whose file server kept refusing to apply new quotas across all user folders—turns out the quota file was internally messed up. The good news? You can fix it without losing your data.

Fix It: Reset the Quota File with fsutil

First, open Command Prompt as Administrator (right-click Start > Command Prompt (Admin) or Terminal Admin). Skip the GUI stuff—it won't help here. Run:

fsutil quota query C:

Replace C: with your affected drive. If you see the 0x0000026D error or a weird output, the quota index file is corrupted. The nuclear option that works 99% of the time is to delete and recreate it. Do this:

1. Close any open files on that drive.
2. In the same admin command prompt, run:

   fsutil behavior set disablequotatracking 1

   This disables quota tracking temporarily.
3. Restart your computer.
4. Delete the hidden $Quota file in the root of the drive. It's normally at C:\$Quota (use File Explorer with hidden files visible or dir /a). If you can't see it, run:

   del /f /q C:\$Quota

5. Re-enable quota tracking:

   fsutil behavior set disablequotatracking 0

6. Reboot again.

After that, reapply your quotas normally. The system will create a fresh quota file.

Why This Works

The error means the NTFS quota structure (stored in the $Quota metadata file) has an internal mismatch—like a database where one table points to a row that doesn't exist. The file system can't reconcile it, so it screams 0x0000026D. By deleting that file and letting Windows recreate it, you're essentially resetting the quota database. The actual data on the drive stays untouched; only the tracking file is rebuilt.

Less Common Variations of the Same Issue

1. Multiple drives with the same problem
If you see this on several drives, it's often a bad disk controller or failing drive. Check Event Viewer for disk errors. Run chkdsk /f on each affected drive first—sometimes it can fix the quota file itself. But if chkdsk fails, use the fsutil method above per drive.

2. Quota errors during backup or migration
When moving data between drives, the quota file might get copied and create inconsistencies. Never copy the $Quota file directly. Instead, reset quotas after the transfer. Use fsutil quota to export/import quota settings (Google that for exact syntax) but skip copying the raw file.

3. System Volume Information corruption
In rare cases, the $Quota file is tied to shadow copies or restore points. If resetting quotas doesn't work, clean up System Volume Information using vssadmin delete shadows (careful—this wipes restore points). Then repeat the fix.

Prevention

Don't let disk quotas get too complex. Keep quota limits reasonable and avoid manually editing the quota file—Windows doesn't like that. Schedule regular chkdsk /f scans monthly on critical drives, and if you're messing with quotas via scripts, always back up the existing quota settings first using fsutil quota export. And for the love of it, never run third-party disk quota tools that aren't signed by Microsoft—they're notorious for corrupting $Quota files.