# Moxnox 1.0: Windows NT-inspired open-source OS debuts with POSIX, Btrfs, self-hosting

> **Key takeaway:** Moxnox 1.0 is a self-hosting, open-source operating system that uniquely combines Windows NT-style system calls and PE executables with Unix filesystem paths, POSIX APIs, and native Btrfs support.

**Published:** 2026-10-27T07:02:01+00:00 
**Source:** Linuxiac 
**Category:** distro-news 
**Canonical URL:** https://fosswire.org/news/moxnox-10-windows-nt-inspired-open-source-os-debuts-with-pos.html 

## Summary
Mark Harmstone, creator of the WinBtrfs driver for Windows, has released Moxnox 1.0, an experimental open-source operating system developed since 2022 as a hobby project. The OS occupies a distinctive architectural position: it employs Windows NT-inspired system calls and low-level interfaces, uses the Portable Executable format for binaries with .exe and .dll extensions, yet implements Unix-style filesystem paths, POSIX compatibility including fork(), and native Btrfs as its filesystem. The 130,000-line C++ codebase supports x86-64 (targeting x86-64-v3) and ARM64 (ARMv8.1+, including Raspberry Pi 5 with UEFI firmware) architectures.

Version 1.0 achieves self-hosting capability, allowing Moxnox to compile its own OS components without requiring Linux or Windows as a build environment, though GCC, Rust, and some other tools still cannot be built natively. The OS cannot run existing Windows applications despite its NT-inspired design; Wine porting remains theoretical. Hardware support covers NVMe, SATA, SD, USB mass storage, VirtIO block, selected Realtek and VirtIO networking, USB HID and PS/2 input, and basic framebuffer graphics including VirtIO GPU, GOP, VBE, and VGA text console. Significant limitations persist: no multiuser support, no security mechanisms, no graphical desktop, no time zones or broad locale support, and performance constraints in memory allocation and networking.

## Architecture and system design
- **Kernel architecture:** Moxnox implements its own independent kernel with Windows NT-inspired system calls and low-level interfaces, distinguishing it from both Linux distributions and Windows clones like ReactOS.
- **Binary format:** Executables use the Windows Portable Executable (PE) format with .exe and .dll extensions rather than Linux ELF, while the filesystem layout follows Unix conventions with POSIX-style paths.
- **POSIX compatibility:** The system supports Unix APIs including fork(), which is absent from traditional Windows, and has ported Bash, GNU Coreutils, Git, Python, Perl, OpenSSH, OpenSSL, Vim, Nano, and other development tools.
- **Btrfs integration:** Native Btrfs support leverages Harmstone's WinBtrfs expertise, though the implementation is warned as untested and suitable only for disposable filesystems.
- **Self-hosting milestone:** Moxnox can compile its own operating system components internally, though GCC (x86-64 only) and Rust still require cross-compilation from external build environments.

## Why it matters
Moxnox represents a rare independent open-source kernel project that challenges conventional OS taxonomy, potentially attracting researchers and developers interested in hybrid NT/Unix architectures. Its self-hosting achievement and toolchain ports demonstrate viability for further expansion, while its Btrfs-first approach and ARM64 support (including Raspberry Pi 5) position it as an unusual platform for storage and embedded experimentation. However, its experimental status and missing security foundations limit immediate practical deployment beyond academic and hobbyist exploration.