Linux Dual-Boot Setup That Doesn’t Break Windows

31 Jul 2026

Installing Linux alongside Windows can give you the best of both operating systems.

Windows remains available for Microsoft 365, specialist business applications, gaming and hardware utilities, while Linux provides a flexible environment for development, privacy, learning, older hardware or everyday computing.

However, a dual-boot installation changes the disk layout and the computer’s startup configuration. Done carelessly, it can trigger BitLocker recovery, hide Windows from the boot menu, overwrite the wrong partition or leave one operating system unable to access shared files.

The safest method is to prepare Windows first, protect the recovery information and allow the Linux installer to use genuinely unallocated space rather than manually modifying Windows partitions from Linux.

What Is Dual Boot?

A dual-boot computer contains two operating systems installed on separate partitions or physical drives.

When the computer starts, a boot menu allows you to choose between:

Windows
Linux

Only one operating system runs at a time.

This differs from:

Windows Subsystem for Linux, which runs a Linux environment within Windows
A virtual machine, which runs Linux inside a window
A live USB, which runs Linux temporarily without installing it
Replacing Windows, which removes Windows completely

Ubuntu’s current installation documentation suggests WSL when someone merely needs Linux tools alongside Windows. A full dual-boot installation is more appropriate when you need native Linux hardware access, desktop performance or an independent operating system.

Decide Whether You Really Need Dual Boot

Dual boot makes sense when you need:

Native Linux performance
Direct access to the graphics processor
Linux-specific development tools
Better performance than a virtual machine
Full control over the Linux desktop
An operating system independent of Windows
Hardware that works better under Linux

Consider WSL or a virtual machine instead when you mainly need:

A Linux command line
Development tools
Docker or scripting
Occasional testing
Linux without repartitioning the disk
A setup that is easier to remove

Dual boot is not difficult, but it creates more recovery considerations than installing an ordinary application.

Back Up Windows Before Touching the Partitions

Partition changes are normally reliable, but no disk operation should be treated as risk-free.

Before starting, protect:

Documents
Photographs
Desktop files
Browser bookmarks
Email archives
Password-manager data
Application licence details
Game saves
Encryption recovery information
Files outside the normal user folders

Use at least one backup stored away from the internal disk.

Microsoft recommends backing up files before installing or reinstalling Windows, and its Recovery Drive tool can create bootable recovery media on an empty USB drive.

To create a Windows recovery drive:

Open Start.
Search for Recovery Drive.
Open the tool.
Select Back up system files to the recovery drive.
Connect an empty USB drive.
Complete the wizard.

The USB drive will be erased.

A recovery drive is not a substitute for a personal file backup, but it can help you reach Windows recovery tools if the boot configuration is damaged.

Save the BitLocker Recovery Key

This is one of the most important steps.

Many Windows 11 computers use BitLocker or automatic device encryption, including devices running editions where the owner may not remember enabling it.

A change to the bootloader, Secure Boot configuration, TPM measurements or firmware environment can cause Windows to request its recovery key. Microsoft explains that boot-file and firmware changes can trigger BitLocker recovery.

Before continuing, confirm that the recovery key is available somewhere other than the computer being modified.

It may be stored in:

Your Microsoft account
Microsoft Entra ID
Active Directory
Your organisation’s device-management platform
A printed record
A secure password manager
A file on separate encrypted storage

Do not store the only copy of the key on the Windows partition you are about to modify.

Check Whether Windows Is Encrypted

Open:

Settings > Privacy & security > Device encryption

You can also search for:

Manage BitLocker

Check the Windows system drive, normally C:.

There is an important distinction between:

Suspending BitLocker
Turning BitLocker off and decrypting the drive

Suspending BitLocker

Suspension keeps the drive encrypted but temporarily disables the normal boot validation checks. Microsoft recommends suspension before non-Microsoft operations that modify boot components, because otherwise Windows may request the recovery key after restarting.

This is useful for bootloader or firmware work.

Decrypting the drive

Some Linux installers cannot safely inspect or resize an encrypted Windows installation. Ubuntu’s installer documentation states that when BitLocker is enabled, the installer cannot gather the disk information needed to install Ubuntu safely alongside Windows; its supported choices are to remove encryption or replace Windows.

