Seeing 0xC019000B pop up when you try to resize the file system log is one of those errors that makes you want to throw something. I've been there — you're just trying to shrink the USN journal or tweak the log size, and Windows flat-out refuses. The good news is the fix is usually quick and involves one command.
The Fix: Clear and Rebuild the USN Journal
The real fix here is to delete the USN journal and let Windows recreate it. This is safe — the journal is just a change log, and deleting it doesn't touch your files. Here's what you do:
- Restart your PC and boot into Safe Mode. The quickest way: hold Shift while clicking Restart, then go to Troubleshoot > Advanced Options > Startup Settings > Restart, and press 4 for Safe Mode.
- Open Command Prompt as Administrator. In Safe Mode, right-click Start and pick Command Prompt (Admin).
- Type the following, replacing
C:with your drive letter:
fsutil usn deletejournal /d C:If that throws an error saying the journal is in use, you need to disable the System Restore service first. Run these two commands, then retry:
net stop vss
net stop swprvAfter the deletejournal succeeds, just restart normally. The journal will be recreated with a fresh default size, and you won't see that error anymore.
Why This Works
The 0xC019000B error means the log size you requested doesn't match what the file system expects. Usually, it happens because the USN journal has gotten corrupted, or there's a mismatch between the journal's current size and what the resize operation thinks it should be. Deleting the journal removes all that mismatch — no journal, no problem. Windows rebuilds it on reboot with clean defaults.
I've seen this happen most often after a failed disk cleanup tool or a third-party defrag utility tries to resize the journal without proper admin rights. Once the journal is corrupt, any resize attempt trips the error. Starting fresh is faster than trying to patch it.
Less Common Variations
Error on a Non-System Drive
If the error points to a data drive (like D: or E:), you might not need Safe Mode. Just close all programs that might be using that drive, then try the fsutil command with the correct drive letter. If it's an external USB drive, unplug it and plug it back in first.
Error During chkdsk
Sometimes 0xC019000B shows up when you run chkdsk /f. That's a different beast — it's the file system log itself that's corrupted, not the USN journal. The fix is to boot from a Windows installation USB, open Command Prompt (Shift+F10), and run:
chkdsk /f /r C:Wait for it to finish — this can take a while on large drives. If it still fails, you may need to run sfc /scannow from the same prompt after a reboot.
Error When Installing Windows Updates
In rare cases, this error appears during a Windows Update when the update tries to modify the NTFS log. The culprit is usually a pending file rename operation stuck in the USN journal. Clearing the journal with the fix above usually clears that too. If not, run DISM /Online /Cleanup-Image /RestoreHealth as admin, then restart.
Prevention Tips
You don't need to resize the USN journal often — most people never touch it. If you're doing it for performance reasons, I'll tell you straight: it's rarely worth it. The default size is fine for 99% of drives. If you use a tool that messes with journal sizes, stick to official utilities from Microsoft or the drive manufacturer.
Also, don't disable System Restore to save space — that's a common mistake that leads to filesystem weirdness down the road. If you're low on disk space, run the Disk Cleanup tool or uninstall bloatware instead.
Back up your important data before running any filesystem commands. Even though the fsutil delete is safe, I've seen people type the wrong drive letter and nuke a journal on the wrong disk — not catastrophic, but still a headache.
That's it. You should be past the error now. If you hit a wall, which Windows version are you on — 10 or 11? And is the error on your system drive or a secondary one? Drop a comment below and I'll help you out.