Going back to Windows 11 from Bazzite is not always a complete reinstall. The correct method depends on whether Windows still exists beside Bazzite, sits on a separate drive, or was erased when Bazzite was installed.
Identify that layout before deleting any partition. The most serious mistakes happen when a Windows recovery partition, the EFI System Partition, or the wrong physical drive is mistaken for Bazzite.
Choose the situation that matches your installation
| Current layout | What you need to do | Is Windows reinstallation required? |
|---|---|---|
| Windows and Bazzite share one drive | Boot Windows, make Windows Boot Manager the default, then remove only confirmed Bazzite partitions | Usually no |
| Windows and Bazzite use separate drives | Confirm Windows boots independently, then erase or repurpose the Bazzite drive | Usually no |
| Bazzite replaced Windows | Create official Windows media and install Windows onto the target drive | Yes |
| Windows remains but its boot entry is missing | Repair Windows boot files before touching partitions | Not necessarily |
| A handheld has an available manufacturer recovery service | Use the vendor recovery option when you want the original factory software and partitions | It restores Windows |
Bazzite does not provide a “Go back to Windows” button. Its own uninstallation guidance also separates dual-boot removal from replacing Bazzite completely.
Protect the data and recovery options first
Back up files stored in Bazzite, including anything under the home folder that has not synchronized to cloud storage. Steam Cloud does not cover every game, and emulator saves, screenshots, custom configurations, and non-Steam game data may exist only on the Linux partition.
Also prepare the following:
- A separate copy of important Windows files when Windows still boots.
- The BitLocker or Device Encryption recovery key for the Windows installation.
- The Windows edition previously activated on the hardware, normally Home or Pro.
- A blank USB drive suitable for Windows 11 installation or recovery.
- Network, storage, chipset, and controller drivers from the device manufacturer when working with unusual hardware.
- The model name and capacity of every internal SSD.
Open Windows Disk Management when Windows is available and record the disk numbers, capacities, partitions, and drive letters. From Bazzite, tools may label disks as /dev/nvme0n1, /dev/nvme1n1, or similar. Those Linux names do not reliably correspond to Windows Disk 0 and Disk 1, so use physical capacity and model information rather than assuming the numbers match.
Do not remove an EFI partition simply because it is small, has no drive letter, or appears unfamiliar in Disk Management. Windows and Bazzite may use separate EFI partitions or share one. Deleting the active Windows EFI System Partition can leave an intact Windows installation unable to boot.
Scenario 1: Windows and Bazzite share the same drive
Use this path only when Windows 11 still starts and both operating systems occupy partitions on one physical SSD.
1. Boot Windows before removing Bazzite
Restart and choose Windows Boot Manager from the firmware boot menu. Sign in and make sure Windows opens normally.
Check that personal files are accessible, BitLocker is not waiting for recovery, and Windows activation still appears under Settings > System > Activation.
2. Make Windows Boot Manager the default
Open the UEFI or BIOS boot settings and place Windows Boot Manager before the Bazzite or Linux entry. The exact key and menu vary by manufacturer. The Windows 11 BIOS access guide covers the supported Settings and startup routes.
Restart twice and confirm that Windows loads without selecting Bazzite manually. Do not change Secure Boot, storage mode, TPM, and several other firmware settings at the same time. Change only the boot priority so any failure has one identifiable cause.
3. Identify Bazzite partitions in Disk Management
Right-click Start, select Disk Management, and locate the physical disk containing Windows and Bazzite.
Linux partitions may appear without drive letters or recognizable file-system labels. That is not enough evidence to delete them. Compare their sizes and positions with the layout recorded during the Bazzite installation. Preserve:
- the Windows C: partition;
- the EFI System Partition used by Windows;
- Microsoft Reserved partitions;
- Windows recovery partitions; and
- manufacturer recovery partitions you still want.
Only delete a partition after confirming that it belongs exclusively to Bazzite and that its files have been backed up. Disk Management may not offer Delete Volume for every Linux partition. Do not respond by running a force-delete command against an uncertain partition.
4. Reclaim the unallocated space
After confirmed Bazzite partitions are removed, the space appears as Unallocated. Windows Disk Management can extend C: only when suitable unallocated space is positioned directly after that partition.
Where Extend Volume is unavailable, do not delete intervening recovery or EFI partitions merely to make the space adjacent. Leave the space unallocated temporarily, create a separate Windows data volume, or use a carefully verified partition plan and full backup.
Restart and confirm that Windows starts, BitLocker remains accessible, and the expected Windows and recovery partitions remain present.
Scenario 2: Bazzite is installed on a separate drive
Separate drives make removal safer, but only after confirming that Windows does not depend on boot files stored on the Bazzite drive.
- Set Windows Boot Manager as the first firmware boot option.
- Shut down the PC completely.
- Disconnect the Bazzite drive temporarily when the hardware allows this safely.
- Start the computer and confirm that Windows boots by itself.
Reconnect the drive only after that test succeeds. Then open Disk Management and identify it by model and capacity.
Delete or format the Bazzite partitions only on that confirmed disk. Create a new NTFS volume when the drive will become Windows storage. Where Disk Management cannot remove the Linux layout, a complete disk-clean operation may be appropriate, but it erases the selected disk instantly. Use a professional or a trusted partition tool when there is any uncertainty about the disk identity.
An old Bazzite entry can remain in the firmware boot menu after the drive is erased. It is harmless when Windows Boot Manager starts correctly. Do not format an EFI partition on the Windows drive just to remove a cosmetic firmware entry.
Scenario 3: Bazzite replaced Windows completely
Windows must be installed again when no usable Windows partition remains. Use another computer to create official installation media.
Microsoft’s Windows installation-media instructions provide the current creation tool and USB requirements.
1. Boot the Windows USB
Connect the USB, open the device’s one-time boot menu, and select the UEFI entry for the installation drive. Use UEFI mode on a normal Windows 11 system.
Official Microsoft media supports standard Windows 11 Secure Boot configurations. Avoid disabling Secure Boot unless the device has a specific boot problem and you understand how to restore it afterward.
2. Start Windows Setup
Choose the correct language and keyboard layout, then select Install Windows 11. When Setup requests a product key, a computer previously activated with Windows 11 can normally use I don’t have a product key and reactivate online later.
Select the same edition that was licensed previously. Installing Pro on hardware licensed only for Home can leave Windows unactivated.
3. Select the correct physical drive
Windows Setup shows disks and partitions without the familiar Linux device names. Identify the target by capacity and hardware arrangement.
For a complete replacement of Bazzite on that drive, delete partitions only from the confirmed target disk until it shows Unallocated Space. Then select that unallocated space and continue. Windows creates the partitions it needs.
Stop when multiple drives have similar capacities or the identity is uncertain. Disconnect non-target internal or external drives when practical rather than gambling with valuable data.
The Windows 11 reinstallation guide explains activation, clean-install choices, and post-install checks in greater detail.
ROG Ally, Ally X, and Legion Go recovery
A gaming handheld can use standard Microsoft installation media, but a manufacturer recovery service may be the better route when you want the original partitions, controller integration, device utilities, and factory driver set.
For an ASUS ROG Ally or Ally X, check whether ASUS Cloud Recovery is available from the device’s UEFI utility. It can restore the factory Windows image but erases the internal drive. Keep the handheld connected to power and a stable network throughout the process.
For a Lenovo Legion Go, use the recovery-media or digital-download process offered for the exact serial number when available. A generic Windows installation can work, but Lenovo power management, controller functions, firmware, audio components, and Legion Space may need separate installation afterward.
Do not use recovery media for a different model simply because the hardware looks similar.
Windows Boot Manager is missing but Windows still exists
A missing boot entry does not prove that Windows was deleted. Look for a large NTFS partition containing the Windows folder before reinstalling or deleting anything.
Boot from Windows installation media, choose Repair your computer > Troubleshoot > Advanced options, and run Startup Repair first. It can recreate some startup information without modifying data partitions manually.
BCDBoot can rebuild Windows boot files when Startup Repair fails, but the correct command depends on the drive letter assigned to Windows and the correct EFI System Partition inside the recovery environment. Those letters can differ from normal Windows. Do not copy a generic BCDBoot or DiskPart command that assumes C: and a particular volume number.
Where the Windows partition is BitLocker-encrypted, unlock it with the recovery key before attempting boot-file repair. Professional help is safer when several EFI partitions exist or the partition layout cannot be identified confidently.
Legacy advice involving bootrec /fixmbr does not rebuild a normal UEFI Windows Boot Manager entry by itself. Modern Windows 11 systems normally use GPT and UEFI, so MBR-only instructions are often irrelevant.
Windows Setup cannot see the SSD
Missing storage in Setup commonly points to a storage-controller driver or firmware mode, not proof that Bazzite damaged the SSD.
Check the manufacturer support page for an Intel Rapid Storage Technology, VMD, RAID, or other storage driver that Windows Setup can load. On a handheld, use the model-specific recovery method or storage package.
Changing RAID, VMD, or AHCI mode can make an existing operating system unbootable and may trigger BitLocker recovery. Record the original setting and avoid changing it merely to experiment. Loading the correct driver is preferable when the manufacturer designed the device for that controller mode.
Also recreate the USB with official media and try a different USB port when the installer behaves inconsistently.
What happens to activation and games?
Windows usually reactivates automatically on the same hardware after the same edition connects to the internet. Check Settings > System > Activation after installation. A motherboard replacement or edition change may require separate activation troubleshooting.
Bazzite games and local saves are erased when their partitions are deleted. Steam can download purchased games again, but only synchronized saves return automatically. Copy unsupported saves, emulator folders, screenshots, mods, and configuration files before removal.
Keeping a Bazzite data partition is technically possible, but Windows does not natively read common Linux file systems. It also leaves a more complicated disk layout. Keep it only when the partition is positively identified and you have a specific plan for accessing or converting its contents.
Finish the Windows setup in the right order
After Windows reaches the desktop:
- Confirm activation.
- Run Windows Update repeatedly until applicable updates and restarts are complete.
- Install the manufacturer’s chipset and storage drivers.
- Install graphics, Wi-Fi, Bluetooth, audio, and controller drivers.
- Install the device-management utility for a gaming handheld or laptop.
- Check Device Manager for missing or warning-marked hardware.
- Restore personal files after confirming that Windows is stable.
Do not install several generic driver-updater utilities. Windows Update and the device manufacturer’s support page are safer sources for a newly restored system.
The return is complete when Windows starts without the Bazzite drive or boot entry, the intended storage capacity is visible, activation succeeds, and Device Manager recognizes the hardware. Leftover unallocated space or a harmless firmware entry can be addressed afterward; neither justifies deleting an uncertain system partition.
