How to Install Bliss OS on PC: 13 Steps, 90 Min [2026]

Windows Subsystem for Android is gone. Microsoft pulled the plug on WSA in 2025, and by 2026 there is no built-in way to run Android apps on a Windows PC without a third-party tool. That gap is why searches for Bliss OS, the open-source x86 build of Android that installs directly on PC hardware, have held steady near 4,400 a month even as the project’s public PC images sit frozen. This guide walks through every practical way to get Bliss OS running today: inside VirtualBox, inside VMware Workstation Player, from a bootable USB stick, or as a full dual-boot partition alongside Windows 11. Alongside Bliss OS, actively maintained options like Waydroid on Linux and Google’s own Google Play Games for PC beta have also emerged as legitimate ways to run Android software without WSA, and this guide notes where each fits below.

Unlike app-player emulators such as BlueStacks or NoxPlayer, which run Android inside a Windows process, Bliss OS is a complete operating system built on the Android-x86 project. It boots on real hardware, claims the whole screen, and behaves like a tablet-sized version of Android running natively on your CPU and GPU. That distinction matters for anyone who wants lower overhead than a virtualized app player, a lightweight OS for an aging laptop, or a lab environment for testing Android apps outside a phone. This tutorial covers prerequisites, download choices, three separate install paths, first-boot configuration, performance tuning, and the troubleshooting steps that come up most often on the Bliss OS forums and Discord.

·

Google · Preferred Sources

Don't miss new tech stories on Google

Add Tech Insider once in the Google app and our stories appear in your news suggestions.

Add Now

What Bliss OS Actually Is (and Why Its PC Builds Are “Paused” in 2026)

Bliss OS is a free, open-source operating system that packages Android for x86 and x86_64 hardware. It descends from the Android-x86 project but adds a custom shell, extra security toggles, and broader device support developed by the BlissRoms team, the same group that ships Bliss ROM builds for phones and tablets. On a PC, Bliss OS can run as a live USB session, a permanent dual-boot install next to Windows, or a guest OS inside VirtualBox or VMware.

Here is the part every 2026 tutorial needs to be upfront about: the official Bliss OS development status page confirmed on October 3, 2026, that public images remain paused, with no official ISO available yet from any of the newer source trees and no ETA given for the next public build. The project’s GitHub organization confirms three active source trees as of August 2025, BlissOS 16 (Android 13), BlissOS 17 (Android 14), and BlissOS 18 (Android 15), but none of those newer trees has shipped as a downloadable PC ISO as of this writing. The most recent widely distributed PC build that people are actually installing right now is Bliss OS 16.9, based on Android 13, packaged as a roughly 2.2 GB ISO, Tech Insider’s own testing as of September 3, 2026 confirmed it remains the most widely installed Bliss OS build available for PC. It is not a 2026-dated release, but it is the current, working, community-supported entry point, and it is what this tutorial is built around.

Development has not stopped. The Bliss OS documentation site was last updated August 26, 2026, with fresh build guides for Bliss OS 14.x, and most recently on October 2, 2026, with clarified PC installation requirements covering TPM, Secure Boot, and partitioning (the specifics are in Step 6 and Step 7 below). The related BlissRoms phone project shipped its v19.6 “Waterlily” build on June 10, 2026, running Android 16. Public images have been paused since August 2026, and development reportedly continued on a new installer, kernels, and device trees, but no release date was provided. The PC track is simply waiting on documentation, mirrors, and testing before the team ships a new public image. If you are setting up Bliss OS today for gaming, app testing, or a lightweight PC install, you are working with 16.9, and that is a completely reasonable, stable starting point.

Prerequisites and System Requirements

Bliss OS does not publish a strict numeric spec sheet the way a commercial app does, but the project’s own SourceForge listing confirms it targets “PCs, MacBooks and Chromebooks equipped with x86/x86_64 compatible CPUs” with both BIOS/CSM and UEFI boot support. Combined with real-world community installs, the practical minimums look like this.

