What LiberNT actually is
ReactOS has spent decades reimplementing the Windows NT architecture so that Windows applications and drivers can run without Windows. IT-Connect notes the project began in the mid-1990s. It has long targeted much older Windows behavior, roughly the Windows Server 2003 era.
LiberNT builds on that code base and aims much higher. It targets compatibility with applications and drivers written for Windows 11 version 24H2. The project says Windows 11 is its behavioral reference. Interfaces and structures come from the Windows SDK and WDK headers and Windows 11 public symbols. Behavior comes from Microsoft documentation and black-box testing on Windows 11.
Some practical points about the project:
- Licensing: LiberNT is a GPL-3.0 ReactOS fork. Files inherited from ReactOS keep their own license terms.
- Independence: LiberNT presents itself as independent, with no affiliation to the ReactOS team or Microsoft.
- Origin: IT-Connect says the project was launched by Ahmed Arif, who maintains it with other contributors.
- Not Wine: Wine translates Windows API calls so Windows programs can run on Linux or macOS. LiberNT is a full operating system with an NT-style kernel.
What changes compared with ReactOS
The project's engineering documentation lists the main departures from ReactOS. The rest of the tree is still shared with ReactOS.
| Area | Documented LiberNT change |
|---|---|
| Memory manager | NVS, a clean-room NT10 memory manager with its own kernel pool |
| Cache manager | A separate clean-room implementation |
| ARM64 | A port covering the kernel, HAL and FreeLoader boot loader |
| RISC-V64 | A HAL port that is still in progress |
| 32-bit apps | WoW64 on every 64-bit target, with FEX running x86 code on ARM64 |
| Graphics | A WDDM graphics kernel and DWM desktop composition |
| File systems | A new NTFS driver and library, with the original driver still in the tree |
| Buses and boards | USB xHCI and SD bus drivers, plus Raspberry Pi drivers |
These are the project's own descriptions of its work. They don't show that each component is finished or ready for production. A listed build target also doesn't mean the hardware support is mature. The documentation itself calls RISC-V64 a port in progress.
The project says its setup tool lists drives the way Windows Setup does, manages partitions, and installs LiberNT on NTFS with an EFI system partition.
The Linux-app experiment
This is the part that drew the headlines. In IT-Connect's test, the Start menu had a "Linux Terminal" shortcut that opened an Ubuntu shell. IT-Connect reports that on first launch it downloaded Ubuntu 26.04 LTS packages from Canonical's servers. The reviewer likened the approach to the first version of WSL: no virtual machine and no Linux kernel, with LiberNT itself running the Linux programs.
Graphical Linux apps, such as GNOME applications, opened in their own windows on the LiberNT desktop. The limits are significant. These programs have no graphics acceleration and no sound.
Treat this as one tester's observation of an experimental feature. It doesn't establish general Linux compatibility, performance or security isolation. It also doesn't tell us how every app is handled internally.
What the hands-on test showed
IT-Connect tested LiberNT in Hyper-V, and the results show how rough the project still is.
- First attempt: Late in October, the VM rebooted in a loop.
- After fixes: IT-Connect says an early-November build booted in a Generation 2 Hyper-V VM. That needed a VHDX disk and Secure Boot disabled.
- Setup wizard: It asks for a computer name and an account. It then offers optional components, including Chrome, Firefox, Steam, Visual C++ runtimes and Wine components.
- Desktop: File Explorer has tabs, an address bar and context menus. The usual C: drive and System32 folder layout is present. Settings follows the Windows 11 structure but has fewer features. Notepad could create and save a text file. The package manager relies on WinGet.
The Secure Boot requirement comes from that specific Hyper-V test. It isn't a universal rule for all hardware or hypervisors. Also, a Chrome or Steam entry in the installer menu doesn't prove those programs install and run reliably.
For file-system and driver work, the project's own repository downloads include a Hyper-V Generation 2 disk image (VHDX), a VHD, a raw disk image and a bootable ISO.
Trying it, or building it yourself
The project recommends VMs or spare hardware. If you want to experiment, a virtual machine is the sensible place to start.
The repository also documents how to build it:
- You need Git, CMake, Ninja and a C/C++ compiler. The RosBE toolchain supplies the compilers used to build LiberNT.
- Linux and macOS are supported build hosts. On Windows, the project suggests WSL2. It also advises keeping the source inside the Linux file system rather than under the mounted Windows drive, because builds are slower there.
- The default
./configure.shsetup produces an AMD64 Debug build with Clang. The-aoption selects another architecture, and--releaserequests an optimized build. menuconfiglets you pick optional components, such as WoW64 and FEX.- Ninja targets can produce a bootable ISO, a preinstalled disk image or a VHD.
Building from source is a developer exercise. It isn't a supported end-user installation path.
AI-assisted code and the clean-room question
The project says AI helps write and review code. It also says human contributors review changes and run end-to-end tests. Its rules forbid leaked Microsoft source code and any transcription of decompiled Windows code. They also forbid copying GPL code from Linux. The project treats black-box observation of Windows 11 as its legal default.
These are the project's own statements. They aren't an independent legal assessment. Nothing here proves every contribution follows the process. Clean-room claims for operating systems tend to get scrutiny, and that is worth watching as the project grows.
Where it stands
Both Wccftech and IT-Connect stress that LiberNT is far from ready for daily use. Wccftech says the public builds are mainly Debug pre-releases, with incomplete app compatibility, limited driver support and possible stability problems. It also cites a pre-release dated October 30, 2026 that adds an optional ICU library for ARM64 application compatibility.
Project claims need the same caution. The repository says LiberNT has proven more stable and faster than ReactOS in CPU, memory and I/O handling. That is a comparison with its own upstream, made by the project itself. It says nothing about parity with Windows 11.
Some caveats on the Windows 11 framing:
- A Windows 11-style interface and a Windows 11 compatibility target don't make LiberNT Windows.
- Behavioral parity with Windows 11 is a goal, not a demonstrated result.
- Broad app, driver and gaming compatibility is unproven. Wccftech's comparison to Valve's Proton is fair in spirit, but Proton is a compatibility layer on Linux. LiberNT is trying to be the whole operating system.
IT-Connect adds a thoughtful warning. In trying so hard to look like Windows 11, the project should be careful not to inherit everything users dislike. It also suggests a lightweight, user-controlled "open-source Windows 11" could make sense.
The takeaway
LiberNT is an active, ambitious experiment in building an NT-compatible OS. It is not a Windows replacement or a Linux alternative you can rely on today. For Windows administrators and enthusiasts, it is worth watching as a technical curiosity. A Hyper-V VM and a spare afternoon will tell you more than any headline.
References
- LiberNT Aims To Recreate Windows 11 Without Microsoft, Offering An Open-Source Alternative That Even Supports Linux Apps - Wccftech Wccftech · 2026-11-17T12:07:11+00:00
- LiberNT: A ReactOS Fork Built Around Windows 11 indiekings.com
- AGENTS.md github.com