Dual-Booting Windows 11 and Linux Without Breaking the Bootloader

4 Aug 2026

Dual-booting gives you full access to Windows 11 and Linux on the same computer.

Unlike a virtual machine or Windows Subsystem for Linux, each operating system runs directly on the hardware. You can use Windows for Microsoft 365, specialist business applications or gaming, then restart into Linux for development, security testing, open-source tools or a different desktop environment.

The arrangement can work extremely well—but only when the storage layout, encryption and boot process are handled properly.

The most common dual-boot failures are not caused by Linux and Windows being fundamentally incompatible. They usually happen because somebody:

Installs the two systems in different boot modes
Deletes or formats the EFI System Partition
Resizes the Windows partition with an unsuitable tool
Changes Intel RST, VMD or AHCI settings without preparing Windows
Ignores BitLocker recovery
Installs Linux over the wrong partition
Disables Secure Boot unnecessarily
Uses commands written for an old BIOS system on a modern UEFI computer
Mistakes a changed boot order for a deleted bootloader

This guide explains how to set up Windows 11 and Linux safely, how the modern UEFI boot process works and what to do if one operating system suddenly disappears from the boot menu.

First: Consider Whether You Actually Need Dual Boot

Dual boot is most useful when Linux needs direct access to the computer’s:

Processor
Graphics card
Memory
Wireless hardware
USB devices
Storage performance
Specialist development or testing hardware

When you mainly need a Linux command line, development environment or a small number of Linux tools, Windows Subsystem for Linux may be simpler. Canonical describes Ubuntu on WSL as a full terminal-based development environment that uses fewer resources than a traditional virtual machine or dual-boot installation. (Ubuntu Documentation⁠)

A virtual machine is another safer option for experimentation. It keeps the Linux installation inside files stored by Windows and does not alter the physical disk’s normal boot process.

Dual boot is appropriate when you need native performance and are comfortable restarting to move between systems.

Understand the Modern UEFI Boot Process

Most Windows 11 computers use:

UEFI firmware
A GPT-partitioned disk
An EFI System Partition
Secure Boot
A Trusted Platform Module
BitLocker or Windows Device Encryption

On a UEFI computer, Windows does not boot solely from the beginning of the physical disk in the way older BIOS systems did.

Instead, the computer contains a small FAT-formatted EFI System Partition, often abbreviated to ESP. Windows stores its boot files under a directory such as:

\EFI\Microsoft\Boot

A Linux distribution normally places its own signed bootloader files in a separate directory on the same EFI System Partition, such as:

\EFI\ubuntu

or:

\EFI\fedora

The firmware also maintains boot entries and a boot order in its non-volatile memory. Ubuntu’s Secure Boot documentation describes these as Boot#### entries, with BootOrder determining which entry the firmware tries first. (Ubuntu Documentation⁠)

This means a well-configured UEFI dual-boot setup can contain:

Windows Boot Manager
A Linux shim and GRUB bootloader
Separate firmware boot entries for both
One shared EFI System Partition
Separate operating-system partitions

The Linux installer should add its boot files alongside Microsoft’s files—not replace or format the Windows boot partition.

Boot Order Is Not the Same as Bootloader Damage

Suppose Windows starts directly after a firmware update.

That does not automatically mean Linux or GRUB has been deleted. The update may simply have moved Windows Boot Manager to the top of the firmware boot order.

You may still be able to start Linux by opening the computer’s one-time boot menu and selecting an entry such as:

ubuntu

Fedora

Linux Boot Manager

The exact key varies by manufacturer, but common choices include F12, F10, F9, Esc and F2. Ubuntu’s installation guidance identifies F12 as a common boot-menu key, with Escape, F2 and F10 also used on many systems. (Ubuntu Documentation⁠)

The Safest Overall Installation Plan

A reliable dual-boot design normally follows these principles:

Install Windows first.
Keep both operating systems in UEFI mode.
Keep the disk using GPT.
Back up the Windows recovery key.
Create Linux space from within Windows.
Boot the Linux installer explicitly in UEFI mode.
Reuse the existing EFI System Partition without formatting it.
Install Linux only into unallocated space or its own drive.
Test both systems before changing the firmware boot order further.
Resume BitLocker protection after the configuration is stable.