Component	Minimum	Recommended for gaming
CPU	64-bit x86/x86_64, any 2015+ Intel/AMD chip	4+ cores with VT-x or AMD-V enabled
RAM	4 GB	8 GB or more
Storage	8 GB free (ISO is ~2.2 GB)	32 GB+ free SSD space
GPU	Any GPU with basic OpenGL ES support	Dedicated GPU with current drivers for 3D games
Boot mode	UEFI or Legacy BIOS/CSM	UEFI with Secure Boot and TPM disabled
USB drive (for install media)	4 GB	8 GB or larger, USB 3.0

You will also need a couple of free tools before you start:

• Rufus (rufus.ie) for building a bootable USB installer, if you plan to dual-boot or run Bliss OS live off a stick
• VirtualBox 7.x or VMware Workstation Player 17.x if you would rather run Bliss OS as a virtual machine with zero risk to your existing Windows install
• A downloaded Bliss OS 16.9 ISO from the official site or its SourceForge mirror
• A full backup of anything important on the target drive, since the dual-boot path repartitions your disk

Step 1: Pick Your Installation Method

There are three realistic ways to run Bliss OS on a Windows PC in 2026, and picking the right one up front saves a lot of backtracking.

• Virtual machine (VirtualBox or VMware) — safest option, zero partitioning risk, easy to delete if it does not work out. GPU acceleration is limited, so it is best for app testing and light gaming rather than demanding 3D titles.
• Live USB — boot Bliss OS straight from a USB stick with no install at all. Nothing touches your hard drive. Performance depends on USB read speed, and changes are not always saved between sessions unless you use a persistent-storage build.
• Dual-boot install — Bliss OS lives on its own partition and boots through GRUB alongside Windows. Best raw performance and full GPU access, but it is the option with the most steps and the most risk if a partition step goes wrong.

This tutorial covers all three, starting with the safest path (VM) and working up to the most involved (dual-boot). If you only want to try Bliss OS once, start with VirtualBox. If you want it as a daily driver for Android gaming, skip ahead to the dual-boot section.

Step 2: Download the Right Bliss OS Build

Head to blissos.org and open the download section, or go directly to the BlissOS-x86 project on SourceForge, which mirrors the official images. You will see a few naming conventions that matter:

• gapps / opengapps — includes Google Play Services and the Play Store pre-installed. Pick this if you want to install apps and games from Google Play.
• foss — no Google apps or services at all. Smaller download, more privacy-friendly, but you will need to sideload APKs manually.
• x86_64 — the build you want for any modern PC; 32-bit x86 builds exist but are legacy and not worth using in 2026.

For a gaming-focused setup, download the current Bliss OS 16.9 GApps x86_64 ISO. As of Tech Insider’s September 3, 2026 testing, it is still the most widely installed Bliss OS build and weighs in around 2.2 GB, so plan for a few minutes on a typical broadband connection. After the download finishes, verify the file size roughly matches what the download page lists, since a truncated ISO is the single most common cause of a failed boot later in this process.

Step 3: Install Bliss OS in VirtualBox

This is the fastest way to get Bliss OS running with no risk to your existing Windows setup. Install VirtualBox if you have not already, then create a new VM.

REM Run from an elevated Command Prompt with VirtualBox's VBoxManage on PATH
VBoxManage createvm --name "BlissOS16" --ostype "Linux_64" --register
VBoxManage modifyvm "BlissOS16" --memory 4096 --cpus 4 --vram 128
VBoxManage modifyvm "BlissOS16" --graphicscontroller vmsvga --accelerate3d on
VBoxManage modifyvm "BlissOS16" --ioapic on --boot1 dvd --boot2 disk
VBoxManage createhd --filename "BlissOS16.vdi" --size 32768
VBoxManage storagectl "BlissOS16" --name "SATA Controller" --add sata --controller IntelAhci
VBoxManage storageattach "BlissOS16" --storagectl "SATA Controller" --port 0 --device 0 --type hdd --medium "BlissOS16.vdi"
VBoxManage storageattach "BlissOS16" --storagectl "SATA Controller" --port 1 --device 0 --type dvddrive --medium "Bliss-v16.9.7-x86_64-OFFICIAL-gapps.iso"

