<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: King Anthony</title>
    <description>The latest articles on DEV Community by King Anthony (@kinganthony).</description>
    <link>https://dev.to/kinganthony</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4112449%2F7f703b1d-bd76-4054-b099-5e5872eb90f5.webp</url>
      <title>DEV Community: King Anthony</title>
      <link>https://dev.to/kinganthony</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kinganthony"/>
    <language>en</language>
    <item>
      <title>Linux Mint: The First Hour After Install (Mirrors, Software, TimeShift, Updates, Tethering)</title>
      <dc:creator>King Anthony</dc:creator>
      <pubDate>Mon, 16 Nov 2026 12:25:11 +0000</pubDate>
      <link>https://dev.to/kinganthony/linux-mint-the-first-hour-after-install-mirrors-software-timeshift-updates-tethering-1iao</link>
      <guid>https://dev.to/kinganthony/linux-mint-the-first-hour-after-install-mirrors-software-timeshift-updates-tethering-1iao</guid>
      <description>&lt;h2&gt;
  
  
  Linux Mint: The First Hour After Install
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Last tested on:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Linux Mint 22.3 (XFCE — steps are identical on Cinnamon and MATE)&lt;/li&gt;
&lt;li&gt;Hardware: HP 15-bs0xx (Pentium N3710) &amp;amp; ASUS VivoBook X509UA (i3-7020U)&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;You installed Linux Mint. GRUB works, Windows still boots, and the desktop is waiting. This is the first hour: five tasks, in the order they should happen. Mirrors come first, because every update you will ever pull travels through them. Software installation comes before updates, because you need to know what a package &lt;em&gt;is&lt;/em&gt; before the numbers start disagreeing. TimeShift comes before anything risky, because an undo button you configure afterward is no undo button at all. Tethering comes last, because it's the backdoor you hope never to need.&lt;/p&gt;

&lt;p&gt;Every step stands alone. The failure recoveries live in collapsibles; the four field reports behind them — two incident reports, one drill, one field note — sit in the Appendix, each linked from the step that spawned it. Skip them all and lose nothing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Haven't installed yet?&lt;/strong&gt; Start with the installation guide: &lt;a href="https://kinganthony.tech/blog/linux-mint-install/" rel="noopener noreferrer"&gt;How to Install Linux Mint (All Editions) on a Windows 11 Laptop&lt;/a&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 1: Optimize Your Software Mirrors {#step-1-mirrors}
&lt;/h2&gt;

&lt;p&gt;Mirrors are the software servers that host Linux Mint's packages. Picking a fast one speeds up every download and update for the life of the install — this takes about two minutes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Open the menu and launch &lt;strong&gt;Software Sources&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Click &lt;strong&gt;Main repository&lt;/strong&gt; (the default, e.g. &lt;code&gt;zena&lt;/code&gt;). Mint runs a speed test against every available mirror — about a minute.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Pick the fastest one (top speed in KB/s or MB/s). It doesn't have to be geographically close to you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Click &lt;strong&gt;Apply&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Repeat for the &lt;strong&gt;Base repository&lt;/strong&gt;, then &lt;strong&gt;Apply&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6.&lt;/strong&gt; Click the &lt;strong&gt;green refresh icon&lt;/strong&gt; to update the cache. Give it a few minutes.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbumrgmt18vmpfjm0qq3s.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbumrgmt18vmpfjm0qq3s.webp" alt="Two-panel collage. Left: the Select a mirror speed-test dialog ranking Liquid Telecom at 359 kB/s above University of Free State, Cicku, Dimension Data, Retention Range, Linux Mint, and an unreachable cloud.mu. Right: the Software Sources window with Main (zena) on mirrors.cicku.me, Base (noble) on archive.ubuntu.com, optional sources off, and the green Click here to update the APT cache button." width="800" height="371"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 1: The two screens that bracket the operation. The speed test ranks mirrors by how fast they answer — Liquid Telecom on top here, cloud.mu unreachable — and once both repositories are Applied, the green button is what kicks off the cache refresh in step 6.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; The speed test ranks mirrors by how fast they &lt;em&gt;answer&lt;/em&gt;, not how long they can &lt;em&gt;carry a download&lt;/em&gt;. The top pick is usually right — but if a refresh ever stalls, the fix is simply taking the next mirror down the list.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;On a bad network day, that final cache refresh can lock up — sometimes for half an hour at a stretch. If it happens to you:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;🚨 The cache refresh froze — or the shield went red&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A stalled mirror fetch does not mean your system is broken. It means the connection somewhere stopped delivering mid-download, and Mint's GUI is holding the line open — politely, forever. It's rare, but on unreliable networks it happens. The recovery path below goes from least to most invasive. Stop the moment the GUI frees.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2tgxrw8zcfvwtqk007oc.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2tgxrw8zcfvwtqk007oc.webp" alt="Software Sources window greyed out mid-refresh: every control disabled, the Main and Base mirror fields frozen, and a blue Updating cache progress bar stretched across the bottom with no movement." width="800" height="548"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The frozen window: controls greyed, the cache bar stretched, no error and no timeout. This is the state the recovery path below assumes — a fetch that stopped delivering while the GUI holds the line open.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Read the red shield correctly.&lt;/strong&gt;&lt;br&gt;
If the Update Manager shield turned red, you saw this:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"Could not refresh the list of updates — Your APT configuration is corrupt. Do not install or update anything — doing so could break your operating system! To switch to a different Linux Mint mirror and solve this problem, click OK."&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Translation:&lt;/strong&gt; This is Mint's standard reaction to a failed mirror fetch. It clears the moment a refresh succeeds. It is not a verdict on your system.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn5brc3blhidu3kxu72zm.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn5brc3blhidu3kxu72zm.webp" alt="The blue desktop notification, cropped: Could not refresh the list of updates — Your APT configuration is corrupt. Do not install or update anything - doing so could break your operating system! To switch to a different Linux Mint mirror and solve this problem, click OK." width="509" height="112"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The notification itself: alarming wording, harmless meaning. Mint is reporting a failed fetch, not a broken system — and the line that matters is the last one, which is the actual fix.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Wait before touching anything.&lt;/strong&gt;&lt;br&gt;
Freezes often resolve on their own — in my testing they cleared in 2–6 minutes, and the longest ran 23 minutes. One freeze outlasted 30 and I ended it with a shutdown; that story's in the incident report.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Identify before you kill.&lt;/strong&gt;&lt;br&gt;
Open a terminal and run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ps aux &lt;span class="o"&gt;|&lt;/span&gt; grep apt
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Read what's actually listed. The holder's name depends on the door: on Mint 22.3 the GUI's fetch runs through a Python script named &lt;strong&gt;&lt;code&gt;aptk&lt;/code&gt;&lt;/strong&gt; (&lt;code&gt;/usr/sbin/aptk&lt;/code&gt;); a terminal update runs through &lt;code&gt;apt-get&lt;/code&gt;. Kill what &lt;code&gt;ps&lt;/code&gt; shows — not what you remember. Ignore the tourists: &lt;code&gt;grep&lt;/code&gt; matches substrings, so unrelated lines like &lt;code&gt;--adaptive&lt;/code&gt; will appear in the output too.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fd0oer5pkdmgd6ug8ertx.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fd0oer5pkdmgd6ug8ertx.webp" alt="ps aux | grep apt on the ASUS: the holder is a root python3 running /usr/sbin/aptk; four _apt workers run methods/http, methods/gpgv and methods/store; the tourists are the avahi and thermald lines, matched only because the hostname Laptop and the flag adaptive contain the substring apt; the final line is the grep catching itself." width="641" height="472"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The anatomy, live: one holder (aptk), four workers, and the tourists that match on substring rather than on being apt. Read this before you kill anything — the frame is the lesson, and it is the same output the prose walks through line for line.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Kill the holder.&lt;/strong&gt;&lt;br&gt;
In every capture taken for this guide, the GUI's holder answered to &lt;code&gt;aptk&lt;/code&gt; — so:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo killall aptk
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;em&gt;Safety line:&lt;/em&gt; this only holds for a cache &lt;strong&gt;refresh&lt;/strong&gt; — no package transaction is in flight, so there's nothing half-installed to damage; the refresh restarts the moment you click the icon again. Mid-&lt;strong&gt;install&lt;/strong&gt; is different — see the Installing Software step's lock note before killing anything. Killing the &lt;em&gt;wrong&lt;/em&gt; name changes nothing. Target what step 3 showed you. &lt;em&gt;(This is the documented recovery path — my freezes released before I needed to fire it in sequence. And a confession: my own first draft of this step named the holder &lt;code&gt;aptd&lt;/code&gt;, from memory. The capture in step 3 says &lt;code&gt;aptk&lt;/code&gt;. The rule caught me too.)&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Clear the lock, if the error persists.&lt;/strong&gt;&lt;br&gt;
If you now get &lt;em&gt;"Could not get lock /var/lib/apt/lists/lock"&lt;/em&gt;: confirm nothing's alive with &lt;code&gt;ps aux | grep apt&lt;/code&gt;, then remove the lock your error names:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo rm /var/lib/apt/lists/lock
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The other usual suspects are &lt;code&gt;/var/cache/apt/archives/lock&lt;/code&gt; and &lt;code&gt;/var/lib/dpkg/lock-frontend&lt;/code&gt;. Remove only the one named in your error. Locks are protection, not obstacles — but when the holder dies mid-fetch, the lock outlives it and blocks the next attempt.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6. Reselect and verify.&lt;/strong&gt;&lt;br&gt;
Back in Software Sources, take the &lt;strong&gt;next mirror down the list&lt;/strong&gt; — not the one that stalled. Apply, then hit the green refresh icon. The shield returning to normal is the exam passed.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Fixed it — or just curious why the GUI froze solid while a terminal &lt;code&gt;sudo apt install&lt;/code&gt; kept working on the same machine at the same time? The full teardown — two laptops, one 23-minute freeze, one forced shutdown, and what &lt;code&gt;ps&lt;/code&gt; was actually showing — lives in Incident Report: The Mirror Cache Freeze at the end of this guide. It's a read for the curious. Skip it, and you lose nothing.&lt;/em&gt;&lt;/p&gt;


