Dual Boot Omarchy and Windows Safely

Plan an Omarchy and Windows dual boot with clear BitLocker, Fast Startup, partition, and UEFI boot safeguards.

Dual boot preserves Windows-only software, but it is not simply clicking an empty area. Partitioning, disk encryption, UEFI entries, and Windows updates all affect recovery. For a first attempt, a separate physical drive is usually easier to recover than sharing partitions on one disk.

Complete these steps first

Save the BitLocker recovery key in Windows and prove you can access it;
disable Fast Startup and perform one full shutdown;
create a verified file backup and Windows recovery media;
shrink the Windows volume from Windows' own disk management, leaving unallocated space;
record the EFI system, Windows, and recovery partitions and do not format them.

Never copy another machine's partition number

/dev/nvme0n1p1 only describes enumeration on one device at one time. Your order can differ. Formatting the wrong EFI or Windows partition can destroy bootability and data.

Lower-to-higher risk order

Separate drive: Omarchy owns a dedicated physical disk;
unallocated space on one drive: demands precise identification of existing partitions;
manual partition moving: has the greatest failure and recovery cost and is a poor first attempt.

Installation and boot

Boot the Omarchy media in UEFI mode and follow the current official dual-boot instructions for bootloader choices. Do not create a conflicting second EFI partition or delete existing boot entries unless the current official procedure requires it and you understand the consequences.

After installation, boot both Omarchy and Windows. Check whether Windows requests a recovery key, whether the clock is correct, and whether networking and updates work. One successful boot is an initial check, not a permanent guarantee.

Checks after updates

A major Windows update, firmware update, or storage change can alter boot order. Confirm the entries still exist in UEFI before attempting repair. Do not repeatedly reinstall a bootloader without enough evidence.

When to avoid dual boot

Use a spare computer, separate drive, or remote test environment if there is only one disk, no recovery media, no accessible BitLocker key, or the work device cannot tolerate hours of downtime. Preserving a production environment is usually more important than completing a migration in one day.