If you prefer the GUI instead of the command line, the settings are the same: 4 GB RAM, at least 2 CPU cores, 128 MB video memory, 3D acceleration enabled, and a 32 GB virtual disk on a SATA controller. Boot the VM, choose the “Installation” option from the Bliss OS boot menu (not “Live”), and let the installer create an ext4 partition on the virtual disk. Reboot once it finishes, remove the ISO from the virtual optical drive, and Bliss OS boots straight into the Android home screen.

Step 4: Install Bliss OS in VMware Workstation Player

VMware Workstation Player is a solid alternative if you already use it for other virtual machines, and in some cases it handles Bliss OS’s graphics driver better than VirtualBox does. Create a new VM, choose “I will install the operating system later,” and set the guest OS type to “Other Linux 5.x kernel 64-bit.” Attach the Bliss OS ISO, allocate at least 4 GB RAM and 2 CPU cores, and enable “Accelerate 3D graphics” under the Display settings before you boot.

# Optional: launch a headless Bliss OS VM from the command line once configured
"C:\Program Files (x86)\VMware\VMware Player\vmrun.exe" start "C:\VMs\BlissOS16\BlissOS16.vmx" nogui

Boot into the installer the same way as in VirtualBox: select “Installation,” format the virtual disk as ext4, install the GRUB bootloader when prompted, and reboot. VMware tends to need one extra step for smooth video: after first boot, go into Settings, disable “3D acceleration on the virtual disk” if you see graphical corruption, and re-enable it after installing VMware Tools equivalents through the Bliss OS display settings.

Step 5: Build a Bootable USB Installer With Rufus

If you want to try Bliss OS live, without touching a virtual machine or your hard drive, a bootable USB is the way to go — and it is also the first step toward a full dual-boot install later. Download and open Rufus, insert a USB drive of at least 8 GB, and configure it as follows.

1. Select your USB drive under “Device”
2. Click “Select” and choose the Bliss OS ISO you downloaded
3. Set “Partition scheme” to GPT for UEFI systems (or MBR for older Legacy BIOS machines)
4. Leave “File system” on FAT32
5. Click “Start” and choose “Write in ISO Image mode” when Rufus prompts you

Rufus takes three to eight minutes depending on USB speed. When it finishes, you have a drive that will boot straight into the Bliss OS menu on any UEFI-capable PC, letting you try the live environment before committing to an install.

Step 6: Prep Your PC for Dual-Boot

Before you boot from that USB drive with the intention of a permanent install, four BIOS/UEFI settings need to change on most modern laptops and prebuilt desktops. The official Bliss OS documentation was updated on October 2, 2026, to spell these out explicitly as installation requirements rather than optional tweaks.

• Disable Secure Boot. Bliss OS’s bootloader is not signed for Microsoft’s Secure Boot chain, so leaving it on will block the USB from booting at all on most systems.
• Disable TPM. The October 2026 documentation update lists TPM as a setting to turn off alongside Secure Boot. If Windows 11’s TPM 2.0 requirement previously had you enable it in UEFI firmware, go back in and switch it off before installing.
• Set SATA mode to AHCI if your BIOS defaults to RAID or Intel RST — the Android-x86 kernel Bliss OS is built on does not include RAID storage drivers.
• Disable Fast Boot / Fast Startup in Windows itself (Control Panel > Power Options > Choose what the power buttons do), since it can leave the Windows partition in a hibernated state that confuses a dual-boot GRUB menu.

Double-check all four settings before booting the installer. Secure Boot and TPM both live in the same UEFI security menu on most motherboards, so it is easy to toggle one off and miss the other.

Step 7: Partition Your Disk and Run the Installer

Before booting the USB installer, shrink your existing Windows partition to free up space for Bliss OS. Open Disk Management in Windows (right-click the Start button), right-click your main C: drive, choose “Shrink Volume,” and free up at least 32 GB of unallocated space.

Reboot, enter your boot menu (usually F12, F10, or Esc depending on manufacturer), and select the USB drive. From the Bliss OS boot menu, choose “Installation.” The installer will show your disk’s partitions. The official documentation, updated October 2, 2026, now specifies a two-partition layout: a dedicated 512 MB EFI partition plus a larger partition formatted as ext4 for the OS itself.

