
A software project is trying to answer a question that usually ends in a shrug: what would a desktop operating system look like if it imitated Windows 11 but owed nothing to Linux? The effort, called Impossible OS, is being assembled from the ground up and targets its first public release on August 8, 2028. Its developers describe the current build as pre-alpha, capable of booting on real hardware and displaying a desktop, but not yet suitable for daily use.
- Key Point: Impossible OS is written from scratch, including a custom UEFI bootloader and a 64-bit symmetric multiprocessing kernel, rather than being derived from Linux or another existing system.
- Key Point: Win32 serves as the native application programming interface, with file paths styled like C:\Impossible\System32\ and a desktop that closely follows Windows 11, described as having slightly frostier glass.
- Key Point: Linux binaries are planned to run through a compatibility layer rather than a renamed POSIX interface, extending the system’s reach without making Linux its foundation.
- Key Point: The project is pre-alpha and targets a first public release on August 8, 2028.
Building an OS from a blank page
The name is a nod to the skepticism that greets anyone proposing a new general-purpose operating system. The developers say they were told that creating a fully functional, feature-rich OS from scratch could not be done, so they named the project after the challenge. Everything, they say, is written from the ground up: a hand-written bootloader, the kernel, a compositing desktop and the layers in between.
The boot path is deliberately unconventional. A hand-written PE/COFF application handles startup with a versioned boot information interface, A/B rollback and a boot menu, and the project notes that it does not rely on GRUB. Secure Boot support is in progress: shim chain-loading has been implemented, but no shim is pinned while the transition around Microsoft’s UEFI CA 2011 settles.
Below that sits a 64-bit SMP kernel with long mode, APIC timers, per-CPU data, guard-paged stacks and structured exception handling. Preemptive multitasking uses a flat round-robin scheduler across all runnable threads, supported by mutexes, semaphores and seqlocks. Virtual memory covers four-level paging, swap and pagefile, mmap and clock page replacement.
What already runs, and what is still missing
Storage and filesystems are listed as shipped, with AHCI and VirtIO drivers using DMA, GPT and MBR partition support, FAT32 and a homegrown filesystem called IXFS sitting behind a virtual filesystem layer. Networking is present through an RTL8139 driver, Ethernet, ARP, IPv4, ICMP, UDP and DHCP. A compositing desktop handles dirty rectangles, acrylic and mica materials, drop shadows and TrueType text. The registry is a hierarchical key-value store that persists to disk, and ACPI support comes from a vendored ACPICA with a kernel services layer.
Several pieces remain works in progress. TPM measured boot has transport, PCR measurement, sealing and attestation underway. The Win32 API surface is being built through the SSDT, with ntdll and the Win32 subsystem layered on top. The Windows 11 shell, including a centered taskbar, Start menu and redesigned system icons, is also unfinished. NTFS, TCP and USB are marked as planned, each with its own roadmap file.
Development discipline is unusually explicit for a hobby-scale project. The roadmap spans 235 planning files across 18 domains, and 3,760 kernel test suites containing 17,663 assertion sites run after every commit. The project states a bare-metal-first philosophy: virtual machines are for fast iteration, but a feature counts as done only when it works on real hardware. Symmetric multiprocessing was built in from day one, with per-CPU data and real locking, so there is no big kernel lock to remove later.
Who can build it, and what comes next
Building the system requires a Linux environment. Ubuntu or Debian 24.04 and later, WSL2 with Ubuntu, GitHub Actions runners and the committed development container are fully supported; Fedora and Arch are best-effort and need the LLVM-19 and OVMF shim described in the host bootstrap contract. Native Windows and macOS are unsupported, with WSL2 recommended for Windows users. Builds run through project scripts rather than raw make, and a successful build ends with a confirmation line in the build log. Disk images are published for QEMU, USB sticks and VirtualBox.
The gap between a booting pre-alpha and a usable desktop is wide, and the 2028 date leaves room for the unfinished shell, Win32 surface and Secure Boot work to mature. For now, Impossible OS is less a product than a statement of intent: that a Windows-compatible desktop can be built without Linux as its skeleton. Whether developers and users embrace that premise will depend on whether the project can deliver a working system on schedule.
