LiberNT Explained: Experimental ReactOS Fork Targeting Windows 11 Compatibility

What LiberNT is, and what it isn't​

Linuxiac reports that LiberNT is an alternative implementation of the Windows NT architecture, with Windows 11 version 24H2 as its compatibility reference. It doesn't use the Linux kernel. It builds on the ReactOS codebase while replacing and extending several core components.

The project's own repository describes NT as the architecture behind every modern version of Windows, covering its kernel, driver model and system services. It calls Windows 11 the reference the project measures itself against. The repository also shows LiberNT as a fork of the upstream ReactOS repository.

"Compatibility target" is the right way to read this. LiberNT is not a Microsoft product and not a Windows installation. It is not a drop-in replacement either. A separate downstream fork, StratumOS, says in its README that it hasn't yet reached Windows 11 compatibility levels, though it is getting closer. That is a fork of a fork rather than LiberNT itself. It still shows how even derivative projects describe the gap.

Platforms: 64-bit first​

The LiberNT README says its kernel, HAL and FreeLoader run on amd64, arm64 and riscv64, with a "64-bit first" emphasis. Linuxiac says ARM64 support is a main priority, particularly for single-board computers and embedded devices.

Linuxiac also says 32-bit x86 is supported and that RISC-V and PowerPC ports are still in development. The project's repository headline lists only amd64, arm64 and riscv64. Treat the 32-bit and PowerPC claims with some caution. Check which images are actually published for your target before you plan around any architecture.

Clean-room claims​

The developers say they follow a clean-room approach. They study Windows behavior through Microsoft's public documentation, SDK and WDK headers, public symbols and black-box testing. They state that no proprietary Windows code is copied or transcribed. A fork's README adds that test results are compared check by check with the same tests run on Windows 11.

These are the project's own statements. No independent audit or legal finding backs them up. The repository also discloses that AI tools help with writing and reviewing code. It says humans review that work and validate it before changes reach the main branch.

Technical changes claimed​

According to Linuxiac, the notable changes include:

• NVS, a new memory manager and kernel pool implementation that replaces the ReactOS equivalents.
• A new cache manager. The developers claim it beats the original ReactOS memory manager in their own memory and cache benchmarks.
• A new NTFS driver, an updated StorPort with NVMe support, USB xHCI and SD bus drivers, and work on the Windows Display Driver Model and Desktop Window Manager.

The README backs the broad areas of work, listing PCIe, PCI, Plug and Play, USB with xHCI, SD/eMMC, and storage and bus drivers. I found no published benchmark figures or independent reproductions. Read the performance claims as developer assertions.

LiberNT Setup is also described. It lists drives the way Windows Setup does, can create, delete, format, shrink and extend partitions, and installs LiberNT on NTFS with the EFI system partition it needs. That ties in with ReactOS's recent NTFS installation work, which Linuxiac covered separately.

App compatibility: five entries​

Linuxiac says the developers' compatibility page already shows early results. Chrome, the strategy game 0 A.D. and Command & Conquer: Yuri's Revenge are reported to work. Steam is listed as usable. The RPCS3 emulator starts but isn't classified as usable.

The caveat matters. The database holds only five entries, all tested against one specific development build. That is a small sample from one build, and it does not show that Windows software broadly works.

On 64-bit targets, LiberNT implements WoW64. ARM64 systems use the FEX emulator to run x86 applications, and ARM64EC support is part of the project. The README describes the graphics driver model with Mesa, and WoW64 with FEX, as build options you can switch on. A feature being part of the project does not mean every downloadable image has it enabled or that it works reliably.

Raspberry Pi and board support​

The README lists real board support, including the Raspberry Pi and its RP1 I/O controller. Linuxiac adds that one ARM64 disk image is designed to boot on Raspberry Pi 3, Raspberry Pi 5 and generic ARM64 QEMU virtual machines. It also says the project includes Raspberry Pi display, networking and audio drivers. I couldn't confirm per-model reliability, so read this as what the project targets, not a guarantee.

Trying it safely​

The README describes three build outputs:

The project's materials recommend trying the preinstalled disk first. Linuxiac says the developers warn that the builds are experimental and belong in a VM or on spare hardware, not on production systems.

A sensible approach:

1. Start with a VM. Hyper-V or VirtualBox with the VHD is the lowest-risk route on a Windows host, and QEMU suits the ARM64 image.
2. Don't point the raw image at a drive you care about. Writing it to USB or SD erases the target device, so double-check the device before you write.
3. Treat Setup as destructive. It can delete or format partitions, so back up first or use a disposable machine.
4. Expect debug builds. The project's own releases are Clang Debug pre-releases, so don't judge performance from them.

Reality check​

ReactOS has spent years chasing Windows compatibility, and LiberNT bets that a more aggressive rewrite of core components will close the gap with modern NT faster. The architecture list is ambitious. The evidence so far is a handful of developer-run app tests on one build, plus unverified benchmark claims.

For Windows enthusiasts, it's a fascinating project for ARM64 boards and driver-model work. For anyone needing a working Windows 11 environment, it isn't there yet. Watch for a larger compatibility database, independent testing and reproducible benchmarks.