&lt;h3&gt;
  
  
  Step 2: Installing Software on Linux {#step-2-installing-software}
&lt;/h3&gt;

&lt;p&gt;Linux organizes software differently than Windows. There's no single &lt;code&gt;.exe&lt;/code&gt; to download from a website — instead, software arrives as &lt;strong&gt;packages&lt;/strong&gt; from &lt;strong&gt;repositories&lt;/strong&gt; (curated software libraries your system trusts). Mint uses two package systems side by side, and understanding the difference between them will save you a lot of confusion later, especially when you run your first system update.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The two systems:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;System packages (&lt;code&gt;.deb&lt;/code&gt;)&lt;/strong&gt; — the native Linux format, maintained and vetted by Mint and Ubuntu developers. They're tightly integrated with your system, relatively small, and updated through the distro's own release cycle. When you run &lt;code&gt;apt&lt;/code&gt; in the terminal, this is what you're working with.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Flatpaks&lt;/strong&gt; — sandboxed packages that bundle their own dependencies, distributed through &lt;a href="https://flathub.org" rel="noopener noreferrer"&gt;Flathub&lt;/a&gt;. They're isolated from your system (a security advantage), but larger on disk because they carry their own libraries instead of sharing the system's. They update independently of Mint's cycle. The terminal command for these is &lt;code&gt;flatpak&lt;/code&gt;, not &lt;code&gt;apt&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Neither system is "better." Most users end up with a mix of both, and Mint's tools handle them together so you don't have to think about the distinction most of the time. But when the numbers don't add up during an update — and they will — this is why.&lt;/p&gt;
&lt;h4&gt;
  
  
  Method 1: The Software Manager (GUI)
&lt;/h4&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Open &lt;strong&gt;Software Manager&lt;/strong&gt; from the menu.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; The first time you open it — or after changing mirrors — the search may sit empty for two or three minutes while the catalog indexes. It's working, not hung.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Type the name of the app you want in the search bar.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Expect a &lt;strong&gt;flood&lt;/strong&gt; of results. Searching &lt;code&gt;vlc&lt;/code&gt; returns the player itself plus a dozen entries with hyphenated suffixes: &lt;code&gt;-plugin-&lt;/code&gt;, &lt;code&gt;-backend-&lt;/code&gt;, &lt;code&gt;-bin&lt;/code&gt;, &lt;code&gt;-bindings&lt;/code&gt;. These are &lt;em&gt;parts&lt;/em&gt; of the program, not the program. The one you want has the plain name, a human-readable description, and usually a star rating.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Click on it. On the detail page, look at the top right, just under the Install button:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;"System Package"&lt;/strong&gt; chip = a native &lt;code&gt;.deb&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cube icon + "Flathub"&lt;/strong&gt; badge = a Flatpak.&lt;/li&gt;
&lt;li&gt;Some apps appear twice — one of each. Search &lt;code&gt;firefox&lt;/code&gt; and you'll see both. A &lt;strong&gt;green check&lt;/strong&gt; on one of them means it's already installed.
&lt;strong&gt;6.&lt;/strong&gt; Click &lt;strong&gt;Install&lt;/strong&gt;, enter your password, let it run.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F12v8rdvx0tzi3onli5ts.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F12v8rdvx0tzi3onli5ts.webp" alt="Software Manager search results for vlc: the plain-named VLC tile (Multimedia player and streamer, 4.6 stars) sits top-left, ringed by hyphenated component packages — Vlc-plugin-fluiddynth, Vlc-plugin-notify, Vlc-plugin-svg, Vlc-plugin-jack, Gem-plugin-vlc, Phonon4qt5-backend-vlc, Python3-vlc, Vlc-bin, Vlc-plugin-access-extra, Vlc-plugin-base, and more." width="800" height="598"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 2: The flood, on screen. The tile you want is the plain name with a human description and a star rating — top-left here. Everything around it (-plugin-, -backend-, -bin, -bindings) is a component other programs depend on, not the program itself.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2e0c1s9o05kl51avnkpv.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2e0c1s9o05kl51avnkpv.webp" alt="Software Manager search results for firefox: the top row holds two Firefox tiles — the left badged Flathub with a cube icon (4.5 stars), the middle carrying a green check with no Flathub badge (4.3 stars) — plus component and unrelated entries below (firefox-geckodriver, firefox-mozsymbols, Webext-* proxies, Add Water, Glate, Floorp, Datcord, Mozilla VPN, Plasma-browser-integration)." width="797" height="596"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 3: The twins. Same app, two package systems. The green check marks the installed native .deb; the cube plus Flathub badge marks the sandboxed Flatpak. Some apps appear twice exactly like this — firefox being the obvious one.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fz3qm7b8tvrx1qi9jb384.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fz3qm7b8tvrx1qi9jb384.webp" alt="VLC detail page in Software Manager: a green Install button at top-right with the System Package chip directly beneath it; the body reads Name vlc, Version 3.0.20-3build6, Size 19 MB to download, 83 MB of disk space required, with a 4.6 star rating and 1753 reviews, and a plugin list (vlc-plugin-access-extra, vlc-plugin-fluiddynth, vlc-plugin-jack, and others) below the description." width="800" height="598"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 4: The chip, in place. System Package beneath the Install button means a native .deb; a cube plus Flathub badge here would mean a Flatpak. Note the size line — 19 MB to download, 83 MB of disk — the same figure the blockquote below unpacks, and the plugin list echoing the flood from Figure 2.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Two numbers on the detail page:&lt;/strong&gt; "19 MB to download, 83 MB of disk space required." Not a contradiction — the download is the compressed package traveling over the wire; the disk size is what it occupies once unpacked and installed. Same program, measured before and after the squeeze.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3&gt;
  
  
  Method 2: The Terminal (&lt;code&gt;apt&lt;/code&gt;)
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Refresh the package index:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo apt update
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Enter your password when prompted. This doesn't install anything — it just downloads the latest catalog of what's available.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Install a package:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo apt install &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;package-name&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Read the output before confirming. It tells you exactly what will be downloaded, how much disk space it will use, and whether any additional dependencies will be pulled in.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Type &lt;strong&gt;Y + Enter&lt;/strong&gt; to confirm.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; To remove a package later:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo apt remove &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;package-name&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; To clean up leftover dependencies nothing needs anymore:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo apt autoremove
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;&lt;code&gt;autoremove&lt;/code&gt; is not a kernel pruner.&lt;/strong&gt; On both test machines — before &lt;em&gt;and&lt;/em&gt; after a fresh kernel install — it swept nothing. Old kernels pile up quietly, and the deliberate tool for trimming them is Update Manager's &lt;strong&gt;Linux Kernels&lt;/strong&gt; window. Removing kernels is the one housekeeping act that can strand your boot path; leave it alone until you know what you're cutting.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Package names are case-sensitive and must be exact.&lt;/strong&gt; &lt;code&gt;sudo apt install Firefox&lt;/code&gt; will fail. &lt;code&gt;sudo apt install firefox&lt;/code&gt; will work. If you're unsure of the exact name, search for it first with &lt;code&gt;apt search &amp;lt;keyword&amp;gt;&lt;/code&gt; or check the Software Manager.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  Key Differences to Remember
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The Software Manager shows everything&lt;/strong&gt; — &lt;code&gt;.deb&lt;/code&gt; packages, Flatpaks, and third-party repo packages — all in one list. The terminal's &lt;code&gt;apt&lt;/code&gt; commands only see &lt;code&gt;.deb&lt;/code&gt; packages. If an app is Flatpak-only, &lt;code&gt;apt install&lt;/code&gt; won't find it. Use &lt;code&gt;flatpak install flathub &amp;lt;name&amp;gt;&lt;/code&gt; instead, or just use the GUI.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The search flood is normal.&lt;/strong&gt; Those hyphenated plugin entries are real packages — they're just components that other programs depend on. You almost never install them directly.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Not every app is in Mint's repositories.&lt;/strong&gt; Some software isn't packaged for Linux at all, and some exists only as a Flatpak or a manual download. If the Software Manager and &lt;code&gt;apt search&lt;/code&gt; both come up empty, the app's official website is your next stop.&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  When You Can't Find a Package Anywhere
&lt;/h4&gt;

&lt;p&gt;Sometimes the app you need isn't in the Software Manager &lt;em&gt;or&lt;/em&gt; &lt;code&gt;apt&lt;/code&gt;. This usually means one of three things:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. It's a Flatpak you need to install manually.&lt;/strong&gt;&lt;br&gt;
Some apps are only distributed through Flathub. The terminal command is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;flatpak install flathub  
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You can find the exact app ID by searching on &lt;a href="https://flathub.org" rel="noopener noreferrer"&gt;flathub.org&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. It's a standalone &lt;code&gt;.deb&lt;/code&gt; from the developer's website.&lt;/strong&gt;&lt;br&gt;
Some projects (like VS Code, Google Chrome, or Discord) provide a &lt;code&gt;.deb&lt;/code&gt; file for download. Once you have it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo apt install ./path-to-file.deb
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Using &lt;code&gt;apt install&lt;/code&gt; instead of &lt;code&gt;dpkg -i&lt;/code&gt; is important — &lt;code&gt;apt&lt;/code&gt; will automatically fetch any missing dependencies, while &lt;code&gt;dpkg&lt;/code&gt; will just fail and leave you to chase them manually.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. It needs a PPA (Personal Package Archive).&lt;/strong&gt;&lt;br&gt;
Some developers maintain their own Ubuntu/Mint repositories. Adding one typically looks like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo add-apt-repository ppa:&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;developer&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;/&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;project&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
sudo apt update
sudo apt install &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;package-name&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;PPAs are not vetted by Mint. Only add them from developers you trust, and read the project's official installation instructions before running anything.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;🧱 A tutorial told you to &lt;code&gt;snap install&lt;/code&gt; — and Mint refuses&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Plenty of internet tutorials start with &lt;code&gt;snap install something&lt;/code&gt;. On Mint, that door is welded shut on purpose:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ sudo apt install snapd
E: Package 'snapd' has no installation candidate
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Nothing is broken — not the repository, not your setup. That line is distro policy speaking through apt's mouth: Mint chose Flatpak as its sandboxed format and dropped snap entirely. The refusal is the feature working.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fv0r8hyykjshamdl2zuii.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fv0r8hyykjshamdl2zuii.webp" alt="Terminal on the ASUS: flatpak remotes lists flathub; snap install hello-world returns Command 'snap' not found, but can be installed with sudo apt install snapd; sudo apt install snapd then reads package lists, builds the dependency tree, reads state information, and reports Package snapd is not available, closing with E: Package 'snapd' has no installation candidate in red." width="656" height="479"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The whole session behind the fence's two lines. snap is missing, the system points you at snapd to fetch it, and snapd itself has no candidate — the red line is the fence's excerpt, shown here inside the chain that produced it. The door is welded shut from both sides.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do instead:&lt;/strong&gt; skip the &lt;code&gt;snap install&lt;/code&gt; step and look the app up in the Software Manager — cube icon + Flathub badge means it's there in Mint's sanctioned sandbox. If it's genuinely not listed anywhere, the &lt;a href="https://flathub.org" rel="noopener noreferrer"&gt;Flathub site&lt;/a&gt; is the authoritative source for what exists.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;🧱 "Waiting for cache lock" — apt is standing in line, not broken&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Run an &lt;code&gt;apt&lt;/code&gt; command while the Software Manager or Update Manager is mid-download and you'll see this wall scroll past:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend.
It is held by process 6205 (aptk)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhgy0br2vl6s3ndes9q3v.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhgy0br2vl6s3ndes9q3v.webp" alt="Terminal on the ASUS scrolled with roughly twenty identical lines: Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 6205 (aptk) — the same holder repeated line after line." width="800" height="353"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This wall, scroll past, made literal: the same line repeated twenty times, the same holder — 6205 (aptk) — every time. Read the first word, not the count: Waiting. apt is queuing behind the GUI, not refusing.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Read the first word: &lt;strong&gt;Waiting&lt;/strong&gt;. apt isn't refusing — it's queuing behind the GUI and resumes the moment the line moves. On our bench it waited 142 seconds, then carried on by itself. Beginners who've seen this wall have been panicking at a queue this whole time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;So the correct move is: wait.&lt;/strong&gt; This is the exact opposite of the mirror freeze. There, the holder was a stalled &lt;em&gt;fetch&lt;/em&gt; with no package work in flight. Here, the holder is mid-&lt;em&gt;install&lt;/em&gt; — real package work. Killing an installer mid-transaction is how you actually damage package state. Let the queue resolve.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If the wait truly never ends&lt;/strong&gt; (many minutes, nothing moving anywhere): confirm the holder is actually dead first — &lt;code&gt;ps aux | grep apt&lt;/code&gt; shows nothing alive — then choose by what it was doing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It was &lt;strong&gt;installing&lt;/strong&gt; (a progress bar was moving): repair any half-finished state, then retry:
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo dpkg --configure -a
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;It was only &lt;strong&gt;refreshing the cache&lt;/strong&gt; (the Mirrors freeze): no package state was in flight — use the Mirrors step's lock-clearing path.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  A Note on Drivers
&lt;/h3&gt;

&lt;p&gt;Linux Mint includes a &lt;strong&gt;Driver Manager&lt;/strong&gt; (Menu → Driver Manager) for proprietary hardware drivers — most commonly Nvidia graphics cards, some Broadcom Wi-Fi chips, and certain printers or scanners.&lt;/p&gt;

&lt;p&gt;Neither laptop used for this guide ever showed anything in Driver Manager, on a fresh install or on any later check: &lt;em&gt;"No drivers needed — Your computer does not need any additional drivers."&lt;/em&gt; That's not a malfunction — it almost always means your hardware is already fully supported by Mint's default, open-source drivers, which is the common case for most mainstream laptop hardware. An empty Driver Manager is a good sign, not a missing step.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0dghcy62nzrml24ysogi.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0dghcy62nzrml24ysogi.webp" alt="Driver Manager window, subtitle Additional and proprietary drivers, showing a large checkmark over the bold line No drivers needed and the muted line Your computer does not need any additional drivers — no entries listed." width="642" height="529"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The good sign, on screen: an empty Driver Manager is not a malfunction. For most mainstream hardware — both laptops here included — the default open-source drivers already cover everything, so this blank window is the correct result. The populated case (an Nvidia card listing an Install option) is the one state I never saw on either machine, which is why the section points you to the official docs for it instead of guessing at a flow I didn't run.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;If you do have hardware that needs a proprietary driver — an Nvidia GPU is the most common case — Driver Manager will list it with a clear "Install" option. I haven't personally walked through that flow on either test machine, so rather than guess at steps I've never run, here's where to go instead:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://linuxmint.com/documentation.php" rel="noopener noreferrer"&gt;Linux Mint User Guide&lt;/a&gt; — official documentation&lt;/li&gt;
&lt;li&gt;Your hardware manufacturer's official Linux driver page, if one exists&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is one of the only places in this guide where I'm pointing you elsewhere instead of walking you through it myself — and that's deliberate. I'd rather tell you honestly that I haven't tested it than hand you a confident-sounding process I made up.&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 3: TimeShift: Your System's Undo Button {#step-3-timeshift}
&lt;/h2&gt;

&lt;p&gt;Timeshift is Mint's built-in rollback tool — not a personal backup app. If an update or experiment breaks your system, Timeshift restores it to an earlier working state. It does not protect your documents, photos, or downloads — &lt;code&gt;/home&lt;/code&gt; is excluded by design. That's a separate job, for a separate tool.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Setup — one-time, under two minutes:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Open &lt;strong&gt;Timeshift&lt;/strong&gt; from the menu. The setup wizard launches automatically on first run.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; &lt;strong&gt;Snapshot Type:&lt;/strong&gt; Leave it on &lt;strong&gt;RSYNC&lt;/strong&gt; — on an ext4 system it's the only available mode, not a recommendation. &lt;em&gt;(The BTRFS option only activates on systems actually running BTRFS — on ext4, RSYNC is the only door.)&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; &lt;strong&gt;Snapshot Location:&lt;/strong&gt; Your Linux root partition is pre-selected and is the only valid target — the wizard blocks NTFS/FAT outright. A dual-booter physically cannot point a snapshot at the Windows drive, even by accident.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; &lt;strong&gt;Schedule:&lt;/strong&gt; Daily, keep 5 is the default. On a smaller SSD (256GB or less), trim this to 3 to curb space creep over time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; &lt;strong&gt;Home Directories:&lt;/strong&gt; Leave &lt;strong&gt;Exclude All&lt;/strong&gt; checked, for both your user folder and root. This keeps Timeshift doing exactly one job — system state, not personal files.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6.&lt;/strong&gt; Click &lt;strong&gt;Finish&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;7.&lt;/strong&gt; Back in the main window, click &lt;strong&gt;Create&lt;/strong&gt; to trigger your first snapshot now. Don't wait for the schedule — you want a baseline sitting there before you ever need one.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2ch1gagrwkeigkdpa92l.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2ch1gagrwkeigkdpa92l.webp" alt="Two-by-two collage of the Timeshift setup wizard. Top-left, Select Snapshot Type: RSYNC selected, BTRFS greyed out. Top-right, Select Snapshot Location: only sda5 (ext4, 98 GB, 85 GB free) listed with no Windows partition, above the note that NTFS and FAT devices are unsupported. Bottom-left, Select Snapshot Levels: Daily checked at Keep 5 with the green Scheduled snapshots are enabled banner. Bottom-right, User Home Directories: root and asus both set to Exclude All Files." width="800" height="830"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 5: the four wizard decisions, on screen. RSYNC is the only live option because this is ext4; the location panel lists no Windows partition because the wizard blocks NTFS outright; Daily/Keep 5 is the default schedule; and both root and the user home are excluded — which is the whole point, Timeshift guards system state, not your files.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fldf9gguxjz35tt48ra3e.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fldf9gguxjz35tt48ra3e.webp" alt="Timeshift main window with an empty snapshot list: toolbar buttons Create, Restore, Delete, Browse, Settings, Wizard across the top; columns Snapshot, System, Tags, Comments with no rows; footer shield reading Timeshift is active, Snapshots will be created at selected intervals, 0 Snapshots, rsync, 85.1 GB Available, /dev/sda5." width="800" height="600"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The armed tool, before the first snapshot: zero entries, rsync active, Create and Restore waiting in the toolbar. This is the state at the end of setup — configured, forgotten, still working — and the only view that shows where Restore lives for the restore flow below.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Restoring a snapshot, if you ever need to:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Open Timeshift and select a snapshot from the list.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Click &lt;strong&gt;Restore&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Review the &lt;strong&gt;Confirm Actions&lt;/strong&gt; screen before confirming anything — it lists every file Timeshift is about to create, restore, or delete, in advance.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Confirm. The system restores the files and reboots automatically.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8ajn3q7vx81m5kd8icor.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8ajn3q7vx81m5kd8icor.webp" alt="Timeshift Confirm Actions screen: a filter box and All Files dropdown above an Action / File (system) table. The first row is a green Create of /etc/motd; below it, orange Restore rows for fwupd device, metadata, quirks and pending files, NetworkManager internals, smartmontools attribution and smartd data, and systemd timer stamps and timesync clock — roughly forty-nine minutes of ordinary system drift queued to be restored, with no /home paths listed." width="500" height="526"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 6: the read-before-confirm screen. The very first line is the wound Timeshift found and named — Create /etc/motd — and everything under it is the drift a restore rolls back alongside it: firmware metadata, network state, disk logs, timer stamps. None of it is /home; the exclusion held. This is why you review this list before you click, not after.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Know the limits before you rely on it:&lt;/strong&gt; snapshots live on the same disk they protect — if the drive fails, the snapshots fail with it. Restoring rolls back &lt;em&gt;everything&lt;/em&gt; since that snapshot, not just the one thing you're trying to undo, so you'll lose any updates or changes made in between. Snapshot before you experiment, not after something breaks.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;em&gt;The numbers in the Timeshift window can look alarming on their own — a single snapshot claiming several gigabytes, times five scheduled copies, on a drive that doesn't have that much room to spare. It's not what it looks like. Here's how to check it yourself.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;🤔 The misconception about Timeshift's disk usage&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Run a size check on a single snapshot folder and you'll see a number that looks like a full copy of your OS — several gigabytes, easily. Multiply that by five scheduled snapshots and the math looks like Timeshift is about to eat your entire drive. It isn't. Here's how to verify that yourself instead of taking my word for it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What the disk actually holds (ground truth):&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;df -h /
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is your root partition's real, total usage — snapshots included, nothing hidden.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What each snapshot actually costs:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo du -sh /timeshift/snapshots/*
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Run against &lt;em&gt;all&lt;/em&gt; your snapshots in one command, and the sizes come back small. RSYNC mode doesn't copy unchanged files between snapshots — it hardlinks to data already on disk. A snapshot only costs you new space for files that actually changed since the last one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What one snapshot actually contains:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo du -sh /timeshift/snapshots/&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;folder-name&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Run it alone, pointed at a single snapshot folder, and the number jumps — because now you're measuring every file it points to, shared or not. That's not what it &lt;em&gt;cost&lt;/em&gt; you. That's what it &lt;em&gt;contains&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fa5paot4w03uom0xuwuus.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fa5paot4w03uom0xuwuus.webp" alt="Terminal on the HP (king@king-HP-Laptop-15-bs0xx) demonstrating the three measurements. df -h / reports /dev/sda5 at 115G size, 58G used, 52G avail, 53%. sudo du -sh across all five snapshots returns their incremental costs — 21G, 2.3G, 941M, 1.6G, 2.3G. Four solo sudo du -sh runs on individual snapshots each return 21 to 22G, the total each contains. Same disk, three different true numbers depending on the question asked." width="657" height="434"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Run it yourself and the rule becomes visible: df tells you what the disk holds, du across all snapshots tells you what each one cost, du on a single snapshot tells you what it contains. The combined figures stay small because RSYNC hardlinks unchanged files; the solo figures balloon because now you are counting shared data too. Neither number is wrong — they answer different questions.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The rule:&lt;/strong&gt; &lt;code&gt;df -h /&lt;/code&gt; tells you what your disk actually holds. &lt;code&gt;du&lt;/code&gt; across all snapshots tells you what each one cost. &lt;code&gt;du&lt;/code&gt; on one snapshot alone tells you what it contains. Three different numbers, all true — pick the one that answers the question you're actually asking.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Care to see how I put this to the test — deleted a system file on purpose, restored it through the GUI, and nearly misread my own proof twice? The full drill — the wound, the restore, two self-caught misdiagnoses, and the metadata that settled it — is in the TimeShift Drill Report at the end of this guide. Fixed or just curious, you lose nothing by stopping here.&lt;/em&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 4: Keeping Your System Updated {#step-4-updates}
&lt;/h2&gt;

&lt;p&gt;Updates patch security holes and keep your kernel and drivers current. Two equivalent paths — pick whichever fits your flow.&lt;/p&gt;

&lt;h3&gt;
  
  
  Method 1: The GUI (Update Manager)
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Click the &lt;strong&gt;shield icon&lt;/strong&gt; on the panel bar — or search for &lt;strong&gt;Update Manager&lt;/strong&gt; in the menu.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; A list of available updates appears.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; &lt;strong&gt;Install Updates&lt;/strong&gt; applies everything, or untick anything you want to skip — the checkboxes are yours.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Enter your password.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Let it run.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6.&lt;/strong&gt; When it's done, the shield reads &lt;strong&gt;"Your system is up to date."&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6lzgrd569ucw0srighix.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6lzgrd569ucw0srighix.webp" alt="Two-panel Update Manager collage. Top: the available-updates list with the toolbar (Clear, Select All, Refresh, Install Updates active), columns Type / Upgrade / Name / New Version, and three ticked rows — brotli 1.1.0-2ubuntu0.1, xapp 3.2.4+mint22.3, xapp-thumbnailers 1.2.10 — over the Information / Packages / Changelog tabs and a footer reading 3 updates selected (886 KB). Bottom: the same window after the run, Install Updates greyed, a large checkmark over the bold line Your system is up to date." width="800" height="885"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 7: the two states the GUI walks you through. The list appears at step 2 — three logical rows here, each a ticked checkbox you can untick — and the shield closes at step 6 once the batch is applied. The footer's 3 updates / 886 KB is the GUI's own tally; the terminal counts the same work differently, and that gap is the field note's subject, not this step's.&lt;/em&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  Method 2: The Terminal
&lt;/h4&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo apt update
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Refreshes the package index. When it finishes, it reports how many packages are upgradable.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;apt list --upgradable
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Shows exactly what's pending — every package, listed individually. Read-only, no password needed. The GUI shows the &lt;em&gt;same packages&lt;/em&gt; grouped into fewer rows, which is exactly why its counts and size quotes differ from the terminal's — the Field Note has the numbers.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo apt upgrade
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Starts the update. Type &lt;strong&gt;Y + Enter&lt;/strong&gt; when prompted, and let it complete.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;flatpak update
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Updates your Flatpaks. &lt;code&gt;apt&lt;/code&gt; can't see them (see the Installing Software step), so a terminal-only routine needs both commands. The Update Manager handles both kinds in one list — one reason its totals rarely match the terminal's.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; The terminal has no checkbox screen — &lt;code&gt;sudo apt upgrade&lt;/code&gt; updates everything by default. To update a single package without touching the rest, use &lt;code&gt;sudo apt install --only-upgrade &amp;lt;package&amp;gt;&lt;/code&gt;. It may bring tightly tied companions along — upgrading &lt;code&gt;firefox&lt;/code&gt; also upgraded &lt;code&gt;firefox-locale-en&lt;/code&gt; on the test machine — but everything else stays exactly where it was.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;em&gt;The GUI said 893 KB once. The terminal said 216 MB for the exact same update. Neither was wrong — they just don't use the same ruler. The full breakdown — two machines, two kinds of mismatch, one shared cause — is in the Field Note at the end of this guide. Purely optional.&lt;/em&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 5: USB Tethering — The Wi-Fi Backdoor {#step-5-usb-tethering}
&lt;/h2&gt;

&lt;p&gt;Sometimes Wi-Fi just dies — a bad driver, a kernel update, a fight with your wireless card that you didn't start and can't immediately win. When that happens, you still need a way online to search for a fix, download a driver, or roll back a kernel. USB tethering turns your phone into a wired lifeline: plug it in, and your laptop treats it like an ethernet connection.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Android:&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;1.&lt;/strong&gt; Connect your phone to the laptop with a USB data cable (not a charge-only cable).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Turn &lt;strong&gt;mobile data on&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Enable &lt;strong&gt;USB Tethering&lt;/strong&gt; — usually in the notification shade, or under &lt;strong&gt;Settings → Network &amp;amp; Internet → Hotspot &amp;amp; Tethering&lt;/strong&gt; &lt;em&gt;(on Samsung phones: Settings → Connections → Mobile Hotspot and Tethering)&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F94wrcmyeadks12rmi82t.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F94wrcmyeadks12rmi82t.webp" alt="Phone screenshot, cropped to the USB settings panel: under USB controlled by, This device is selected; under Use USB for, five radio options are listed — Transferring files / Android Auto (currently selected), USB tethering, MIDI, Transferring images, Charging phone only." width="720" height="791"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The Android door, open. USB tethering is one option in this list — not the selected one yet (file-transfer is lit here), so this is the screen where you &lt;em&gt;choose&lt;/em&gt; it. The lesson is in the words, not the pixels: pick USB tethering from this list after mobile data is on, and Mint takes it from there.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Linux Mint detects it automatically as a wired connection. No terminal, no setup. If your phone has mobile data, you're online.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;iPhone:&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;1.&lt;/strong&gt; Turn &lt;strong&gt;mobile data on&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Go to &lt;strong&gt;Settings → Personal Hotspot&lt;/strong&gt; and switch it on &lt;em&gt;(The hotspot shares the phone's mobile connection over the cable — with data off the link forms but no internet flows, and Mint's wired icon won't finish the handshake.)&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnie2u1pgx14j53tvspgu.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnie2u1pgx14j53tvspgu.webp" alt="Phone screenshot, cropped to the first Settings group: Airplane Mode (toggle off), WLAN (Not Connected), Bluetooth (On), Mobile Service, Personal Hotspot, and Battery, each with its icon and a chevron." width="800" height="749"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Where the hotspot lives on iOS — the Personal Hotspot row in the first Settings group. Switch it on here, after mobile data, and the cable handshake completes on its own; Mint ships the iPhone driver, so there is no terminal step waiting behind this screen.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Connect the iPhone to the laptop with a USB cable.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; The phone will prompt &lt;strong&gt;"Trust This Computer?"&lt;/strong&gt; — tap &lt;strong&gt;Trust&lt;/strong&gt;, and enter your passcode if asked.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft79n1yu6m2wkihfysw7a.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft79n1yu6m2wkihfysw7a.webp" alt="Close-up of the Trust This Computer? dialog over a thin margin of dimmed screen: the dialog reads Your settings and data will be accessible from this computer when connected wirelessly or using a cable, with Don't Trust and Trust buttons, neither pressed." width="630" height="403"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The gate, on screen. Tap Trust and enter your passcode; declining it is the most common way tethering fails silently on your own laptop. The dialog is the whole instruction — there is no confirmation screen after it, just the wired icon in Mint's tray once the link forms.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Check the network icon in the Mint taskbar — it switches to a wired/ethernet icon once connected.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Always tap Trust.&lt;/strong&gt; There's no reason to decline it on your own laptop, and skipping it is the most likely way this fails silently.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This isn't a permanent fix — it's a bridge to get you online long enough to actually solve the Wi-Fi problem. Speaking of which:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;🧯 Wi-Fi suddenly dead? Try the previous kernel first&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If Wi-Fi was working fine and then vanished right after a routine update, the new kernel is the prime suspect — not your hardware. Kernel updates occasionally ship without full driver support for a specific wireless chip, and the failure is often silent: no error, no warning, just a radio that never connects again.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The fix, if this is what happened to you:&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;1.&lt;/strong&gt; Reboot the laptop.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; At the GRUB boot screen, select &lt;strong&gt;Advanced options for Linux Mint&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Choose the &lt;strong&gt;previous kernel version&lt;/strong&gt; — the plain entry, &lt;strong&gt;not&lt;/strong&gt; recovery mode. &lt;em&gt;(Recovery mode boots a minimal repair shell, not a normal desktop, so it won't bring your Wi-Fi back the way a regular older kernel will. Any plain entry below the newest one works.)&lt;/em&gt;&amp;nbsp;&amp;nbsp;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1nscb2v5zindeggr3vgz.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1nscb2v5zindeggr3vgz.webp" alt="Phone photo of the GNU GRUB boot menu, cropped to the menu strip: the top entry, Linux Mint 22.3 Xfce with Linux 7.0.0-38-generic, is highlighted with an asterisk as the default; below it every kernel appears twice — a plain line and a (recovery mode) twin — running 7.0.0-38, 7.0.0-34, 7.0.0-31, 7.0.0-28, 6.17.0-35, and 6.14.0-37." width="800" height="238"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The menu the fallback walks you through. The starred line at the top is the newest kernel — the one that broke Wi-Fi — and it is already selected, so do not press Enter here. Arrow down to a plain older entry (7.0.0-34 is the one that revived the connection in the kernel-war report) and avoid every line marked (recovery mode): those boot a minimal repair shell, not a desktop, so they will not bring your Wi-Fi back. The pairs are the trap this step warns about, visible.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Boot into it, and check whether Wi-Fi reconnects.&lt;/p&gt;

&lt;p&gt;If it does, you're not stuck. You can keep using that older kernel while a fix lands, or dig further yourself.&lt;/p&gt;

&lt;p&gt;I went through this myself — two hours fighting a wireless card that had no business dying, before I found the previous kernel sitting in the GRUB menu the entire time. It worked. I've been back on the newest kernel since, with zero recurrence — and I still don't have a fully confirmed answer for exactly what failed that night.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Curious about the full two-hour fight — the dead ends, the configuration file I found with a typo baked into it, and the honest admission that I can't prove exactly what fixed it? The full report is in Incident Report: The Kernel War.&lt;/em&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  Appendix {#appendix}
&lt;/h2&gt;


&lt;h3&gt;
  
  
  A1. Incident Report: The Mirror Cache Freeze {#a1-mirror-freeze}
&lt;/h3&gt;

&lt;p&gt;&lt;em&gt;Two machines. One frozen GUI. Zero reinstallations.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Classification:&lt;/strong&gt; Observational report from field testing, not a diagnosis. Where I'm inferring, I say so.&lt;/p&gt;
&lt;h4&gt;
  
  
  Context
&lt;/h4&gt;

&lt;p&gt;The initial post-install mirror selection ran clean on both test machines (HP Pentium N3710, ASUS VivoBook X509UA). The freeze below appeared later — on re-selection during routine maintenance, which is exactly the scenario the Mirrors step's collapsible covers. Fresh installs behaved. The second visit is where the floor got slippery.&lt;/p&gt;
&lt;h4&gt;
  
  
  Machine 1 — HP (the 23-minute hold)
&lt;/h4&gt;

&lt;p&gt;Routine maintenance: switched the Main repository mirror, clicked Apply, hit the cache refresh. The refresh froze completely — no progress, no error, no timeout. Exactly 23 minutes later, it released on its own.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6legn9rsh5k5kyz7erf4.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6legn9rsh5k5kyz7erf4.webp" alt="Full desktop capture on the HP workspace: the dark-green branded Linux Mint wallpaper, the same backdrop as the article's opening image. Centered, the Software Sources window is greyed mid-refresh — controls disabled, an Updating cache bar stretched along the bottom. A red shield sits in the system tray beside a blue desktop notification reading: Could not refresh the list of updates / Your APT configuration is corrupt. / Do not install or update anything - doing so could break your operating system! / To switch to a different Linux Mint mirror and solve this problem, click OK." width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The HP freeze, whole: cache window locked mid-refresh, red shield, and the corrupt-config notification — the same standard warning the Step 1 crop isolates, here shown in context. The surrounding desktop is the author's established workspace, the same branded backdrop as the opening image, which is why the capture ships uncropped: the wallpaper is the proof this is the article's own machine.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The moment the freeze began, the Update Manager shield went red with the standard warning: &lt;em&gt;"Your APT configuration is corrupt. Do not install or upgrade anything…"&lt;/em&gt; The moment the freeze released, the shield returned to normal and showed the standard pending-updates indicator. Nothing was ever corrupt — the shield was reporting a failed fetch, not a broken system.&lt;/p&gt;

&lt;p&gt;Afterward, I ran the lock-clearing commands to clean up the stale state the stalled fetch left behind. Clean recovery. Confirmed working.&lt;/p&gt;
&lt;h4&gt;
  
  
  Machine 2 — ASUS (the ghost)
&lt;/h4&gt;

&lt;p&gt;Same flow, worse manners. The freeze ran past 30 minutes with no shield warning at all. Two details worth their weight in gold:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; &lt;strong&gt;The terminal never froze.&lt;/strong&gt; While the GUI sat locked, &lt;code&gt;sudo apt install &amp;lt;package&amp;gt;&lt;/code&gt; ran fine in a terminal on the same machine, at the same time. Whatever was stuck was stuck inside the GUI's own fetch — one wedged connection, not a dead network: the terminal's transactions ran fine beside it the whole time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; &lt;strong&gt;Killing the wrong name does nothing.&lt;/strong&gt; I ran &lt;code&gt;sudo killall apt&lt;/code&gt; — the GUI stayed frozen, because the holder wasn't &lt;code&gt;apt&lt;/code&gt;. It was &lt;code&gt;aptk&lt;/code&gt;, Mint's GUI package worker — a name I only learned later, from a &lt;code&gt;ps&lt;/code&gt; capture I should have read more carefully the first time. The GUI never freed; I shut the machine down hard. It booted clean afterward — no damage — but the lesson stuck: the holder's name depends on the door.&lt;/p&gt;
&lt;h4&gt;
  
  
  The reproduction attempt
&lt;/h4&gt;

&lt;p&gt;I went back to trigger it deliberately, for screenshots. Couldn't get the deep freeze — only 2-, 3-, and 6-minute holds that cleared on their own. Selecting deliberately dead mirrors produced an error popup, not a freeze. The deep stall appears to require a specific flavor of network misbehavior — the kind you can't order on demand.&lt;/p&gt;

&lt;p&gt;The &lt;code&gt;ps aux | grep apt&lt;/code&gt; anatomy captured during a hold:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The holder:&lt;/strong&gt; a root &lt;code&gt;python3&lt;/code&gt; process — &lt;code&gt;/usr/sbin/aptk&lt;/code&gt;, Mint's GUI package worker&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The workers:&lt;/strong&gt; multiple &lt;code&gt;_apt&lt;/code&gt; child processes — &lt;code&gt;methods/http&lt;/code&gt; (the actual downloads), &lt;code&gt;methods/gpgv&lt;/code&gt; (signature verification), &lt;code&gt;methods/store&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The tourists:&lt;/strong&gt; unrelated lines like &lt;code&gt;thermald --adaptive&lt;/code&gt;, matching by substring because &lt;code&gt;grep&lt;/code&gt; doesn't check whole words&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
  
  
  What I believe happened (suspected, not proven)
&lt;/h4&gt;

&lt;p&gt;The mirror speed test ranks servers by latency — how fast they answer, not how long they can carry a conversation. A mirror that aces the ping test can still stall mid-fetch. The GUI holds that fetch open with no timeout aggressive enough to matter on a bad route. The red shield is Mint interpreting a failed fetch as possible corruption — conservative by design, alarming by accident.&lt;/p&gt;

&lt;p&gt;It also likely explains why the terminal kept working beside the frozen GUI: a cache refresh holds the package-list lock (&lt;code&gt;/var/lib/apt/lists/lock&lt;/code&gt;), while an install needs the dpkg lock — different doors, so one stuck refresh didn't block the other. A GUI &lt;em&gt;install&lt;/em&gt; is different: it holds the dpkg lock, and terminal apt queues behind it (see the Installing Software step).&lt;/p&gt;
&lt;h4&gt;
  
  
  Scorecard
&lt;/h4&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Confirmed:&lt;/strong&gt; waiting works (HP, 23 min) · lock-clearing works (HP) · killing the wrong process name frees nothing (ASUS) · the terminal survives a GUI freeze (ASUS)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Suspected:&lt;/strong&gt; the latency-vs-throughput gap as root cause&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unresolved:&lt;/strong&gt; the deep freeze would not reproduce on demand; network conditions appear to be a prerequisite&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
  
  
  The transferable lesson
&lt;/h4&gt;

&lt;p&gt;Fastest ≠ most reliable. A ranking is a suggestion, not a verdict. When a fetch stalls: identify the actual holder before killing anything, remove only the lock your error names, and take the next mirror down. The system was never broken. The server was.&lt;/p&gt;


&lt;h3&gt;
  
  
  A2. Incident Report: The Kernel War {#a2-kernel-war}
&lt;/h3&gt;

&lt;p&gt;&lt;em&gt;Two hours. One dead wireless card. One config file with a typo in it. No fully confirmed cause.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Classification:&lt;/strong&gt; Unplanned incident. Real time lost, mid-work, with a resolution that arrived before the diagnosis finished — the honest kind of ending, not the tidy kind.&lt;/p&gt;
&lt;h4&gt;
  
  
  Context
&lt;/h4&gt;

&lt;p&gt;The HP 15-bs0xx — my daily driver, holding every asset for this article — was fully up to date via the terminal, like it had been for weeks. The wireless chip is a Realtek RTL8188EE, a controller with a long, well-documented history of kernel-to-kernel instability. That history matters: this wasn't a freak event on unusual hardware. It's a known trouble spot, which is exactly why it's worth documenting properly instead of guessing.&lt;/p&gt;
&lt;h4&gt;
  
  
  The Timeline
&lt;/h4&gt;

&lt;p&gt;Reconstructed from &lt;code&gt;last -x reboot&lt;/code&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;20:31 → 22:37&lt;/strong&gt; — Boot into the newest kernel (&lt;code&gt;7.0.0-38-generic&lt;/code&gt;). Wi-Fi dead for the full two hours.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;22:39 → 23:18&lt;/strong&gt; — A retry boot, same kernel. Still dead.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;23:21 → 23:40&lt;/strong&gt; — Boot into the previous kernel (&lt;code&gt;7.0.0-34-generic&lt;/code&gt;). Connection restored within two minutes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Oct 21, 07:39 onward&lt;/strong&gt; — Back on the newest kernel. No recurrence since.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fz4nytbhbbxiosg0v2l42.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fz4nytbhbbxiosg0v2l42.webp" alt="last -x reboot | head -15 on the HP: fifteen rows of boot records, each beginning reboot system boot 7.0.0-3x-generic, with dates and times spanning Oct 19 to Oct 26 2026 — including the 7.0.0-38 boot from Oct 19 that ran until Oct 21 09:03 (still running), the 7.0.0-34 boot on Oct 26 13:22, and the 7.0.0-38 boot on Oct 24 21:41. The kernel column encodes the Confound matrix without the reader having to compute it." width="800" height="325"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The four bullets of the Timeline, on the screen that reconstructed them. Each row is a boot with its kernel version in the rightmost column, so the reader can see the 38/34 alternations the prose describes without having to trust the reconstruction. The kernel column is what encodes the Confound matrix for free.&lt;/em&gt;&lt;/p&gt;
&lt;h4&gt;
  
  
  What Didn't Change
&lt;/h4&gt;

&lt;p&gt;&lt;code&gt;/var/log/apt/history.log&lt;/code&gt; for October 20 records no kernel, no firmware, and no network-stack changes — an &lt;code&gt;acpi&lt;/code&gt; install at 14:44 and a handful of small upgrades at 14:46 (&lt;code&gt;cifs-utils&lt;/code&gt;, &lt;code&gt;git&lt;/code&gt;, &lt;code&gt;python3-jwt&lt;/code&gt;, and friends). The failing kernel had been installed five weeks earlier, on September 14. Whatever sprang at 20:31, it was not a fresh package landing under the machine. The trigger was state, not installation — which is precisely why the diagnosis never closed.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fiuru6d688wdek7b4mvdx.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fiuru6d688wdek7b4mvdx.webp" alt="grep -A8 '^Start-Date: 2026-10-20' /var/log/apt/history.log on the HP: two red Start-Date: 2026-10-20 blocks — the first at 14:44:29 with install acpi, the second at 14:46:14 with an aptkit Upgrade of cifs-utils, git, python3-jwt and friends — followed by a third Start-Date: 2026-10-21 07:58:47 block, confirming the incident night has no kernel, firmware, or network-stack changes in the log." width="800" height="305"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The night the Wi-Fi died, in the apt log. Two red blocks on Oct 20 — acpi at 14:44, a small aptkit upgrade at 14:46 — and then nothing else until Oct 21 07:58. The failing kernel had been installed Sep 14, five weeks earlier. Whatever sprang at 20:31, it was not a fresh package landing under the machine.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frlxyvwjp28xvlb017atr.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frlxyvwjp28xvlb017atr.webp" alt="ls -lh /boot/vmlinuz-* &amp;amp;&amp;amp; uname -r on the HP: six -rw------- root root 17M /boot/vmlinuz-... files listed by date — Nov 20 2025, May 26, Jul 1, Aug 10, Sep 4, and Sep 14 — with the last line alone reading 7.0.0-38-generic. The Sep 14 mtime on vmlinuz-7.0.0-38-generic proves the failing kernel was installed five weeks earlier, not that night." width="657" height="434"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The five-weeks claim, proven by mtime. Six kernels in /boot, with vmlinuz-7.0.0-38-generic dated Sep 14 16:28 — the failing kernel was already on disk when the incident happened. The roster also matches the six pairs in the GRUB menu from Step 5's fallback, so a reader can cross-reference the two.&lt;/em&gt;&lt;/p&gt;
&lt;h4&gt;
  
  
  The Void
&lt;/h4&gt;

&lt;p&gt;&lt;code&gt;journalctl&lt;/code&gt; from the dead window shows the driver initializing correctly at boot — the hardware itself was never the problem. What failed was the authentication handshake, on a 30-second retry loop, for two straight hours:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Oct 20 20:33:07 wpa_supplicant: wlo1: SME: Trying to authenticate with 16:1a:64:2f:42:5b (SSID='Galaxy A07 ecff' freq=2412 MHz)
Oct 20 20:33:07 kernel: wlo1: send auth to 16:1a:64:2f:42:5b (try 1/3)
Oct 20 20:33:09 kernel: wlo1: send auth to 16:1a:64:2f:42:5b (try 2/3)
Oct 20 20:33:11 kernel: wlo1: send auth to 16:1a:64:2f:42:5b (try 3/3)
Oct 20 20:33:11 kernel: wlo1: authentication with 16:1a:64:2f:42:5b timed out
Oct 20 20:33:32 NetworkManager: &amp;lt;warn&amp;gt; device (wlo1): Activation: (wifi) association took too long; failing activation
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This block repeated, almost unchanged, every ~30 seconds until the 22:37 reboot. The shape of the failure is important: initialization succeeded, operation failed. This was never a missing driver — it was a driver that loaded and then couldn't finish a handshake it used to complete without issue.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fp6kcskzhg0i1vttr7bfa.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fp6kcskzhg0i1vttr7bfa.webp" alt="sudo journalctl --since '2026-10-20 20:32' --until '2026-10-20 23:20' | grep -iE 'NetworkManager|wlo1|rtl8188|rtlwifi|firmware|dhcp' | head -40 on the HP. Output shows Config: added 'ssid' 'Galaxy A07 ecff', 'psk' value '&lt;hidden&gt;', 'scan_ssid', 'bgscan', 'key_mgmt' 'WPA-PSK', 'auth_alg' 'OPEN'; SME: Trying to authenticate with 16:1a:64:2f:42:5b (SSID='Galaxy A07 ecff' freq=2412 MHz); kernel: wlo1: send auth to 16:1a:64:2f:42:5b (try 1/3) (try 2/3) (try 3/3); kernel: wlo1: authentication with 16:1a:64:2f:42:5b timed out; wpa_supplicant: wlo1: CTRL-EVENT-DISCONNECTED bssid=16:1a:64:2f:42:5b reason=4 locally_generated=1; NetworkManager: state change: config -&gt; failed (reason 'ssid-not-found'); NetworkManager state is now DISCONNECTED; then a second retry beginning at 20:33:37 with auto-activating connection 'Galaxy A07 ecff' and the frame cuts off mid-second-attempt." width="800" height="476"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The two-hour loop, in one scroll. The first full cycle shows the config being added, the SME auth attempt against 16:1a:64:2f:42:5b, the three tries, the timeout, the ssid-not-found reason, the DISCONNECTED state, and then the second attempt starting at 20:33:37. This frame shows cycle one; the prose owns the claim that it repeated until 22:37.&lt;/em&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  The Relic
&lt;/h4&gt;

&lt;p&gt;At 23:08 — thirteen minutes before the rescue boot — a configuration file was dropped into &lt;code&gt;/etc/modprobe.d/rtl8188ee.conf&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;options rtl8188ee fswconn=0 ips=0 swenc=1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpquneej3a806rv7wz5e3.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpquneej3a806rv7wz5e3.webp" alt="Three commands on the HP. grep -H rtl8188ee /etc/modprobe.d/*.conf prints /etc/modprobe.d/rtl8188ee.conf:options rtl8188ee fswconn=0 ips=0 swenc=1 in red. grep -H . /etc/NetworkManager/conf.d/*.conf prints four lines of existing drop-ins. ls -l --time-style=long-iso on /etc/modprobe.d and /etc/NetworkManager/conf.d shows the file listings — rtl8188ee.conf dated 2026-10-20 23:08, the NetworkManager drop-ins dated 2024 and 2026-09-30, both predating the incident." width="800" height="381"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The Relic's file, with its metadata. grep finds the three options in /etc/modprobe.d/rtl8188ee.conf; ls shows that file dated 2026-10-20 23:08 — thirteen minutes before the rescue boot. The NetworkManager drop-ins beside it are dated 2024 and 2026-09-30, so the only config that changed that night was the relic.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Two of these are real, documented fixes for this exact chip: &lt;code&gt;ips=0&lt;/code&gt; disables idle power save, and &lt;code&gt;swenc=1&lt;/code&gt; forces software encryption instead of hardware crypto — both known workarounds for RTL8188EE handshake failures on forums going back years. The third, &lt;code&gt;fswconn=0&lt;/code&gt;, is not a real parameter for this driver at all. It's been silently ignored by the kernel at every boot since — &lt;code&gt;unknown parameter 'fswconn' ignored&lt;/code&gt;, logged and forgotten, a dead instruction carried for days without doing anything.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpwsh7it0df5ctreat2ss.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpwsh7it0df5ctreat2ss.webp" alt="sudo journalctl --since '2026-10-20 23:21' --until '2026-10-20 23:40' | grep -iE 'NetworkManager|wlo1|rtl8188|rtlwifi|firmware|dhcp' | head -30 on the HP. The first output line is kernel: rtl8188ee: unknown parameter 'fswconn' ignored, followed by rtl8188ee driver loaded, Power Save off, Using firmware rtlwifi/rtl8188efw.bin, renamed from wlan0 to wlo1, NetworkManager plugin-load lines, ending interfaces file /etc/network/interfaces doesn't exist." width="800" height="544"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The kernel's own confession, in the first line of the rescue boot's log: unknown parameter 'fswconn' ignored. The Scorecard's 'confirmed dead end' on screen. Then the firmware loads, the rename from wlan0 to wlo1, and the init succeeding — the same driver that failed for two hours was initializing cleanly on the older kernel.&lt;/em&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  The Handshake, Restored
&lt;/h4&gt;

&lt;p&gt;Booting into the older kernel (&lt;code&gt;7.0.0-34-generic&lt;/code&gt;) at 23:21, the first connection attempt still failed — same signature as before. The second attempt, two minutes later, succeeded outright:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Oct 20 23:23:07 kernel: wlo1: authenticated
Oct 20 23:23:07 kernel: wlo1: associated
Oct 20 23:23:07 wpa_supplicant: wlo1: WPA: Key negotiation completed with 16:1a:64:2f:42:5b [PTK=CCMP GTK=CCMP]
Oct 20 23:23:08 NetworkManager: &amp;lt;info&amp;gt; manager: NetworkManager state is now CONNECTED_SITE
Oct 20 23:23:10 NetworkManager: &amp;lt;info&amp;gt; manager: NetworkManager state is now CONNECTED_GLOBAL
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Same chip. Same access point. Same night. One kernel change, plus the config file dropped thirteen minutes earlier.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgtnz7bbv9j0idnsgwior.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgtnz7bbv9j0idnsgwior.webp" alt="sudo journalctl --since '2026-10-20 23:21' --until '2026-10-20 23:40' | grep -iE 'NetworkManager|wlo1|rtl8188|rtlwifi|firmware|dhcp' | tail -12 on the HP. Output shows wpa_supplicant: wlo1: Associated with 16:1a:64:2f:42:5b, kernel: wlo1: 4-way handshake completed, wpa_supplicant: wlo1: WPA: Key negotiation completed with 16:1a:64:2f:42:5b [PTK=CCMP GTK=CCMP], wpa_supplicant: wlo1: CTRL-EVENT-CONNECTED - Connection to 16:1a:64:2f:42:5b completed [id=0 id_str=], Connected to wireless network 'Galaxy A07 ecff', DHCP lease 10.116.236.172, NetworkManager: NetworkManager state is now CONNECTED_SITE, then NetworkManager state is now CONNECTED_GLOBAL." width="569" height="689"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The handshake restored. The fence's five lines inside their chain: Associated with 16:1a:64:2f:42:5b, 4-way handshake completed, Key negotiation, CTRL-EVENT-CONNECTED, DHCP lease 10.116.236.172, CONNECTED_SITE, CONNECTED_GLOBAL. Same chip, same AP, same night — one kernel change later.&lt;/em&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  The Confound
&lt;/h4&gt;

&lt;p&gt;Two variables changed in the window between the failure and the fix: the kernel version, and the driver options file. The tested matrix:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Newest kernel, no options file → dead (twice, over two hours).&lt;/li&gt;
&lt;li&gt;Older kernel, options file present → alive, within two minutes.&lt;/li&gt;
&lt;li&gt;Newest kernel, options file present → stable, from the next morning onward.&lt;/li&gt;
&lt;li&gt;Older kernel, no options file → never tested.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;The honest ruling: it's not possible to say with certainty which variable did the work.&lt;/strong&gt; The options file could have been the real fix, with the kernel downgrade being incidental. The kernel downgrade could have been the real fix, with the options file being irrelevant noise that happened to arrive first. Both are consistent with every data point collected that night. Nothing here points to a single, provable root cause — and manufacturing one for the sake of a cleaner story would be exactly the kind of claim this guide refuses to make.&lt;/p&gt;

&lt;h4&gt;
  
  
  External Corroboration
&lt;/h4&gt;

&lt;p&gt;The RTL8188EE has a long paper trail of exactly this failure pattern: open complaints on Kernel Bugzilla describing dropped connections across kernel versions, forum reports of the same "authentication timed out" signature appearing on newer kernels while older LTS kernels stay stable, and descriptions elsewhere of a reboot reviving the card "for a few minutes" before it degrades again. None of this proves what happened on this specific machine, this specific night — but it confirms the failure class is real, known, and not unique to this hardware.&lt;/p&gt;

&lt;h4&gt;
  
  
  Scorecard
&lt;/h4&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Confirmed:&lt;/strong&gt; the failure was a handshake timeout, not a missing driver · the newest kernel failed twice, consistently, over two hours · the older kernel succeeded within two minutes of booting into it · the system has run stable on the newest kernel since, with no recurrence · no kernel, firmware, or network-stack package changed on the night of the incident — the failing kernel was five weeks old&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Suspected:&lt;/strong&gt; either the driver options file, the kernel downgrade, or both together resolved the handshake failure&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unresolved, and staying that way:&lt;/strong&gt; which single variable (or combination) was actually responsible · whether the newest kernel alone, without the options file, would have failed indefinitely or eventually recovered on its own&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Confirmed dead end:&lt;/strong&gt; the &lt;code&gt;fswconn=0&lt;/code&gt; parameter does nothing — it isn't a real option for this driver, and the kernel has silently ignored it since the night it was written&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6v0j59weniz85gxkz42w.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6v0j59weniz85gxkz42w.webp" alt="nmcli device status on the HP showing enxcaec2a9ca74b ethernet connected to Wired connection 2 and wlo1 wifi connected to Galaxy A07 ecff, followed by nmcli radio wifi off &amp;amp;&amp;amp; curl -sI https://linuxmint.com returning HTTP/2 200 with date: Mon, 26 Oct 2026, then a NetworkManager status table showing connected full enabled disabled missing enabled, and finally nmcli radio wifi on. The curl succeeds with Wi-Fi off because the USB ethernet adapter is the control path." width="657" height="434"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Six days on. The device table shows wlo1 connected to Galaxy A07 ecff and the USB ethernet as Wired connection 2; the curl returns HTTP/2 200 with Wi-Fi radio off, because the USB adapter is the control path; the status table shows connectivity full; then radio wifi on. The Timeline's last bullet — 'no recurrence since Oct 21' — on screen.&lt;/em&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  The Transferable Lesson
&lt;/h4&gt;

&lt;p&gt;When the cause is genuinely ambiguous, say so. The kernel rollback worked. The reason it worked is less certain than the fact that it worked — and a guide that pretends otherwise, for the sake of sounding more authoritative, is lying by omission. If your Wi-Fi dies right after an update and the previous kernel brings it back, that's a legitimate fix to use immediately. It doesn't obligate you to also know exactly why.&lt;br&gt;
Most Wi-Fi deaths follow a fresh kernel update. Mine was a ghost — a state failure on a kernel that had been stable for five weeks. The rollback worked anyway, which is why it's the first thing to try.&lt;/p&gt;


&lt;h3&gt;
  
  
  A3. Drill Report: The TimeShift Stress Test {#a3-timeshift-drill}
&lt;/h3&gt;

&lt;p&gt;&lt;em&gt;A deleted file, a GUI restore, and two predictions that turned out wrong — caught before they shipped.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Classification:&lt;/strong&gt; A deliberate, controlled test — not an accident, not a crisis. I broke the system on purpose to find out if the tool actually does what it claims.&lt;/p&gt;
&lt;h4&gt;
  
  
  The Setup
&lt;/h4&gt;

&lt;p&gt;Before touching anything, the machine already had three snapshots sitting on disk — one taken automatically during the fresh install ten days earlier, and two taken the night of this drill. That install-day snapshot had been quietly on deck the entire time, untouched, exactly how most users will actually encounter Timeshift: configured once, forgotten, still working.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Num  Name                Tags  Description
0  &amp;gt; 2026-10-15_12-00-01  D
1  &amp;gt; 2026-10-25_22-00-01  D
2  &amp;gt; 2026-10-25_22-49-51  O     drill-second
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;One technical note from setup:&lt;/strong&gt; Timeshift is single-instance — the GUI and the terminal share one lock. Trying to run a CLI snapshot while the GUI is open gets refused outright: &lt;code&gt;Another instance of this application is running&lt;/code&gt;. Close the GUI first.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj8x7v9e1upi44ss9iaq6.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj8x7v9e1upi44ss9iaq6.webp" alt="Terminal over the dark Linux Mint desktop on the ASUS: sudo timeshift --list and the first sudo timeshift --create --comments drill-second are both refused with Another instance of this application is running (PID=2572); the third attempt succeeds — Mounted /dev/sda5, Creating new snapshot (RSYNC), Linking from snapshot 2026-10-25_22-00-01, RSYNC Snapshot saved successfully (102s), Tagged snapshot 2026-10-25_22-49-51: ondemand. A desktop notification top-right echoes RSYNC Snapshot saved successfully (102s); the clock reads 22:51, 2026-10-25. The final line is a benign /tmp/timeshift-… line 10: status artifact after the success." width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The single-instance lock, live. Two refusals while the GUI held the lock, then success the moment it was closed — 102 seconds, echoed by the desktop notification. The stray /tmp line at the bottom is a harmless post-success script hiccup the drill ignored; the snapshot itself saved clean.&lt;/em&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  The Space Truth, Measured Three Ways
&lt;/h4&gt;

&lt;p&gt;Before breaking anything, I checked the disk usage numbers — and got my own prediction wrong on the first try.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;df -h /
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;/dev/sda5    89G   27G   58G  32% /
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The whole root partition — system plus all three snapshots combined — was using 27G. Modest.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo du -sh /timeshift/snapshots/*
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;7.5G  /timeshift/snapshots/2026-10-15_12-00-01
412M  /timeshift/snapshots/2026-10-25_22-00-01
4.2G  /timeshift/snapshots/2026-10-25_22-49-51
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I expected this command to show three separate, enormous, near-identical numbers — the classic "panic" scenario. It didn't. Run against &lt;em&gt;all&lt;/em&gt; snapshots in a single command, &lt;code&gt;du&lt;/code&gt; deduplicates hardlinks across every argument it's given, so what comes back is the actual &lt;em&gt;cost&lt;/em&gt; of each snapshot — the incremental space it added, not the total it contains.&lt;/p&gt;

&lt;p&gt;To see the panic-inducing number, I had to isolate one snapshot and run &lt;code&gt;du&lt;/code&gt; against it alone:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo du -sh /timeshift/snapshots/2026-10-25_22-49-51
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;8.4G
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Same snapshot. Different question. Run combined, it cost 4.2G. Run solo, it contains 8.4G. Both numbers are true — &lt;code&gt;du&lt;/code&gt; combined tells you what a snapshot &lt;em&gt;cost&lt;/em&gt;, &lt;code&gt;du&lt;/code&gt; solo tells you what it &lt;em&gt;contains&lt;/em&gt;, and &lt;code&gt;df&lt;/code&gt; settles what the disk actually &lt;em&gt;holds&lt;/em&gt;. I predicted 11–12G for the solo figure and got 8.4G instead — lower than expected, because files already deleted since the Oct 15 baseline (old caches, rotated logs, removed packages) only exist inside the &lt;em&gt;older&lt;/em&gt; snapshots now. That's also the real argument for keeping more than one snapshot: older ones aren't redundant copies — they're the only remaining holders of history the newer ones no longer carry.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcay2r9et8028kxh6lsro.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcay2r9et8028kxh6lsro.webp" alt="ASUS terminal: the timeshift --list header (Device /dev/sda5, Mode RSYNC, Status OK, 3 snapshots, 61.5 GB free) above the three-row table ending in the drill-second entry; then df -h / reporting /dev/sda5 at 89G size, 27G used, 58G avail, 32%; then sudo du -sh across all snapshots returning 7.5G, 412M, 4.2G; then sudo du -sh on the single 2026-10-25_22-49-51 snapshot returning 8.4G." width="663" height="476"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Three questions, three true answers, one screen. df settles what the disk holds (27G); du across all snapshots settles what each cost (7.5G, 412M, 4.2G); du on one alone settles what it contains (8.4G). The numbers that look like a contradiction are the same disk answering different questions.&lt;/em&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  The Wound
&lt;/h4&gt;

&lt;p&gt;With the baseline established, I opened a terminal and deleted a real system file:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo rm /etc/motd
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;cat /etc/motd
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;cat: /etc/motd: No such file or directory
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The wound was real, confirmed on the spot.&lt;/p&gt;

&lt;h4&gt;
  
  
  The Restore
&lt;/h4&gt;

&lt;p&gt;I deliberately bypassed the terminal for the fix and used the Timeshift GUI instead — the exact window a panicked user would actually see. Selected the snapshot taken minutes before the deletion, clicked &lt;strong&gt;Restore&lt;/strong&gt;, and reviewed the &lt;strong&gt;Confirm Actions&lt;/strong&gt; screen before confirming anything.&lt;/p&gt;

&lt;p&gt;The very first line of the repair plan: &lt;strong&gt;&lt;code&gt;Create /etc/motd&lt;/code&gt;&lt;/strong&gt;. Timeshift wasn't guessing — it compared the live system to the snapshot and named the wound first.&lt;/p&gt;

&lt;p&gt;Below it, roughly 49 minutes of ordinary system drift — firmware metadata, NetworkManager state, SMART disk logs, systemd timer stamps — all queued to be restored or recreated alongside the one file I actually cared about. None of it was &lt;code&gt;/home&lt;/code&gt; — the exclusion held, exactly as configured. But &lt;code&gt;/boot/efi&lt;/code&gt; needs a correction, and the correction is the lesson: the Confirm Actions screen showed no &lt;code&gt;/boot/efi&lt;/code&gt; rows, and I first read that as "the ESP was left alone." It wasn't. The restore log shows &lt;code&gt;Re-installing GRUB2 bootloader... Installing for x86_64-efi platform&lt;/code&gt; — a separate post-restore step that writes into the ESP, which the file plan never enumerates. The warning dialog had listed &lt;code&gt;/dev/sda1 → /boot/efi&lt;/code&gt; under "devices where data will be modified" before I clicked anything. The file list was one layer of the process; the bootloader re-install was the second. Absence in one screen is not absence in the operation.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fscl6zhm0tcgms2p8k999.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fscl6zhm0tcgms2p8k999.webp" alt="The Timeshift Select Target Device dialog: / mapped to sda5 ~ ext4 (95 GB), /boot set to Keep on Root Device, /boot/efi mapped to sda1 ~ vfat (101 MB), /home set to Keep on Root Device, with a Bootloader Options (Advanced) button below and Previous / Next / Cancel at the foot." width="500" height="526"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The ESP's first naming. Before any warning and long before any log line, the restore wizard's target screen lists /boot/efi → sda1 as a device files will be restored to, pre-selected. The file plan's silence about the ESP was never the operation's silence.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faoww6865p64h7caewpnb.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faoww6865p64h7caewpnb.webp" alt="The Timeshift Comparing Files (Dry Run) dialog: a progress bar at 00:00:00 remaining above Files and directory counts — No Change: 531,400, Created: 3, Deleted: 0, Changed: 35 — and a Changed items breakdown of Checksum 0, Size 14, Timestamp 21, Permissions 0, Owner 0, Group 0, with a Cancel button." width="500" height="526"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The drift, counted. Against 531,400 untouched files, the restore plans to touch 38 — three created, including the wounded /etc/motd, and 35 changed, mostly timestamps. This is what "it undoes everything since that snapshot" looks like as a number: a rounding error of history, your one file inside it.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1usgcb7v1n2uduqlp483.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1usgcb7v1n2uduqlp483.webp" alt="The Timeshift Warning dialog: under Data will be modified on following devices, a table listing /dev/sda5 mounted at / and /dev/sda1 mounted at /boot/efi; then Please save your work and close all applications, System will reboot after files are restored; then the Disclaimer paragraph — This software comes without absolutely NO warranty and the author takes no responsibility for any damage arising from the use of this program — with Previous greyed, Next, and Cancel at the foot." width="500" height="526"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The ESP's second naming, and the disclaimer upstream ships with the tool. The warning lists /dev/sda1 → /boot/efi among devices to be modified before a single click — the layer the Confirm Actions file plan never enumerated, stated plainly one screen earlier.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjykfadob15t5xph5uwiz.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjykfadob15t5xph5uwiz.webp" alt="The restore's terminal log on the ASUS: an rsync tail (sent 65,761,211 bytes, total size is 8,180,385,287, speedup 124.39), then Re-installing GRUB2 bootloader... / Installing for x86_64-efi platform. / Installation finished. No error reported., then Updating GRUB menu... finding both linux images (7.0.0-38 and 6.14.0-37) and Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi, ending at Syncing file systems..." width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The ESP's third naming — the write itself. The log's GRUB2 re-install for the x86_64-efi platform is the post-restore step that touches the ESP the file plan never listed, and the Windows Boot Manager line confirms the same partition still carries Windows' loader afterward. Target screen named it, warning named it, log wrote it: absence in one screen was never absence in the operation.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;That drift is the honest cost of a restore: &lt;strong&gt;it doesn't undo one thing. It undoes everything since that snapshot.&lt;/strong&gt; Confirm, and the warning screen is explicit about what's about to happen — right down to carrying over upstream's own disclaimer verbatim:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;"This software comes without absolutely NO warranty and the author takes no responsibility for any damage arising from the use of this program. If these terms are not acceptable to you, please do not proceed beyond this point!"&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;I proceeded. The system restored the files and rebooted on schedule.&lt;/p&gt;

&lt;h4&gt;
  
  
  The Verification — and Two Mistakes I Caught Myself
&lt;/h4&gt;

&lt;p&gt;Post-reboot, my first attempt to confirm the fix had a typo:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;cat/etc/motd
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;bash: cat/etc/motd: No such file or directory
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Misdiagnosis #1 — mine, caught immediately.&lt;/strong&gt; That's a &lt;code&gt;bash:&lt;/code&gt; error, not a &lt;code&gt;cat:&lt;/code&gt; error — the shell couldn't find a command literally named &lt;code&gt;cat/etc/motd&lt;/code&gt; because I forgot the space. The restore never failed. My verification sentence was just misspelled. The prefix is the tell: &lt;code&gt;bash:&lt;/code&gt; means the command itself was never found; &lt;code&gt;cat:&lt;/code&gt; means the command ran and the &lt;em&gt;target&lt;/em&gt; was the problem. Two completely different failures that look identical to a tired pair of eyes.&lt;/p&gt;

&lt;p&gt;Corrected:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ls -l /etc/motd
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;-rw-r--r-- 1 root root 1 Jan 8 2026 /etc/motd
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This single line settled three things at once:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; &lt;strong&gt;It's a regular file, not a symlink.&lt;/strong&gt; I'd assumed going in that &lt;code&gt;/etc/motd&lt;/code&gt; might be a symlink into &lt;code&gt;/run&lt;/code&gt; (a known Ubuntu/Mint pattern for other files), which would have meant a successful-looking restore could still mask a broken link. &lt;strong&gt;Misdiagnosis #2 — also mine, also wrong.&lt;/strong&gt; The file itself corrected the theory; no symlink was involved here.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; &lt;strong&gt;The 1-byte size&lt;/strong&gt; confirms this file was always just a lone trailing newline. Even a correctly typed &lt;code&gt;cat&lt;/code&gt; would have printed nothing visible — &lt;code&gt;cat&lt;/code&gt; was never going to be a convincing verification tool for this particular file, typo or not.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; &lt;strong&gt;The timestamp — &lt;code&gt;Jan 8 2026&lt;/code&gt;, not the date of the restore.&lt;/strong&gt; This is the actual proof. A recreated file gets today's date. This one carried its &lt;em&gt;original&lt;/em&gt; timestamp through the entire wound-and-restore cycle, because &lt;code&gt;rsync&lt;/code&gt; preserves file attributes. The file wasn't rebuilt from scratch — it was restored, signature intact.&lt;/p&gt;

&lt;p&gt;One last check, just to see the invisible byte directly:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;cat -A /etc/motd
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That &lt;code&gt;$&lt;/code&gt; is &lt;code&gt;cat -A&lt;/code&gt;'s way of marking a newline character. One byte, present, correct, photographed.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fb8ibhj6ym9lhfxg0orye.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fb8ibhj6ym9lhfxg0orye.webp" alt="ASUS terminal, three commands in sequence: cat/etc/motd returning bash: cat/etc/motd: No such file or directory (the missing-space typo); ls -l /etc/motd returning -rw-r--r-- 1 root root 1 Jan 8 2026 /etc/motd; and cat -A /etc/motd returning a lone $ — cat -A's marker for a newline byte." width="655" height="438"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Existence plus metadata, in three lines. The bash: prefix exposes the typo as a shell error, not a restore failure; the ls line proves a regular file, one byte, carrying its original Jan 8 timestamp through the wound and the restore; and the lone $ photographs the invisible byte itself. Three checks, one screen, no trust required.&lt;/em&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  Scorecard
&lt;/h4&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Confirmed:&lt;/strong&gt; the restore correctly identified and recreated the deleted file as the first action in its plan · &lt;code&gt;/home&lt;/code&gt; exclusion held throughout · file timestamp survived the round trip, proving restoration rather than recreation · combined vs. solo &lt;code&gt;du&lt;/code&gt; genuinely report different, equally valid numbers · Timeshift enforces single-instance locking between GUI and CLI&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Self-corrected in real time:&lt;/strong&gt; my prediction that combined &lt;code&gt;du&lt;/code&gt; would show three independently huge numbers (wrong — hardlinks dedupe across arguments) · my assumption that &lt;code&gt;/etc/motd&lt;/code&gt; was a symlink into &lt;code&gt;/run&lt;/code&gt; (wrong — it's a regular file) · my reading that &lt;code&gt;/boot/efi&lt;/code&gt; was untouched (wrong — the file plan omitted it, but the warning device table and the GRUB2 re-install log showed the ESP was modified)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unresolved, left unclaimed:&lt;/strong&gt; the exact cause of the 4.2G delta between the two same-day snapshots (candidates: package cache, logs — never independently verified, so it stays unclaimed) · a live-USB restore path (booting the install media and restoring from there) was never actually tested, so it isn't claimed here either&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Available, not demonstrated here:&lt;/strong&gt; a CLI restore path exists (&lt;code&gt;sudo timeshift --restore&lt;/code&gt;) — this drill deliberately used the GUI throughout, since that's the window most users will actually face when something breaks&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  The Lesson
&lt;/h4&gt;

&lt;p&gt;Timeshift works exactly as advertised. But the drill surfaced something more useful than a pass/fail result: &lt;strong&gt;the verification step is where mistakes actually happen&lt;/strong&gt;, not the restore itself. I made two wrong calls in the space of thirty seconds — a typo misread as a tool failure, and a filesystem assumption that turned out to be wrong — and caught both only because I checked metadata instead of trusting a single command's surface-level output. Existence alone isn't proof. Existence plus metadata is.&lt;/p&gt;

&lt;p&gt;Snapshot before you experiment, not after something breaks. And when the disk usage numbers look alarming, remember there are three different true answers depending on which question you're actually asking: what it cost, what it contains, or what the disk holds.&lt;/p&gt;




&lt;h3&gt;
  
  
  A4. Field Note: The GUI Said 893 KB. The Terminal Said 216 MB. Both Were Telling the Truth. {#a4-update-mismatch}
&lt;/h3&gt;

&lt;p&gt;&lt;em&gt;A kernel update, two machines, and two numbers that only looked like a contradiction.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Classification:&lt;/strong&gt; Observational — nothing broke, nothing needed fixing. Filed because the explanation is satisfying, not because anything went wrong.&lt;/p&gt;

&lt;h4&gt;
  
  
  The Setup
&lt;/h4&gt;

&lt;p&gt;Routine update cycle on both machines, same three-command habit: &lt;code&gt;sudo apt update&lt;/code&gt;, then a bare &lt;code&gt;sudo apt install&lt;/code&gt; — no target, just a status check — then &lt;code&gt;sudo apt upgrade&lt;/code&gt;. On both machines, the GUI's Update Manager and the terminal disagreed. Not just on how many packages were involved — on how much they'd weigh.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;ASUS (no kernel update)&lt;/th&gt;
&lt;th&gt;HP (kernel update included)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;GUI rows shown&lt;/td&gt;
&lt;td&gt;3 (&lt;code&gt;brotli&lt;/code&gt;, &lt;code&gt;xapp&lt;/code&gt;, &lt;code&gt;xapp-thumbnailers&lt;/code&gt;)&lt;/td&gt;
&lt;td&gt;4 (adds &lt;code&gt;Linux kernel 7.0.0-42.42&lt;/code&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;"Not upgraded" count (after bare &lt;code&gt;apt install&lt;/code&gt;)&lt;/td&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;15&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Final result (after &lt;code&gt;apt upgrade&lt;/code&gt;)&lt;/td&gt;
&lt;td&gt;12 upgraded, 0 new&lt;/td&gt;
&lt;td&gt;15 upgraded, &lt;strong&gt;8 new&lt;/strong&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GUI's quoted download size&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;886 KB&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;893 KB&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Terminal's actual download size&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;886 KB&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;216 MB&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Extra disk space used&lt;/td&gt;
&lt;td&gt;0 B&lt;/td&gt;
&lt;td&gt;355 MB&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The ASUS numbers matched end to end — no kernel in the batch, nothing for the two tools to disagree about. The HP numbers split on both axes at once: package count &lt;em&gt;and&lt;/em&gt; download size. Same cause, two symptoms.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fl9l6veqtsm259f4e1qkd.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fl9l6veqtsm259f4e1qkd.webp" alt="ASUS terminal running the three-command habit top to bottom: sudo apt update with its Get/Hit mirror lines and 12 packages can be upgraded; a bare sudo apt install with no target returning 0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded; then sudo apt upgrade listing twelve packages (gir1.2-xapp-1.0, libbrotli1, libxapp1, python3-brotli and eight xapp thumbnailer entries) and ending 12 upgraded, 0 newly installed, Need to get 886 kB of archives, After this operation 0 B of additional disk space, Do you want to continue? [Y/n]." width="800" height="407"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The habit that produced the matched column: update for the catalog, a bare install as a status check — no target, just the shallow count — then upgrade for the real tally. On this machine the GUI and the terminal agree on both count and size, because nothing in the batch needed resolving.&lt;/em&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  Why the Numbers Never Lied
&lt;/h4&gt;

&lt;p&gt;&lt;strong&gt;The GUI groups by logical unit, not by package.&lt;/strong&gt; One row — &lt;code&gt;xapp&lt;/code&gt;, say — can represent a dozen individual &lt;code&gt;.deb&lt;/code&gt;s underneath it: &lt;code&gt;libxapp1&lt;/code&gt;, &lt;code&gt;gir1.2-xapp-1.0&lt;/code&gt;, &lt;code&gt;xapps-common&lt;/code&gt;, and a run of thumbnailer plugins. The GUI shows the headline; the terminal shows everything the headline is made of.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbxrpnz85tf86xv6e8rsz.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbxrpnz85tf86xv6e8rsz.webp" alt="Composite: the ASUS terminal's apt upgrade tail — the twelve-package list, 12 upgraded, Need to get 886 kB, 0 B of additional disk space, the [Y/n] prompt — layered over the top of the light-grey Update Manager window below, which shows three ticked rows (brotli 1.1.0-2ubuntu0.1, xapp 3.2.4+mint22.3, xapp-thumbnailers 1.2.10) and a footer reading 3 updates selected (886 KB)." width="800" height="623"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The grouping thesis in one frame. Twelve packages in the terminal, three rows in the GUI, one identical 886 KB on both: the GUI folds a dozen .debs into three headlines, the terminal shows what the headlines are made of. The counts disagree; the bytes never do.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Both the "not upgraded" count and the GUI's price tag are computed from the same shallow pass.&lt;/strong&gt; They only know about packages that are already installed and simply need a version bump — the 15 (or 12) packages visible &lt;em&gt;before&lt;/em&gt; any resolver has run. Neither figure has met the kernel's real dependency chain yet.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The kernel is the one update that can't be priced in advance.&lt;/strong&gt; A kernel bump isn't a version swap of something that already exists — it's the installation of an entirely new, independently versioned set of packages: image, headers, modules, tools, plus any DKMS rebuilds for things like webcam or ZFS drivers. That cost is invisible until &lt;code&gt;apt upgrade&lt;/code&gt; runs a full dependency resolution and those new packages surface for the first time — bringing their package count &lt;em&gt;and&lt;/em&gt; their download weight with them. That's where the HP's extra 8 packages came from, and it's the same resolution step that took the price from 893 KB to 216 MB. One mechanism, two numbers moving at once.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F50s5i83xo9merrmsvkzi.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F50s5i83xo9merrmsvkzi.webp" alt="Two-panel montage of the HP's kernel-inclusive update. Top: the dark-themed Update Manager with four ticked rows — brotli (highlighted), Linux kernel 7.0.0-42.42~24.04.1, xapp, xapp-thumbnailers — and a footer reading 4 updates selected (893 KB). Bottom: the HP terminal after sudo apt upgrade, opening with The following NEW packages will be installed: and eight linux-* entries (headers, hwe-headers, hwe-tools, image, v4l2loopback modules, zfs modules, modules, tools for 7.0.0-42-generic), then the upgrade list, then 15 upgraded, 8 newly installed, Need to get 216 MB of archives, After this operation 355 MB of additional disk space, [Y/n]." width="800" height="1025"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The HP column's two rulers, stacked. The GUI quotes 893 KB for four rows, the kernel among them as a single headline; the terminal, after full dependency resolution, prices the same batch at 216 MB — and the eight NEW linux-&lt;/em&gt; packages between the two numbers are exactly the fan-out the GUI could not see in advance. Same update, roughly 240 times apart, neither tool lying.*&lt;/p&gt;

&lt;h4&gt;
  
  
  The Lesson
&lt;/h4&gt;

&lt;p&gt;When a kernel update or a Flatpak runtime is in the list, treat the toolbar's download size as a placeholder, not a forecast. Kernels make the terminal's total bigger than the GUI predicted (new dependency packages the GUI hadn't counted yet). Flatpak runtimes make the GUI's total bigger than the terminal can see (&lt;code&gt;apt&lt;/code&gt; cannot count Flatpak packages at all). Same root cause — two package ecosystems, one aggregated view — opposite directions.&lt;/p&gt;

&lt;p&gt;In this case the real download — 216 MB — was roughly 240 times larger than what the GUI quoted up front. On a metered or unstable connection, don't plan your data budget around the number shown before you hit Install.&lt;/p&gt;

&lt;h4&gt;
  
  
  Scorecard
&lt;/h4&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Confirmed:&lt;/strong&gt; ASUS matched perfectly on both count and size with no kernel in the mix · HP diverged on both metrics, and the divergence landed exactly on the kernel's new dependency fan-out&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Suspected:&lt;/strong&gt; both mismatches trace to one root cause — the GUI and the pre-upgrade tally only know about packages already installed; full dependency resolution during &lt;code&gt;apt upgrade&lt;/code&gt; is what first reveals the kernel's new packages, and their weight, together&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unresolved:&lt;/strong&gt; no byte-level audit of what the GUI priced internally (would need &lt;code&gt;apt show&lt;/code&gt; per package to fully confirm) · only one kernel-inclusive data point exists — "expect substantially more" is a direction, not yet a calibrated range&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;— King Anthony | kinganthony.tech | &lt;a href="mailto:hello@kinganthony.tech"&gt;hello@kinganthony.tech&lt;/a&gt;&lt;br&gt;
&lt;em&gt;If this guide saved you from a disaster, share it. If you found something I didn't cover, reach out. I'm still learning.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Haven't installed yet?&lt;/strong&gt; Start here: &lt;a href="https://kinganthony.tech/blog/linux-mint-install/" rel="noopener noreferrer"&gt;How to Install Linux Mint (All Editions) on a Windows 11 Laptop&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Want the full story behind every step?&lt;/strong&gt; Read the companion narrative series: &lt;a href="https://kinganthony.tech/blog/dual-booting-linux-mint-xfce-part-0/" rel="noopener noreferrer"&gt;Dual Booting Linux on a Machine That Barely Runs Windows&lt;/a&gt;&lt;/p&gt;

</description>
      <category>linux</category>
      <category>timeshift</category>
      <category>linuxmint</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How to Install Linux Mint (All Editions) on a Windows 11 Laptop</title>
      <dc:creator>King Anthony</dc:creator>
      <pubDate>Mon, 16 Nov 2026 02:21:30 +0000</pubDate>
      <link>https://dev.to/kinganthony/how-to-install-linux-mint-all-editions-on-a-windows-11-laptop-227j</link>
      <guid>https://dev.to/kinganthony/how-to-install-linux-mint-all-editions-on-a-windows-11-laptop-227j</guid>
      <description>&lt;h1&gt;
  
  
  How to Install Linux Mint (All Editions) on a Windows 11 Laptop
&lt;/h1&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Last tested on:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Linux Mint 22.3 (XFCE)&lt;/li&gt;
&lt;li&gt;Ventoy 1.1.17&lt;/li&gt;
&lt;li&gt;Windows 11 &lt;/li&gt;
&lt;li&gt;Hardware: ASUS VivoBook (i3-7020U) &amp;amp; HP (Pentium N3710)&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;A complete guide to installing Linux Mint alongside Windows 11. While this guide uses &lt;strong&gt;Linux Mint XFCE&lt;/strong&gt; as the primary case study (due to its performance on low-end hardware), these steps apply to &lt;strong&gt;Cinnamon&lt;/strong&gt; and &lt;strong&gt;MATE&lt;/strong&gt; 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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which guide should you read?
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;This guide&lt;/strong&gt; = Clean step-by-step reference. Use this if you want to install Linux Mint efficiently with a proven procedure.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The narrative series&lt;/strong&gt; = 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.&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Note on Editions &amp;amp; File Names:&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
This guide applies equally to the XFCE, Cinnamon, and MATE editions. To keep the text clean, we use the &lt;strong&gt;XFCE&lt;/strong&gt; 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.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;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.&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 0: Suspend BitLocker (~5-10 minutes)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;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.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Open &lt;strong&gt;PowerShell as Administrator&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Check current status:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;manage&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;bde&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;status&lt;/span&gt; &lt;span class="no"&gt;C&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; If "Protection Status" is &lt;strong&gt;ON&lt;/strong&gt;, inspect which protectors actually exist on the volume:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;manage&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;bde&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;protectors&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;get&lt;/span&gt; &lt;span class="no"&gt;C&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Back up your 48-digit recovery key based on what that output shows:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;If a "Numerical Password" protector is listed:&lt;/strong&gt; copy the key to your clipboard:
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;manage&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;bde&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;protectors&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;get&lt;/span&gt; &lt;span class="no"&gt;C&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Type&lt;/span&gt; &lt;span class="nc"&gt;RecoveryPassword&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="n"&gt;clip&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;em&gt;(This prints nothing — the key is now on your clipboard. Paste it into Notepad immediately to confirm it copied.)&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;If only "TPM" is listed (no Numerical Password):&lt;/strong&gt; no recovery key exists on this volume yet. Create one first:
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;manage&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;bde&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;protectors&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;add&lt;/span&gt; &lt;span class="no"&gt;C&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;RecoveryPassword&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The new 48-digit key is printed directly in the command output.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;🛑 &lt;strong&gt;Do not proceed until your 48-digit recovery key exists in at least two places off this machine&lt;/strong&gt; — 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.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Suspend BitLocker protection (this takes seconds and does not decrypt the drive):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;manage&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;bde&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;protectors&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;disable&lt;/span&gt; &lt;span class="no"&gt;C&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;RebootCount&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;em&gt;(Without &lt;code&gt;-RebootCount 0&lt;/code&gt;, suspension expires after ONE reboot and silently re-arms mid-install. Zero means suspended until you re-enable it manually in Step 9.)&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6.&lt;/strong&gt; Verify suspension:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;manage&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;bde&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;status&lt;/span&gt; &lt;span class="no"&gt;C&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;em&gt;(Protection Status should now say "Off", but Percentage Encrypted will remain 100%).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffiwmwbn27rltyfv9lfjp.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffiwmwbn27rltyfv9lfjp.webp" alt="manage-bde output: TPM-only protectors, redacted key creation, Protection Off" width="800" height="1268"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Step 0 receipts: inspect, create the key, verify suspension.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;▶ Why is BitLocker dangerous for dual boot?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The TPM Measurement Trap&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;When the typical Microsoft backup routes fail&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
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.&lt;/p&gt;

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

&lt;p&gt;&lt;strong&gt;Re-enabling after install:&lt;/strong&gt; covered in &lt;strong&gt;Step 9&lt;/strong&gt;, after dual-boot verification. Do not re-enable before then.&lt;/p&gt;


&lt;h2&gt;
  
  
  Step 1: Disable Fast Startup (~3 minutes)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Press &lt;strong&gt;Win + R&lt;/strong&gt; → type &lt;code&gt;control&lt;/code&gt; → Enter&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Go to &lt;strong&gt;Power Options&lt;/strong&gt; → &lt;strong&gt;Choose what the power buttons do&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Click &lt;strong&gt;Change settings that are currently unavailable&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Uncheck &lt;strong&gt;Turn on fast startup (recommended)&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Click &lt;strong&gt;Save changes&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6.&lt;/strong&gt; &lt;em&gt;(Optional but Recommended)&lt;/em&gt; Open &lt;strong&gt;PowerShell as Administrator&lt;/strong&gt; and run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;powercfg -h off
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;em&gt;(This fully disables hibernation and deletes hiberfil.sys, ensuring a clean shutdown)&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbt3initjkhvupvpdov5t.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbt3initjkhvupvpdov5t.webp" alt="Windows System Settings under Power Options: Turn on fast startup is unchecked, while Sleep and Lock remain checked and Hibernation is unchecked." width="800" height="423"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;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.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;▶ Why does Fast Startup break dual boot?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Fast Startup is a hybrid shutdown feature. Instead of fully shutting down, Windows writes the kernel session to a file called &lt;strong&gt;hiberfil.sys&lt;/strong&gt; and hibernates. This leaves the NTFS partition in a semi-locked state.&lt;/p&gt;

&lt;p&gt;When Linux tries to access that partition during dual boot, it can cause file system conflicts, write errors, and strange boot behavior.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The fix is simple:&lt;/strong&gt; disable Fast Startup so Windows performs a true, complete shutdown every time.&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 2: Shrink the Windows Partition (~15-30 minutes)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;This is where most dual-boot attempts fail.&lt;/strong&gt; If Windows only lets you shrink a tiny amount, see the collapsible section below.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Right-click &lt;strong&gt;Start&lt;/strong&gt; → &lt;strong&gt;Disk Management&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Right-click &lt;strong&gt;C:&lt;/strong&gt; → &lt;strong&gt;Shrink Volume&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Wait for Windows to calculate available space&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Enter the amount to shrink in MB (1GB ≈ 1024 MB)&lt;/p&gt;

&lt;p&gt;&lt;em&gt;(Windows Disk Management labels these values "MB," but they behave like MiB: 1 GiB = 1024 MiB. Use the formula: &lt;code&gt;intended Linux space in GiB × 1024 = MB to enter&lt;/code&gt;. Example: 90 GiB = 92160 MB. Do not enter more than the "Size of available shrink space in MB" value shown above it.)&lt;/em&gt;&lt;br&gt;
&lt;strong&gt;5.&lt;/strong&gt; Click &lt;strong&gt;Shrink&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6.&lt;/strong&gt; Verify the &lt;strong&gt;Unallocated&lt;/strong&gt; space appears&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5u74f6nurl1czyo5vxe1.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5u74f6nurl1czyo5vxe1.webp" alt="Disk Management side by side with red BEFORE and AFTER labels: before, C: is 237.77 GB with no free block; after, C: is 87.77 GB and a 150.00 GB black Unallocated block sits between it and the Recovery partition." width="799" height="214"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;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.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Recommended partition split for a 256GB SSD:&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Partition&lt;/th&gt;
&lt;th&gt;Size&lt;/th&gt;
&lt;th&gt;Purpose&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Windows 11 (C:)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;~80-120GB&lt;/td&gt;
&lt;td&gt;Windows system and apps&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Unallocated&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;~90-150GB&lt;/td&gt;
&lt;td&gt;Reserved for Linux Mint&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;EFI / Recovery&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Remaining&lt;/td&gt;
&lt;td&gt;System partitions (do not touch)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;DRIVE LAYOUT VISUALIZED:
BEFORE: [EFI][MSR][Windows C: ████████████][Recovery]
AFTER:  [EFI][MSR][Windows C: ██████][Unallocated █████][Recovery]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;&lt;strong&gt;⚠️ Problem: Windows only lets you shrink a tiny amount?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why this happens:&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Windows has &lt;strong&gt;unmovable system files&lt;/strong&gt; (pagefile.sys, hiberfil.sys, System Restore points) pinned to the end of the partition. Disk Management cannot shrink past them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How to fix it:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A. Disable the pagefile temporarily:&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;1.&lt;/strong&gt; Press &lt;code&gt;Win + R&lt;/code&gt; → type &lt;code&gt;sysdm.cpl&lt;/code&gt; → Enter&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Go to &lt;strong&gt;Advanced&lt;/strong&gt; tab → &lt;strong&gt;Performance&lt;/strong&gt; Settings&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Go to &lt;strong&gt;Advanced&lt;/strong&gt; tab → &lt;strong&gt;Virtual Memory&lt;/strong&gt; Change&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Uncheck "Automatically manage paging file size"&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Select &lt;strong&gt;No paging file&lt;/strong&gt; → click &lt;strong&gt;Set&lt;/strong&gt; → OK&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6.&lt;/strong&gt; Restart when prompted&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;B. Disable hibernation:&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;1.&lt;/strong&gt; Open &lt;strong&gt;PowerShell as Administrator&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;powercfg&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;h&lt;/span&gt; &lt;span class="n"&gt;off&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;C. Disable System Protection:&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;1.&lt;/strong&gt; Press &lt;code&gt;Win + R&lt;/code&gt; → type &lt;code&gt;sysdm.cpl&lt;/code&gt; → Enter&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Go to &lt;strong&gt;System Protection&lt;/strong&gt; tab → Select C: → click &lt;strong&gt;Configure&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Select &lt;strong&gt;Disable system protection&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Click &lt;strong&gt;Apply&lt;/strong&gt; to commit the change while keeping the dialog open.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Click &lt;strong&gt;Delete&lt;/strong&gt; to remove existing restore points. &lt;em&gt;(Warning: This removes an existing Windows recovery option. Ensure you have backups).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6.&lt;/strong&gt; Click &lt;strong&gt;OK&lt;/strong&gt; to close the dialog.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;D. Restart the computer and try shrinking again.&lt;/strong&gt; The available shrink space should increase significantly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;E. After shrinking, RE-ENABLE only these settings:&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;1.&lt;/strong&gt; &lt;strong&gt;Pagefile:&lt;/strong&gt; Check "Automatically manage paging file size".&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; &lt;strong&gt;System Protection:&lt;/strong&gt; Turn on system protection.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpkkoaip768ir8r923eey.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpkkoaip768ir8r923eey.webp" alt="Annotated four-panel Windows cleanup sequence: Virtual Memory with automatic paging file management boxed and No paging file selected, PowerShell running powercfg -h off, System Protection with Disable system protection and Delete boxed, and Shrink C with available shrink space and entered shrink amount boxed." width="800" height="662"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;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.&lt;/em&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  Step 3: Download the Linux Mint ISO (~15-60 minutes)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Go to the &lt;a href="https://linuxmint.com/download.php" rel="noopener noreferrer"&gt;official Linux Mint download page&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Select your Edition (&lt;strong&gt;XFCE&lt;/strong&gt;, &lt;strong&gt;Cinnamon&lt;/strong&gt;, or &lt;strong&gt;MATE&lt;/strong&gt;)&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Choose a download method: &lt;strong&gt;Direct mirror&lt;/strong&gt; or &lt;strong&gt;Torrent&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Wait for the download to complete (~2.5GB to 2.8GB)&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; &lt;strong&gt;Verify the ISO Checksum:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Quick Method:&lt;/strong&gt; Open Command Prompt, paste this exact line (adjust the path), and press Enter:
&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;certutil -hashfile "C:\Users\YourName\Downloads\linuxmint-22.3-xfce-64bit.iso" SHA256
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;ul&gt;
&lt;li&gt;Compare the output hash with the official checksum on &lt;a href="https://linuxmint.com/verify.php" rel="noopener noreferrer"&gt;linuxmint.com/verify.php&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;▶ When and why to use torrent instead of mirrors, including qBittorrent setup&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is a mirror?&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
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.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why use a torrent?&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
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 &lt;code&gt;.torrent&lt;/code&gt; 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.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How to set up qBittorrent (Standard Flow):&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Download qBittorrent from the &lt;a href="https://www.qbittorrent.org/" rel="noopener noreferrer"&gt;official site&lt;/a&gt; ONLY. &lt;em&gt;(Fake installers carrying malware are common on third-party sites).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhogcobo530xre61cseiy.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhogcobo530xre61cseiy.webp" alt="Annotated four-panel qBittorrent acquisition path: green box on the homepage download arrow, the    official download page with its PGP signing block and a red box on the stable v5.2.4 link while the v5.3.0rc1 beneath it is left unmarked, green box on Latest Version 64_setup.exe on SourceForge, and the setup.exe download bubble marked scanned for malware." width="800" height="603"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;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.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Install and open qBittorrent. Approve administrator access &lt;em&gt;only&lt;/em&gt; for the installer if Windows requests it, and click through any post-installation wizards using default settings.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fa6r43ghhbwb1gsxwqo5u.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fa6r43ghhbwb1gsxwqo5u.webp" alt="Four-panel installer sequence: the qBittorrent 5.2.4 x64 welcome screen, the Nullsoft progress bar extracting at 44 percent, the completion screen with Launch qBittorrent ticked, and the freshly opened empty client showing DHT at 90 nodes." width="800" height="603"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;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.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Download the Linux Mint &lt;code&gt;.torrent&lt;/code&gt; file from the Mint download page.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgd44oj7x72hyhsmgazzu.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgd44oj7x72hyhsmgazzu.webp" alt="Linux Mint download page Information block with the 64-bit torrent link boxed in red and a red arrow labeling it 28.5KB - click this, beside the Size 2.8GB, Installation Guide, Release Announcement and Release Notes links." width="799" height="517"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;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.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; &lt;strong&gt;Add the torrent to qBittorrent:&lt;/strong&gt; Open the qBittorrent app. Click the &lt;strong&gt;"+" (Add Torrent File) icon&lt;/strong&gt; on the top toolbar (or go to &lt;strong&gt;File &amp;gt; Add Torrent File&lt;/strong&gt;). Browse to your Downloads folder, select the &lt;code&gt;.torrent&lt;/code&gt; file, and click &lt;strong&gt;Open&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; A "New Torrent" dialogue menu will appear. Leave it on default settings and click &lt;strong&gt;OK&lt;/strong&gt;. The download starts.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe5gd61iffta5yzqnfdos.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe5gd61iffta5yzqnfdos.webp" alt="qBittorrent New Torrent dialog for linuxmint-22.3-xfce-64bit.iso with every option at its default - Start torrent checked, content layout Original, save path set to the Downloads folder - and a red annotation reading Defaults - click OK with an arrow pointing at the OK button." width="800" height="631"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;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.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6.&lt;/strong&gt; &lt;em&gt;(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).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpzswpp7zevltvd42e4fz.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpzswpp7zevltvd42e4fz.webp" alt="qBittorrent mid-download: linuxmint-22.3 xfce 64-bit at 26.2 percent, status Downloading, 90 seeds and 3 peers, 5.3 MiB/s on the row and 6.7 MiB/s aggregate, ETA 8 minutes, 764.3 MiB received so far." width="799" height="423"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;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.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flx0oyl8xky5k74zf341k.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flx0oyl8xky5k74zf341k.webp" alt="qBittorrent showing linuxmint-22.3 xfce 64-bit at 100 percent Completed but stopped, with 0 seeds and 0 peers connected, 0 B/s both directions, and cumulative counters of 2.85 GiB received and 848 KiB sent." width="799" height="421"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;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.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fallback for Unstable/Restricted Connections:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If the download is stalling or painfully slow:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; &lt;strong&gt;Add trackers:&lt;/strong&gt; Go to &lt;a href="https://newtrackon.com/lists" rel="noopener noreferrer"&gt;newtrackon.com/lists&lt;/a&gt; and click the green copy icon to copy all trackers. In qBittorrent, highlight the downloading Mint file and right-click it → &lt;strong&gt;Edit trackers&lt;/strong&gt;. A dialogue box appears with a single default tracker ending in &lt;code&gt;...announce&lt;/code&gt;. Move your cursor to the very end of that text and press &lt;strong&gt;ENTER&lt;/strong&gt; to create a blank line, then paste the new trackers. &lt;em&gt;(Without this line spacing, qBittorrent may parse the pasted trackers as a single entry).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; &lt;strong&gt;Adjust connection limits:&lt;/strong&gt; Click the &lt;strong&gt;Option icon (⚙️)&lt;/strong&gt; in the top left bar → click &lt;strong&gt;Connection&lt;/strong&gt;. Change the values from default to the recommended values:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Global Maximum Number of connections:&lt;/strong&gt; 200-300&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Maximum Number of connection per Torrent:&lt;/strong&gt; 50-80&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Global Maximum Number of Uploaded slots:&lt;/strong&gt; 4
&lt;em&gt;(DHT and PeX are enabled by default. No action needed there).&lt;/em&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fd2n3cxqmkf0t0j7ocdlb.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fd2n3cxqmkf0t0j7ocdlb.webp" alt="qBittorrent Connection options with the four limits enabled and set to 250 global connections, 60 per torrent, 4 global upload slots and 4 per-torrent upload slots; the Apply button is greyed out, confirming the values were saved." width="800" height="642"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;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.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Verify File Integrity (Step-by-step for Beginners):&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Windows has a built-in tool to verify the ISO without needing third-party software.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Open the &lt;strong&gt;Command Prompt&lt;/strong&gt; (Press &lt;code&gt;Win + R&lt;/code&gt;, type &lt;code&gt;cmd&lt;/code&gt;, and press Enter).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Type &lt;code&gt;certutil -hashfile&lt;/code&gt; &lt;em&gt;(⚠️ Make sure to leave exactly one space after the word hashfile)&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; &lt;strong&gt;Get the file path into the Command Prompt:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;em&gt;If you have a mouse:&lt;/em&gt; Click and &lt;strong&gt;drag the downloaded Linux Mint ISO file&lt;/strong&gt; directly into the black Command Prompt window and let go. Windows will paste the path automatically.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;If you are using a trackpad (or drag-and-drop fails):&lt;/em&gt; Right-click the downloaded ISO file in your folder and select &lt;strong&gt;"Copy as path"&lt;/strong&gt;. Then, &lt;strong&gt;right-click&lt;/strong&gt; anywhere inside the black Command Prompt window to paste the path.
&lt;strong&gt;4.&lt;/strong&gt; Type a space, then &lt;code&gt;SHA256&lt;/code&gt;. Your full command should look something like this (using our running example): &lt;code&gt;certutil -hashfile "C:\Users\Name\Downloads\linuxmint-22.3-xfce-64bit.iso" SHA256&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Press &lt;strong&gt;ENTER&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6.&lt;/strong&gt; &lt;strong&gt;Wait:&lt;/strong&gt; The prompt will appear to freeze for 1 to 5 minutes while it reads the file. This is normal. Do not close the window.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;7.&lt;/strong&gt; &lt;strong&gt;Read the output:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;SHA256 hash of C:\Users\Name\Downloads\linuxmint-22.3-xfce-64bit.iso:
a1b2c3d4e5f6...[long string of numbers and letters]...
CertUtil: -hashfile command completed successfully.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;em&gt;(Cinnamon and MATE readers: your output will show your edition's filename here. That is expected — compare the hash string, not the filename label).&lt;/em&gt;&lt;br&gt;
&lt;strong&gt;8.&lt;/strong&gt; &lt;strong&gt;Compare:&lt;/strong&gt; Open the &lt;a href="https://linuxmint.com/verify.php" rel="noopener noreferrer"&gt;official Linux Mint verification page&lt;/a&gt;. Find the exact edition (Cinnamon, MATE, or XFCE) and version you downloaded. Compare the long string of characters in your Command Prompt with the one on the website.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;If they match exactly:&lt;/strong&gt; Your download is perfect.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;If even a single character is different:&lt;/strong&gt; The download is corrupted. Delete it and download again.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flppnkbiajxu5ug6fbgwb.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flppnkbiajxu5ug6fbgwb.webp" alt="Split receipt: top, a Command Prompt certutil run printing a SHA256 hash for the xfce ISO, labeled Your output; bottom, the official sha256sum.txt in a browser where the third line, xfce-64bit.iso, carries the identical hash, labeled Official - must match." width="800" height="329"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The match that matters is the third line — xfce-64bit.iso. Your certutil output and that official string are character‑for‑character identical, which is the only acceptable result. Cinnamon and MATE readers: your edition is a different line in the same file, and the same equality rule applies to it.&lt;/em&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  Step 4: Create Boot Media with Ventoy (~10-15 minutes)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Download &lt;a href="https://www.ventoy.net/" rel="noopener noreferrer"&gt;Ventoy&lt;/a&gt; from the official site.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Insert your USB drive or SD card in a dedicated reader (8GB+). Ensure it is formatted and empty.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Run &lt;strong&gt;Ventoy2Disk.exe&lt;/strong&gt; (Allow Admin rights).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Select your USB device from the dropdown.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Set the Partition style to GPT.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6.&lt;/strong&gt; Click &lt;strong&gt;Install&lt;/strong&gt; → Accept formatting warnings.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;7.&lt;/strong&gt; Copy the Linux Mint ISO file (~2.5GB to 2.8GB) into the Ventoy drive.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;8.&lt;/strong&gt; &lt;strong&gt;Verify the file integrity&lt;/strong&gt; on the USB drive using &lt;code&gt;certutil&lt;/code&gt; (same as Step 3).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;▶ Full Ventoy walkthrough for beginners (Critical Step)&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why Ventoy?&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Unlike Rufus or Etcher, Ventoy prepares the drive once. After that you simply copy ISO files onto it like normal files. You can keep multiple ISOs on the same stick.&lt;/p&gt;
&lt;h3&gt;
  
  
  1. Download Ventoy
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Go to the &lt;a href="https://www.ventoy.net/" rel="noopener noreferrer"&gt;official Ventoy website&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Download the latest Windows release (the &lt;code&gt;.zip&lt;/code&gt; file).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Extract the Zip folder to your Downloads folder.&lt;/p&gt;
&lt;h3&gt;
  
  
  2. Prepare the USB drive
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Back up anything important that is currently on the USB drive. Ventoy will &lt;strong&gt;erase the entire drive&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Insert the USB drive (or SD card in a dedicated reader) into your computer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; &lt;em&gt;(Note: After previous formatting, Windows File Explorer sometimes does not show the drive immediately. This is normal. Do not panic.)&lt;/em&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  3. Launch Ventoy2Disk
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Go to your Downloads folder and locate the Ventoy &lt;code&gt;.zip&lt;/code&gt; file you just downloaded.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Right-click it → &lt;strong&gt;Extract All&lt;/strong&gt; (or extract with 7-Zip / WinRAR).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Open the extracted folder.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Find and double-click &lt;strong&gt;Ventoy2Disk.exe&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; When Windows asks for permission, click &lt;strong&gt;Yes&lt;/strong&gt; (run as administrator).&lt;/p&gt;
&lt;h3&gt;
  
  
  4. Set the partition style to GPT
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; In the Ventoy2Disk window, click &lt;strong&gt;Option&lt;/strong&gt; in the top menu bar.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Go to &lt;strong&gt;Partition Style&lt;/strong&gt; → select &lt;strong&gt;GPT&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; The interface will switch from MBR to GPT.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why GPT?&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Your laptop is running 64-bit Windows 11 in UEFI mode. GPT is the correct partition style for native UEFI boot. Using MBR could force the system into Compatibility Support Module (CSM/Legacy) mode, which is unnecessary and can cause problems later.&lt;/p&gt;
&lt;h3&gt;
  
  
  5. Install Ventoy on the USB drive
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; In the device dropdown, carefully select your USB drive.  &lt;/p&gt;

&lt;p&gt;Double-check the drive letter and size so you do not accidentally select your internal hard drive.&lt;br&gt;
&lt;strong&gt;2.&lt;/strong&gt; Click &lt;strong&gt;Install&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Accept both warning dialogs that appear. Ventoy will format the drive and install its bootloader.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; When the process finishes, Windows File Explorer should show a new drive named &lt;strong&gt;Ventoy&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;At this point the USB drive is ready. It will contain a small Ventoy system partition (usually hidden) and a large open partition where you will place ISO files.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnv9bpqba9nwaayau82et.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnv9bpqba9nwaayau82et.webp" alt="Annotated two-stage Ventoy install: red BEFORE over an explorer window listing a single drive, Local Disk C, with the Ventoy installer still on its form; red AFTER over an explorer now listing two drives, the second being Ventoy D, with the installer advanced to a green ready state." width="799" height="218"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The install, measured by what Windows sees: before, the stick is not a usable volume and the explorer counts one drive; after, Ventoy writes its layout and a second volume, Ventoy (D:), appears. The green ready state is the installer confirming it, but the drive count is the receipt you check on your own screen.&lt;/em&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  6. Copy the Linux Mint ISO
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Go to your Downloads folder.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Locate the Linux Mint ISO.  &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Important:&lt;/strong&gt; It must be the large file (~2.5–2.8 GB). Do &lt;strong&gt;not&lt;/strong&gt; copy the tiny &lt;code&gt;.torrent&lt;/code&gt; file (~28 KB).&lt;br&gt;
&lt;strong&gt;3.&lt;/strong&gt; Copy the ISO file.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Open the &lt;strong&gt;Ventoy&lt;/strong&gt; drive in File Explorer and paste the ISO there.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Wait for the transfer to finish.  &lt;/p&gt;

&lt;p&gt;Expected speed on a normal USB 2.0/3.0 connection: roughly 7–10 MB/s → about 5–7 minutes for a 2.8 GB file.&lt;br&gt;
&lt;strong&gt;6.&lt;/strong&gt; Confirm the ISO is visible inside the Ventoy drive.&lt;/p&gt;
&lt;h3&gt;
  
  
  7. Verify the ISO on the Ventoy drive
&lt;/h3&gt;

&lt;p&gt;Copying can introduce corruption. Always verify the file that is actually sitting on the boot media.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Open &lt;strong&gt;Command Prompt&lt;/strong&gt; (&lt;code&gt;Win + R&lt;/code&gt; → type &lt;code&gt;cmd&lt;/code&gt; → Enter).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Type the following (leave a space after &lt;code&gt;hashfile&lt;/code&gt;):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;certutil -hashfile 
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Drag the Linux Mint ISO &lt;strong&gt;from the Ventoy drive&lt;/strong&gt; into the Command Prompt window (or right-click the file → Copy as path and paste it).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Type a space and then &lt;code&gt;SHA256&lt;/code&gt;. The full command should look similar to:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;certutil -hashfile "E:\linuxmint-22.3-xfce-64bit.iso" SHA256
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Press &lt;strong&gt;Enter&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6.&lt;/strong&gt; Wait 1–5 minutes while the hash is calculated. The window may appear frozen — this is normal.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;7.&lt;/strong&gt; Compare the resulting hash string with the official checksum on &lt;a href="https://linuxmint.com/verify.php" rel="noopener noreferrer"&gt;linuxmint.com/verify.php&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgi9csm0uy5qb2g9bfsub.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgi9csm0uy5qb2g9bfsub.webp" alt="Command Prompt running certutil -hashfile on D:\linuxmint-22.3-xfce-64bit.iso, returning SHA256 45a835b5dddaf40e84d776549e0b19b3fbd49673b6cc6434ebddbfcd217df776 and CertUtil: -hashfile command completed successfully." width="799" height="193"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Re-hash the copy, not just the download. The path is D: — the same Ventoy volume that appeared in the figure above — so this proves the bytes survived the trip onto the stick. The string matches the official xfce hash character for character, and the success line is the closer.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If the hashes match exactly&lt;/strong&gt;, the file on the Ventoy drive is clean and ready for booting.&lt;br&gt;&lt;br&gt;
&lt;strong&gt;If even one character is different&lt;/strong&gt;, delete the ISO from the Ventoy drive and copy it again.&lt;/p&gt;

&lt;p&gt;This verification step is one of the most important safeguards in the entire process. A corrupted ISO on the boot media is a common cause of later boot failures that look like hardware or BIOS problems.&lt;/p&gt;


&lt;h2&gt;
  
  
  Step 5: Configure BIOS Settings (MOK Enrollment) (~5 minutes)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Boot Menu Keys by Manufacturer:&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Brand&lt;/th&gt;
&lt;th&gt;Boot Menu&lt;/th&gt;
&lt;th&gt;BIOS Setup&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;HP&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;F9 or Esc&lt;/td&gt;
&lt;td&gt;F10&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;ASUS&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Esc or F8&lt;/td&gt;
&lt;td&gt;F2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Dell&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;F12&lt;/td&gt;
&lt;td&gt;F2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Lenovo&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;F12 or Fn+F12&lt;/td&gt;
&lt;td&gt;F1 or F2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Acer&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;F12&lt;/td&gt;
&lt;td&gt;F2&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Primary Method: Enroll Ventoy Key (Keep Secure Boot ON)&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Insert the Ventoy boot device. Restart and press your &lt;strong&gt;boot menu key&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Select your USB device from the boot menu. It appears under the drive's own name, usually with a &lt;strong&gt;UEFI:&lt;/strong&gt; prefix (e.g., &lt;code&gt;UEFI: SanDisk&lt;/code&gt; or &lt;code&gt;UEFI: Kingston&lt;/code&gt;). It will NOT say "Linux Mint" — the Ventoy menu loads after the device boots. If the same drive appears twice, choose the entry with the &lt;strong&gt;UEFI&lt;/strong&gt; prefix.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; If you see a &lt;strong&gt;blue screen failure&lt;/strong&gt; (MOK Management), press &lt;strong&gt;ENTER&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Select &lt;strong&gt;Enroll Key from Disk&lt;/strong&gt; → Select &lt;strong&gt;VTOYEFI&lt;/strong&gt; → Select &lt;strong&gt;ENROLL_THIS_KEY_IN_MOKMANAGER.cer&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Select &lt;strong&gt;Continue&lt;/strong&gt; → Select &lt;strong&gt;Yes&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6.&lt;/strong&gt; If prompted for a password, &lt;strong&gt;try leaving it blank and pressing Enter&lt;/strong&gt;. If rejected, try &lt;code&gt;ventoy&lt;/code&gt;. &lt;em&gt;(If both fail, consult the official Ventoy Secure Boot documentation for your specific version).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;7.&lt;/strong&gt; Select &lt;strong&gt;Reboot&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;(Note: Enrolling Ventoy's key adds it to your machine's trust store, allowing its bootloader to pass Secure Boot. Only use Ventoy from its official source).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;▶ Fallback Method: Disable Secure Boot&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If MOK Enrollment fails, disable Secure Boot as a last resort.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Restart and press your &lt;strong&gt;BIOS key&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Navigate to &lt;strong&gt;Security&lt;/strong&gt; or &lt;strong&gt;Boot&lt;/strong&gt; tab.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; &lt;strong&gt;Disable Secure Boot&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Verify &lt;strong&gt;UEFI mode&lt;/strong&gt; is still active. &lt;strong&gt;(⚠️ Do NOT switch to Legacy/CSM)&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Save and exit.&lt;/p&gt;


&lt;h2&gt;
  
  
  Step 6: Boot into the Live Environment (~3-5 minutes)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; At the Ventoy menu, select the Linux Mint ISO.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Choose &lt;strong&gt;Boot in normal mode&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; At the GRUB menu, select &lt;strong&gt;Start Linux Mint Xfce 22.3 64-bit&lt;/strong&gt; &lt;em&gt;(or your downloaded edition's name, e.g., Cinnamon)&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Wait for the live desktop to load.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcjeh8ah4npedmnnvb5s6.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcjeh8ah4npedmnnvb5s6.webp" alt="Four-panel boot chain: Ventoy selecting linuxmint-22.3-xfce-64bit.iso, Ventoy boot mode menu with Boot in normal mode selected, GNU GRUB 2.12 with Start Linux Mint 22.3 Xfce 64-bit selected, and the Linux Mint live desktop appearing after boot." width="800" height="460"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The path from stick to live session: Ventoy loads the ISO, normal boot mode is selected, GRUB launches Linux Mint 22.3 Xfce 64-bit, and the live desktop appears. This is the moment the machine is testing Mint without installing it yet.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Test WiFi, Sound, Keyboard, and Display.&lt;/p&gt;


&lt;h2&gt;
  
  
  Step 7: Install Linux Mint (~15-30 minutes)
&lt;/h2&gt;

&lt;p&gt;⚠️ &lt;strong&gt;WARNING: Home Folder Encryption&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Do &lt;strong&gt;not&lt;/strong&gt; enable home-folder encryption on Intel Pentium, Celeron, or older dual-core CPUs, or on machines with 4 GB RAM or less. The cryptographic overhead will noticeably degrade performance on constrained hardware and is difficult to reverse without a fresh installation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Standard Installation Steps:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Double-click the &lt;strong&gt;Install Linux Mint&lt;/strong&gt; icon.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Select &lt;strong&gt;Language&lt;/strong&gt; → &lt;strong&gt;Keyboard Layout&lt;/strong&gt; → Continue.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Connect to WiFi → Check &lt;strong&gt;Install multimedia codecs&lt;/strong&gt; → Continue.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; If prompted about mounted partitions, click &lt;strong&gt;Yes&lt;/strong&gt; to unmount.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnpvbbor0x32ksa7dk9o3.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnpvbbor0x32ksa7dk9o3.webp" alt="Two-by-two pre-install run: Welcome with English selected, Keyboard layout with English (US) selected, Multimedia codecs with the Install multimedia codecs checkbox ticked and red-boxed, and the Unmount partitions that are in use dialog on /dev/sda with Yes red-boxed." width="800" height="616"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The four screens before the partitioning choice. Pick your language and keyboard as usual; the two red boxes are the only forced calls here — tick Install multimedia codecs so video and sites render, and when the installer asks to unmount the in-use /dev/sda, answer Yes so it can lay out the unallocated window you freed in Step 2.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;🛑 STOP AND VERIFY BEFORE PROCEEDING:&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Select &lt;strong&gt;Install Linux Mint alongside Windows Boot Manager&lt;/strong&gt; ONLY IF:  &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Windows Boot Manager is explicitly detected.
&lt;/li&gt;
&lt;li&gt;The proposed Linux space corresponds to the unallocated region you created in Step 2.
&lt;/li&gt;
&lt;li&gt;The Windows partition remains visible and is NOT marked for formatting.
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;DO NOT select "Erase disk and install Linux Mint".&lt;/strong&gt; That option removes Windows and all existing data. If "Install alongside" is missing, stop and back up your data.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0vhcb2no2v9z3wgd3gv3.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0vhcb2no2v9z3wgd3gv3.webp" alt="Installation type screen headed This computer currently has Windows Boot Manager on it, with Install Linux Mint alongside Windows Boot Manager selected and red-boxed THIS ONE, Erase disk and install Linux Mint struck with a red X and NEVER, and Something else unmarked; Advanced features shows None selected." width="800" height="595"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The header is the proof the installer found your Windows — without that line, the alongside option would not appear, so if your screen differs, stop and read before clicking. The red marks settle the choice: alongside is THIS ONE; Erase disk, which wipes every file on every OS, is NEVER. Leave Advanced features at None selected and continue.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; Select &lt;strong&gt;Install Linux Mint alongside Windows Boot Manager&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6.&lt;/strong&gt; Create your user account.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3qpu7hrmuawg2wondt85.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3qpu7hrmuawg2wondt85.webp" alt="Who are you screen with empty name, computer-name, username, password and confirm fields, Require my password to log in selected over Log in automatically, and the Encrypt my home folder checkbox red-boxed with a red arrow reading Leave unchecked on low end." width="800" height="516"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Fill the fields and leave Require my password to log in as the default. The one trap the red box flags: Encrypt my home folder. It looks like free security, but on low-end hardware the home-directory encryption tax is real CPU and RAM on every file access — leave it unchecked, exactly as the mark says.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;7.&lt;/strong&gt; Click &lt;strong&gt;Install Now&lt;/strong&gt; and confirm.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;8.&lt;/strong&gt; Wait for the installation to complete.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;9.&lt;/strong&gt;  When prompted, &lt;strong&gt;remove the boot media&lt;/strong&gt; and press &lt;strong&gt;Enter&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Important:&lt;/strong&gt; The installer should reuse the existing Windows EFI System Partition. If it offers to create a &lt;em&gt;new&lt;/em&gt; EFI partition, stop. Creating a second EFI partition is a common source of later GRUB / Windows boot problems.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Swap: The automated installer creates a swapfile by default. Manual setup is only needed if you chose 'Something Else' or are recovering from an interrupted installation (see Step 8).&lt;/em&gt;&lt;/p&gt;


&lt;h2&gt;
  
  
  Step 8: Verify the Dual Boot &amp;amp; Configure Swap (~3 minutes)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Restart the laptop.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; The &lt;strong&gt;GRUB menu&lt;/strong&gt; should appear automatically.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fknql087jr4ntfe8i4rr0.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fknql087jr4ntfe8i4rr0.webp" alt="GNU GRUB 2.12 boot menu listing Linux Mint 22.3 Xfce as the highlighted default entry, Advanced options for Linux Mint 22.3 Xfce, Windows Boot Manager on /dev/sda1, and UEFI Firmware Settings, with the arrow-key help footer." width="799" height="411"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The menu the finished install hands you at power-on: Linux Mint and Windows Boot Manager both listed, Mint as the default. Arrow down and Enter reaches Windows; the /dev/sda1 tag names the EFI partition Windows was installed to. Both operating systems, one switch, no USB stick required anymore.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Select &lt;strong&gt;Linux Mint&lt;/strong&gt; → verify it boots to the desktop.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fg0mdv0yxbw8lz67e8zxo.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fg0mdv0yxbw8lz67e8zxo.webp" alt="Linux Mint Welcome window on a fresh install: sidebar with Welcome selected plus First Steps, Documentation, Help and Contribute; body greeting Welcome to your new operating system with a green Let's go button; footer logo reading Linux Mint 22.3 Xfce 64-bit and an unchecked Show this dialog at startup box." width="800" height="547"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The first thing the new system shows after the reboot: a welcome screen, version-locked to 22.3 Xfce 64-bit, with the startup nag left off. Let's go! opens the guided first-run. Nothing here is required — it is the machine saying it is alive and yours.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Restart → select &lt;strong&gt;Windows Boot Manager&lt;/strong&gt; → verify Windows boots.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Verify Swap Configuration:&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Once booted into your new Linux desktop, open a terminal and run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;swapon --show
free -h
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If no swap is listed, create it manually:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sudo fallocate -l 4G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
grep -q &lt;span class="s1"&gt;'/swapfile'&lt;/span&gt; /etc/fstab &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"Already present"&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s1"&gt;'/swapfile none swap sw 0 0'&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; sudo tee -a /etc/fstab
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;▶ Post-installation checklist&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Task&lt;/th&gt;
&lt;th&gt;How&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Run updates&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Open Update Manager in Linux Mint and install available updates&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Check disk layout&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Open Disks or run &lt;code&gt;lsblk&lt;/code&gt; in the terminal&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Test reboot&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Restart a few times to confirm GRUB appears consistently&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Run neofetch&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Open a terminal and type &lt;code&gt;neofetch&lt;/code&gt; (or &lt;code&gt;fastfetch&lt;/code&gt;) to see your system specs&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdc7548di0dq5z3muk445.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdc7548di0dq5z3muk445.webp" alt="Update Manager window with a blue banner asking Do you want to switch to a local mirror, noting local mirrors are usually faster than packages.linuxmint.com, offering Yes and No; a package list with Upgrade boxes ticked and New Version strings; status bar reading 186 updates selected (566 MB)." width="800" height="577"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The Run updates row, executed: 186 updates, 566 MB, queued and selected. The mirror prompt at the top is the same latency lever the download step relied on — a local mirror is what keeps a flaky link from stalling the update run.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fl9db5e88rdnlv0tfl98f.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fl9db5e88rdnlv0tfl98f.webp" alt="neofetch on the demo machine: asus@asus-VivoBook-ASUS-Laptop-X509UA, Linux Mint 22.3 x86_64, kernel 6.14.0-37-generic, Intel i3-7020U, 701MiB of 3794MiB used, 1280x720, Xfce 4.18, 1907 packages." width="800" height="597"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The Run neofetch row, executed: the starting XI's own receipt — three minutes into its first Mint session, the ASUS that ran every step of this guide idles at 701 MiB on 4 GB. The weaker box's numbers live in the narrative series; this frame is the demo machine testifying for itself.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;One more validation, from the bench: this same guide was also run end-to-end on the HP 15-bs0xx — the Pentium box that barely runs Windows and stars in the four-part narrative series. Its finish line:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faavk3h1rz8rn2pwr5jkn.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faavk3h1rz8rn2pwr5jkn.webp" alt="king@king-HP-Laptop-15-bs0xx: neofetch shows Linux Mint 22.3 Xfce on an Intel Pentium N3710 with 692MiB of 7840MiB used, and lsblk shows sda5 mounted at / beside intact Windows partitions." width="800" height="352"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The substitute's call-up: the weaker HP, dual-booted by this same guide, Windows partitions untouched. Its full story and its own benchmarks live in the narrative series; here it only testifies that the guide generalizes past the demo box.&lt;/em&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 9: Re-enable BitLocker (Optional, ~2 minutes)
&lt;/h2&gt;

&lt;p&gt;You suspended BitLocker with &lt;code&gt;-RebootCount 0&lt;/code&gt; in Step 0. Protection stays off until you turn it back on manually. Do this only after you have booted into Windows through GRUB at least once and confirmed both systems work.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; Boot into &lt;strong&gt;Windows&lt;/strong&gt; through the GRUB menu.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; Open &lt;strong&gt;PowerShell as Administrator&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; Resume protection:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;manage&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;bde&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;protectors&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;enable&lt;/span&gt; &lt;span class="no"&gt;C&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; Verify:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;manage&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;bde&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;status&lt;/span&gt; &lt;span class="no"&gt;C&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;em&gt;(Protection Status should say "On").&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;⚠️ &lt;strong&gt;CRITICAL WARNING:&lt;/strong&gt; The first time you reboot into Windows after re-enabling BitLocker, the TPM may measure the GRUB bootloader and trigger the recovery screen. Have your 48-digit recovery key ready to type in manually. Once entered, subsequent boots should be seamless. If you never had BitLocker enabled, skip this step.&lt;/p&gt;




&lt;h2&gt;
  
  
  Performance Comparison
&lt;/h2&gt;

&lt;p&gt;These measurements were taken at the 3-minute mark after a fresh boot with no applications open, on the ASUS test machine. The HP from the narrative series is benchmarked separately, in the series.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;Windows 11&lt;/th&gt;
&lt;th&gt;Linux Mint XFCE&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Idle RAM&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;2.1 / 3.9GB&lt;/td&gt;
&lt;td&gt;923.3MiB / 3.7GiB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Boot Time (average)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;~28.6s&lt;/td&gt;
&lt;td&gt;~25.6s&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;A note on measurement conditions:&lt;/strong&gt; Boot times were measured with a stopwatch across three runs per OS. OS memory accounting differs, but based on the displayed idle usage, Linux showed roughly 1GB more physical-memory headroom under these test conditions.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;On constrained hardware, that extra gigabyte prevents aggressive background swapping. Linux Mint (XFCE baseline) consumes roughly half the idle RAM of Windows 11. Cinnamon and MATE will use slightly more RAM at idle, but the installation workflow and the performance benefits over Windows remain identical.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkcn3xv64szlh38ekk25a.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkcn3xv64szlh38ekk25a.webp" alt="Windows 11 Task Manager Performance tab at up time 0:00:03:06: CPU 1% at 1.18 GHz on an Intel i3-7020U, Memory 2.1/3.9 GB (54%), 151 processes, both disks and the GPU idle; taskbar clock reads 05/10/2026." width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The demo machine at rest under Windows 11: three minutes in, over half of its usable RAM is already spoken for — 54% — with the CPU idling at 1%. This is the baseline the next figure is measured against: same box, same idle mark, nothing else running.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F063f0n5apxg0ejo0ucrk.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F063f0n5apxg0ejo0ucrk.webp" alt="Xfce Task Manager on Linux Mint at the same idle mark: CPU 7%, 212 processes, Memory 24% (923.3 MiB of 3.7 GiB), with the per-process RSS list showing each daemon's individual footprint." width="800" height="407"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Same machine, same three-minute mark, Mint XFCE: 923 MiB of 3.7 GiB — 24%, less than half of Windows' 54%. And note the process count, 212 against 151: more daemons, far less weight. Process count is not memory footprint; the RSS column is where you check each service's share for yourself.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F20yzb9it7tgjl2ijgyk4.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F20yzb9it7tgjl2ijgyk4.webp" alt="Terminal on asus@asus-VivoBook-ASUS-Laptop-X509UA running systemd-analyze: startup finished in 2.506s firmware + 6.152s loader + 2.617s kernel + 13.862s userspace = 25.139s; graphical.target reached after 13.804s in userspace." width="800" height="535"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;One representative boot, itemized: firmware 2.5s, loader 6.2s, kernel 2.6s, userspace 13.9s — 25.1s to a graphical session. The table's ~25.6s is the three-run stopwatch average; this frame is the single run that shows where those seconds actually live, reproducible by any reader with one command.&lt;/em&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Troubleshooting Quick Reference
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Problem&lt;/th&gt;
&lt;th&gt;Likely Cause&lt;/th&gt;
&lt;th&gt;Fix&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Boot device absent from boot menu&lt;/td&gt;
&lt;td&gt;Port/reader incompatibility, firmware USB boot disabled&lt;/td&gt;
&lt;td&gt;Try another USB port, use a dedicated reader, enable USB boot in BIOS&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Device visible but boot rejected&lt;/td&gt;
&lt;td&gt;Secure Boot verification, incompatible boot mode&lt;/td&gt;
&lt;td&gt;Follow MOK enrollment (Step 5) or Disable Secure Boot&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Frozen logo during boot&lt;/td&gt;
&lt;td&gt;Graphics incompatibility&lt;/td&gt;
&lt;td&gt;Try compatibility mode from GRUB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Windows partition locked&lt;/td&gt;
&lt;td&gt;Fast Startup still enabled&lt;/td&gt;
&lt;td&gt;Disable Fast Startup in Power Options&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;BitLocker recovery screen&lt;/td&gt;
&lt;td&gt;TPM detected hardware change&lt;/td&gt;
&lt;td&gt;Enter your backed-up 48-digit recovery key&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Tiny shrink space&lt;/td&gt;
&lt;td&gt;Unmovable system files&lt;/td&gt;
&lt;td&gt;Disable pagefile, hibernation, and System Protection (Step 2)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;ISO boot fails&lt;/td&gt;
&lt;td&gt;Corrupted download&lt;/td&gt;
&lt;td&gt;Re-verify SHA256 checksum and re-download&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GRUB missing after install&lt;/td&gt;
&lt;td&gt;Boot order reset or Windows Update&lt;/td&gt;
&lt;td&gt;In UEFI firmware, move the &lt;code&gt;ubuntu&lt;/code&gt; or &lt;code&gt;Linux Mint&lt;/code&gt; EFI entry above Windows Boot Manager. Do not switch to Legacy/CSM.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Laptop boots to live environment&lt;/td&gt;
&lt;td&gt;Boot media not removed&lt;/td&gt;
&lt;td&gt;Shut down, remove USB/SD, restart&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;ext4 creation or mkfs fails with I/O error&lt;/td&gt;
&lt;td&gt;Drive fault or geometry conflict&lt;/td&gt;
&lt;td&gt;Stop; back up; see Incident Report
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  Incident Report: Installation Failure and I/O Recovery on the ASUS VivoBook {#incident-report-asus-io}
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;⚠️ NOTE FOR BEGINNERS:&lt;/strong&gt; This section documents an edge-case recovery from one specific machine. If your installation completes without errors, you don't need to read this. Bookmark it in case you face similar issues later.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;This section is not a standard procedure. This is an incident report from the ASUS test machine.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This is a field report from one machine, not a diagnosis of Ubiquity, parted, ext4, or SSDs in general. Everything below is what I observed, what I ran, and what changed as a result. Where I inferred, I say so. Where I don't know, I say that too.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Happened
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; &lt;strong&gt;Initial Setup:&lt;/strong&gt; I shrunk Windows to 87.8 GiB, leaving an unallocated window of ~150 GiB (sectors 184,303,616–498,878,463) for Linux Mint.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; &lt;strong&gt;Automated Failure:&lt;/strong&gt; Selecting "Install alongside Windows Boot Manager" halted the installer at the filesystem-creation step. The exact dialog: &lt;em&gt;"Failed to create a file system — The ext4 file system creation in partition #5 of SCSI1 (0,0,0) (sda) failed."&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fb4jqwo0dzfs3a40pjbwi.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fb4jqwo0dzfs3a40pjbwi.webp" alt="Ubiquity installer on the Where are you? timezone screen with Lagos entered, overlaid by the failure dialog: Failed to create a file system — The ext4 file system creation in partition #5 of SCSI1 (0,0,0) (sda) failed." width="800" height="617"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The trigger, verbatim: ext4 creation failed on partition #5, mid-install, over the timezone screen. Everything in this report starts at this dialog.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; &lt;strong&gt;The Table the Installer Left:&lt;/strong&gt; In GParted (live session), &lt;code&gt;/dev/sda5&lt;/code&gt; existed at its full 150.00 GiB with filesystem type "unknown" and a warning flag. &lt;strong&gt;No truncation existed at this stage.&lt;/strong&gt; Every truncated geometry in this report was created later, by me, during recovery.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; &lt;strong&gt;Manual ext4 Creation Attempts:&lt;/strong&gt; I attempted filesystem creation by hand from the live session. Four attempts died at the identical final line — &lt;code&gt;Writing superblocks and filesystem accounting information: mkfs.ext4: Input/output error while writing out and closing file system&lt;/code&gt; — across three different geometries, with and without discard. One attempt completed clean.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;#&lt;/th&gt;
&lt;th&gt;Command&lt;/th&gt;
&lt;th&gt;Span&lt;/th&gt;
&lt;th&gt;Flags&lt;/th&gt;
&lt;th&gt;Outcome&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Ubiquity (automated)&lt;/td&gt;
&lt;td&gt;~150 GiB window&lt;/td&gt;
&lt;td&gt;installer defaults&lt;/td&gt;
&lt;td&gt;Failed at ext4 creation (dialog above)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;&lt;code&gt;mkfs.ext4 -F&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;94GB→100% (150 GiB)&lt;/td&gt;
&lt;td&gt;default&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;Discarding device blocks: failed - Input/output error&lt;/code&gt;, then died at final superblock write-out&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;&lt;code&gt;mkfs.ext4 -F -E nodiscard&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;same&lt;/td&gt;
&lt;td&gt;nodiscard&lt;/td&gt;
&lt;td&gt;Died at the identical final line&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;&lt;code&gt;mkfs.ext4 -F -E nodiscard&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;94GB→248GB (143 GiB)&lt;/td&gt;
&lt;td&gt;nodiscard&lt;/td&gt;
&lt;td&gt;Died at the identical final line&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;&lt;code&gt;mkfs.ext4 -F -O ^has_journal -E nodiscard&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;100GB→200GB (93.1 GiB)&lt;/td&gt;
&lt;td&gt;nodiscard, journal-less&lt;/td&gt;
&lt;td&gt;Completed without error (24,414,208 blocks)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Observed pattern, stated as observation only:&lt;/strong&gt; every failed creation spanned beyond the 200 GB decimal mark; the single clean creation did not. The clean creation was also the only journal-less one, so end-offset and journal presence are confounded in the data. I did not separate those variables, and I am not claiming to.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj46rrklq8p9xhodb0ywm.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj46rrklq8p9xhodb0ywm.webp" alt="Three stacked live-session terminals: mkfs.ext4 -F on the 94GB-100% span failing at discard then at the final superblock write; the same span with -E nodiscard dying at the identical line; and the 94GB-248GB nodiscard attempt dying there too — three different filesystem UUIDs, one identical death." width="575" height="1307"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The three identical deaths, table rows 2 through 4 on screen: different spans, different flags, three distinct UUIDs — and every one of them dying at the same final superblock write. The first panel even shows the discard failure that preceded them. Same last line, three times, is not a coincidence; it is a pattern.&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  The Geometry Phase I Caused
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;This part was my error, and the report says so plainly.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;While attempting to resize partitions, I ran &lt;code&gt;parted /dev/sda resizepart 5 100GB&lt;/code&gt; and later &lt;code&gt;resizepart 5 95GiB&lt;/code&gt;, believing the argument was a size. &lt;strong&gt;&lt;code&gt;parted resizepart&lt;/code&gt; takes the partition's END position, not a size.&lt;/strong&gt; On a partition starting at the ~100 GB mark, "100GB" as an end position leaves roughly 884 sectors. The results, captured live:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Partition collapsed to &lt;strong&gt;110 4k blocks&lt;/strong&gt;; &lt;code&gt;resize2fs&lt;/code&gt; refused with "The containing partition (or device) is only 110 (4k) blocks."&lt;/li&gt;
&lt;li&gt;A later &lt;code&gt;resizepart 5 95GiB&lt;/code&gt; produced a partition of &lt;strong&gt;489,728 blocks (1.9 GiB)&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F56pkds1g1rtl1ozokrbh.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F56pkds1g1rtl1ozokrbh.webp" alt="fdisk -l on the collapsed disk: sda1 EFI 100M, sda2 Microsoft reserved 16M, sda3 Windows 87.8G, sda4 recovery 604M, and sda5 Linux filesystem at 1.9G spanning sectors 195311616-199229439; Partition table entries are not in disk order; opening fdisk prints the red warning that the disk is currently in use and repartitioning is probably a bad idea." width="634" height="451"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The collapsed table, read straight off the disk: partition 5 at 1.9 GiB — 3,917,824 sectors, which times 512 is exactly the 2,005,925,888 bytes blockdev reported two figures earlier — entries out of disk order, Windows partitions untouched beside the wreckage, and fdisk's red warning that the disk is in use. This is the state the rewrite started from.&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;e2fsck&lt;/code&gt; then reported the superblock/device mismatch: &lt;em&gt;"The filesystem size... is 20971520 blocks / The physical size of the device is 489728 blocks... Either the superblock or the partition table is likely to be corrupt!"&lt;/em&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsg96hzrfbum78r0jmabf.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsg96hzrfbum78r0jmabf.webp" alt="Live-session terminal: e2fsck -b 32768 -y /dev/sda5 deleting an invalid journal, then reporting the filesystem size as 20971520 blocks against a physical device of 489728 blocks; blockdev --getsize64 returns 2005925888 bytes — exactly 489728 4k blocks." width="800" height="567"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The mismatch, with its arithmetic proof: the superblock claims 20,971,520 blocks, the device holds 489,728 — and blockdev confirms it in bytes, 2,005,925,888, which is 489,728 × 4096. Even the backup-superblock repair path ran into the same wall.&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;One collapse was performed from inside the booted installation, on the partition mounted as &lt;code&gt;/&lt;/code&gt;. After it, even running tools failed: &lt;code&gt;sudo: unable to execute /usr/sbin/e2fsck: Input/output error&lt;/code&gt;. &lt;strong&gt;Do not repair a partition table from an operating system booted off that table.&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fc9ipze4bdkh5igjzdwz5.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fc9ipze4bdkh5igjzdwz5.webp" alt="Four-panel diagnostic sweep: GParted showing the 150 GiB partition typed unknown with a warning flag beside the 87.77 GiB Windows partition and a 1.11 MiB unallocated sliver; a resizepart 5 100% attempt whose resize2fs dies with an Input/output error; a live-session e2fsck -f -y scroll deleting the journal and reporting the 20971520-versus-489728 mismatch; and the booted install where even sudo e2fsck -n fails with Unable to execute /usr/sbin/e2fsck: Input/output error." width="800" height="603"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Every probe, same verdict: the table the installer left — 150 GiB typed unknown, a 1.11 MiB sliver — then resize attempts dying on I/O errors from the live session and from the booted system alike, until the booted system could not even run its own repair tool. This sweep is the evidence behind the report's hardest lesson: never repair a partition table from an OS booted off it.&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  The Recovery Chain That Worked
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Warning: The following steps are high-risk. I ran them from a live session, as a last resort. They are not guaranteed to work and can destroy data.&lt;/strong&gt; These steps recovered this specific drive configuration. Your hardware may differ. If you're not comfortable with terminal-based partitioning, do not attempt this. Replace the SSD instead.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; &lt;strong&gt;Rewrote the partition table with fdisk:&lt;/strong&gt; deleted &lt;code&gt;/dev/sda5&lt;/code&gt; and recreated it explicitly at sectors &lt;strong&gt;195311616 → 385311616 (90.6 GiB)&lt;/strong&gt;, declining signature removal (&lt;code&gt;N&lt;/code&gt;) to preserve ext4 metadata, then &lt;code&gt;w&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; &lt;strong&gt;Reconciled filesystem metadata:&lt;/strong&gt; &lt;code&gt;sudo e2fsck -b 32768 -y /dev/sda5&lt;/code&gt;. &lt;em&gt;(Note: On this specific filesystem, backup superblock 32768 worked. On other drives, use &lt;code&gt;sudo mke2fs -n /dev/sdXN&lt;/code&gt; to list valid backup superblock locations without formatting).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; &lt;strong&gt;Expanded the filesystem:&lt;/strong&gt; &lt;code&gt;sudo resize2fs /dev/sda5&lt;/code&gt; grew ext4 to &lt;strong&gt;23,750,000 4k blocks&lt;/strong&gt;, exactly matching the new partition.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; &lt;strong&gt;Verified:&lt;/strong&gt; &lt;code&gt;sudo e2fsck -f -y /dev/sda5&lt;/code&gt; passed clean.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0p7n7f8rsogiyekgao39.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0p7n7f8rsogiyekgao39.webp" alt="Four-panel recovery chain: the journal-less mkfs on the 100GB-200GB span ending in Writing superblocks done; the fdisk rewrite creating partition 5 at 90.6 GiB with the ext4-signature warning answered N; then two e2fsck -b 32768 passes fixing orphaned inodes, block bitmaps, and group counts, ending FILE SYSTEM WAS MODIFIED." width="800" height="603"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The chain that worked, mid-work: the single clean journal-less creation, the fdisk rewrite that kept the ext4 signature by answering N, and the backup-superblock fsck rebuilding group metadata count by count. Every panel here ends closer to alive than the last — the opposite of the mkfs collage above.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frcti3raouyen25dxl2se.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frcti3raouyen25dxl2se.webp" alt="Terminal: the backup-superblock e2fsck closing with FILE SYSTEM WAS MODIFIED at 2395500/20971520 blocks; resize2fs growing /dev/sda5 to 23750000 (4k) blocks; then a final e2fsck -f -y running all five passes with no Fix prompts, ending 482657/5939200 files and 2439190/23750000 blocks." width="800" height="561"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Resolution, in three movements: the repair pass closes with the filesystem modified at its old size; resize2fs grows it to exactly 23,750,000 blocks; and the final forced e2fsck runs all five passes without asking a single question — the first check in this entire report with nothing left to answer yes to.&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  The Outcome &amp;amp; What I Did Not Establish
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Current Status:&lt;/strong&gt; The system boots and functions normally. The final filesystem spans sectors 195,311,616–385,311,616 and has been stable since.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unknown Root Cause:&lt;/strong&gt; The root cause of the raw I/O failures is unproven. Candidates visible in the data — writes beyond the ~200 GB decimal offset, journal presence at mkfs time, underlying media fault — are confounded. &lt;strong&gt;No &lt;code&gt;smartctl&lt;/code&gt; output and no syslog/dmesg excerpt were captured during the incident.&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Counter-evidence:&lt;/strong&gt; The final 90.6 GiB filesystem lives entirely beyond the originally suspected offset and runs stable, weakening a simple bad-sector story.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Advice for Readers
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1.&lt;/strong&gt; &lt;strong&gt;Stop Immediately:&lt;/strong&gt; Do not re-run automated installers repeatedly over failed operations.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2.&lt;/strong&gt; &lt;strong&gt;Backup Everything:&lt;/strong&gt; Secure critical data to external storage or cloud before any block-level work.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.&lt;/strong&gt; &lt;strong&gt;Work From Live Media Only:&lt;/strong&gt; Never modify a partition table from an OS booted off that table.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4.&lt;/strong&gt; &lt;strong&gt;Know Your Tools' Semantics:&lt;/strong&gt; &lt;code&gt;parted resizepart&lt;/code&gt; takes an end position, not a size.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5.&lt;/strong&gt; &lt;strong&gt;Change One Variable at a Time:&lt;/strong&gt; When mkfs or resize2fs fails, alter a single parameter per attempt and record every output.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6.&lt;/strong&gt; &lt;strong&gt;Expect Hardware Replacement:&lt;/strong&gt; Persistent raw I/O errors may indicate failing media. Recovery is sometimes possible; replacement is often the safer long-term answer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;7.&lt;/strong&gt; &lt;strong&gt;Dual-Boot Isn't Always Clean:&lt;/strong&gt; Automated tools work most of the time. Hardware variables exist. This report exists so you know both things at once: recovery is possible, and humility about root causes is not weakness.&lt;/p&gt;




&lt;h2&gt;
  
  
  Resources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://linuxmint.com/download.php" rel="noopener noreferrer"&gt;Linux Mint Official Download&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://linuxmint.com/verify.php" rel="noopener noreferrer"&gt;Linux Mint SHA256 Checksums&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.qbittorrent.org/" rel="noopener noreferrer"&gt;qBittorrent Official Site&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.ventoy.net/" rel="noopener noreferrer"&gt;Ventoy Official Site&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ventoy/Ventoy/releases" rel="noopener noreferrer"&gt;Ventoy GitHub Releases&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;— King Anthony | kinganthony.tech | &lt;a href="mailto:hello@kinganthony.tech"&gt;hello@kinganthony.tech&lt;/a&gt;&lt;br&gt;&lt;br&gt;
If this guide saved you from a disaster, share it. If you found something I didn't cover, reach out. I'm still learning.&lt;br&gt;&lt;br&gt;
Next in this infrastructure series: Automating M365 tenant onboarding with PowerShell — no GUI required.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Installed and running?&lt;/strong&gt; Continue to the first-hour setup: &lt;a href="https://kinganthony.tech/blog/linux-mint-first-hour-after-install/" rel="noopener noreferrer"&gt;Linux Mint: The First Hour After Install&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Want the full story behind every step?&lt;/strong&gt; Read the companion narrative series: &lt;a href="https://kinganthony.tech/blog/dual-booting-linux-mint-xfce-part-0/" rel="noopener noreferrer"&gt;Dual Booting Linux on a Machine That Barely Runs Windows&lt;/a&gt;&lt;/p&gt;

</description>
      <category>linux</category>
      <category>linuxmint</category>
      <category>tutorial</category>
      <category>dualboot</category>
    </item>
  </channel>
</rss>