# Inside the Bliss OS installer, at the partition selection screen:
# 1. Select the unallocated free space you created in Windows Disk Management
# 2. Choose "Create/Modify partitions" -> cfdisk opens
#    - First partition: 512 MB, type = EFI System
#    - Second partition: remaining free space, type = Linux (do NOT format as NTFS)
#    - Write changes, then Quit
# 3. Format the 512 MB partition as the EFI system partition, and format the larger partition as ext4
# 4. When asked "Install boot loader GRUB?" -> Yes
# 5. When asked "Install /system directory as read-write?" -> Yes (recommended for updates)

Confirm the summary screen carefully. This is the step where selecting the wrong partition can overwrite Windows data, so double-check the partition sizes match the free space you created before continuing, the 512 MB EFI partition plus the larger ext4 partition should roughly add up to the total you freed up in Disk Management.

Step 8: Install GRUB2 and Confirm Dual-Boot Works

When the installer finishes, remove the USB drive and reboot. You should land on a GRUB menu offering both “Bliss OS” and “Windows Boot Manager.” If GRUB does not appear and your PC boots straight to Windows, the EFI boot order needs a manual fix.

# From an elevated Windows Command Prompt or PowerShell, list the current boot entries
bcdedit /enum firmware

# Then use your motherboard's boot menu (F12/F10/Esc at startup) to manually
# select the "Bliss OS" or "grubx64.efi" entry once to confirm it boots correctly.
# Most UEFI firmware will remember it as an option afterward.

Once GRUB shows both operating systems and you can boot into each one reliably, the dual-boot install is complete. From here on, every reboot presents a short menu where you pick Bliss OS or Windows.

Step 9: First Boot Setup — Google Account, Play Store, and Play Integrity

The first boot into Bliss OS walks through a setup wizard nearly identical to a new Android phone: language, Wi-Fi (or Ethernet, covered in the troubleshooting section below), and signing into a Google account if you installed the GApps build. Once you reach the home screen, open the Play Store and update it before installing anything else, since an outdated Play Store is a frequent cause of failed downloads on x86 builds.

Google Play Integrity and SafetyNet

Set expectations here: Google Play Integrity checks (the successor to SafetyNet) typically fail on x86 PC builds of Android, Bliss OS included, because the hardware and bootloader signature do not match a certified Android device. In practice this means banking apps, some streaming apps with DRM requirements, and games with strict anti-cheat or anti-tamper checks may refuse to install or run. Most casual and mid-tier mobile games install and run fine; it is the small subset of apps that specifically check device integrity that will give you trouble, and there is no reliable universal workaround for a from-scratch community OS build.

Step 10: Map Keyboard and Mouse Controls for Android Games

Bliss OS includes built-in keymapping tools similar to what you would find in BlueStacks or MEmu Play. Open Settings, scroll to the Bliss-specific tools section, and look for the keymap/game control utility. From there you can:

• Assign WASD to virtual joystick movement for shooters and racing games
• Bind the mouse to touch-and-aim controls for FPS-style mobile titles
• Map number keys to on-screen ability buttons for MOBA-style games
• Save per-app control profiles so settings persist across launches

If a specific title does not show up in the keymap tool’s app list, most Bliss OS builds let you add it manually by selecting the APK from the installed-apps picker inside the control-mapping settings.

Step 11: Optimize Performance

Three settings make the biggest difference to how Bliss OS feels day to day, whether you installed it dual-boot or in a VM.

GPU rendering mode

In Developer Options (tap Build Number seven times under About Device to unlock it), check the “Force GPU rendering” and “GPU rendering backend” settings. If you see graphical glitches or low frame rates, toggling between the SwiftShader software renderer and native GPU acceleration often resolves it — which option performs better depends heavily on your specific graphics driver.

# From a terminal app installed on Bliss OS, or via adb from your Windows PC:
adb shell settings put global debug.hwui.renderer skiagl
adb shell setprop debug.egl.hw 1
adb reboot