When possible, installing Linux on a second physical SSD reduces the partitioning risk. Each operating system can have its own storage while both remain available from the UEFI menu.

A second disk does not remove every bootloader consideration, however. The installer can still place Linux boot files on the Windows disk’s EFI partition unless you carefully review the selected destination.

Before You Begin: Create a Real Backup

Partition changes always carry some risk.

Before resizing or installing anything, back up:

Desktop
Documents
Downloads containing important files
Pictures and videos
OneDrive files not fully synchronised
Browser bookmarks
Email archives
Application data
Licence information
Virtual machines
Encryption keys
Any business-critical data

Do not treat a restore point as a backup. A restore point is intended to reverse certain Windows system changes; it is not a safe substitute for independent copies of personal or business files.

Your backup should exist on another physical device or protected cloud service and should be tested before you alter the disk.

Save the BitLocker Recovery Key

Windows 11 computers may use either BitLocker Drive Encryption or the broader Device Encryption feature available on supported Home and Pro devices. Device Encryption can be enabled automatically when a supported PC is set up using a Microsoft or work account. (Microsoft Support⁠)

Before changing partitions, firmware settings, Secure Boot or boot order, confirm that you possess the recovery key.

A BitLocker recovery key is a unique 48-digit number that can unlock an encrypted Windows drive when the normal TPM-based unlock process does not succeed. Windows may ask for it after hardware, firmware or boot-configuration changes because those changes can resemble an unauthorised attempt to access the drive. (Microsoft Support⁠)

To back it up:

Open Start.
Search for Manage BitLocker.
Open the BitLocker control panel.
Find the Windows drive.
Select Back up your recovery key.
Save it somewhere you can access without using the affected PC.

Microsoft advises verifying that the key exists and is accessible before relying on the account copy. On a company-managed device, the key may be stored by the organisation and require assistance from its IT department. (Microsoft Support⁠)

Do not keep the only copy of the key on the encrypted Windows drive.

Check Whether Windows Uses UEFI

Press Windows key + R, enter:

msinfo32

and select OK.

In System Information, check:

BIOS Mode

For a normal modern Windows 11 installation, this should say:

UEFI

You can also open Disk Management and inspect the disk’s properties to determine whether it uses GPT.

Do not boot the Linux installer in Legacy or CSM mode when Windows is installed in UEFI mode.

Fedora’s installation documentation warns that an operating system installed in one firmware mode cannot simply switch between UEFI and BIOS afterwards. (Fedora Documentation⁠)

Mixing modes can leave you with:

Windows visible only through one boot method
Linux visible only through another
A Linux installer that cannot correctly register its UEFI entry
Boot menus that do not detect the other operating system
Repair commands that target the wrong boot architecture

When the USB boot menu shows two versions of the installer, choose the one beginning with:

UEFI:

Update Windows Before Partitioning

Before modifying the disk:

Install pending Windows updates.
Restart the computer.
Confirm that Windows starts normally.
Check Device Manager for unresolved hardware problems.
Confirm that important files have synchronised.
Run a basic disk check where appropriate.
Shut down unnecessary applications.

Avoid beginning the installation immediately after a failed Windows update, storage warning or unexplained blue screen.

A dual-boot installation should begin from a computer already known to be stable.

Create the Linux Space from Windows

Do not delete the Windows partition from inside the Linux installer.

Instead, shrink it through Windows Disk Management:

Right-click Start.
Select Disk Management.
Locate the main Windows partition, normally C:.
Right-click it.
Select Shrink Volume.
Enter the amount of space to release.
Select Shrink.

Microsoft documents Disk Management as the built-in Windows utility for viewing partitions and shrinking basic NTFS volumes. (Microsoft Learn⁠)

The result should be shown as:

Unallocated

Leave it unallocated.

Do not create an NTFS volume in that space unless the Linux installation instructions specifically require it. The Linux installer can create the filesystems it needs.

How Much Space Should You Allocate?

The appropriate size depends on what Linux will be used for.

A basic installation may fit into a relatively small area, but development tools, container images, games, virtual machines and local project data can consume storage quickly.

