This page sits in our support section because dual boot questions are among the most common follow-ups after someone installs a lightweight Linux distribution or tries ChromeOS Flex alongside an existing Windows setup. The search intent is preventative: you want to know what can go wrong and how to avoid it before you start modifying your disk.
After more than a decade of setting up dual boot configurations on refurbished hardware - from 2010 netbooks with tiny eMMC storage to 2017 business laptops with NVMe drives - I have seen every flavour of partition accident and bootloader conflict. Most of them are entirely preventable with a thirty-minute preparation routine. Below we cover partition safety, bootloader behaviour (GRUB and Windows Boot Manager), what actually goes wrong in practice, how to prepare safely, and a step-by-step checklist you can follow before your first dual boot installation. For broader support topics, visit the Support hub.
Understanding Partition Safety
A dual boot setup requires at least two operating system partitions on your disk - one for Windows and one for Linux. If your machine currently has a single Windows partition filling the entire drive, you need to shrink it to make room. This resizing step is where the highest risk of data loss occurs.
Modern partition tools handle this reliably in most cases, but there are situations where the operation fails or produces unexpected results:
- The drive has filesystem errors that were not detected before resizing
- Power is lost during the resize operation (always use a charged battery or UPS)
- The Windows partition has unmovable system files near the end of the disk, preventing a clean shrink
- The disk has bad sectors that cause read errors during data relocation
- BitLocker encryption is active and the partition tool does not handle it correctly
Bootloader Behaviour - GRUB and Windows Boot Manager
When you install Linux on a dual boot machine, the installer typically writes GRUB (Grand Unified Bootloader) to the disk's boot sector or EFI System Partition. GRUB then becomes the first thing that runs when your machine starts, and it presents a menu letting you choose between Linux and Windows.
This works well in most cases. The problems arise in specific scenarios:
UEFI systems (most machines from 2013 onward)
GRUB installs as an EFI application alongside the Windows Boot Manager. Both bootloaders coexist on the EFI System Partition. The firmware's boot order determines which one loads first. A Windows update can sometimes reset the boot order, making it appear that Linux has vanished - but it is still installed. You just need to change the boot order back in your BIOS/UEFI settings or use the firmware boot menu (usually F12 or Esc at startup).
Legacy BIOS systems (pre-2013 machines)
GRUB writes to the Master Boot Record (MBR), replacing the Windows bootloader entry. If you later remove the Linux partition without restoring the MBR first, the machine will fail to boot entirely. The fix requires a Windows recovery USB and the commands bootrec /fixmbr and bootrec /fixboot. Always restore the MBR before deleting a Linux partition on legacy BIOS setups.
Hybrid BIOS/UEFI systems (2011-2013 transitional machines)
Some machines from this era support both modes but behave unpredictably when both are enabled. If your machine has a "Legacy/UEFI" or "CSM" option in BIOS settings, pick one mode and stick with it. Installing Windows in UEFI mode and Linux in legacy mode (or vice versa) creates a configuration where GRUB cannot see the Windows installation at all.
What Can Go Wrong with Dual Boot Setups
These are the failure modes I see most often when helping people set up dual boot configurations on older hardware:
Accidentally formatting the wrong partition
The Linux installer shows a list of partitions identified by labels like /dev/sda1, /dev/sda2. If you are not sure which partition is which, you can identify them by size - your Windows partition is usually the largest one. Better still, use a tool like GParted from a live USB to label your partitions before starting the installer. A clearly labelled "WINDOWS" and "LINUX" partition removes all ambiguity.
Windows update resets the boot order
Major Windows feature updates (the kind that run for 20-40 minutes) often reset the UEFI boot order so Windows Boot Manager loads first. GRUB and Linux are still present - you just need to enter your firmware boot menu and select the Linux entry, or change the boot order back in BIOS settings.
Running out of space on the Windows partition
If you shrink your Windows partition too aggressively, Windows will eventually run out of room for updates. Leave at least 40-50 GB for a Windows 10 partition that needs to receive updates. If your total drive is only 120 GB, consider whether dual booting is practical or whether a full replacement with Linux would be a better use of the limited space.
Clock discrepancy between Windows and Linux
Windows stores the system clock as local time. Linux stores it as UTC by default. When you switch between the two, the clock jumps by your timezone offset. The fix is to tell Linux to use local time instead: timedatectl set-local-rtc 1. This is harmless and eliminates the annoyance.
How to Prepare Safely
Preparation takes roughly thirty minutes and eliminates nearly all risk from the dual boot process. Every step below is something I do as standard practice before any partitioning work, even on machines I have worked with before.
- Back up everything to an external drive. Use Windows Backup, Clonezilla, or simply copy your important folders to a USB hard drive. If the partition operation fails, you need a way to get your files back.
- Run chkdsk on the Windows partition. Open Command Prompt as administrator and run
chkdsk C: /f. This fixes filesystem errors that could cause the resize to fail. Reboot if prompted. - Disable BitLocker if it is active. Resizing an encrypted partition requires decryption first. Go to Control Panel, BitLocker Drive Encryption, and select "Decrypt drive." This can take several hours on a mechanical drive.
- Disable Fast Startup in Windows. Fast Startup locks the NTFS partition in a hibernated state. Linux cannot safely mount or resize a hibernated NTFS partition. Disable it in Power Options, "Choose what the power buttons do," then uncheck "Turn on fast startup."
- Note your firmware boot mode. Check whether your machine is running in UEFI or Legacy BIOS mode. On Windows, open System Information (msinfo32) and look at "BIOS Mode." Install Linux in the same mode that Windows uses.
- Prepare a Windows recovery USB. Even if everything goes perfectly, having a recovery drive means you can fix the Windows bootloader if it ever gets displaced. Create one from Settings, Recovery, "Create a recovery drive."
Step-by-Step Dual Boot Checklist
Follow this sequence when you are ready to install. Each step is in the order I recommend from years of doing this on machines ranging from netbooks to workstations.
Step 1 - Verify your backup is complete and accessible
Plug in your external backup drive and confirm you can open files from it. A backup you cannot read is not a backup.
Step 2 - Shrink the Windows partition from inside Windows
Open Disk Management (right-click Start, select "Disk Management"), right-click the main Windows partition, and select "Shrink Volume." Let Windows calculate the available space. Leave at least 40-50 GB for Windows. The freed space will appear as "Unallocated" - do not format it. The Linux installer will use it.
Step 3 - Boot from your Linux live USB
Insert the USB drive and restart. Enter the firmware boot menu (F12, F2, Esc, or Del depending on manufacturer) and select the USB drive. If it does not appear, check that USB boot is enabled in BIOS settings. For more on USB boot issues, see our USB boot troubleshooting guide.
Step 4 - Test the live environment first
Before installing, verify that Wi-Fi, display, and audio work in the live session. If critical hardware does not work from the live USB, it is unlikely to work after installation without manual driver configuration.
Step 5 - Choose "Install alongside Windows" or manual partitioning
Most modern Linux installers detect the existing Windows installation and offer an "Install alongside" option. This is the safest automated choice. If you prefer full control, select manual partitioning and point the installer at the unallocated space you created in Step 2.
Step 6 - Verify the GRUB menu after first reboot
After installation completes and the machine reboots, you should see a GRUB menu with entries for both Linux and Windows. Select each one to confirm both operating systems boot correctly. If Windows is missing from the menu, boot into Linux and run sudo update-grub to regenerate the menu.