Home / Troubleshooting / Dual Boot

Dual Boot Problems

Windows and Linux sharing a computer? Here's how to fix the most common issues that come with dual booting.

Symptoms

"Windows Update Killed My Linux Boot"

This is the single most common dual boot issue. A Windows update overwrites the UEFI boot order, making the computer go straight to Windows and skip GRUB entirely. Your Linux install is still there - Windows just pushed it aside.

Quick fix

  1. Restart your computer and enter UEFI/BIOS setup (press F2, F12, Del, or Esc during boot - it depends on your motherboard)
  2. Go to the Boot tab
  3. Find "ubuntu", "fedora", or your Linux distro's name in the boot entries list
  4. Move it above "Windows Boot Manager"
  5. Save and exit

If your Linux entry isn't in the UEFI boot list at all, you'll need to reinstall GRUB. See the boot troubleshooting page for step-by-step instructions.

Prevent this from happening again

You can use efibootmgr to set the boot order from Linux, so it stays set even after Windows updates:

# See current boot order
efibootmgr

# The output shows entries like:
# Boot0000* ubuntu
# Boot0001* Windows Boot Manager
# Boot order: 0001,0000

# Set Linux first
sudo efibootmgr --bootorder 0000,0001

# Verify
efibootmgr

Some UEFI firmwares let Windows override this anyway. If it keeps happening, consider switching to systemd-boot (see the boot page) or using the bcdedit command in Windows to add Linux as a boot option through Windows' own boot manager.

Time Sync Issues

You boot into Linux, the time is correct. You boot into Windows, the clock is wrong (usually off by several hours). Or vice versa.

Why this happens

Windows stores the time on your hardware clock as local time (your timezone). Linux stores it as UTC (universal time) and then calculates your local time from that. When you switch between the two, each one interprets the hardware clock differently.

The fix

The easiest solution is to tell Linux to use local time, matching Windows:

# Tell Linux to use local time on the hardware clock
timedatectl set-local-rtc 1

# Verify
timedatectl
Alternative: Make Windows use UTC instead

If you'd prefer to change Windows instead (technically the "correct" way, since UTC is better practice):

  1. Open PowerShell or Command Prompt as Administrator in Windows
  2. Run this command:
reg add "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation" /v RealTimeIsUniversal /d 1 /t REG_DWORD /f

Then restart Windows. Both OSes will now treat the hardware clock as UTC.

Note: Some older Windows programs may not handle this well. The Linux-side fix (timedatectl set-local-rtc 1) is safer and easier.

Sharing Files Between Windows and Linux

You can access your Windows files from Linux, but there are some things to know.

Reading Windows drives (NTFS)

Modern Linux kernels include an NTFS driver called ntfs3 that lets you read and write NTFS partitions. Older systems use ntfs-3g (FUSE-based, slower but reliable).

# See your partitions
lsblk -f
# Look for "ntfs" partitions - that's Windows

# Mount a Windows partition
sudo mount /dev/sda3 /mnt/windows

# If you get errors about the partition being "dirty" or "hibernated":
# Boot into Windows, disable Fast Startup, then shut down properly
# (Don't use "Restart" - use "Shut down")
Disable Fast Startup in Windows. When Fast Startup is enabled, Windows doesn't fully shut down - it hibernates the kernel. This locks the NTFS partition and Linux can't safely write to it. To disable: Windows Settings > System > Power > Additional power settings > Choose what the power buttons do > Change settings that are currently unavailable > uncheck "Turn on fast startup."
Auto-mount Windows partition on boot

Add an entry to /etc/fstab to mount your Windows partition automatically:

# Find the UUID of your Windows partition
blkid /dev/sda3

# Create a mount point
sudo mkdir -p /mnt/windows

# Add to /etc/fstab (replace the UUID):
# UUID=XXXX-XXXX  /mnt/windows  ntfs3  defaults,nofail  0  0

# For ntfs-3g (older systems):
# UUID=XXXX-XXXX  /mnt/windows  ntfs-3g  defaults,nofail  0  0

# Test the mount
sudo mount -a

The nofail option means Linux will still boot even if the Windows partition can't be mounted (handy if the drive is removed or encrypted).

Shared data partition (recommended approach)

Instead of accessing each other's system partitions, create a separate partition formatted as exFAT or NTFS that both OSes can use as a shared folder:

  • exFAT - Both Windows and Linux support it natively. No file permission issues. Best for a shared data drive.
  • NTFS - Works too, but has the Fast Startup gotcha and may have permission issues on Linux.
  • ext4 - Windows can't read this natively (you'd need third-party software on Windows).
# Install exFAT support (if not already available)
# Ubuntu/Debian:
sudo apt install exfatprogs

# Fedora:
sudo dnf install exfatprogs

# Arch:
sudo pacman -S exfatprogs

BitLocker Warnings

If Windows has BitLocker encryption enabled, you might see a BitLocker recovery screen when booting Windows after modifying the UEFI boot order or partitions from Linux.

Why this happens and how to handle it

BitLocker uses the TPM (Trusted Platform Module) chip to verify that the boot chain hasn't been tampered with. When you install Linux or change the boot order, BitLocker thinks someone is trying to tamper with the system and locks you out.

Before installing Linux alongside Windows with BitLocker:

  1. Back up your BitLocker recovery key - Go to your Microsoft account at account.microsoft.com/devices/recoverykey or find it in Windows Settings > Update & Security > Device encryption
  2. Consider disabling BitLocker on the Windows partition before installing Linux:
# In Windows PowerShell (as Admin):
manage-bde -off C:

If you're already locked out:

  1. Enter your BitLocker recovery key when prompted
  2. Boot into Windows
  3. Suspend BitLocker temporarily when you need to make boot changes:
# Suspend BitLocker for one reboot:
manage-bde -protectors -disable C:
Don't lose your recovery key. If BitLocker locks you out and you don't have the recovery key, your Windows data is unrecoverable. Save it to your Microsoft account, print it, or store it somewhere safe before touching the boot config.

"Should I Dual Boot or Use a VM?"

If you're tired of dual boot headaches, a virtual machine might be a better fit. Here's when each option makes sense:

Dual BootVirtual Machine
PerformanceFull hardware access, native speedShared resources, ~80-90% of native speed
GamingRequired for best performancePossible with GPU passthrough, but complex
ConvenienceMust reboot to switchRun both at the same time
RiskOS updates can break bootIsolated, won't affect host
Disk spaceNeeds separate partitionUses a virtual disk file, can resize easily
Hardware accessFull access to all hardwareLimited (USB passthrough available)
Recommendation: If you just need Linux for development or learning, start with a VM (VirtualBox is free, VMware Workstation Player is free for personal use). You can always dual boot later if you need more performance. If you're gaming or doing GPU-intensive work, dual boot is the way to go.
Quick VM setup options
  • VirtualBox - Free, open source, works on Windows/Mac/Linux. Easy to set up.
  • VMware Workstation Player - Free for personal use. Better performance than VirtualBox.
  • WSL2 (Windows Subsystem for Linux) - Not a full VM, but gives you a Linux terminal and filesystem inside Windows. Great for development, no GUI desktop though (unless you set up WSLg).
  • QEMU/KVM - Linux-native virtualization. Best performance on Linux hosts. Use with virt-manager for a GUI.

Related Issues