A practical workstation installation may require considerably more space than the distribution’s published minimum.

Leave enough space in Windows for:

Updates
Applications
Temporary files
OneDrive synchronisation
Hibernation
System recovery
Future growth

Do not shrink the Windows drive until only a few gigabytes remain free.

Understand BitLocker: Suspend or Decrypt?

There are two distinct actions:

Suspending Protection

Suspending BitLocker temporarily stops the normal TPM validation from blocking access after an expected boot or firmware change.

The drive remains encrypted, but the protection mechanism is temporarily made available so Windows can start while the configuration changes. Microsoft documents suspension through the BitLocker control panel, PowerShell or manage-bde. (Microsoft Learn⁠)

From an Administrator Command Prompt:

manage-bde -protectors -disable C:

To resume it later:

manage-bde -protectors -enable C:

Suspension is often appropriate before expected firmware or boot changes.

Turning BitLocker Off

Turning BitLocker off decrypts the drive.

This takes longer and removes its at-rest encryption until you enable it again.

Some Linux installers cannot safely inspect, resize or install beside a BitLocker-protected Windows volume and will instruct you to deactivate BitLocker first. Ubuntu’s current installer documentation notes that behaviour can depend on the installer version and the available unallocated space. (Ubuntu Documentation⁠)

Follow the instructions for the exact Linux distribution and release you are installing.

Do not assume that suspending protection and fully decrypting the volume are interchangeable. An installer that cannot understand the encrypted partition may still refuse to continue while BitLocker is merely suspended.

Disable Windows Fast Startup

Windows Fast Startup does not perform the same type of shutdown as a traditional full power-off.

It logs out users and preserves part of the Windows kernel and driver session in the hibernation file, allowing the next startup to load that saved state. (Microsoft Learn⁠)

That behaviour can create problems when Linux attempts to write to a Windows NTFS volume that Windows has left in a hibernated state.

To disable Fast Startup through the graphical interface:

Open Control Panel.
Select Hardware and Sound.
Select Power Options.
Select Choose what the power buttons do.
Select Change settings that are currently unavailable.
Clear Turn on fast startup.
Save the changes.

You can disable hibernation and Fast Startup together from an Administrator Command Prompt:

powercfg.exe /hibernate off

Microsoft documents this command as the supported way to disable hibernation. Disabling hibernation also removes its functionality and can affect hybrid sleep, so understand the power-management consequences before using it. (Microsoft Learn⁠)

You can re-enable it later with:

powercfg.exe /hibernate on

For a dual-boot computer that regularly accesses shared Windows data from Linux, leaving Fast Startup disabled is generally the safer arrangement.

Keep Secure Boot Enabled Where Possible

Secure Boot checks that boot components are signed by trusted keys before allowing them to run.

You do not automatically need to disable it to install Linux.

Ubuntu provides a Microsoft-signed shim bootloader, a Canonical-signed GRUB package and signed kernels. On supported Ubuntu releases, Secure Boot validates the bootloader, kernel and kernel modules. (Ubuntu Documentation⁠)

Fedora installation media is likewise designed to boot on UEFI systems with Secure Boot enabled. (Fedora Documentation⁠)

Keeping Secure Boot enabled preserves an important protection used by Windows and supported Linux distributions.

When Secure Boot Causes Driver Problems

Third-party Linux kernel modules may not be signed by a key trusted by the firmware.

This can affect software such as:

Proprietary graphics drivers
Virtualisation modules
Specialist network drivers
Hardware-monitoring tools
Custom-built kernel modules

A supported distribution may use the Machine Owner Key process to enrol an additional key for approved modules.

Do not disable Secure Boot immediately because one driver fails to load. Check the distribution’s current guidance for signing and MOK enrolment first.

Changing Secure Boot may also cause Windows to request the BitLocker recovery key because BitLocker monitors boot-integrity measurements. (Microsoft Support⁠)

Watch for Intel RST and VMD

Some PCs expose NVMe storage through Intel Rapid Storage Technology, Intel VMD or a firmware RAID mode.

A Linux installer may not see the Windows drive while that mode is active.

Do not simply switch the firmware from RAID, RST or VMD to AHCI.