To use adb from Windows against a dual-boot Bliss OS install, enable USB debugging in Developer Options first, then connect with the Android Platform Tools you likely already have if you have set up other emulators from this site before.

RAM and background apps

Android’s memory management assumes a phone-class device by default. On a dual-boot PC install with 8 GB or more of RAM, go to Settings > Apps > and disable “Aggressively kill background apps” if your build exposes that toggle, or install a lightweight task manager to prevent Android from unnecessarily closing games when you alt-tab between apps.

Bliss OS vs Android-x86 vs Waydroid vs PrimeOS vs WSA in 2026

Bliss OS is one of several ways to run Android software on PC hardware, and each option trades off differently on setup complexity, performance, and how current the Android base version is.

Option	Android base	Install type	2026 status
Bliss OS	Android 13 (16.9, current public build)	Dual-boot, VM, or live USB	Active dev; public PC images paused, 16.9 still widely used
Android-x86 project	Varies by release, generally close to stock AOSP	Dual-boot, VM, or live USB	Active, more minimal UI than Bliss OS
Waydroid	Depends on LineageOS base image used	Linux container (LXC), Wayland only	Active, Linux-only, near-native performance
PrimeOS	Generally older Android base than Bliss OS’s newest source	Dual-boot or VM, desktop-style UI with taskbar	Active but smaller community
Google Play Games for PC	Curated Google Play game catalog, not a full OS	Native Windows app (Google-published beta)	Actively maintained by Google; official support but limited to approved titles
Windows Subsystem for Android (WSA)	Android 13 (final version)	Native Windows integration	Discontinued by Microsoft; no longer usable

The practical takeaway: if you are on Windows and want a full Android desktop experience with broad hardware support, Bliss OS and Android-x86 are the two realistic options left standing now that WSA is gone, although Android-x86 appears dormant, with Android-x86 9.0-r2 from March 2020 as its newest release. If you are already running Linux, Waydroid is worth checking out separately since it integrates more tightly with a Wayland session and avoids the dual-boot step entirely. PrimeOS is worth a look if you specifically want a taskbar-based desktop metaphor layered over Android, though its community and release cadence are smaller than Bliss OS’s.

One more option worth flagging for 2026: Google Play Games for PC, Google’s own official beta application for running a curated catalog of Android games directly on Windows. Unlike Bliss OS or Android-x86, it does not install a full Android operating system or require a dual-boot partition — it runs as a native Windows app limited to the specific titles Google has approved for the program, trading Bliss OS’s broad app compatibility and Play Integrity headaches for a narrower but officially supported and actively maintained experience. For readers who only care about a handful of big-name mobile games rather than full Android app flexibility, it is worth comparing against other install-light options the way we compare cloud and lightweight alternatives in our now.gg vs BlueStacks vs LDPlayer comparison.

Popular Use Cases: What People Actually Run on Bliss OS

Public 2026 sources do not publish an official list of endorsed titles, so treat the following as community-reported patterns rather than an official compatibility list. The most common reason people install Bliss OS in the first place is to play mobile games on a bigger screen with a keyboard and mouse instead of a touchscreen. Lightweight, casual, and mid-tier titles — puzzle games, card games, idle games, and most single-player mobile RPGs — tend to install and run without issue on GApps builds once the Play Store is updated. Competitive shooters and battle royale titles with server-side anti-cheat are the category most likely to run into Play Integrity friction, so it is worth checking a title’s specific anti-cheat policy before building a setup around it.

A second common use case is app testing. Developers who need to check how an Android app behaves outside a phone, or who want an x86 target for automated UI testing, use Bliss OS as a disposable VM that can be reverted to a clean snapshot between test runs. A third use case is repurposing older laptop hardware. A machine too slow for a modern version of Windows can often run Bliss OS comfortably, since Android’s resource footprint scales down further than a full desktop OS, which is part of why the SourceForge listing specifically calls out compatibility with hardware “released in the last 4 years” and older Chromebooks.

Updating Bliss OS and Handling Future Releases

