A Windows and Linux dual boot changes how a computer starts and usually changes disk layout. The installation may be routine, but a wrong target disk, lost recovery key, incompatible storage mode, interrupted resize, or missing recovery media can turn it into data loss. A Windows and Linux dual boot checklist matters more than memorizing a universal partition command.

Key Takeaways

Make and test an independent backup before changing partitions or encryption.

Retrieve every Windows BitLocker and Linux encryption recovery key before firmware or boot changes.

Confirm UEFI mode, storage controller support, target-disk identity, and free space.

Test Linux hardware from live media and write down a Windows rollback path.

Use the staged approach in Device and App Troubleshooting Guide: observe, back up, make one deliberate change, and verify both operating systems.

Does the Windows and Linux dual boot checklist apply to you?

Dual boot provides native Linux access to hardware and performance, but it adds boot, partition, encryption, and update interactions. Consider whether one of these meets the goal with less risk:

Windows Subsystem for Linux for command-line development tasks;
a virtual machine for learning or isolated applications;
a live USB for hardware testing and occasional use;
a separate computer;
a separate physical drive, which can reduce but not remove boot and recovery complexity.

Choose dual boot when you need a native Linux installation and accept the maintenance. Do not use a work- or school-managed PC without explicit administrator approval.

Back up and prove you can restore

Ubuntu’s installer documentation recommends backing up a previously used computer before installation and warns that writing installation media erases the selected USB drive.［1］ A backup is not complete merely because a job says “successful.”

Before proceeding:

Copy important files to storage independent of the internal disk.
Include browser exports, password-manager recovery material, license information, development keys, and application-specific data where appropriate.
Open several restored files from the backup.
Verify that encrypted backups can be unlocked from another device.
Record how to restore Windows and personal data.
Disconnect unrelated backup drives during installation to reduce target mistakes.

Cloud sync is not always a full backup: deletions, corruption, online-only files, app databases, and encryption keys may behave differently.

Which recovery keys should you find first?

BitLocker can request its 48-digit recovery key after a security or hardware change. Microsoft says support cannot retrieve or recreate a lost key and explains that it may be stored in a Microsoft account, work or school account, printout, or USB file.［2］ Record the key ID and verify you can access the matching key from another device.

If Windows is organization-managed, the key may belong to that organization. Do not suspend, decrypt, resize, or change firmware settings without its process.

If the Linux installation will use encryption, record its recovery key or passphrase separately too. Ubuntu notes that systems with Windows BitLocker and Ubuntu hardware-backed encryption may require recovery keys for both, including after some firmware changes.［3］ Store keys outside the computer; do not put the only copy on the disk you are changing.

Inventory firmware and storage mode

Record before changing anything:

computer manufacturer and exact model;
current BIOS/UEFI version;
whether Windows boots in UEFI mode;
Secure Boot state;
storage controller mode, including Intel RST or RAID settings;
disk models, sizes, and which disk contains Windows;
BitLocker or device-encryption state for every volume;
partition layout and free space;
boot-order entries.

Ubuntu’s current installer warns that some systems using Intel RST cannot proceed until Windows is safely reconfigured for AHCI.［1］ Do not simply toggle a storage mode in firmware: Windows may stop booting unless it was prepared for the change. Follow the exact manufacturer and operating-system procedure, with backup and recovery keys available.

Avoid mixing legacy BIOS and UEFI installation modes. Boot the installer in the same UEFI model used by Windows unless platform-specific official guidance says otherwise.

Test Linux from live media

Create installation media from the official Linux distribution and verify the image using the publisher’s current instructions. Confirm the exact USB target because imaging erases it.

Boot the live environment without installing and test the hardware before committing to the installer’s disk changes.［4］ Check:

keyboard, touchpad, mouse, display, scaling, and external monitors;
Wi-Fi, Ethernet, Bluetooth, audio, microphone, and camera;
sleep, wake, shutdown, battery reporting, and thermals;
storage visibility and the exact identity of each disk;
graphics behavior and any manufacturer-specific controls;
access to the network and any critical peripheral.

A successful live session does not prove every installed driver or future update will work, but it can reveal major incompatibilities before partition changes.

How should you plan disk space?

Use Windows’ own storage view to identify occupied and available capacity. Remove unneeded files and complete file-system checks before resizing. Leave enough Windows free space for updates, applications, paging, and growth; leave enough Linux space for the system, updates, applications, logs, and personal data.