Windows may fail to start because the storage controller it expects has changed.

Canonical provides a specific procedure for reconfiguring Windows to use AHCI before installing Ubuntu beside an RST-managed Windows installation. It warns that Windows may initially fail to boot if the change is made without the correct preparation. (Ubuntu Documentation⁠)

This is one of the stages where professional assistance is sensible. Storage-controller mistakes can leave both the installer and Windows unable to access the drive.

Create the Installation USB Properly

Download the Linux image from the distribution’s official website.

Use the distribution’s recommended media-writing tool or another reputable utility that writes bootable images correctly.

Do not drag the ISO file onto a USB drive and expect it to become bootable.

Canonical’s current guidance recommends an 8GB or larger USB drive and warns that creating installation media erases the existing contents of that drive. (Ubuntu⁠)

Before installing:

Verify the download where checksums or signatures are provided.
Create the bootable USB.
Open the UEFI one-time boot menu.
Choose the UEFI version of the USB.
Start the live environment.
Test the hardware before modifying the disk.

Test Linux Before Installing

Most desktop Linux installers provide a live environment.

Use it to check:

Wi-Fi
Ethernet
Bluetooth
Sound
Microphone
Webcam
Display scaling
Touchpad
Keyboard
External monitors
Graphics performance
Sleep and wake
USB devices

Ubuntu’s official Try Ubuntu process runs the desktop from the USB without making permanent changes to the computer. (Ubuntu⁠)

Testing does not guarantee every installed feature will work, but it can reveal obvious hardware incompatibilities before the disk is altered.

Choose the Installation Option Carefully

A Linux installer may offer options such as:

Install alongside Windows Boot Manager
Use free space
Manual partitioning
Erase disk and install Linux

Do not select:

Erase disk

unless you genuinely intend to remove Windows and all existing data.

When the installer correctly detects Windows and offers an install alongside option, that is normally the simplest choice.

Manual partitioning provides more control but also creates more opportunities to select or format the wrong partition.

Do Not Format the EFI System Partition

During manual partitioning, identify the EFI System Partition.

It is usually:

Small compared with the Windows partition
Formatted as FAT32
Marked as EFI or System
Already populated with Windows boot files

Mount it as:

/boot/efi

when the installer requires a mount point.

Do not select its format option.

Formatting it can remove Windows Boot Manager and any other operating-system boot files stored there.

Windows Disk Management identifies the EFI System Partition as the partition supporting the startup process on modern computers. (Microsoft Learn⁠)

Typical Linux Partitions

A straightforward Linux installation may use:

Root partition

Mounted at:

Commonly formatted as ext4, Btrfs or another Linux filesystem supported by the distribution.

Home partition

Mounted at:

/home

This is optional. Separating user files can make some reinstallations easier, although it does not replace a backup.

Swap

Many distributions now use a swap file by default. A dedicated swap partition is not always necessary.

EFI System Partition

Mounted at:

/boot/efi

Reused without formatting on a normal single-disk UEFI dual-boot installation.

The exact layout depends on the distribution, encryption choice and whether Linux is installed on a separate drive.

Decide Where the Bootloader Should Go

On UEFI systems, the Linux installer normally copies its signed shim and GRUB files into an EFI directory and creates a firmware boot entry.

Fedora uses GRUB2 and installs its UEFI boot components through the EFI System Partition. GRUB can boot compatible operating systems directly or chain-load another bootloader such as Windows Boot Manager. (Fedora Documentation⁠)

When Linux is installed on the same drive as Windows, reusing the existing ESP is normal.

When Linux is installed on a separate physical disk, you have two main designs:

Place Linux boot files in the existing Windows disk’s ESP.
Create or use an ESP on the Linux disk.

The second arrangement can provide greater physical separation, but firmware behaviour and installer options vary.

Check the installer’s partition summary before approving changes.

After Installation: Test Both Operating Systems

When the installation finishes:

Remove the USB when prompted.
Restart the computer.
Confirm that the Linux boot menu appears.
Start Linux.
Restart and choose Windows.
Confirm that Windows loads normally.
Restart again and return to Linux.
Check the clock, network and shared storage.
Confirm that the BitLocker recovery key is not being requested repeatedly.
Resume BitLocker protection when the setup is stable.