Because Bliss OS’s PC image pipeline is currently paused, updates work a little differently than they would on a phone. There is no automatic OTA channel actively pushing new builds for the 16.9 PC release the way BlissRoms ships monthly security patches for phones. In practice, this means updating Bliss OS today involves periodically checking the official download page for a newer ISO and performing a fresh install when one appears, rather than expecting an in-place update notification to show up on your device. Existing installations will not OTA-update or sideload onto the new codebase and will require a clean installation.

If you installed the dual-boot version and want to move to a future release once the paused Android 14 or Android 15 PC builds ship, the safest path is to keep your existing Bliss OS partition intact, download the new ISO, and either install it to a fresh partition (so you can compare the two before deleting the old one) or back up your APKs and app data first if you plan to overwrite the same partition. Since GRUB already recognizes multiple operating systems on your disk from the original dual-boot setup, adding a second Bliss OS partition alongside the first is usually a matter of repeating the partitioning and installer steps from earlier in this guide, then confirming both entries appear in the boot menu.

Common Pitfalls When Setting Up Bliss OS

These are the mistakes that account for most failed installs and frustrated first-boot experiences, based on patterns that show up repeatedly across Bliss OS community threads and installer feedback.

1. Leaving Secure Boot enabled. The single most common reason a Bliss OS USB drive refuses to boot at all. Disable it in your UEFI settings before attempting to boot the installer.
2. Downloading the wrong variant. Grabbing a FOSS build and then wondering why the Play Store is missing is an easy mistake — double-check you downloaded a gapps or opengapps ISO if you want Google apps.
3. Formatting the install partition as NTFS instead of ext4. Android’s file system will not boot from NTFS; always select ext4 in the installer’s partition tool.
4. Selecting the wrong disk during partitioning. On multi-drive systems it is easy to point the installer at the wrong physical disk. Confirm the drive size and label match your intended target before writing changes.
5. Expecting every app and game to work. Play Integrity failures block a real subset of apps, particularly banking apps and games with strict anti-cheat. This is a platform limitation, not something specific to your install.
6. Skipping the ISO checksum. A partially downloaded or corrupted ISO often boots partway before failing, which looks like a hardware compatibility issue but is actually a bad download.
7. Not backing up before dual-boot partitioning. Shrinking a Windows volume is generally safe, but any partitioning operation carries some risk. Back up first, every time.

Troubleshooting Bliss OS: 8+ Common Issues and Fixes

Symptom	Likely cause	Fix
USB drive does not appear in boot menu	Secure Boot enabled, or Rufus wrote in ISO mode incorrectly	Disable Secure Boot; rewrite the USB in Rufus using “DD Image mode” instead of ISO mode
No Wi-Fi after install	Laptop’s Wi-Fi chipset lacks a driver in the Android-x86 kernel	Use a USB Wi-Fi adapter with broad Linux driver support, or connect via Ethernet/USB-C dongle
Black screen after GRUB, before Android boot animation	GPU driver mismatch, common on newer discrete GPUs	At the GRUB menu, press E to edit boot parameters and add nomodeset, then boot
Play Store shows “error retrieving information from server”	Google account or Play Services not fully synced yet	Remove and re-add the Google account under Settings > Accounts, then reboot
Banking app or game refuses to launch	Play Integrity / SafetyNet check failing on x86 hardware	No reliable fix on a from-source OS build; check if the developer offers an APK sideload that skips the check
Choppy video or stuttering 3D games	GPU acceleration not enabled, or wrong renderer selected	Toggle GPU rendering backend in Developer Options; in a VM, confirm 3D acceleration is enabled in the hypervisor settings
System stuck on “Starting Apps” for several minutes	First boot after install is rebuilding the Dalvik/ART cache	Wait it out on first boot only — this is normal and typically resolves in 3 to 8 minutes
Dual-boot GRUB menu disappeared after a Windows update	Windows Update overwrote the EFI boot entry	Boot from your Bliss OS USB, choose “Repair GRUB” if offered, or manually reset the boot order in your UEFI firmware
Sound not working	Audio driver not auto-detected for your specific chipset	Check Settings > Sound for an alternate audio output device, or try the HDMI audio path if using an external display
Touchpad gestures do not work like on Windows	Android was designed for touchscreens, not laptop touchpads	Use a USB mouse for reliable input, or enable “Touchpad as mouse” mode in Bliss-specific input settings if your build includes it