Do not copy a generic destructive partition command from a guide. Device names differ, and one mistaken character can target the backup or Windows disk. Prefer the current installer’s guided “alongside” option when it correctly identifies the systems and proposed changes. Manual partitioning is for users who can independently identify every disk, partition, filesystem, mount point, boot component, and rollback consequence.

At the final confirmation screen, stop and compare the proposed changes with your recorded inventory. Cancel if the target disk, erase operation, or Windows partition does not match your plan.

What does BitLocker change before resizing?

Ubuntu’s installation guidance says BitLocker can prevent the installer from obtaining the drive information needed for a safe alongside installation. Depending on the layout and installer, the supported choices may include canceling, using a separate unencrypted drive, or following the documented Windows process to turn BitLocker off and later re-enable it.［1］

Do not improvise. Confirm:

whether your Windows edition can re-enable the intended encryption;
that decryption or suspension has fully reached the documented state;
that Windows boots and data is intact before returning to the installer;
that all recovery keys remain available;
what encryption state is expected after installation.

Encryption changes and partition changes each carry risk. Avoid combining them with firmware updates or unrelated repairs in the same maintenance window.

Prepare recovery and rollback

Have these ready before installation:

verified Windows recovery media or the manufacturer’s supported recovery path;
the official Linux installer USB;
Windows and Linux recovery keys;
the backup and restore instructions;
firmware-access and boot-menu instructions for the exact model;
another device with official documentation access;
time to restore rather than rushing before travel or a deadline.

Define rollback conditions. Examples include the installer not recognizing the expected layout, a drive-health warning, Windows failing to boot after a preparatory change, or essential hardware failing in the live session. When a condition occurs, stop and return to the last verified state rather than changing more variables.

Verify both systems after installation

After the first successful boot:

Start Windows and confirm encryption state, updates, storage, files, and critical applications.
Restart, start Linux, and confirm updates, storage mounts, networking, audio, graphics, and sleep.
Restart each system again to verify the boot menu and default behavior.
Confirm the system time is correct in both environments.
Reconnect external backup drives only after the internal layout is confirmed.
Create a fresh post-installation backup and update your recovery notes.

Do not treat one successful Linux boot as proof that Windows recovery and encryption still work.

Summary

Safe dual boot preparation is a recovery exercise as much as an installation exercise. Verify backups and recovery keys, inventory UEFI and storage, test Linux from live media, understand BitLocker, and review the exact proposed disk changes. If any identity or recovery assumption is unclear, cancel before writing to disk.

FAQ

Does dual boot erase Windows?

An alongside installation is intended to preserve Windows, but a wrong disk, erase option, failed resize, or recovery problem can still cause data loss. Back up first.

Do I need my BitLocker recovery key?

Yes. Boot, firmware, security, or disk-layout changes can trigger recovery. Verify the matching key from another device before proceeding.［2］

Must I disable BitLocker?

It depends on the layout and current installer. Follow the distribution’s current documented path; do not improvise encryption changes.［1］

Is a separate drive completely safe?

It reduces partition overlap but does not remove wrong-target, boot-order, firmware, encryption, or recovery risks.

Should I disable Secure Boot?

Not automatically. Many current distributions support it. Follow current distribution and hardware guidance for the exact configuration.

Can I use a generic partition command from a tutorial?

No. Disk identifiers and layouts differ. Use guided installation when applicable or obtain expert review of the exact device.

What should make me cancel installation?

An unexpected disk layout, missing recovery key, unverified backup, health warning, unsupported storage mode, wrong erase target, or essential hardware failure in the live session.

Sources:

Ubuntu Desktop Documentation — Install Ubuntu Desktop — https://ubuntu.com/download/help/install-desktop-latest
Microsoft Support — Find your BitLocker recovery key — https://support.microsoft.com/en-us/windows/security/encryption/find-your-bitlocker-recovery-key
Ubuntu Desktop Documentation — Hardware-backed disk encryption — https://ubuntu.com/desktop/docs/en/latest/explanation/hardware-backed-disk-encryption/
Ubuntu Desktop Documentation — Install Ubuntu Desktop — https://ubuntu.com/desktop/docs/en/latest/tutorial/install-ubuntu-desktop/

Sources checked 27 August 2026.

Related Articles:

Windows and Linux Dual Boot Checklist Before You Install