Moxnox 1.0 Released: A Windows NT-Inspired Open-Source Operating System
Moxnox is an experimental hobby OS that combines Windows NT-inspired low-level interfaces with POSIX-oriented software, Unix-style paths, and native Btrfs support.
A different take on the operating system
Moxnox 1.0 is not a Linux distribution and is not a Windows clone. It is an independent, open-source operating system built around an NT-like system-call design while aiming to run software ported from Unix-like environments.
NT-inspired interfacesPOSIX compatibilityBtrfsAMD64 + ARM64
Featured visual: Moxnox 1.0 and its NT-inspired, POSIX-oriented design. For social previews, also upload a separate 1200 × 675 px WordPress featured image.
Moxnox has its own kernel architecture; it is neither Linux nor a Windows reimplementation.
The system can build its own operating-system components, although some toolchain limitations remain.
No desktop GUI or mature security and multiuser model is available yet.
What Is Moxnox?
Moxnox is an open-source hobby operating system developed by Mark Harmstone, known for work on the WinBtrfs filesystem driver for Windows. Version 1.0 represents a major milestone for a project developed since 2022. The codebase is approximately 130,000 lines of C++ and targets AMD64 (x86-64) and AArch64 (ARM64) systems.
Its design takes inspiration from Windows NT system calls and low-level interfaces, while using Unix-style filesystem paths and aiming to support software written for POSIX environments after that software is recompiled. Moxnox uses the Portable Executable (PE) format for executables and libraries, with .exe and .dll extensions.
What Makes Moxnox Different?
Windows NT-inspired interfaces
The system-call contract and several low-level conventions are modeled after NT. However, Moxnox uses its own kernel design rather than trying to recreate Windows internally. Its filesystem namespace follows Unix conventions, with forward slashes, a root directory, and mounted directories.
POSIX-oriented application environment
Moxnox implements a substantial subset of POSIX functionality, including fork(), and includes a GNU-style base system. The developer reports implementing 642 of roughly 1,200 functions in POSIX 2024; software may need to be ported or recompiled, and compatibility is not complete.
Native Btrfs filesystem
The operating system uses Btrfs as its filesystem. This is a notable choice given the developer’s experience with WinBtrfs, but the Moxnox Btrfs implementation has not been battle-tested. The project explicitly warns users not to mount important data or anything other than disposable filesystems.
Self-hosting capability
Moxnox can compile its own operating-system components from within Moxnox. That is an important development milestone, although some tools and components—including parts of the GCC and Rust toolchain—still have limitations or require an external build environment.
Software and Hardware Support
Ported software
The project lists a growing collection of developer tools and command-line software, including:
- Bash and GNU Coreutils
- GCC and LLVM toolchain components
- Git, CMake, and Zstandard
- Python, Perl, and Rust-related tooling
- OpenSSH, OpenSSL, Vim, and Nano
Availability does not imply that every application or every feature works exactly as it would on Linux. Ports may be incomplete, and GCC is currently available only for x86-64.
Hardware and graphics
Moxnox includes support for selected storage devices such as NVMe, SATA, SD cards, USB mass storage, and VirtIO block devices. Networking includes VirtIO adapters and selected Realtek controllers. Input support includes USB HID and PS/2 keyboards and mice.
Graphics remain basic: framebuffer output, VirtIO GPU, GOP framebuffer, VBE, and VGA text-console functionality are listed, but there is no graphical desktop environment.
Limitations to Understand Before Testing
Moxnox 1.0 is a milestone release, not a production-ready operating system. The project’s own documentation identifies several important gaps:
- No graphical desktop: interaction is currently focused on console and framebuffer output.
- No mature security model: the project lists security mechanisms and multiuser/group support among missing features.
- Incomplete locale and keyboard support: time zones, multiple keyboard layouts, and broader locale handling are not yet implemented.
- Limited hardware support: drivers and supported devices are still evolving.
- Performance issues: the developer notes bottlenecks in memory allocation and networking, among other areas.
- Windows apps do not run: the presence of NT-inspired interfaces and PE-format binaries does not provide Win32 compatibility.
How to Try Moxnox 1.0 in QEMU
The simplest low-risk way to explore Moxnox is to use the prebuilt disk image and EFI kernel in a virtual machine. Download the appropriate artifacts from the official release page linked below, then follow the project’s current instructions for your architecture.
Download the official release
Open the Moxnox v1.0 release page and select the disk image and kernel matching your target architecture. Verify filenames and instructions against the release page.
Install QEMU and required virtualization support
Use a trusted package source for your host operating system. For best results, ensure your QEMU build supports the machine type and devices shown in the official README. The upstream example uses a Q35 machine for x86-64.
Follow the upstream QEMU command
The project README provides separate example commands for AMD64 and ARM64, including the kernel, disk image, VirtIO networking, and input devices. Copy the current command from the official documentation rather than relying on an unverified command snippet.
Explore only with disposable data
Test the console, supported tools, and self-hosting features in the VM. Do not attach production disks or personal data, and take snapshots where your virtualization software supports them.
Safety Recommendations
- Use a disposable virtual disk and avoid mounting valuable filesystems.
- Keep the VM isolated from sensitive networks and services.
- Do not assume production-grade access controls, isolation, or security hardening.
- Expect incomplete drivers, application compatibility, and performance.
- Read the current README and release notes before testing or installing on physical hardware.
Frequently Asked Questions
Is Moxnox a Linux distribution?
No. Moxnox is an independent operating system with its own kernel architecture. It borrows ideas from Windows NT and supports a POSIX-oriented software environment.
Can Moxnox run Windows applications?
Not currently. Its NT-inspired design and PE executable format do not mean that the Win32 APIs and DLLs required by normal Windows applications are available.
Does Moxnox have a graphical desktop?
No. Version 1.0 provides text-console and basic framebuffer graphics functionality, but no full desktop environment.
Is Moxnox suitable for daily use or production?
No. It is an experimental hobby operating system with significant gaps in security, multiuser support, drivers, and performance. Use it for research and isolated experimentation.
Where can I download Moxnox?
Use the official GitHub v1.0 release page and follow the project’s documentation.
Final Thoughts
Moxnox 1.0 is an intriguing operating-system experiment because it combines NT-inspired interfaces with POSIX-oriented software and Btrfs rather than attempting to become a Windows clone. Its self-hosting milestone makes it especially interesting to developers and OS enthusiasts. Still, the lack of a graphical desktop, incomplete security and multiuser support, limited hardware coverage, and unproven filesystem implementation mean that it belongs in a lab environment for now.
Explore the Moxnox Project
Read the developer’s documentation, review the source code, and download release artifacts directly from the official project.
References & Sources
Editorial note: Moxnox is experimental software. Features and compatibility may change; consult upstream documentation for the latest details before attempting installation.