Therefore:

If you have already created unallocated space in Windows and will install Linux only into that space, suspension may be sufficient for the boot changes.
If the Linux installer needs to resize or analyse the Windows partition, decrypting Windows first is safer and may be required.
On a managed business computer, do not decrypt or suspend protection without authorisation.

After the full setup has been tested, resume BitLocker or re-enable encryption as appropriate.

Check the Current Firmware Mode

Modern Windows 11 installations normally use:

UEFI firmware
A GPT-partitioned disk
Secure Boot capability

Open:

Windows + R

Enter:

msinfo32

Check:

BIOS Mode

It should normally say:

UEFI

Install Linux in the same firmware mode as Windows.

Do not install Windows in UEFI mode and Linux in legacy BIOS or Compatibility Support Module mode. Fedora’s installation guidance warns that an operating system installed in one firmware mode may no longer boot if the machine is switched to another mode.

When choosing the USB from the firmware boot menu, select the entry that explicitly begins with:

UEFI:

where more than one version is shown.

Do Not Disable Secure Boot Automatically

Many current mainstream Linux distributions support Secure Boot.

Ubuntu and Fedora installation media are designed to boot on supported UEFI systems with Secure Boot enabled.

Leaving Secure Boot enabled can preserve a stronger startup-security configuration and reduce unnecessary changes to Windows.

You may need to disable it when:

The selected distribution does not support it
You require an unsigned kernel module
A specialised driver cannot load
The installer documentation explicitly instructs you to do so

If you change Secure Boot settings while BitLocker is active, be prepared for a recovery-key prompt. Microsoft notes that Secure Boot and UEFI changes can affect BitLocker’s boot measurements.

Record the original firmware settings before altering anything.

Check the Disk Layout

Open Disk Management:

Windows + X > Disk Management

You will probably see several partitions, including:

EFI System Partition
Microsoft Reserved Partition
Windows C:
Recovery partition
Manufacturer recovery partitions

Do not delete small partitions merely because they do not have drive letters.

The EFI System Partition contains startup files used by Windows and, in a properly configured dual-boot installation, can also hold Linux boot files.

The recovery partitions support Windows recovery and manufacturer servicing.

Shrink Windows from Inside Windows

Create space for Linux using Windows Disk Management rather than resizing the live Windows partition from an unfamiliar third-party tool.

In Disk Management:

Right-click the Windows C: volume.
Select Shrink Volume.
Wait while Windows calculates the available shrink space.
Enter the amount to release.
Select Shrink.

Microsoft documents Disk Management as the supported Windows tool for shrinking NTFS basic volumes.

The resulting area should appear as:

Unallocated

Leave it unallocated.

Do not create a new NTFS volume there. The Linux installer can create the required Linux partitions from the empty space.

How Much Space Should You Allocate?

The exact requirement depends on the distribution and workload.

Practical starting points are:

40–60GB: basic Linux testing and light use
80–120GB: general desktop use
150GB or more: development, games, virtual machines or large projects

Leave plenty of space for Windows updates, applications and temporary files.

Avoid shrinking Windows until it has only a few gigabytes free. Both operating systems need room for updates and working data.

Windows Will Not Shrink as Far as Expected

Disk Management may offer much less shrink space than the free-space figure suggests.

This can happen because immovable Windows files are located near the end of the volume.

Before using third-party partition software:

Back up the computer.
Restart Windows.
Install pending Windows updates.
Empty the Bin.
Remove unnecessary large files.
Check the file system.
Try Disk Management again.

Do not aggressively delete page files, recovery files or shadow-copy data unless you understand the recovery impact.

Creating slightly less Linux space is safer than forcing a large partition move with an unfamiliar utility.

Disable Windows Fast Startup

Windows Fast Startup does not perform a completely fresh shutdown. Microsoft describes it as writing parts of the operating-system state to the hibernation file so the next startup can be faster.

This can cause problems in a dual-boot environment because the Windows NTFS volume may remain in a hibernated state. Linux may therefore refuse to mount it as writable, or writing to it may risk file-system inconsistency.

To disable Fast Startup:

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