Advanced Tips for Power Users

Once the base install is stable, a few advanced moves get more out of Bliss OS.

• Multi-boot with three or more OSes. If you already dual-boot Windows and Linux, Bliss OS’s GRUB installer can typically detect and chain-load existing GRUB entries rather than overwrite them — always let the installer scan for other operating systems during setup rather than skipping that step.
• Building from source. The official documentation covers building Bliss OS 14.x from source using a Linux build environment, useful if you need a variant with drivers for hardware the public ISO does not support out of the box.
• Using the Windows installer tool. The BlissRoms-x86 GitHub repository ships an Androidx86-Installer-for-Windows utility that can install Bliss OS directly from within Windows without needing a separate USB boot step, useful for less technical dual-boot setups.
• Persistent live USB. Some Bliss OS ISOs support a persistence option during the Rufus write process, letting you carry a working Bliss OS environment on a USB stick between different PCs without a full install on each machine.
• Watching the status page. Since the project has confirmed new source trees for Android 14 and Android 15 are in progress, bookmark blissos.org/status.html if you want to catch the next public PC image the moment it ships.

A Complete Working Project: Building a Bliss OS Gaming Rig

Putting the whole guide together, here is a realistic end-to-end build for someone who wants Bliss OS as a dedicated Android gaming setup on a spare PC or an older laptop repurposed for the job.

1. Confirm the machine meets the recommended specs: 8 GB RAM, an SSD with 32 GB+ free, and a UEFI-capable motherboard.
2. Download the Bliss OS 16.9 GApps x86_64 ISO from blissos.org.
3. Write it to an 8 GB+ USB drive with Rufus in DD Image mode.
4. In BIOS/UEFI, disable Secure Boot and TPM, and set SATA to AHCI.
5. In Windows Disk Management, shrink the main volume to free at least 32 GB.
6. Boot from the USB, run the installer, create a 512 MB EFI partition plus a larger ext4 partition, and install GRUB.
7. Reboot into Bliss OS, complete the setup wizard, and sign into your Google account.
8. Update the Play Store, then install your target games.
9. Open the keymap tool and configure WASD-plus-mouse controls for your primary game.
10. Enable Developer Options, test both GPU rendering backends, and keep whichever performs smoother.
11. Connect a USB Wi-Fi adapter if your built-in wireless chipset is not detected.
12. Test dual-boot stability by rebooting into Windows and back into Bliss OS at least twice before calling the setup finished.

That full sequence, following the detailed steps above, typically takes around 90 minutes for someone doing it for the first time, most of which is the Windows partition shrink, the USB write, and the Bliss OS first-boot cache rebuild. Once it is running, day-to-day use looks a lot like turning on a large Android tablet: press the power button, wait for GRUB, select Bliss OS, and you are looking at a home screen you can install games on, sign into, and customize the same way you would on a phone, just with a mouse cursor and a full-size keyboard instead of a touchscreen.

Keep a written note of your exact build filename (for example, Bliss-v16.9.7-x86_64-OFFICIAL-gapps-20241011.iso), the partition layout you chose, and any BIOS settings you changed. If you ever need to reinstall after a Windows update disrupts the boot order, or if you want to replicate the same setup on a second PC, that record turns a repeat install into a 20-minute job instead of another full 90-minute session working from scratch.

Latest Bliss OS updates (October 2026)

A few developments from the past few months are worth noting for anyone following the Bliss OS project or comparing it against the other Android-on-PC options covered above.

