How to Install Linux Mint (All Editions) on a Windows 11 Laptop
DEV Community

How to Install Linux Mint (All Editions) on a Windows 11 Laptop

Last Tested On

Linux Mint 22.3 (XFCE), Ventoy 1.1.17, Windows 11

Hardware: ASUS VivoBook (i3-7020U) & HP (Pentium N3710)

A complete guide to installing Linux Mint alongside Windows 11. While this guide uses Linux Mint XFCE as the primary case study (due to its performance on low-end hardware), these steps apply to Cinnamon and MATE editions as well.

Cinnamon and MATE install identically but want more RAM and GPU headroom. Below 8 GB RAM, or on graphics hardware that struggles with desktop effects, use XFCE.

I wrote this after dual-booting two laptops - an HP Pentium with a phone-bridged download bottleneck, and an ASUS whose drive threw unexplained I/O errors mid-install. Every step here was run on real hardware in real conditions. If something could go wrong, it went wrong here first.

Which Guide Should You Read?

This guide = Clean step-by-step reference. Use this if you want to install Linux Mint efficiently with a proven procedure.

The narrative series = The full story of why this guide exists, including failures, kernel errors, and the diagnostic process behind every decision made here. Use this if you want to understand how to troubleshoot when YOUR installation doesn't go as planned.

Note on Editions & File Names

This guide applies equally to the XFCE, Cinnamon, and MATE editions. To keep the text clean, we use the XFCE filename and performance baseline as the running example. If you are installing Cinnamon or MATE, simply swap xfce for cinnamon or mate in the ISO filenames and GRUB menu selections. The commands, partition sizes, and installation steps remain identical.

This guide uses progressive disclosure. Each step shows the essential instructions first. If you need deeper explanations, troubleshooting, or advanced procedures, click the expandable sections.

Step 0: Suspend BitLocker (~5-10 minutes)

If BitLocker is enabled, you MUST suspend it before partitioning. If you alter partitions or add a new bootloader (GRUB) while BitLocker is actively enforcing TPM checks, Windows will lock the drive on the next reboot and demand a 48-digit recovery key.

Open PowerShell as Administrator.

Check current status:

manage-bde -status C:

If Protection Status is ON, inspect which protectors actually exist on the volume:

manage-bde -protectors -get C:

Back up your 48-digit recovery key based on what that output shows:

  • If a Numerical Password protector is listed: copy the key to your clipboard:

manage-bde -protectors -get C: -Type RecoveryPassword | clip

(This prints nothing - the key is now on your clipboard. Paste it into Notepad immediately to confirm it copied.)

  • If only TPM is listed (no Numerical Password): no recovery key exists on this volume yet. Create one first:

manage-bde -protectors -add C: -RecoveryPassword

The new 48-digit key is printed directly in the command output.

🛑 Do not proceed until your 48-digit recovery key exists in at least two places off this machine - saved to your Microsoft account or cloud AND written on paper. A key stored only on the encrypted drive is not a backup. If BitLocker locks the drive and the key is gone, everything on C: is gone.

Suspend BitLocker protection (this takes seconds and does not decrypt the drive):

manage-bde -protectors -disable C: -RebootCount 0

(Without -RebootCount 0, suspension expires after ONE reboot and silently re-arms mid-install. Zero means suspended until you re-enable it manually in Step 9.)

Verify suspension:

manage-bde -status C:

(Protection Status should now say Off, but Percentage Encrypted will remain 100%).

Step 0 receipts: inspect, create the key, verify suspension.

▶ Why is BitLocker dangerous for dual boot? The TPM Measurement Trap BitLocker ties the decryption key to the TPM (Trusted Platform Module) chip. The TPM measures the boot chain. When you install Linux and add GRUB to the EFI partition, you change the boot chain. On the next boot, the TPM may detect this unauthorized change and lock the drive to protect the data. By suspending BitLocker, you temporarily place a clear-text key in the volume metadata, allowing the system to boot through the new GRUB chain without tripping the TPM alarm.

When the typical Microsoft backup routes fail The standard GUI paths - Control Panel → BitLocker → Back up your recovery key, Settings → Device encryption - only work if a recovery key was escrowed when BitLocker was provisioned. On many machines, BitLocker was enabled TPM-only. There is no key in your Microsoft account, no key in the GUI, and nothing to print. The CLI chain above is authoritative because it queries the volume directly.

