One disk, two operating systems, one shared boot partition. Cloning a dual-boot disk works fine — if you respect three caveats that single-system clones never teach you.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ Dual boot workflow
🎥 Watch the full video — HDD change and complete disk clone, step by step
Dual-boot disks clone differently for one reason: the EFI partition and the disk IDs are shared by both systems. Copy everything as a whole disk, keep the old drive out of the first boot, and know the two Windows features that sabotage dual-boot clones before they start.
UEFI boot menu — one disk, two systems
Windows Boot ManagerWindows 11
ubuntuGRUB bootloader
UEFI Firmware SettingsSetup
A dual-boot disk carries two bootloaders sharing one EFI partition. The clone must copy that partition exactly, or one system loses its way in.
1
Always Clone the Whole Disk, Never the Partitions One by One
A dual-boot disk is a single machine with shared parts: one EFI System Partition holding both the Windows boot files and the GRUB bootloader, plus the Windows partitions and the Linux partitions side by side. Partition-by-partition cloning invites mistakes — a missed EFI partition, a wrong order, a Linux swap or root partition skipped by a tool that does not understand it. Choose whole disk clone so every partition lands in the same layout on the new drive.
2
First Boot — Old Disk Disconnected, No Exceptions
This matters even more with dual boot. Both disks now carry partitions with identical UUIDs and identical disk signatures. Linux finds its root partition by UUID, so with both disks attached it may mount the root from the old disk while booting the kernel from the new one — a mix that can corrupt both systems' view of the data. Boot the clone alone first. Only reconnect the old disk after both systems have started cleanly from the new drive, and even then, expect to adjust boot order so the firmware never picks the old disk.
3
GRUB Problems After the Clone
If the PC boots straight to Windows and GRUB never appears, the firmware is simply using the Windows Boot Manager entry first. Open the UEFI boot menu or BIOS boot order and put the ubuntu entry first — GRUB then offers both systems.
If a GRUB rescue prompt appears, the bootloader cannot find its configuration — usually because the EFI partition copy was incomplete. Boot a Linux live USB, and reinstall GRUB to the new disk; the live environment of most distros includes the tools, and Rescuezilla even ships a GRUB repair utility.
Windows updates occasionally rewrite the boot order and hide GRUB again. That is a boot-order problem, not a broken clone — fix it the same way, in firmware settings.
4
Windows Habits That Break Dual Boot During Cloning
Fast Startup: Windows hibernates the system partition instead of shutting down. A partition cloned in that half-asleep state can mount read-only or dirty in Linux afterwards. Disable Fast Startup and do a full shutdown before cloning.
BitLocker: an encrypted Windows partition clones as raw data and may demand the recovery key on the new disk, because the TPM sees changed hardware. Suspend or decrypt BitLocker before cloning, and keep the recovery key ready.
Hibernation files: never clone while either system is hibernated or suspended. Both systems must be fully shut down.
5
Pick a Tool That Understands Linux Partitions
Many Windows cloning tools treat ext4 partitions as unknown data — some copy them blindly sector by sector (slow, and impossible to a smaller drive), and a few skip them entirely. Clonezilla understands ext4, btrfs and other Linux filesystems natively and copies only used blocks; Rescuezilla wraps the same abilities in a friendly interface. For a dual-boot disk these are the safe free choices, with the usual Clonezilla caveat: by default it will not shrink partitions for a smaller destination.
🔴 Honest note: dual-boot cloning is not harder because of Linux — it is harder because two bootloaders and two sets of disk IDs are involved. Whole-disk clone, fully shut down, first boot alone: follow those three and dual boot clones are routine.
🎥 Watch the Complete Video Guide
The full process on a real PC — changing the HDD and cloning the complete disk, step by step.
GRUB disappeared after cloning and Windows starts directly. Is the clone broken?
Almost never. The firmware is just booting the Windows Boot Manager entry first. Put the ubuntu entry first in the UEFI boot order and GRUB returns with both systems listed. Nothing about the clone itself needs redoing.
Can I clone a dual-boot disk to a smaller SSD?
Yes, with the same used-space rule — but your tool must be able to shrink both NTFS and ext4 partitions. Clonezilla-based tools handle both filesystems, though partitions must be shrunk beforehand; pure Windows tools often cannot resize the Linux side at all.
Linux boots but Windows shows the wrong time afterwards. Related?
Yes, and harmless. Windows expects the hardware clock in local time, Linux in UTC, so dual-boot systems often disagree by a few hours after switching systems. It is a clock convention issue that exists with or without cloning — set one system to match the other and it disappears.
This guide is based on the Technical Anshu video on cloning a full disk to a new drive • Stuck on a step — ask in the video comments and the community will help 🙏