• October 3, 2026: The official Bliss OS development status page confirmed that no official ISO from the newer source trees is currently available, with public PC images still paused and development continuing in the codebase, reconfirming that Bliss OS 16.9 remains the build to install for now.
• October 2, 2026: The Bliss OS documentation was updated with clarified PC installation requirements: disable TPM and Secure Boot, set SATA to AHCI, create a 512 MB EFI partition, and format the larger installation partition as ext4 (folded into Step 6 and Step 7 above).
• September 3, 2026: Tech Insider’s own testing confirmed the roughly 2.2 GB Bliss OS 16.9 ISO, based on Android 13, remains the most widely installed PC build.
• August 25, 2026: A dedicated 2026 installation guide was published documenting a reproducible 13-step, roughly 90-minute workflow for installing Bliss OS 16.9 on PCs, aligning the process with current firmware, partitioning, and bootloader practices — a similar step-by-step format to our own Batocera installation guide on this site.
• August 16, 2026: An updated Linux-focused tutorial refined best practices for installing Bliss OS from a bootable USB, with specific guidance on tools like Balena Etcher or Ventoy and on handling Secure Boot and TPM before booting the installer.
• June 10, 2026: BlissRoms announced version 19.6 (“Waterlily”) for phones, merging the May and June 2026 Android security patches and adding features such as LMOFreeform integration — a sign the broader Bliss ecosystem is still actively maintaining newer Android 16-based code, even though that work has not yet reached a public Bliss OS PC image.

Frequently Asked Questions

Is Bliss OS still being updated in 2026?

Yes, but with a caveat. The project’s source code and documentation are actively maintained, the BlissOS Blog put the BlissOS 16 branch at version 16.7 beta as of August 2025, and Bliss Labs’ download page lists Bliss OS 15 as added on July 29, 2025, so newer Android 13, 14, and 15 based trees (BlissOS 16, 17, and 18 in the GitHub organization in 2026) exist on GitHub. Public, downloadable PC images remain paused, however, the official status page reconfirmed this on October 3, 2026, with 0 current official ISOs in October 2026 and no official ISO yet available from any of the newer trees, so the version most people are installing right now, Bliss OS 16.9, which Tech Insider’s testing confirmed on September 3, 2026 as still the most widely installed public build, predates 2026 even though the project behind it is alive.

Is Bliss OS free?

Yes. Bliss OS is fully open-source and free to download, install, and use, with no license fee or account requirement to run the base OS.

Can I run Bliss OS without replacing Windows?

Yes, in three ways: as a virtual machine in VirtualBox or VMware, as a live session booted from a USB drive with nothing installed to your hard disk, or as a dual-boot partition that sits alongside Windows and lets you choose which OS to load at startup.

Will my games run well on Bliss OS?

Most casual and mid-tier Android games run well, especially with GPU acceleration enabled and keyboard/mouse mapping configured. Titles with strict anti-cheat or Play Integrity checks may refuse to launch on x86 hardware, which is a platform-level limitation shared by every Android-x86 based OS, not something unique to Bliss OS.

What is the difference between Bliss OS and Android-x86?

Bliss OS is built on top of the Android-x86 project, adding a custom interface, extra security settings, and broader hardware support developed by the BlissRoms team. Android-x86 itself stays closer to a minimal, stock Android experience with less customization layered on top.

Does Bliss OS support Google Play and the Play Store?

Yes, if you download a gapps or opengapps build. Bliss OS also offers foss builds with no Google apps at all for users who prefer to sideload APKs and skip Google services entirely.

Why isn’t my Wi-Fi working after installing Bliss OS?

Many laptop and desktop Wi-Fi chipsets lack a compatible driver in the Android-x86 kernel that Bliss OS is built on. A USB Wi-Fi adapter or a wired Ethernet connection is the most reliable workaround until (or unless) a driver for your specific chipset is added upstream.

Is Bliss OS a safe replacement now that WSA is discontinued?

It is a reasonable open-source alternative for running Android software on a Windows PC, particularly for gaming and app testing, but it comes without official vendor support. For anything security-sensitive, treat it the way you would any community-maintained OS: keep it updated where possible and do not rely on it for tasks that require Play Integrity to pass, such as mobile banking. Readers who want an actively developed, officially backed alternative for just a handful of supported titles should also weigh Google Play Games for PC, and Linux users have Waydroid as a well-maintained option that sidesteps the dual-boot step entirely. For hands-on control mapping once you’re up and running on any of these, our gyro aiming setup guide covers input tuning that carries over well to Android-on-PC gaming.