Do not perform a major Linux upgrade or delete installation media before you have proved that both systems start.

What If Windows Does Not Appear in GRUB?

First, confirm that Windows still boots through the firmware’s one-time boot menu.

Select:

Windows Boot Manager

If Windows loads, its boot files are present and the immediate issue is the GRUB menu rather than the Windows installation.

On Ubuntu, rebuilding the generated GRUB configuration is commonly done with:

sudo update-grub

Operating-system detection policies vary between distributions and releases. Some systems may require os-prober to be installed or enabled before Windows is added to the GRUB menu.

Do not edit:

/boot/grub/grub.cfg

manually. It is a generated file and later updates may overwrite direct changes.

Even when Windows is absent from GRUB, you can continue using the firmware boot menu until the Linux configuration is repaired.

What If the PC Boots Straight into Windows?

Open the UEFI one-time boot menu and look for the Linux entry.

If the entry works, change the normal firmware boot order so that Linux or its shim entry appears before Windows Boot Manager.

The Linux boot files probably remain intact.

A Windows or firmware update may have changed the order rather than deleted them.

Do not immediately reinstall Linux or overwrite the EFI partition.

What If the Linux Boot Entry Has Disappeared?

If no Linux firmware entry remains:

Boot from the Linux live USB in UEFI mode.
Confirm that the Linux partitions still exist.
Mount the installed system.
Reinstall or re-register the distribution’s UEFI shim and GRUB packages.
Rebuild the GRUB configuration.
Restart and test both systems.

The exact commands differ between Ubuntu, Fedora, Arch and other distributions.

Avoid running an old instruction such as:

grub-install /dev/sda

unless the distribution’s current UEFI recovery instructions explicitly require it. Commands designed for BIOS/MBR installations can be inappropriate on a UEFI/GPT system.

Fedora documents GRUB reinstallation as a repair for missing files or an incorrectly installed bootloader, but the correct paths and packages depend on whether the machine uses BIOS or UEFI. (Fedora Documentation⁠)

What If Windows Boot Manager Is Damaged?

Windows provides the BCDBoot tool for creating or repairing boot files on the system partition. Microsoft describes it as a tool for repairing the Windows boot environment and rebuilding the necessary Boot Configuration Data files. (Microsoft Learn⁠)

A typical UEFI repair may involve booting into Windows Recovery Environment, assigning a drive letter to the EFI partition and running a command similar to:

bcdboot C:\Windows /s S: /f UEFI

However:

Windows may not be C: inside the recovery environment.
The EFI partition may not be S:.
Assigning the wrong partition can produce further problems.
Rebuilding Windows boot files may alter the firmware boot order.

Microsoft’s BCDBoot documentation notes that it can repair the UEFI boot environment by copying the required files into \EFI\Microsoft\Boot. (Microsoft Learn⁠)

This is an advanced repair. Verify the Windows and EFI partition letters before running it.

What If BitLocker Requests the Recovery Key?

Enter the recovery key that matches the identifier shown on the recovery screen.

Do not repeatedly reset the TPM, delete protectors or erase the drive.

BitLocker may be reacting to:

A changed Secure Boot state
A new firmware boot order
Bootloader changes
A firmware update
TPM measurements that no longer match the previous configuration

Once Windows starts successfully and the boot configuration is stable, suspend and resume protection to reseal it to the intended state where appropriate:

manage-bde -protectors -disable C:

manage-bde -protectors -enable C:

Microsoft documents these commands for disabling and enabling BitLocker protectors. (Microsoft Learn⁠)

If the recovery prompt continues at every startup, investigate the firmware, Secure Boot and TPM configuration rather than permanently turning encryption off.

Sharing Files Between Windows and Linux

Linux can normally read and write supported Windows NTFS volumes, but avoid mounting the Windows system partition for writing when Windows has been hibernated or Fast Startup has left it in a saved state.

Safer options include:

A separate shared NTFS data partition
A supported exFAT partition for simple cross-platform storage
OneDrive or another cloud service
A network share
Separate local storage for each operating system