A full Windows restart normally performs a fresh boot, but disabling Fast Startup is clearer when the computer will regularly switch between Windows and Linux.

Also avoid hibernating Windows and then writing to the Windows partition from Linux.

Check Windows for Errors

Before resizing or installing:

Open Terminal or Command Prompt as administrator.
Run:

chkdsk C: /scan

If Windows reports file-system problems, repair them before continuing.

Also check that Windows:

Starts normally
Shuts down normally
Has no pending restart
Has enough free storage
Is fully backed up

Do not begin a dual-boot installation while Windows is already unstable.

Download Linux from the Official Source

Use the distribution’s official website.

Popular beginner-friendly choices include:

Ubuntu
Linux Mint
Fedora Workstation
Xubuntu
Lubuntu

Choose a current supported release rather than an old ISO from a third-party mirror or forum attachment.

Verify the published checksum where practical. This confirms that the ISO was downloaded correctly and has not been altered.

Create the Installation USB Properly

Use the distribution’s recommended image-writing tool.

Depending on the distro, suitable choices may include:

Rufus
Fedora Media Writer
balenaEtcher
The distro’s own media creator

The USB drive will be erased.

Avoid simply dragging the ISO file onto the USB. A bootable installer needs the image written in the correct structure.

Fedora warns that tools which extract or rearrange ISO contents can bypass the boot configuration included in the official hybrid image and may produce inconsistent UEFI or Secure Boot results.

Test the Live Environment First

Boot the USB and choose the option to try Linux without installing it.

Ubuntu’s live environment is designed to let you test the system without making permanent changes.

Check:

Wi-Fi
Bluetooth
Sound
Touchpad
Keyboard
Screen brightness
Webcam
External displays
Sleep and wake
Graphics performance
USB devices

Also confirm that the installer can see:

The internal disk
Windows
The unallocated space

If the installer cannot see the internal drive, stop.

Possible causes include:

BitLocker
RAID or Intel VMD configuration
Unsupported storage hardware
The USB being booted in the wrong firmware mode
Drive-controller settings
A failing disk

Do not randomly change RAID, AHCI or VMD settings. Doing so can make Windows unbootable unless Windows has been prepared for the change.

Use “Install Alongside Windows” Where Available

The safest option for most users is the installer’s guided choice:

Install alongside Windows Boot Manager

or similar wording.

Ubuntu’s installer supports an alongside option when it can safely identify the existing Windows installation and disk layout.

Before continuing, verify that the summary clearly shows:

Windows is being retained
Linux is using the intended unallocated space
The correct physical disk is selected
No unexpected partitions are marked for formatting

Do not proceed if the installer offers only:

Erase disk and install

unless you genuinely intend to delete Windows.

Manual Partitioning Is for Advanced Setups

The option may be called:

Manual partitioning
Custom
Something else
Advanced storage configuration

Use it only when you understand:

GPT partitions
EFI System Partitions
Mount points
Linux file systems
Bootloaders
Multiple physical disks

A typical manual configuration might include:

Existing EFI System Partition mounted at /boot/efi
Linux root partition mounted at /
Optional separate /home
Swap file or swap partition

Do not format the existing EFI System Partition. Both systems can normally share it while keeping separate boot files.

Do not modify the Microsoft Reserved, Windows Recovery or manufacturer partitions.

Be Careful with the EFI System Partition

The EFI System Partition is small, usually FAT-formatted and contains bootloader files.

The Linux installer may use the existing partition to add its own boot files.

That is normal.

The dangerous actions are:

Deleting the EFI partition
Formatting it
Replacing its entire contents
Creating an unnecessary second EFI partition on the same Windows disk without understanding the firmware behaviour

A correctly configured installer should add Linux without removing the Windows Boot Manager.

Installing Linux on a Second Physical Drive Is Safer

Where the computer has two storage devices, using a separate drive for Linux reduces the risk of resizing Windows.

A cautious method is:

Back up Windows.
Identify both drives by capacity and model.
Install Linux onto the second drive.
Place Linux partitions on that drive.
Keep the Windows partitions untouched.
Use the firmware boot menu or Linux bootloader to choose the operating system.

The installer may still place boot files in the existing EFI partition unless manually directed otherwise.

