30 years of dev experience, never enough free time. I always wanted a proper ext4 driver on Windows and never had eight weeks to spare to write one. Turns out with Claude doing the typing, I needed about three hours.
Before anyone rolls their eyes: "AI wrote it" usually means nobody understood it. That's not what happened. I know how to code. Claude knows the manuals — ext4 on-disk layout, WinFsp, MBR/GPT, the SCM dispatcher — in a way nobody carries in their head. My job was telling it what it got wrong, which spec section it misread, which bug to chase, what the test suite needed to prove. A lot of "no, re-read section 4.2, that field is little-endian." It works because I knew what wrong looked like, not because the model is magic.
⚠️ Heads up: this isn't a finished product yet. It's read/write — yes, it really does write to your ext disk, and yes, that means a bug can corrupt it. Back your data up first. Beta quality: works well in practice, but you're still the QA team.
That said: in daily use it's been solid. I've never lost a disk to it, including on the write path. I think it's a marriage of three things: the ext3/4 journal catches anything that goes sideways before it becomes corruption, Rust makes it hard to be sloppy with the on-disk structures (no accidental field mis-sizes, no UB, no "oh I forgot that case"), and the spec ties it together — if you follow it correctly, the FS does what it's supposed to do. Plug in a Linux USB on Windows, it shows up as a drive letter, you read and write like any other drive.
I actually use this every day. I work on a Raspberry Pi project, and the typical setup is SD cards bouncing between the Pi, Windows, and Mac. I'm on Mac, a developer I work with is on Windows — so I built an ext4 driver for me and one for him. This isn't a hobby I'll lose interest in next month; making it rock solid is in my own self-interest.
Two repos:
ext4-win-driver — the driver itself. Read/write ext2/3/4, auto-mounts on plug-in.
winfsp-fs-skeleton — want to build your own Windows FS driver? Start here. I pulled all the WinFsp boilerplate (service, disk-arrival watcher, partition parsing, raw I/O, MSI installer, CI) into a reusable skeleton. Plug in a detect() and a winfsp-rs FileSystemContext and the Windows side is done. FAT, XFS, btrfs, ZFS, HFS+, APFS, your weird hobby FS — go.
It's Rust, but you're not locked in. If your existing FS code is C or C++ (most reference implementations are), build it as a library with a C ABI and link it from the FileSystemContext. Rust does C FFI fine. Keep your battle-tested parser, write the Windows glue once.
And Rust is a genuinely good fit for working with an LLM. The compiler doesn't let trivial mistakes slide — no nulls, no implicit conversions, exhaustive matches, lifetimes. The "looks plausible, crashes at 3am" class of AI-generated C bug just doesn't survive cargo build. The borrow checker is a much harsher code reviewer than I am, and it never gets tired.
GPL-3 (WinFsp is, so anything linking winfsp-rs ends up GPL anyway).
I'm posting because I want testers. Bug reports, crashes, "it mounted the wrong partition on my 16TB array", "it scrambled my journal" — all welcome. Especially interested in weird setups: LVM, encrypted volumes, ext4 with unusual feature flags. If you've only got one copy of the data, please don't be the first person to find a bug. Spare USB stick or a disk image.