Do not store the only copy of important files on a shared partition. Both systems can alter or delete it.

Keep Both Systems Updated

After the dual-boot configuration is stable:

Install Windows updates regularly.
Install Linux security and kernel updates.
Keep the firmware current.
Maintain the Linux bootloader packages.
Keep the BitLocker recovery key accessible.
Retain the Linux live USB.
Maintain Windows recovery media.
Back up both operating systems.
Test both systems after major firmware or bootloader updates.

A Linux kernel update should normally update the distribution’s boot menu automatically. A major distribution upgrade or firmware change deserves more careful testing.

Common Mistakes That Break Dual Boot

Installing Linux in Legacy Mode

Both operating systems should use the same UEFI boot mode.

Formatting the EFI System Partition

This can remove Windows and Linux boot files.

Deleting the Windows Recovery Partition

It is not spare space. It contains Windows recovery tools.

Changing RAID, RST or VMD to AHCI Without Preparing Windows

Windows may become unable to access its own boot drive.

Ignoring BitLocker

Always possess the recovery key before changing the boot configuration.

Leaving Fast Startup Enabled

This can leave Windows volumes in a state that Linux should not modify.

Using “Erase Disk”

This removes the existing operating system and data.

Running Old BIOS Repair Commands on UEFI

Confirm the firmware mode before using bootloader instructions.

Assuming a Changed Boot Order Means Linux Was Deleted

Check the firmware boot menu first.

Modifying GRUB’s Generated Configuration Directly

Use the distribution’s supported configuration files and rebuild command.

Using a Partitioning Tool Without a Verified Backup

Even reputable software cannot protect against a power loss, hardware fault or incorrect selection.

A Safe Dual-Boot Checklist

Before installing Linux beside Windows 11:

Decide whether WSL or a virtual machine would meet the requirement.
Back up all important data.
Test the backup.
Create Windows recovery media.
Save and verify the BitLocker recovery key.
Check that Windows uses UEFI.
Confirm that the disk uses GPT.
Install pending Windows updates.
Confirm that Windows is stable.
Shrink the Windows partition through Disk Management.
Leave the resulting space unallocated.
Suspend or decrypt BitLocker as required by the installer.
Disable Windows Fast Startup.
Keep Secure Boot enabled when the distribution supports it.
Investigate RST or VMD before changing controller mode.
Download Linux only from the distribution’s official source.
Create the bootable USB properly.
Boot the USB in UEFI mode.
Test the live environment.
Select Install alongside or carefully use free space.
Never format the existing EFI System Partition.
Review every proposed partition change before continuing.
Test Linux after installation.
Test Windows immediately afterwards.
Resume BitLocker protection after the setup is stable.
Keep both recovery environments available.
Maintain regular backups of both systems.

How Hamilton Group Can Help

Dual boot is not necessarily difficult, but mistakes involving encryption, storage-controller mode or the EFI System Partition can leave both operating systems inaccessible.

Hamilton Group’s experienced IT team can help with:

Assessing whether dual boot is the right solution
Preparing Windows safely
Backing up and verifying BitLocker recovery keys
Checking UEFI, GPT and Secure Boot compatibility
Resizing partitions
Configuring second-drive installations
Resolving Intel RST and VMD problems
Installing supported Linux distributions
Repairing GRUB and Windows Boot Manager
Recovering inaccessible Windows or Linux systems
Protecting shared data
Rebuilding damaged EFI boot configurations
Creating tested recovery media
Designing safer alternatives using WSL or virtual machines

For business devices, we can also establish whether dual boot is compatible with the organisation’s encryption, endpoint security, compliance and device-management requirements.

Hamilton Group aims to make first contact on IT support requests within 15 minutes, helping you get experienced guidance before an incorrect boot or partitioning change becomes a data-recovery emergency.

Get Expert Help with Windows and Linux

A properly configured UEFI dual-boot system can run reliably for years.

The key is to protect the data first, keep both systems in the same boot mode, preserve the EFI System Partition and understand how BitLocker, Secure Boot and the firmware boot order interact.

Call 0330 043 0069, book a meeting with one of our experts or visit hgmssp.com for experienced help installing or repairing Windows 11 and Linux dual-boot systems.