Project Samples

Project Activity

See All Activity >

Follow Lindows OS

Lindows OS Web Site

Other Useful Business Software
$300 Free Credits to Build on Google Cloud Icon
$300 Free Credits to Build on Google Cloud

New customers can spin up VMs, build with AI, and query data at no cost.

Put your $300 in credit toward real workloads, then keep building with free monthly usage for 20+ products. No commitment and no charge until you upgrade.
Start Free
Rate This Project
Login To Rate This Project

User Ratings

★★★★★
★★★★
★★★
★★
★
5
0
0
0
0
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5

User Reviews

  • 5 out of 5 stars
    Awesome I,m downloading now beta 5.2 iso is 5.8GB. Good luck
  • 5 out of 5 stars
    Very Impressive.
  • 5 out of 5 stars
    It is so cool to have Lindows back! I customized it a lot so that it looks just like the original Version 4.5. Keep up the good work and good luck bringing Lindows back!
    1 user found this review helpful.
    Reply from Lindows OS
    Edited 2026-10-24
    Thank you for the 5 start review. It would be nice to keep those Windows style icons and logos, but as the project draws more attention, we cannot keep using Microsoft copyrighted material in the OS. However, we are trying to use something as close as possible in it's place.
  • 5 out of 5 stars
    One AWESOME project.
    1 user found this review helpful.
  • 5 out of 5 stars
    Hello! Thank you for your work on Lindows. I ran into a boot problem and wanted to share what helped. I tried lindows-v5-fenix_x86-64_beta4.4.iso on both BIOS and UEFI computers. Neither the normal boot option nor nomodeset worked. After rebuilding the image with GRUB for BIOS and UEFI, all boot options worked. The original kernel, initrd and squashfs were kept unchanged. One possible issue is set root=(cd0) in the original UEFI menu. This assumes the boot medium is a CD-ROM, which is unreliable when booting from USB. A safer approach is to find the medium using a unique marker file. For example, create an empty .lindows-live file in the ISO root and use: search --no-floppy --file --set=root /.lindows-live The kernel and initrd can then be loaded from /live/vmlinuz and /live/initrd, without hardcoding a device. The other original menu entry searches by the LINDOWSLIVE volume label, so that label must be preserved if this method is used. For rebuilding, I used grub-mkrescue with both the i386-pc and x86_64-efi modules installed. I did not isolate the exact BIOS failure, but rebuilding the boot structure resolved it too. I hope this helps with the next release. Thank you, and good luck with the project!
    2 users found this review helpful.
    Reply from Lindows OS
    Posted 2026-10-20
    Thanks for letting know and and the complimentary review! Beta 4.6 is now uploaded and hopefully fixes the issue
Read more reviews >

Additional Project Details

Registered

2026-10-09