Windows 11 Home Note (Device Encryption) If you are on Windows 11 Home, you likely have Device Encryption. Warning: Clicking Turn off in the Settings GUI initiates a full decryption process that can take hours. It does not temporarily suspend the TPM. Use the PowerShell manage-bde commands above for instant suspension.

Re-enabling after install: covered in Step 9, after dual-boot verification. Do not re-enable before then.

Step 1: Disable Fast Startup (~3 minutes)

  • Press Win + R → type control → Enter
  • Go to Power Options → Choose what the power buttons do
  • Click Change settings that are currently unavailable
  • Uncheck Turn on fast startup (recommended)
  • Click Save changes
  • (Optional but Recommended) Open PowerShell as Administrator and run:

powercfg -h off

(This fully disables hibernation and deletes hiberfil.sys, ensuring a clean shutdown)

The one box that matters: fast startup off. Sleep and lock stay on - you are not disabling power management, only the hybrid shutdown that freezes NTFS.

▶ Why does Fast Startup break dual boot? Fast Startup is a hybrid shutdown feature. Instead of fully shutting down, Windows writes the kernel session to a file called hiberfil.sys and hibernates. This leaves the NTFS partition in a semi-locked state. When Linux tries to access that partition during dual boot, it can cause file system conflicts, write errors, and strange boot behavior. The fix is simple: disable Fast Startup so Windows performs a true, complete shutdown every time.

Step 2: Shrink the Windows Partition (~15-30 minutes)

This is where most dual-boot attempts fail. If Windows only lets you shrink a tiny amount, see the collapsible section below.

  • Right-click Start → Disk Management
  • Right-click C: → Shrink Volume
  • Wait for Windows to calculate available space
  • Enter the amount to shrink in MB (1GB ≈ 1024 MB) (Windows Disk Management labels these values MB, but they behave like MiB: 1 GiB = 1024 MiB. Use the formula: intended Linux space in GiB × 1024 = MB to enter. Example: 90 GiB = 92160 MB. Do not enter more than the Size of available shrink space in MB value shown above it.)
  • Click Shrink
  • Verify the Unallocated space appears

The shrink on real hardware: C: drops to 87.77 GB and the 150 GB unallocated window appears exactly where the installer lays Linux. Black fill is Windows' own Unallocated legend; the red labels are added for orientation.

Recommended partition split for a 256GB SSD:

  • Partition Size Purpose Windows 11 (C:) ~80-120GB Windows system and apps Unallocated ~90-150GB Reserved for Linux Mint EFI / Recovery Remaining System partitions (do not touch)

DRIVE LAYOUT VISUALIZED: BEFORE: [EFI][MSR][Windows C: ████████████][Recovery] AFTER: [EFI][MSR][Windows C: ██████][Unallocated █████][Recovery]

⚠️ Problem: Windows only lets you shrink a tiny amount? Why this happens: Windows has unmovable system files (pagefile.sys, hiberfil.sys, System Restore points) pinned to the end of the partition. Disk Management cannot shrink past them. How to fix it:

A. Disable the pagefile temporarily:

  1. Press Win + R → type sysdm.cpl → Enter
  2. Go to Advanced tab → Performance Settings
  3. Go to Advanced tab → Virtual Memory Change
  4. Uncheck Automatically manage paging file size
  5. Select No paging file → click Set → OK
  6. Restart when prompted

B. Disable hibernation:

  1. Open PowerShell as Administrator
  2. Run:
powercfg -h off

C. Disable System Protection:

  1. Press Win + R → type sysdm.cpl → Enter
  2. Go to System Protection tab → Select C: → click Configure
  3. Select Disable system protection
  4. Click Apply to commit the change while keeping the dialog open.
  5. Click Delete to remove existing restore points. (Warning: This removes an existing Windows recovery option. Ensure you have backups).
  6. Click OK to close the dialog.

D. Restart the computer and try shrinking again. The available shrink space should increase significantly.

E. After shrinking, RE-ENABLE only these settings:

  1. Pagefile: Check Automatically manage paging file size.
  2. System Protection: Turn on system protection.

The unmovable-file cleanup, in order: release the pagefile, disable hibernation, disable System Protection and delete restore points, then return to Shrink Volume with a larger available-shrink number. Red boxes mark the controls to change.

