Fix ERROR_LOG_METADATA_FLUSH_FAILED 0X000019F5

Quick Answer

Run chkdsk /f /r on the system drive from an elevated Command Prompt, then restart. That fixes 90% of cases.

Why This Happens

ERROR_LOG_METADATA_FLUSH_FAILED (error code 0X000019F5) shows up when Windows tries to write metadata from the NTFS log to disk and fails. The metadata is the table of contents for your file system — it tracks changes before they're committed. If the drive drops a write or returns a bad status, the log flush fails.

I've seen this most often on systems where the disk had bad sectors, the SATA cable was loose, or the system had a sudden power loss. It can also hit if you're running Windows 11 with an older driver for a RAID controller or SSD. Think of it as Windows saying "I couldn't save my notes about what I just changed."

The event log usually shows Event ID 667 from source Ntfs — you can check it in Event Viewer under Windows Logs > System. If you see that ID with the error code, you're in the right spot.

Fix Steps

1. Open Command Prompt as Administrator
   Press Win + X, select "Command Prompt (Admin)" or "Terminal (Admin)".
2. Run chkdsk on the system drive
   Type chkdsk C: /f /r and press Enter. The /f flag fixes errors, /r locates bad sectors and recovers readable info. This will ask to schedule a scan on next boot — press Y and restart the machine.
3. Let the scan complete
   Windows will boot into a blue screen with white text showing the scan progress. It can take 30 minutes to a couple hours on a large drive. Let it run. Don't interrupt it.
4. After restart, check the event log
   Open Event Viewer, go to Windows Logs > System. Filter by source Ntfs and look for Event ID 667 or 55. If you see no new errors, the fix worked.
5. Run SFC scan for system file health
   In Command Prompt (Admin), type sfc /scannow. This checks protected system files. If it finds corruption, run DISM /Online /Cleanup-Image /RestoreHealth next, then SFC again.

Alternative Fixes

If chkdsk didn't clear the error, try these:

• Check disk health with CrystalDiskInfo
  Download CrystalDiskInfo (free portable version). Open it and look at the "Health Status" field. If it says "Caution" or "Bad" — especially with reallocated sectors or bad sector counts — the drive is failing. Back up immediately and replace the drive.
• Update your storage drivers
  Go to your motherboard or laptop manufacturer's site. Download the latest SATA, AHCI, or NVMe drivers. For Windows 11, also check for Intel RST (Rapid Storage Technology) driver updates. Old storage drivers sometimes lose writes on high-load flushes.
• Disable write caching on the drive
  Open Device Manager, expand Disk Drives. Right-click your drive, select Properties. Go to the Policies tab. Uncheck "Enable write caching on the device". This slows writes slightly but prevents the error if the drive is flaky.
• Clear the NTFS log (advanced)
  If chkdsk passed but the error persists, you can force a log reset. Boot from a Windows installation USB. Open Command Prompt (Shift + F10). Run chkdsk C: /f /x — the /x flag dismounts the volume first, then fixes the log. This is rare, but I've used it on stubborn systems.

Prevention Tips

Once you've fixed the current error, avoid it coming back:

• Use a UPS
  Power loss during a write is the most common trigger. A $40 UPS keeps the machine running long enough for a clean shutdown.
• Run chkdsk quarterly
  Schedule it every 3 months. On Windows 10/11, you can use Task Scheduler to run chkdsk C: /f after a reboot once a quarter.
• Keep your storage firmware updated
  NVMe SSDs and some SATA SSDs have firmware fixes for write flush bugs. Check your drive manufacturer's support page (Samsung, WD, etc.) every 6 months.

If you see this error on a system that also has random blue screens or freezes, don't trust the drive — replace it. I've chased this error across three rebuilds only to find the SSD had a bad controller. Sometimes hardware is just done.