Dual-Booting Windows 11 and Linux Without Breaking the Bootloader
MmMm
Dual boot gives you two complete operating systems on the same computer.
You might use:
Windows 11 for Microsoft 365, gaming or specialist business applications
and:
Linux for development, open-source tooling, security work or a different desktop environment.
Unlike Windows Subsystem for Linux or a virtual machine, each operating system runs directly on the hardware.
That can be extremely useful.
But dual boot also means modifying:
partitions
UEFI boot entries
encryption-sensitive startup components
sometimes storage-controller settings
So the objective should not be:
“Install Linux and hope GRUB finds Windows.”
The safer approach is:
protect Windows first → create Linux space deliberately → install both in UEFI mode → preserve the EFI System Partition → test both boot paths before changing anything else.
First: Do You Really Need Dual Boot?
Before repartitioning the computer, decide whether dual boot is actually necessary.
Consider WSL if you mainly need:
Linux shell
development tools
package managers
scripting
containers
Consider a virtual machine if you need:
an isolated Linux environment
testing
experimentation
snapshots
quick disposal/recreation
Dual boot makes more sense when you need:
native GPU access
maximum CPU performance
direct USB/hardware access
specialist Linux drivers
native storage performance
For a business workstation, simpler is usually better unless there is a clear reason Linux needs direct hardware access.
Understand the Modern Boot Process
Most Windows 11 PCs now use:
UEFI
GPT partitioning
Secure Boot
TPM
BitLocker or Device Encryption
The old BIOS/MBR model found in many internet tutorials is therefore the wrong mental model.
On UEFI systems there is normally a small FAT-formatted:
EFI System Partition — ESP
Windows stores its boot files in a location such as:
\EFI\Microsoft\Boot
A Linux distribution may add its own files under something like:
\EFI\ubuntu
or:
\EFI\fedora
The UEFI firmware also stores separate boot entries.
A correctly configured machine can therefore contain:
Windows Boot Manager
and:
Ubuntu/Fedora/Linux Boot Manager
at the same time.
Linux does not need to overwrite Windows Boot Manager to coexist with it.
Before You Start: Back Up Properly
Partition changes are normally safe.
Normally is not enough when the disk contains important data.
Back up:
documents
photographs
local email archives
application data
VMs
licence information
unsynchronised OneDrive data
anything business-critical
Use another physical device or a properly protected cloud backup.
A Windows restore point is not an adequate substitute.
Save the BitLocker Recovery Key
This should happen before touching UEFI settings or partitions.
Windows 11 devices may use either:
BitLocker
Device Encryption
BitLocker uses TPM measurements of the boot environment as part of its protection model. Changes to firmware or boot configuration can therefore trigger recovery. Microsoft describes BitLocker as using UEFI/TPM integrity measurements to protect the pre-boot environment.
Make sure you have the 48-digit recovery key somewhere accessible without relying on the PC you are modifying.
Do not keep the only copy on the encrypted C: drive.
For a company-owned computer, the recovery key may already be escrowed by IT.
Suspend BitLocker Before Expected Boot Changes
Suspending BitLocker is different from decrypting the disk.
Suspension temporarily relaxes the normal TPM-based boot validation while leaving the actual data encrypted.
For planned bootloader/firmware work, that can be preferable to decrypting the whole drive.
From an elevated Command Prompt:
manage-bde -protectors -disable C:
After everything works:
manage-bde -protectors -enable C:
Still keep the recovery key.
Never assume suspension removes the need for it.
Check That Windows Uses UEFI
Press:
Windows + R
and run:
msinfo32
Look for:
BIOS Mode
For a modern Windows 11 installation you would normally expect:
UEFI
Now check the disk.
Open:
Disk Management
and confirm that the Windows disk uses:
GPT — GUID Partition Table
The key rule is:
Windows UEFI + Linux UEFI
Do not install Linux in Legacy/CSM mode next to a UEFI Windows installation.
Mixing the two creates unnecessary boot complications.
Shrink Windows From Windows
If both systems will share the same SSD, create Linux space using:
Disk Management
Right-click the Windows partition.
Choose:
Shrink Volume
Release the amount of storage you want Linux to use.
Then leave the result as:
Unallocated
Do not create a temporary NTFS volume merely so Linux can delete it again.
And do not shrink your active Windows NTFS partition from Linux unless you have a specific expert reason.
Let Windows resize its own filesystem.
Leave Enough Space for Windows
Do not shrink C: until Windows has barely any room left.
Windows still needs space for:
feature updates
cumulative updates
applications
temporary files
OneDrive
recovery
hibernation/pagefile
future growth
How much Linux needs depends on workload.
A lightweight installation may use relatively little storage.
A developer machine with:
Docker
VMs
SDKs
games
local repositories
can consume hundreds of gigabytes surprisingly quickly.
Do Not Delete the EFI System Partition
During Linux installation you may see several small Windows partitions.
Examples include:
EFI System Partition
Microsoft Reserved Partition
Recovery partition
Do not delete them because they look unfamiliar.
In particular:
do not format the existing Windows EFI System Partition.
Linux normally needs to place its own UEFI files alongside the existing Windows boot files.
Formatting the ESP can remove Windows Boot Manager and turn a straightforward installation into a recovery job.
Keep Secure Boot Enabled Where Possible
Modern distributions such as Ubuntu support Secure Boot using signed boot components. Ubuntu describes its boot chain as using signed components validated through Canonical's certificate and a Microsoft-signed shim.
So:
“Installing Linux? Disable Secure Boot.”
is outdated as general advice.
In 2026 there is another reason to use current installation media.
Microsoft transitioned signing of third-party UEFI applications from the older 2011 certificate authority to its newer 2023 UEFI CA on 26 June 2026.
That means:
Use a newly downloaded installer image.
Do not reach for a USB stick containing a five-year-old Linux installer.
Be Careful With Intel RST, VMD and AHCI
This is one area where dual-boot guides can genuinely break Windows.
A Linux installer may fail to see the internal SSD because the laptop uses:
Intel RST
Intel VMD
RAID-style storage mode
You may then find advice saying:
“Just change the BIOS setting to AHCI.”
Do not do that blindly.
If Windows was installed expecting its current storage-controller mode, changing it without preparing Windows can make Windows unbootable. Your current article already warns about this correctly.
If Linux cannot see the SSD:
1. Check the laptop manufacturer's guidance.
2. Check the Linux distribution's current installer guidance.
3. Verify whether that specific storage controller is supported.
4. Only change firmware storage mode when you understand how Windows will be prepared for it.
Fast Startup Matters if Linux Will Write to Windows Partitions
Windows Fast Startup uses a hybrid shutdown state.
That becomes relevant if Linux will mount and write to Windows NTFS partitions.
A Windows filesystem left in a hibernated/fast-startup state should not casually be modified from another operating system.
For systems regularly sharing Windows volumes with Linux, consider disabling Fast Startup.
One option is:
powercfg /hibernate off
from an elevated Command Prompt.
Be aware that this also disables normal Windows hibernation.
If Linux never writes to Windows volumes, this issue becomes considerably less important.
Boot the Linux Installer Explicitly in UEFI Mode
When opening the PC's one-time boot menu, you may see more than one entry for the USB stick.
Choose the one identified as:
UEFI
Then carefully review the installer partition screen.
For mainstream distributions, an option such as:
Install alongside Windows Boot Manager
may be the simplest choice.
For manual partitioning:
place / in the unallocated Linux space
optionally use /home
use swap according to distribution/current requirements
The critical rule is:
Linux goes into Linux space.
Not:
“that large Windows partition looks about right.”
Test Both Operating Systems Immediately
Once installation completes:
1. Boot Linux.
2. Restart.
3. Boot Windows.
4. Restart.
5. Boot Linux again.
Check:
networking
graphics
storage
clock
BitLocker behaviour
boot menu
Do this before:
repartitioning further
performing a distribution upgrade
deleting the installer USB
You want proof that both boot paths are healthy.
Windows Suddenly Boots Directly? Don't Reinstall GRUB Yet
This is one of the biggest misconceptions around dual boot.
Suppose Windows starts directly after:
Windows Update
BIOS update
firmware reset
That does not automatically mean GRUB was deleted.
The firmware may simply have moved:
Windows Boot Manager
to the top of its boot order.
Open the one-time UEFI boot menu.
Look for:
Ubuntu
Fedora
Linux Boot Manager
If Linux starts:
your Linux bootloader still exists.
Simply restore the preferred UEFI boot order.
Your current article correctly makes this distinction.
There Is No Requirement for GRUB to Control Windows
Another useful simplification:
You do not have to configure one giant GRUB menu.
You can keep:
Windows Boot Manager first
and use the PC's UEFI boot menu when you want Linux.
That can actually produce cleaner separation.
If you prefer GRUB as the normal menu, that is also fine.
The point is:
both boot managers can coexist.
Windows Missing From GRUB?
First, try:
Windows Boot Manager
from the UEFI firmware menu.
If Windows starts normally, its bootloader is fine.
Then on Ubuntu-family systems:
sudo update-grub
may detect the Windows installation.
But be aware that automatic Windows detection through os-prober varies between distributions and configurations.
Do not manually edit:
/boot/grub/grub.cfg
because that file is generated and your changes can be overwritten.
Linux Entry Missing Completely?
If the Linux partitions still exist but the firmware boot entry is gone:
1. Boot a current Linux live USB in UEFI mode.
2. Verify that the Linux partitions still exist.
3. Mount the installed Linux system.
4. Follow that distribution's current UEFI bootloader recovery procedure.
5. Re-register/reinstall its signed UEFI boot files.
6. Rebuild its boot configuration.
Avoid copying an old:
grub-install /dev/sda
tutorial designed for BIOS/MBR systems onto a modern UEFI/GPT machine.
Repair the boot architecture you actually have.
Windows Boot Manager Broken?
Windows provides BCDBoot for rebuilding its boot files.
If the Windows partitions are intact but Windows Boot Manager has genuinely been damaged, use Windows Recovery Environment and repair the Windows boot environment.
Do not immediately delete Linux.
A broken Windows boot entry and a perfectly healthy Linux installation can exist at exactly the same time.
Again:
repair the broken layer.
Two SSDs Are Usually Cleaner
If the PC supports two physical drives, I generally prefer:
SSD 1 → Windows
SSD 2 → Linux
Advantages include:
no shrinking of Windows
simpler OS replacement
less risk of formatting the wrong partition
clearer physical separation
For even greater independence, each disk can have its own EFI System Partition.
That way, either SSD can potentially remain bootable by itself.
But verify where the Linux installer intends to place its EFI files.
Do not assume that choosing SSD 2 for / automatically means the installer will also put the bootloader there.
A Safe Dual-Boot Checklist
Before installation:
back up important data
save the BitLocker recovery key
confirm Windows uses UEFI
confirm the disk is GPT
download current Linux installation media
keep Secure Boot enabled where supported
shrink Windows using Windows Disk Management
leave the Linux space unallocated
During installation:
boot the USB in UEFI mode
confirm the correct disk
do not format the Windows ESP
leave Windows Recovery/MSR partitions alone
install Linux only into the intended space
do not casually change RST/VMD/AHCI
After installation:
test Linux
test Windows
verify BitLocker
inspect firmware boot entries
retain the installer/recovery media until everything is proven stable
The key principle is:
Protect Windows first, then add Linux alongside it. Do not rebuild a bootloader until you have proved it is actually broken.
How Hamilton Group Can Help
Hamilton Group can help with:
Windows 11
Linux
dual-boot installations
UEFI/GPT
Secure Boot
BitLocker
GRUB
bootloader recovery
storage and partitioning
Linux workstations
For business systems, we can also advise whether dual boot is genuinely the best architecture or whether WSL, virtualisation or a dedicated Linux device would provide lower risk and simpler support.
Visit hgmssp.com or call 0330 043 0069.