Step 3: Download the Linux Mint ISO (~15-60 minutes)

  • Go to the official Linux Mint download page
  • Select your Edition ( XFCE , Cinnamon , or MATE )
  • Choose a download method: Direct mirror or Torrent
  • Wait for the download to complete (~2.5GB to 2.8GB)
  • Verify the ISO Checksum:

Quick Method: Open Command Prompt, paste this exact line (adjust the path), and press Enter:

certutil -hashfile "C:\Users\YourName\Downloads\linuxmint-22.3-xfce-64bit.iso" SHA256

Compare the output hash with the official checksum on linuxmint.com/verify.php.

▶ When and why to use torrent instead of mirrors, including qBittorrent setup What is a mirror? A mirror is a server in a specific country that hosts a copy of the Linux Mint ISO. Mirror availability depends on local infrastructure. During our installation in Nigeria, the closest African mirrors were unreliable. Why use a torrent? A torrent downloads the file in small pieces from multiple peers simultaneously. This is more resilient on unstable connections because the download can pause and resume without losing progress. The .torrent file (a tiny ~28KB metadata file) is universal; it will automatically fetch the specific edition (Cinnamon, MATE, or XFCE) you selected on the download page. How to set up qBittorrent (Standard Flow):

  1. Download qBittorrent from the official site ONLY. (Fake installers carrying malware are common on third-party sites). The colored boxes are the route: official homepage arrow, then the stable v5.2.4 link - the release candidate below it deliberately unmarked - then SourceForge's Latest Version, then the malware-scanned setup.exe. This is what official source only looks like click by click, with the decoy rc build visibly declined.
  2. Install and open qBittorrent. Approve administrator access only for the installer if Windows requests it, and click through any post-installation wizards using default settings. Next, Next, Finish - the wizard adds nothing you didn't ask for. The last panel is the prize: a clean, empty client with a live DHT count, ready for the .torrent you are about to feed it.
  3. Download the Linux Mint .torrent file from the Mint download page. The torrent is the 28.5 KB line, not the 2.8 GB one. The red box marks the metadata file you actually pull into qBittorrent; the 2.8 GB figure above it is the ISO itself, which the torrent then fetches.
  4. Add the torrent to qBittorrent: Open the qBittorrent app. Click the "+" (Add Torrent File) icon on the top toolbar (or go to File > Add Torrent File). Browse to your Downloads folder, select the .torrent file, and click Open.
  5. A New Torrent dialogue menu will appear. Leave it on default settings and click OK. The download starts. Leave it alone and click OK. The red mark is the whole instruction: default settings, no tweaking, Start torrent already ticked so the pull begins the moment you confirm.
  6. (Note on Seeding: After reaching 100%, you are uploading (seeding) to others. On metered or capped data, right-click the file → Pause. On unmetered connections, leaving it seeding for a while keeps the torrent alive for the next person in your region). A healthy pull on a flaky link: 90 seeds feeding 3 peers, speed holding in the MiB/s range, ETA under ten minutes. This is the resilience the torrent method buys you when a mirror stalls. The finish line, paused: 100% and stopped rather than seeding - the state the step-6 note describes for metered or capped connections. The bottom counters (2.85 GiB down, 848 KiB up) are the proof the pull was real.

Fallback for Unstable/Restricted Connections: If the download is stalling or painfully slow:

  1. Add trackers: Go to newtrackon.com/lists and click the green copy icon to copy all trackers. In qBittorrent, highlight the downloading Mint file and right-click it → Edit trackers. A dialogue box appears with a single default tracker ending in ...announce. Move your cursor to the very end of that text and press ENTER to create a blank line, then paste the new trackers. (Without this line spacing, qBittorrent may parse the pasted trackers as a single entry).
  2. Adjust connection limits: Click the Option icon (⚙️) in the top left bar → click Connection. Change the values from default to the recommended values:
    • Global Maximum Number of connections: 200-300
    • Maximum Number of connection per Torrent: 50-80
    • Global Maximum Number of Uploaded slots: 4 (DHT and PeX are enabled by default. No action needed there). The tuned tab: 250 / 60 / 4, all four boxes ticked. The greyed-out Apply is the receipt - these are committed values, not typed-and-abandoned.

Verify File Integrity (Step-by-step for Beginners): Windows has a built-in tool to verify the ISO without needing third-party software.

Read on DEV Community ↗ ← Back to News

Comments

No comments yet. Start the discussion.