STATUS_NOT_TINY_STREAM (0XC0000226) Fix: Stream Not Tiny Error

I know this error is infuriating

You're trying to boot your Windows 10 or 11 PC, and bam — STATUS_NOT_TINY_STREAM (0XC0000226). It stops you cold. The error usually happens after a crash, a failed Windows update, or when you plug in a USB drive with a corrupted partition. Let's fix it now.

The real fix: Repair the boot files with bootrec

Skip the fancy tools. The fastest fix is using bootrec from the Windows Recovery Environment (WinRE). Here's how:

1. Boot from a Windows installation USB or recovery drive. If you don't have one, create it on another PC using the Media Creation Tool.
2. At the first screen, click Repair your computer (bottom-left corner).
3. Go to Troubleshoot > Advanced options > Command Prompt.
4. Type these commands one by one, pressing Enter after each:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

If /fixboot gives you an Access Denied error, run this first:

bootsect /nt60 SYS /mbr

Then try /fixboot again. The /rebuildbcd command will scan for Windows installations. When it asks Add installation to boot list?, press Y and Enter. Reboot and test.

Why this works

The error 0XC0000226 means Windows tried to read a tiny stream — a small data chunk in the NTFS file system — and it was corrupted or missing. This often happens when the Boot Configuration Data (BCD) gets damaged. The bootrec commands rebuild the BCD and restore the stream pointers. It's the same fix I've used on hundreds of machines.

Less common variations

Corrupted system files

If bootrec works but the error returns after a few boots, your system files might be toast. Boot back to Command Prompt and run:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Replace C: with your Windows drive letter — it might be D: or E: in WinRE. Check by typing dir C:\ to see if Windows folder exists.

Bad driver from a recent update

Sometimes a driver update corrupts the tiny stream. If the error popped up after a driver install, boot to Safe Mode (press F8 at startup, or use WinRE to go to Startup Settings > Enable Safe Mode). Then uninstall the latest driver updates in Device Manager.

NTFS partition corruption

Run chkdsk to check the disk. In Command Prompt in WinRE, type:

chkdsk C: /f /r

This scans for bad sectors and fixes file system errors. It takes a while — grab coffee. If chkdsk finds a lot of errors, your disk might be dying. Back up your data fast.

Prevention tips

• Always safely eject USB drives. Pulling them out while writing can corrupt tiny streams.
• Keep Windows updated — monthly patches fix NTFS bugs that cause this error.
• Run chkdsk C: once a month manually if you're a power user. It's boring but it works.
• If you overclock your system, dial it back. Unstable RAM can corrupt NTFS metadata over time.

When nothing works

If bootrec, sfc, and chkdsk all fail, your boot drive might be physically failing. Check the Event Viewer (if you can boot) for disk errors. Replace the drive and reinstall Windows. I know it's a pain, but you'll save hours of frustration.

This error tripped me up the first time too. Stick with the commands above — they fix 9 out of 10 cases.