For maximum separation, advanced users sometimes disconnect the Windows drive during Linux installation. This ensures Linux creates its own EFI partition on the Linux disk, but it also means the firmware boot order may need adjustment after reconnecting Windows.

Read the Final Installation Summary Carefully

Before the installer writes changes, review the proposed operations.

Stop immediately if it plans to:

Format the Windows partition
Delete the EFI System Partition
Delete the Windows recovery partition
Erase the entire disk
Install to the wrong physical drive
Use space belonging to a data partition you intended to retain

Disk model names and capacities are more reliable than labels such as “Drive 0” when several disks are installed.

Complete the Installation Without Interrupting It

Keep the computer connected to power.

Do not:

Remove the USB early
Force the computer off
Close the laptop lid
Change firmware settings during installation
Disconnect the installation drive

When the installer finishes, follow its instruction about removing the USB and restarting.

The first restart should display a Linux boot menu or the firmware’s operating-system menu.

Confirm Both Operating Systems Boot

Before making further changes, test each system separately.

Test Linux

Confirm:

It reaches the desktop
Wi-Fi works
Updates can install
Sound and graphics work
The internal partitions are as expected

Test Windows

Select Windows Boot Manager from the Linux boot menu or firmware boot menu.

Confirm:

Windows starts normally
BitLocker accepts the platform state
The Windows partition size is correct
Windows Update works
No partitions are missing

Do not consider the installation complete until both systems have been started successfully more than once.

Resume BitLocker Protection

If BitLocker was suspended, resume it after confirming that Windows starts through the new boot configuration.

You can use the BitLocker Control Panel or an elevated PowerShell session.

Microsoft’s BitLocker operations guidance supports suspending and resuming protection around system changes.

Keep the recovery key even after everything works.

Linux or firmware updates may alter boot components again in future.

Run Updates in Both Systems

After installation:

In Linux, use the distribution’s normal update tool.

In Windows, open:

Settings > Windows Update

Install updates separately in each operating system.

Do not assume that updating one system updates:

Firmware
Graphics drivers
The other operating system
The other system’s applications

Firmware updates delivered through Windows can affect the Linux bootloader or boot order, so keep the recovery information available.

Windows Boots Directly and Skips Linux

A Windows update or firmware change may place Windows Boot Manager first in the UEFI boot order.

This does not necessarily mean Linux was deleted.

Open the computer’s one-time firmware boot menu—often using a key such as:

F12
F9
F10
Escape

Look for entries such as:

Ubuntu
Fedora
Linux Boot Manager
Windows Boot Manager

Select the Linux entry.

Then adjust the firmware boot order or use the Linux bootloader repair tools where necessary.

Do not reinstall Linux until you have confirmed whether its partitions and UEFI entry still exist.

Linux Boots but Windows Is Missing from the Menu

Windows may still be fully intact.

First, use the firmware’s boot menu and select:

Windows Boot Manager

If Windows starts, the problem is limited to the Linux boot menu.

Possible fixes include:

Updating the Linux bootloader configuration
Enabling operating-system detection where the distro disables it by default
Creating a manual boot entry
Selecting Windows through the firmware menu instead

Avoid deleting and reinstalling partitions merely because one boot-menu entry is absent.

Windows Requests the BitLocker Recovery Key

Enter the recovery key you saved before installation.

This can happen because the measured boot environment changed.

Once Windows starts successfully, it may accept the new configuration and stop requesting the key. Microsoft explains that after a recovery password is used successfully, the platform-validation state can be updated so the same change does not trigger recovery repeatedly.

If it asks on every boot:

Confirm Secure Boot and TPM settings have not changed unexpectedly
Resume or reconfigure BitLocker correctly
Check the selected boot path
Review whether the firmware is switching between bootloaders
Contact IT on a managed device

Do not clear the TPM without understanding the impact on encryption keys and credentials.

Linux Cannot Write to the Windows Drive

Check whether Windows was:

Hibernated
Shut down with Fast Startup
Left in an unclean state
Encrypted

Boot Windows and perform a full shutdown.

Do not force Linux to mount an NTFS volume as writable when it reports that Windows left it hibernated. Overriding the warning can damage the Windows file system.

