Despite the lack of an official release, the open-source community has not given up. Several GitHub projects and forum threads (on XDA Developers, Reddit r/windowsonarm, and the WoA Project) have attempted to create a Tiny10-like experience for ARM64.
The table below outlines the key differences between the two "Tiny" projects.
Unlike standard Windows 10 IoT Enterprise or the official Windows on ARM images, tiny10 is a custom modification. tiny10 arm64
Not all packages can be removed safely on ARM64. Trying to strip out the "Windows Defender" or "Cortana" packages often breaks the Start Menu on ARM builds.
Low-power ARM nodes running specific enterprise or display software benefit from a minimized attack surface and reduced background activity. The Trade-offs: Is it Safe and Functional? Despite the lack of an official release, the
The Arm64 ecosystem is fragmented. A Tiny10 image that works on a Raspberry Pi 4 (with its custom BCM2711 chip) will not boot on a Lenovo ThinkPad X13s (Snapdragon 8cx Gen 3). Unlike x86 PCs with standardized UEFI and ACPI, Arm64 devices often require device-tree blobs or custom firmware. Thus, "Tiny10 arm64" is not a single OS but a family of highly specific builds.
To help you get started with your lightweight ARM project, let me know: Unlike standard Windows 10 IoT Enterprise or the
Standard Windows 10 on ARM often struggles on older or low-tier processors due to high RAM usage and background processes. Tiny10 ARM64 solves this problem by drastically reducing the operating system's footprint, making it ideal for hobbyists, developers, and users reviving old hardware. What Makes Tiny10 ARM64 Different? Minimal System Footprint
Yes—but with important caveats.
Unlike many "lite" builds, Tiny10 is designed to pull security updates through standard Windows Update. tiny10 23H2 : NTDEV : Free Download, Borrow, and Streaming
Disclaimer: Tiny10 is an unofficial modification. Microsoft does not support it. Use at your own risk. Always respect software licenses and local laws.