For shared files, consider creating a separate data partition rather than routinely writing into the Windows system partition.

Creating a Shared Data Partition

A shared ExFAT or NTFS data partition can be useful for documents accessed from both operating systems.

However:

ExFAT lacks journalling and advanced permissions
NTFS write support under Linux depends on the installed driver
Neither should replace a proper backup
Application databases may not be safe to share
Windows hibernation can still complicate access to NTFS volumes

Suitable shared data includes:

Documents
Media
Installers
Project exports

Avoid sharing live application databases, browser profiles or mail stores between the two operating systems.

Do Not Store the Same Cloud-Sync Folder in Both Systems Carelessly

Using OneDrive, Dropbox or another sync service from Windows and Linux against the same physical folder can create:

Duplicate files
Permission differences
Conflicts
Unsupported metadata
Constant re-indexing

Configure each sync client according to the provider’s supported method.

Do not point two different sync implementations at the same data folder without testing.

Windows Updates May Change the Boot Order

Major Windows or firmware updates can sometimes make Windows Boot Manager the default again.

Prepare by knowing:

The firmware boot-menu key
The name of the Linux boot entry
How to enter UEFI settings
Where the Linux recovery USB is stored
Where the BitLocker recovery key is stored

This turns a worrying boot change into a manageable configuration repair.

Keep Installation and Recovery Media

Retain:

The Linux installation USB
A Windows recovery drive
Current backups
The BitLocker recovery key
Notes about the original firmware settings

The Linux USB can normally boot into a live environment for:

Copying files
Repairing the bootloader
Checking partitions
Accessing the internet
Diagnosing hardware

Windows installation media can also boot into Windows Recovery Environment when the installed Windows system will not start.

Avoid These Common Mistakes

Choosing “Erase disk”

This removes Windows and its partitions.

Formatting the EFI partition

This can remove the boot files required by both operating systems.

Installing in legacy mode

Mixing UEFI Windows with legacy Linux complicates booting.

Ignoring BitLocker

This can lead to unexpected recovery prompts or prevent the installer from safely detecting Windows.

Shrinking Windows from an unverified third-party tool

Use Windows Disk Management first.

Leaving Windows hibernated

Linux should not write to a hibernated Windows NTFS volume.

Installing to the wrong disk

Always verify model and capacity.

Assuming the first successful Linux boot means Windows is safe

Test both systems before changing encryption or removing recovery media.

When Dual Boot Is Not Appropriate

Avoid or reconsider dual boot when:

The Windows installation is already unstable
The drive is failing
The device has very little storage
There is no verified backup
The BitLocker key is unavailable
The computer is company-managed
The required Linux distribution does not support the hardware
You cannot risk losing access to a business application
Firmware settings are locked
The device uses an unusual storage controller unsupported by Linux

A virtual machine, WSL or a second computer may be safer.

A Safe Dual-Boot Order

Use this sequence:

Confirm that dual boot is genuinely required.
Back up all important data.
Create Windows recovery media.
Save the BitLocker recovery key externally.
Check encryption and decide whether to suspend or decrypt.
Confirm Windows is installed in UEFI mode.
Leave Secure Boot enabled where the distro supports it.
Check Windows for disk errors.
Disable Fast Startup.
Shrink the Windows volume through Disk Management.
Leave the new space unallocated.
Download a supported Linux ISO from the official source.
Create the USB with a trusted imaging tool.
Boot the USB in UEFI mode.
Test the live environment.
Select Install alongside Windows where available.
Read the proposed partition changes carefully.
Install without interrupting the computer.
Test Linux.
Test Windows.
Resume BitLocker.
Install updates in both systems.
Keep the recovery keys and USB media.

Need Help Setting Up Linux and Windows Safely?

A dual-boot installation can provide excellent performance and flexibility, but the disk partitions, encryption and UEFI bootloader must be handled carefully. One incorrect selection can remove Windows or make an encrypted system difficult to recover.

Hamilton Group can assess the computer, protect the existing Windows installation, create a suitable Linux partition and configure a reliable boot menu without unnecessarily wiping the device.

Call 0330 043 0069 or visit hgmssp.com to speak with one of our IT experts.

Previous Next