<?xml version="1.0" encoding="utf-8" standalone="yes"?><?xml-stylesheet type="text/css" href="https://techfuelhq.com/feed.css"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>TechFuel HQ</title><link>https://techfuelhq.com/</link><description>Recent content on TechFuel HQ</description><generator>Hugo</generator><language>en-us</language><managingEditor>contact@techfuelhq.com (LK Wood IV)</managingEditor><lastBuildDate>Mon, 16 Nov 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://techfuelhq.com/index.xml" rel="self" type="application/rss+xml"/><atom:link href="https://pubsubhubbub.appspot.com/" rel="hub"/><item><title>How to Enable XMP or EXPO and Prove It's Stable (2026)</title><link>https://techfuelhq.com/tutorials/how-to-enable-xmp-expo-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/how-to-enable-xmp-expo-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;p>You paid for 6000 MT/s and your machine is running at 4800. Nothing is broken. The kit is sitting on its JEDEC default speed, which is the safe configuration every board can boot, and the rated number on the box is an overclock profile the module vendor validated and stored in the DIMM&amp;rsquo;s SPD chip. Corsair publishes both numbers side by side for its Vengeance 6000 CL30 kit: 4800MHz at CL40 and 1.1V by default, 6000 MT/s at CL30 and 1.40V on the tested profile. G.Skill lists the same split.&lt;/p>
&lt;p>Turning the profile on takes about ninety seconds in UEFI. Proving the machine is actually stable at that speed takes longer, and it is the half of the job most people skip. Here is the full sequence, including what to do when the board refuses to boot.&lt;/p>
&lt;h2 id="1-why-your-ddr5-kit-boots-at-jedec-speed">1. Why your DDR5 kit boots at JEDEC speed&lt;/h2>
&lt;p>A DDR5 module carries two sets of numbers. The SPD default is what the memory presents to any board with no configuration: a conservative speed, loose timings and 1.1V. The overclock profile is what the vendor tested and certified, and both Intel XMP and AMD EXPO are just standardized containers for it. ASUS describes the job plainly on its support page: the board loads the preset overclock file and DRAM timing from the memory SPD chip.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Specification&lt;/th>
&lt;th scope="col">Corsair Vengeance CMK32GX5M2B6000Z30&lt;/th>
&lt;th scope="col">G.Skill Flare X5 F5-6000J3038F16GX2-FX5&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Specification">Default (SPD) speed&lt;/td>
&lt;td data-label="Corsair Vengeance CMK32GX5M2B6000Z30">4800MHz&lt;/td>
&lt;td data-label="G.Skill Flare X5 F5-6000J3038F16GX2-FX5">4800 MT/s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Default SPD latency&lt;/td>
&lt;td data-label="Corsair Vengeance CMK32GX5M2B6000Z30">CL40&lt;/td>
&lt;td data-label="G.Skill Flare X5 F5-6000J3038F16GX2-FX5">not published as a CL value&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Default SPD voltage&lt;/td>
&lt;td data-label="Corsair Vengeance CMK32GX5M2B6000Z30">1.1V&lt;/td>
&lt;td data-label="G.Skill Flare X5 F5-6000J3038F16GX2-FX5">1.10V&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Tested profile speed&lt;/td>
&lt;td data-label="Corsair Vengeance CMK32GX5M2B6000Z30">6000 MT/s&lt;/td>
&lt;td data-label="G.Skill Flare X5 F5-6000J3038F16GX2-FX5">6000 MT/s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Tested profile timings&lt;/td>
&lt;td data-label="Corsair Vengeance CMK32GX5M2B6000Z30">CL30&lt;/td>
&lt;td data-label="G.Skill Flare X5 F5-6000J3038F16GX2-FX5">30-38-38-96&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Tested profile voltage&lt;/td>
&lt;td data-label="Corsair Vengeance CMK32GX5M2B6000Z30">1.40V&lt;/td>
&lt;td data-label="G.Skill Flare X5 F5-6000J3038F16GX2-FX5">1.35V&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Profile standard&lt;/td>
&lt;td data-label="Corsair Vengeance CMK32GX5M2B6000Z30">AMD EXPO and Intel XMP&lt;/td>
&lt;td data-label="G.Skill Flare X5 F5-6000J3038F16GX2-FX5">Intel XMP 3.0 and AMD EXPO&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Those two kits are not slow hardware. They are hardware waiting for a setting. AMD&amp;rsquo;s EXPO page describes the profiles as a way to get easy DDR5 overclocking on socket AM5 with Ryzen-optimized settings, which is the same bargain Intel&amp;rsquo;s XMP makes on its platforms: one menu choice instead of hand-entering timings.&lt;/p>
&lt;p>One caution belongs up front, because AMD is explicit about it. AMD&amp;rsquo;s own footnotes state that overclocking processors and memory outside AMD&amp;rsquo;s published specifications, including altering memory timing or voltage, will void any applicable AMD product warranty, even when it is enabled through AMD hardware or software. Enabling EXPO is that kind of change. If the machine has to stay inside a support contract, that is a decision to make deliberately.&lt;/p>
&lt;h2 id="2-step-1-confirm-the-rated-profile-and-the-slot-pair">2. Step 1: Confirm the rated profile and the slot pair&lt;/h2>
&lt;p>Before you open UEFI, establish three facts.&lt;/p>
&lt;p>&lt;strong>The exact kit.&lt;/strong> Read the part number from the module label or from the memory details in Windows, then look it up on the vendor&amp;rsquo;s own specification page. You want the tested speed, the tested primary timings and the tested voltage. If the page lists only an Intel XMP 3.0 profile and your board is AM5, the board may still accept it as DOCP, but you are now outside the kit&amp;rsquo;s documented path.&lt;/p>
&lt;p>&lt;strong>Whether the pair is a matched kit.&lt;/strong> G.Skill&amp;rsquo;s specification page for the Flare X5 states it directly: do not mix memory kits, because kits are sold as matched sets designed to run together. Two separately purchased pairs are not the same thing as one four-module kit, even when the part numbers match.&lt;/p>
&lt;p>&lt;strong>The slot pair.&lt;/strong> ASUS&amp;rsquo;s failure checklist starts with using modules from its qualified vendors list, keeping a kit together rather than mixing modules, and testing a single module in the recommended slot. That is the practical version of the rule: two DIMMs in the pair your manual calls out, not two in whichever slots were easiest to reach. The &lt;a href="https://techfuelhq.com/articles/ddr5-ram-buying-guide-2025/">DDR5 buying guide&lt;/a> covers why pairs behave this way, and the live &lt;a href="https://techfuelhq.com/data/ram-price-index/">RAM price index&lt;/a> is the place to check kit pricing before buying a second pair you do not need.&lt;/p>
&lt;p>AMD also publishes a tested-memory list that flags each kit as EXPO-certified, certified with Ultra Low Latency, or merely XMP-compatible. Worth checking when a profile keeps failing.&lt;/p>
&lt;h2 id="3-step-2-load-xmp-or-expo-in-uefi">3. Step 2: Load XMP or EXPO in UEFI&lt;/h2>
&lt;p>The menu sequence below is ASUS&amp;rsquo;s documented path, because that is the vendor documentation I can point you at line by line. On MSI, Gigabyte and ASRock boards the same toggle lives in that vendor&amp;rsquo;s overclocking or tweaker section under its own label, so follow your board manual rather than assuming the ASUS wording appears on your screen.&lt;/p>
&lt;ol>
&lt;li>Restart the machine and tap &lt;code>Del&lt;/code> or &lt;code>F2&lt;/code> during POST to enter BIOS setup. Most boards land in an EZ Mode summary screen.&lt;/li>
&lt;li>Press &lt;code>F7&lt;/code> to switch to Advanced Mode. If the board boots straight into Advanced Mode, skip this.&lt;/li>
&lt;li>Open the &lt;strong>Ai Tweaker&lt;/strong> page. Some ROG boards label this tab &lt;strong>Extreme Tweaker&lt;/strong>.&lt;/li>
&lt;li>Select &lt;strong>Ai Overclock Tuner&lt;/strong>. On an Intel 600-series or newer board with an XMP kit, choose &lt;strong>XMP I&lt;/strong> or &lt;strong>XMP II&lt;/strong>. On an AMD AM5 board with an EXPO kit, choose &lt;strong>EXPO I&lt;/strong> or &lt;strong>EXPO II&lt;/strong>. On an AMD board with an XMP kit, ASUS uses &lt;strong>DOCP&lt;/strong> to apply the XMP timings.&lt;/li>
&lt;li>Press &lt;code>F10&lt;/code> and confirm to save and exit. The board reboots on its own.&lt;/li>
&lt;/ol>
&lt;p>Two checks are worth making before you leave UEFI. The EZ Mode memory information panel shows the DRAM frequency the board intends to run, and &lt;strong>Tool → SPD Information&lt;/strong> shows whether the installed module reports an XMP profile or an EXPO profile at all. A kit with no visible profile is a kit that will not accept one.&lt;/p>
&lt;p>What changes after the reboot: the board retrains memory against the new timings. That first POST after enabling a profile routinely takes longer than a normal boot, sometimes with a dark screen or a pause on the memory LED, and cutting power during that window is how people turn a two-minute setting into a CMOS clear. Let it finish. Once Windows loads, open Task Manager, go to &lt;strong>Performance → Memory&lt;/strong>, and read the &lt;strong>Speed&lt;/strong> figure. ASUS documents exactly this check. If it says 6000 MT/s, the profile is live; if it still says 4800, the profile did not take, and the next section is for you.&lt;/p>
&lt;h2 id="4-step-3-recover-a-failed-boot-without-guessing">4. Step 3: Recover a failed boot without guessing&lt;/h2>
&lt;p>A board that cannot train the profile generally does not sit there blinking at you forever; most fall back to defaults and boot. Do not read a successful desktop as proof the profile applied. Check the speed.&lt;/p>
&lt;p>If the machine genuinely will not come back, clear CMOS. ASUS documents three methods on its boards, and the same three exist in some form on every consumer board:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Method&lt;/th>
&lt;th scope="col">What you do&lt;/th>
&lt;th scope="col">Notes&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Method">Clear CMOS button&lt;/td>
&lt;td data-label="What you do">Power off, unplug the cord, hold the button about 5-10 seconds&lt;/td>
&lt;td data-label="Notes">Present on many mid-range and high-end boards&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Method">CLRTC pins&lt;/td>
&lt;td data-label="What you do">Power off, unplug, short the two pins about 5-10 seconds with a jumper cap or metal object&lt;/td>
&lt;td data-label="Notes">Most common on boards without a button&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Method">CMOS battery&lt;/td>
&lt;td data-label="What you do">Power off, unplug, remove the battery, then clear with the pin or button&lt;/td>
&lt;td data-label="Notes">Needed when the other two are inaccessible&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>After restoring power, the board announces that BIOS settings were reset. Press &lt;code>F1&lt;/code> to enter setup, &lt;code>F5&lt;/code> to load optimized defaults, &lt;code>F10&lt;/code> to save and exit. Your fan curves, boot order and memory profile are all gone at that point, so plan to set them again.&lt;/p>
&lt;p>If the board posts but stays at JEDEC speed after you enabled the profile, work the list in order: confirm the two DIMMs are in the recommended pair, pull one module and try again, check whether the profile is one the kit actually carries, and look at the firmware version. An older BIOS with a stale memory-training routine is a real cause of profiles that refuse to train, and our &lt;a href="https://techfuelhq.com/tutorials/how-to-update-bios-2026/">BIOS update walkthrough&lt;/a> covers how to flash one safely. If the machine never reaches the point of training memory at all, the &lt;a href="https://techfuelhq.com/articles/computer-wont-turn-on-2026/">no-power checklist&lt;/a> and the &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">diagnostic workbench&lt;/a> separate a memory problem from a power or board problem.&lt;/p>
&lt;h2 id="5-step-4-prove-the-profile-is-stable">5. Step 4: Prove the profile is stable&lt;/h2>
&lt;p>A machine that boots and games for an hour is not the same as a machine that stores data correctly. HCI Design&amp;rsquo;s MemTest manual is blunt about the consequence: an unstable system gets worse over time as corrupted data is written to the hard disk. That is the failure mode worth spending an afternoon to avoid, because it looks like a filesystem problem or a bad game install long before it looks like memory.&lt;/p>
&lt;p>Two tools do the job, and I use them for different stages.&lt;/p>
&lt;p>&lt;strong>MemTest86, booted from USB, is the check that counts.&lt;/strong> PassMark&amp;rsquo;s technical documentation lists DDR5 SPD reporting, including kits that carry Intel XMP 3.0 or AMD EXPO profiles, plus per-module error tracking and a running count of uncorrected and corrected errors. Because it runs before any operating system, nothing else is occupying the memory it is testing. I start it, leave it overnight, and treat any error as a failed profile. There is no pass count that turns a reported error into an acceptable one.&lt;/p>
&lt;p>&lt;strong>HCI MemTest, run inside Windows, is the faster sanity check.&lt;/strong> Its manual gives concrete numbers: 100 percent coverage is a very thorough test that catches all but the most intermittent problems, running to 400 percent is what catches the rare ones, and 60 percent of bad RAM is detected after just 10 percent coverage. On a multi-core machine it recommends one instance per core with the RAM divided between them. I use it when I want a quick answer before committing to an overnight run.&lt;/p>
&lt;p>Alongside the memory test, check the two places Windows reports what actually happened:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Task Manager → Performance → Memory → Speed&lt;/strong> should show the rated figure, not 4800.&lt;/li>
&lt;li>&lt;strong>Event Viewer → Windows Logs → System&lt;/strong>, scanned for new WHEA entries after a test run. Microsoft describes WHEA as the architecture Windows uses for hardware error reporting and recovery, so a fresh WHEA entry during a stress run is a signal that something in the platform, not just the memory test, objected.&lt;/li>
&lt;/ul>
&lt;p>A profile that passes an overnight bootable run, shows the rated speed in Windows, and logs no new hardware errors is a profile I will leave enabled. A profile that passes only the quick test gets re-run overnight before I trust it.&lt;/p>
&lt;h2 id="6-xmp-and-expo-are-not-manual-tuning">6. XMP and EXPO are not manual tuning&lt;/h2>
&lt;p>The profile is a starting point the module vendor validated, and it changes a defined set of values: the data rate, the primary timings, and the voltage. On the Corsair kit in the table, that is 1.40V against a 1.1V default; on the G.Skill kit, 1.35V against 1.10V. Everything the profile sets, the vendor tested as a combination.&lt;/p>
&lt;p>Manual tuning is a different activity. You set the voltage yourself, you change the primary timings yourself, and you take on the secondary and tertiary timings and the refresh interval, which the profile leaves to the board&amp;rsquo;s training. That is where enthusiasts find the last few percent, and it is also where a machine that passes a short test starts corrupting files a month later. Motherboard &amp;ldquo;try it&amp;rdquo; presets are not the same thing, because nobody certified them against your specific modules.&lt;/p>
&lt;p>My rule: enable the profile, prove it, and stop there. Manual tuning only makes sense against a specific problem you can measure, and it needs a longer stability proof than the profile does.&lt;/p>
&lt;h2 id="7-when-to-leave-the-profile-at-jedec">7. When to leave the profile at JEDEC&lt;/h2>
&lt;p>Some machines are better off at the default speed, and I would rather say so than pretend every kit should be overclocked.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Four modules or a mixed set.&lt;/strong> Matching the kit matters more than the headline speed. If you need the capacity, buy one larger matched pair instead of adding a second pair.&lt;/li>
&lt;li>&lt;strong>A profile that fails a bootable memory test.&lt;/strong> The gap between 4800 and 6000 is worth less than the files a corrupted write can destroy.&lt;/li>
&lt;li>&lt;strong>A compact build with no airflow over the DIMMs.&lt;/strong> Voltage headroom and module temperature are related, and a sealed small-form-factor case is not the place to discover that.&lt;/li>
&lt;li>&lt;strong>A machine under a support contract.&lt;/strong> AMD&amp;rsquo;s own warranty language treats memory overclocking as outside its published specifications. That decision is yours, not the profile&amp;rsquo;s.&lt;/li>
&lt;/ul>
&lt;p>For everyone else, the sequence is the same: enable the profile, confirm the speed in Task Manager, run the bootable test until it has earned your trust, and check again after every BIOS update, because a flash puts the kit straight back on its default. If you are still choosing a kit, the &lt;a href="https://techfuelhq.com/articles/ddr5-6000-cl30-explained-2026/">DDR5-6000 CL30 explainer&lt;/a> covers why that speed and timing combination became the AM5 default recommendation, and the &lt;a href="https://techfuelhq.com/tools/pc-builder/">PC Builder&lt;/a> will check the kit against the rest of a parts list.&lt;/p></description></item><item><title>How to Clean a PC Without Damaging It (2026 Guide)</title><link>https://techfuelhq.com/tutorials/how-to-clean-pc-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/how-to-clean-pc-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;p>Dust is not cosmetic. It mats the fins, slows the fans that have to push through it, and raises every temperature in the case at once, which is why a machine that ran quiet in January sounds like a leaf blower by July. Cleaning it is a twenty-minute job with a fixed order and a short list of things you must not do.&lt;/p>
&lt;p>The order matters more than the tools. Filters first, because that is where most of the dust is and because you do not want to blow it deeper into the case. Heatsinks and fans second. The area around the power supply third. Anything involving liquid is a separate, much narrower job.&lt;/p>
&lt;h2 id="step-1-power-off-unplug-and-drain-the-rails">Step 1: Power off, unplug, and drain the rails&lt;/h2>
&lt;p>Corsair&amp;rsquo;s guide is specific here: power the PC down and set the power supply switch to the off position before you start. I go one step further out of habit. After the PSU switch is off, I hold the case power button for a few seconds, which discharges the standing voltage on the rails so nothing is live when a fan cable comes loose under my hand.&lt;/p>
&lt;p>Then unplug the machine from the wall. Not because the switch is unreliable, but because a cable you have not touched cannot be knocked back on by someone else in the room.&lt;/p>
&lt;p>Work where dust can land somewhere other than the carpet you sleep on. A garage, a patio, or a well-ventilated room with the machine on a hard surface is fine. The point is that you will be blowing a season&amp;rsquo;s worth of particulate into the air, and you would rather it not settle back into the case you just cleaned.&lt;/p>
&lt;h2 id="step-2-clean-filters-and-mesh-before-anything-inside">Step 2: Clean filters and mesh before anything inside&lt;/h2>
&lt;p>Corsair calls the dust filters the easiest step and the place to start, and it is right for a practical reason: every filter you clear is dust that never reaches a heatsink. Slide them out or pry off the magnetic ones, then clean them with a damp cloth or under running water.&lt;/p>
&lt;p>The one rule that matters is drying them completely before they go back on the case. A damp filter sitting against a metal front panel is a worse idea than a dusty one.&lt;/p>
&lt;p>While the filters are off, look at the intake mesh and the top exhaust mesh if your case has them. They clog the same way and they are the reason a machine can run hot with clean heatsinks. This is also the moment to notice whether the front intake is blocked by a drive cage, a cable bundle, or the desk cabinet the case is pushed into, because no amount of cleaning fixes an intake that has nowhere to draw from.&lt;/p>
&lt;h2 id="step-3-heatsinks-fans-and-the-psu-shroud-area">Step 3: Heatsinks, fans, and the PSU shroud area&lt;/h2>
&lt;p>Open the side panel and work from the top of the case downward, which is what Corsair recommends and what keeps dislodged dust from settling on parts you already cleaned.&lt;/p>
&lt;p>Three techniques carry the whole job:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Hold the fan blades still.&lt;/strong> Corsair&amp;rsquo;s guidance is to hold the fan still while hitting it with compressed air, and both failure modes it prevents are real. A fan spun far past its rated speed loads the bearing, and a motor driven by an outside force acts as a generator, pushing a voltage back at the header instead of drawing current from it. Use a finger or a plastic tool, never a screwdriver.&lt;/li>
&lt;li>&lt;strong>Use short bursts, and hold the can upright.&lt;/strong> Corsair specifies an upright canister and short bursts. Upright keeps the liquid propellant in the can instead of spotting the PCB, and short bursts keep you from parking a jet of cold propellant on one component.&lt;/li>
&lt;li>&lt;strong>Keep the nozzle back.&lt;/strong> You want moving air, not a pressure washer. Blasting a heatsink at contact distance drives dust into the fin stack and can knock a fan connector or a jumper loose. Back the nozzle off until you can see the dust leaving rather than feel the jet landing.&lt;/li>
&lt;/ol>
&lt;p>Work the CPU cooler fins, then the GPU cooler and its fans, then the case fans, then the nooks around the drive bays. On the motherboard and the RAM, Corsair&amp;rsquo;s caution is worth following exactly: short bursts only, and no brush on those parts, because a brush catches on a capacitor or a latch and takes it with it. For the fan blades themselves, Corsair&amp;rsquo;s fan guide suggests wiping them with a clean microfiber cloth first, then using cotton swabs with a small amount of isopropyl alcohol for the gap between the blades and the inner frame, and finishing with compressed air for the loose dust that is left.&lt;/p>
&lt;p>The power supply gets air, not disassembly. Corsair lists the PSU as something you can clean with compressed air. That means blowing through the fan grille and the vents from outside the unit. Do not open a power supply to clean it; the capacitors hold a charge after the unit is unplugged, and there is nothing inside that user cleaning improves.&lt;/p>
&lt;p>If the machine sits in a case with a PSU shroud, clean the shroud&amp;rsquo;s vents and the floor filter under it. That is where the intakes for the power supply and often the bottom case fans live, and it is the area people forget because it is at floor level and out of sight.&lt;/p>
&lt;h2 id="step-4-isopropyl-alcohol-belongs-on-a-cloth-not-the-board">Step 4: Isopropyl alcohol belongs on a cloth, not the board&lt;/h2>
&lt;p>Isopropyl alcohol has exactly one job in a PC: removing thermal paste from a CPU heat spreader and a cooler cold plate. Corsair&amp;rsquo;s thermal paste instructions say to clean both surfaces with a paper towel lightly moistened with isopropyl alcohol before applying new paste. Damp, not wet. The cloth does the work.&lt;/p>
&lt;p>The concentration is where vendor guidance stops agreeing with itself. Corsair specifies isopropyl alcohol without naming a percentage, and cooler and paste makers publish their own wording, which does not always match. So I will not give you a number that no manufacturer in front of me printed. Follow the instructions that came with your cooler or your paste, and if they conflict, follow the cooler&amp;rsquo;s, because it is the part with a warranty on the surface you are wiping.&lt;/p>
&lt;p>What alcohol is not for: the motherboard, the GPU board, connectors, fan hubs, or anything you would describe as &amp;ldquo;wiping down.&amp;rdquo; Do not pour it on the board, do not spray it at the board, and do not use it to chase dust into a socket. Alcohol on a cotton swab for a fan&amp;rsquo;s inner frame, as Corsair&amp;rsquo;s fan guide describes, is a different and much smaller operation than wetting down a PCB.&lt;/p>
&lt;h2 id="what-not-to-do-and-why">What not to do, and why&lt;/h2>
&lt;p>Most cleaning damage is not subtle. It is a specific mistake that seemed reasonable at the time.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Do not&lt;/th>
&lt;th scope="col">Why&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Do not">Put a vacuum nozzle on the board&lt;/td>
&lt;td data-label="Why">Suction tools generate static, and a plastic nozzle dragged across components is the wrong combination to introduce into a live-adjacent machine&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Do not">Use water inside the case&lt;/td>
&lt;td data-label="Why">Water is for removable filters, which then have to be fully dry; nothing inside the case is meant to get wet&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Do not">Spray canned air at an angle so it spits&lt;/td>
&lt;td data-label="Why">Holding the can upright and using short bursts is what keeps liquid propellant off the PCB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Do not">Let fans freewheel under air&lt;/td>
&lt;td data-label="Why">Bearing load and back-fed voltage at the header, which is why the blades get held&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Do not">Brush the motherboard and RAM&lt;/td>
&lt;td data-label="Why">Corsair&amp;rsquo;s caution is explicit: short bursts of air only on those parts&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Do not">Repaste because you are already in there&lt;/td>
&lt;td data-label="Why">A remount changes mounting pressure and paste spread; without a temperature baseline you cannot tell whether you improved anything&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Do not">Open the power supply&lt;/td>
&lt;td data-label="Why">Stored charge, no user-serviceable parts, and nothing to gain&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The repaste line is the one I get asked about most. If the cooler is working, a cleaning session should end with the cooler exactly as it was. If temperatures are the reason you opened the case, diagnose that first with the &lt;a href="https://techfuelhq.com/articles/how-to-check-cpu-temp-2026/">CPU temperature check&lt;/a> and the &lt;a href="https://techfuelhq.com/articles/safe-cpu-temp-2026/">safe temperature ranges&lt;/a>, then decide whether the thermal interface is implicated. Cleaning dust out of a cooler and remounting it are two different jobs with two different risk profiles.&lt;/p>
&lt;h2 id="how-often-to-clean-read-the-dust-not-the-calendar">How often to clean: read the dust, not the calendar&lt;/h2>
&lt;p>Corsair&amp;rsquo;s general rule of thumb is every three to six months. It shortens that to two to three months for a dusty area, a home with pets, or indoor smoking, and considers a twice-yearly clean adequate in a relatively dust-free environment.&lt;/p>
&lt;p>I use those numbers as a range and let the machine set the interval. Once a month, look at the front intake filter without opening anything. If it is visibly matted, that machine needs a shorter cycle than the calendar suggests; if it is barely hazy after two months, the six-month end of the range is fine. A machine on a carpeted floor next to a shedding dog and a machine on a hard floor in a closed office are not on the same schedule, and pretending they are is how people either waste an afternoon or cook a GPU.&lt;/p>
&lt;p>Season is a reasonable proxy in most homes, because heating season and air conditioning season change how much particulate circulates. It is a worse proxy than the filter in front of you.&lt;/p>
&lt;h2 id="what-to-check-after-reassembly">What to check after reassembly&lt;/h2>
&lt;p>Before the side panel goes back on:&lt;/p>
&lt;ul>
&lt;li>Every fan header is seated on the header it came off, and no cable is resting where a blade will hit it.&lt;/li>
&lt;li>The filters are dry and fully seated.&lt;/li>
&lt;li>Nothing is resting on the top of the power supply shroud or blocking a front intake.&lt;/li>
&lt;/ul>
&lt;p>Then power on and check the machine, not the panel:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Every fan spins.&lt;/strong> Open the board&amp;rsquo;s hardware monitor screen in UEFI, or watch the fans at first POST. A fan that does not spin after a cleaning is usually a header you missed, and occasionally a cable you strained.&lt;/li>
&lt;li>&lt;strong>Temperatures return to baseline.&lt;/strong> Idle first, then the same load you used before cleaning. A number that is worse than it was before you opened the case is a reason to stop and look, not a reason to close the panel.&lt;/li>
&lt;li>&lt;strong>Nothing new is audible.&lt;/strong> A tick or a scrape is a cable in a blade or a fan that is not seated flat.&lt;/li>
&lt;/ol>
&lt;p>If a fan will not spin at all, work through the &lt;a href="https://techfuelhq.com/articles/cpu-fan-not-spinning-2026/">fan fault check&lt;/a> before replacing it. If temperatures are still high with clean filters and spinning fans, the problem is airflow, mounting, or the cooler itself rather than dust, and the &lt;a href="https://techfuelhq.com/articles/cpu-gpu-thermal-throttling-fix-2026/">thermal throttling walkthrough&lt;/a> and the &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">diagnostic workbench&lt;/a> are the next stops. For a GPU that stays hot after a clean, the &lt;a href="https://techfuelhq.com/articles/gpu-overheating-2026/">GPU overheating guide&lt;/a> covers what the sensors can and cannot tell you before you consider opening the card.&lt;/p></description></item><item><title>ZFS vs Btrfs (2026): Which Should Your NAS Run?</title><link>https://techfuelhq.com/homelab/zfs-vs-btrfs-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/homelab/zfs-vs-btrfs-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;p>Two filesystems get recommended for the same job, and they are not the same tool. ZFS is a storage stack that happens to ship a filesystem inside it. Btrfs is a filesystem that learned to manage more than one device. On a NAS, a Proxmox datastore, or a backup target, the decision collapses to one question: do you need parity RAID you can trust with data you cannot rebuild?&lt;/p>
&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · ZFS vs Btrfs&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Parity array of three or more drives:&lt;/strong> ZFS RAIDZ. Stable, checksummed, no RAID-5 write hole.&lt;/li>
&lt;li>&lt;strong>Two-drive mirror or single disk:&lt;/strong> Btrfs. Cheap snapshots, subvolumes, and no ARC budget.&lt;/li>
&lt;li>&lt;strong>Proxmox VM datastore:&lt;/strong> mirrors on either filesystem, never RAIDZ, because IOPS matter more than bandwidth.&lt;/li>
&lt;li>&lt;strong>Small ARM board or 4 GB NAS:&lt;/strong> Btrfs. ZFS wants 2 GiB plus 1 GiB per TiB.&lt;/li>
&lt;li>&lt;strong>Never:&lt;/strong> Btrfs RAID5 or RAID6 for data you care about.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;h2 id="what-both-filesystems-actually-guarantee">What both filesystems actually guarantee&lt;/h2>
&lt;p>Both are copy-on-write. New data lands in free space, the checksum is written, and only then does the tree pointer move to the new block. An interrupted write leaves the old tree intact, which is why neither filesystem needs an fsck pass on every unclean shutdown.&lt;/p>
&lt;p>Both checksum. ZFS states plainly that all metadata and data is checksummed, and that it automatically repairs bad data from a good copy when corruption is detected (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/7/zpoolconcepts.7.html" rel="noopener">OpenZFS zpoolconcepts&lt;/a>). Btrfs checksums data and metadata by default and verifies those checksums after reading, using crc32c unless you switch to xxhash, sha256, or blake2 (&lt;a href="https://btrfs.readthedocs.io/en/latest/Checksumming.html" rel="noopener">Btrfs Checksumming&lt;/a>).&lt;/p>
&lt;p>Both snapshot, both scrub, and both have a send stream. The divergence is not in the feature list. It is in how much verification each one performs without being asked, and in which RAID profiles are actually finished.&lt;/p>
&lt;h2 id="where-zfs-wins-raidz-the-write-hole-and-repair-on-read">Where ZFS wins: RAIDZ, the write hole, and repair on read&lt;/h2>
&lt;p>The single most important line in the OpenZFS manual is that raidz does not suffer from the RAID-5/6 write hole, the window after a power loss where data and parity can be left inconsistent (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/7/zpoolconcepts.7.html" rel="noopener">zpoolconcepts&lt;/a>). That is the property that makes parity RAID defensible on a home array at all.&lt;/p>
&lt;p>Capacity follows the usual arithmetic. A mirror of N disks each holding X bytes stores X bytes and survives N-1 failures. A raidz vdev holds roughly (N minus parity) times X, raidz1 has one parity disk, raidz2 has two, raidz3 has three, and the manual recommends keeping a raidz vdev between three and nine disks (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/7/zpoolconcepts.7.html" rel="noopener">zpoolconcepts&lt;/a>). A four-drive raidz1 gives you three drives of usable space. The same four drives as two mirrors give you two, plus double the random read performance.&lt;/p>
&lt;p>Expansion used to be the fatal flaw. It is not anymore. &lt;code>zpool attach&lt;/code> can add a device to an existing raidz vdev while maintaining redundancy, and the documentation is explicit that expansion does not change the number of failures a vdev tolerates, so a RAID-Z2 stays a RAID-Z2 afterwards (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/8/zpool-attach.8.html" rel="noopener">zpool-attach&lt;/a>). Two footnotes matter: expansion reserves about 3.5 MiB per disk for a boot area, and the per-vdev disk limit drops from 255 to 56 disks at ashift=16 (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/8/zpool-attach.8.html" rel="noopener">zpool-attach&lt;/a>). Proxmox documents raidz expansion as available from Proxmox VE 9 on ZFS 2.3.3 (&lt;a href="https://pve.proxmox.com/wiki/ZFS_on_Linux" rel="noopener">Proxmox ZFS wiki&lt;/a>).&lt;/p>
&lt;p>Self-healing is the second win, and it is subtler than the marketing suggests. ZFS repairs bad data from a good copy as corruption is detected, not only during a scrub (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/7/zpoolconcepts.7.html" rel="noopener">zpoolconcepts&lt;/a>). The &lt;code>zpool scrub&lt;/code> command exists to force a full sweep of every block (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/8/zpool-scrub.8.html" rel="noopener">zpool-scrub&lt;/a>), but a verified read of a damaged block already triggers repair. That difference shows up years later, when a drive starts returning bad sectors silently.&lt;/p>
&lt;h2 id="where-btrfs-wins-flexible-devices-cheap-snapshots-small-hardware">Where Btrfs wins: flexible devices, cheap snapshots, small hardware&lt;/h2>
&lt;p>Btrfs treats a pool as a set of devices you can add, remove, or replace on demand, and it lets you change the RAID profile of existing data with &lt;code>btrfs balance&lt;/code> rather than rebuilding the filesystem (&lt;a href="https://btrfs.readthedocs.io/en/latest/Volume-management.html" rel="noopener">Volume-management&lt;/a>). If you started with two drives as RAID1 and later want RAID0 for scratch space, you convert in place. ZFS has no equivalent; you plan the vdev layout up front.&lt;/p>
&lt;p>Subvolumes are the other practical advantage. One pool can hold a dozen independently snapshot-able filesystems, which is how distros implement rollback-on-upgrade and how a Proxmox host can snapshot a container root without carving out a zvol. Btrfs send and receive carry those subvolumes to another host as full or incremental streams, with each command protected by CRC32C (&lt;a href="https://btrfs.readthedocs.io/en/latest/Send-receive.html" rel="noopener">Send-receive&lt;/a>). ZFS does the same thing with &lt;code>zfs send&lt;/code>, but the memory cost of getting there is higher (&lt;a href="https://openzfs.github.io/openzfs-docs/man/master/8/zfs-send.8.html" rel="noopener">zfs-send&lt;/a>).&lt;/p>
&lt;p>Memory is where Btrfs quietly wins the small-hardware argument. ZFS runs an Adaptive Replacement Cache in RAM, and Proxmox recommends budgeting at least 2 GiB of base memory plus 1 GiB per TiB of stored data, with the ARC enforcing a hard 64 MiB minimum (&lt;a href="https://pve.proxmox.com/wiki/ZFS_on_Linux" rel="noopener">Proxmox ZFS wiki&lt;/a>). On a 4 GB ARM NAS or a mini PC you also use as a media server, that budget is the whole machine. Btrfs has no ARC and simply borrows the kernel page cache, which is why it remains the sane default for single-board boxes.&lt;/p>
&lt;h2 id="the-decision-table">The decision table&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Requirement&lt;/th>
&lt;th scope="col">ZFS&lt;/th>
&lt;th scope="col">Btrfs&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Requirement">Parity RAID in production&lt;/td>
&lt;td data-label="ZFS">RAIDZ1/2/3, stable&lt;/td>
&lt;td data-label="Btrfs">RAID5/6 unstable, evaluation only&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">RAID-5/6 write hole&lt;/td>
&lt;td data-label="ZFS">Not present in raidz&lt;/td>
&lt;td data-label="Btrfs">Documented, journal not implemented&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Two-drive mirror with snapshots&lt;/td>
&lt;td data-label="ZFS">Works, needs ARC budget&lt;/td>
&lt;td data-label="Btrfs">Works, minimal overhead&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Single disk with rollback&lt;/td>
&lt;td data-label="ZFS">Possible, heavier&lt;/td>
&lt;td data-label="Btrfs">Native subvolume snapshots&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">VM datastore IOPS&lt;/td>
&lt;td data-label="ZFS">Mirrors only, raidz is one disk of IOPS&lt;/td>
&lt;td data-label="Btrfs">Mirrors only, same logic&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Add a disk to existing parity set&lt;/td>
&lt;td data-label="ZFS">&lt;code>zpool attach&lt;/code>, OpenZFS 2.3+&lt;/td>
&lt;td data-label="Btrfs">Not applicable, no stable parity&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Change RAID profile in place&lt;/td>
&lt;td data-label="ZFS">No, plan the layout first&lt;/td>
&lt;td data-label="Btrfs">&lt;code>btrfs balance&lt;/code> convert&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Metadata checksums&lt;/td>
&lt;td data-label="ZFS">Always&lt;/td>
&lt;td data-label="Btrfs">Default, crc32c unless changed&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Repair on a normal read&lt;/td>
&lt;td data-label="ZFS">Yes, from a good copy&lt;/td>
&lt;td data-label="Btrfs">Verifies, but needs a scrub to find all copies&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Send/receive to remote&lt;/td>
&lt;td data-label="ZFS">&lt;code>zfs send&lt;/code>/&lt;code>zfs receive&lt;/code>&lt;/td>
&lt;td data-label="Btrfs">&lt;code>btrfs send&lt;/code>/&lt;code>btrfs receive&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Memory floor&lt;/td>
&lt;td data-label="ZFS">2 GiB base + 1 GiB/TiB&lt;/td>
&lt;td data-label="Btrfs">No dedicated cache&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Requirement">Per-vdev disk guidance&lt;/td>
&lt;td data-label="ZFS">3-9 disks for raidz&lt;/td>
&lt;td data-label="Btrfs">Profile-dependent&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="recovery-and-the-operational-caveats-that-bite">Recovery and the operational caveats that bite&lt;/h2>
&lt;p>The Btrfs RAID56 warning is not a legacy footnote. The project&amp;rsquo;s own manual says RAID5 and RAID6 should not be used in production, only for evaluation or testing, that power-failure safety for metadata with RAID56 is not complete, and that you should not use raid5 or raid6 for metadata at all, using raid1 or raid1c3 instead (&lt;a href="https://btrfs.readthedocs.io/en/latest/btrfs-man5.html" rel="noopener">btrfs(5)&lt;/a>). The status page still lists RAID56 as unstable (&lt;a href="https://btrfs.readthedocs.io/en/latest/Status.html" rel="noopener">Btrfs Status&lt;/a>). Anyone selling you a four-bay Btrfs NAS on the promise of RAID5 is selling you a test rig.&lt;/p>
&lt;p>Btrfs auto-repair is real but conditional. It salvages data from another valid copy when the profile has redundancy, and the documentation notes that other damaged copies are not detected unless a scrub runs (&lt;a href="https://btrfs.readthedocs.io/en/latest/Auto-repair.html" rel="noopener">Auto-repair&lt;/a>). So your scrub schedule is not optional housekeeping on Btrfs; it is the only mechanism that finds the second bad copy.&lt;/p>
&lt;p>Device replacement has a sharp edge on Btrfs: replace aborts if it hits an input/output error reading the source device (&lt;a href="https://btrfs.readthedocs.io/en/latest/Status.html" rel="noopener">Status&lt;/a>). A source disk that is dying slowly can stall the rebuild you started because it was dying. Replace early, not at the first sign of failure, and never treat a rebuild as a backup.&lt;/p>
&lt;p>On the ZFS side, the caveats are about planning rather than corruption. A raidz vdev behaves approximately like a single disk for IOPS while providing a lot of bandwidth, and Proxmox is direct that IOPS is the more important metric for running virtual machines (&lt;a href="https://pve.proxmox.com/wiki/ZFS_on_Linux" rel="noopener">Proxmox ZFS wiki&lt;/a>). This is why a six-drive RAIDZ2 pool can feel sluggish hosting eight VMs while a three-mirror pool on the same disks feels instant. If your workload is databases, virtual machines, or anything with small random reads, mirrors beat parity on both filesystems.&lt;/p>
&lt;p>ECC memory is worth the money on ZFS, and the reason is narrow: ZFS trusts RAM, and a bad DIMM can write a checksum that matches bad data. I cover which failure modes ECC actually prevents in &lt;a href="https://techfuelhq.com/homelab/ecc-home-server-verify-2026/">what breaks without ECC on a home server&lt;/a>, and it is a more honest treatment than the usual blanket warning.&lt;/p>
&lt;h2 id="which-one-should-you-pick">Which one should you pick&lt;/h2>
&lt;p>If you are building a parity array, run ZFS. Three to nine drives in raidz1 or raidz2, checksums on everything, no write hole, and a scrub that actually finds silent corruption. Use the &lt;a href="https://techfuelhq.com/tools/nas-storage-calculator/">NAS storage calculator&lt;/a> to size usable capacity before you buy, because raidz overhead is not intuitive once you subtract the 80 percent fill guideline you should be respecting anyway.&lt;/p>
&lt;p>If you are building a two-drive mirror, a single-disk boot volume, or anything on a small ARM board, run Btrfs. You give up nothing that matters at that scale, and you keep your RAM.&lt;/p>
&lt;p>If you are virtualizing, the filesystem is the second decision. The first is mirrors versus parity, and it decides everything downstream. The &lt;a href="https://techfuelhq.com/tools/proxmox-capacity-planner/">Proxmox capacity planner&lt;/a> will tell you how much usable space a given layout leaves you, but the IOPS answer is already settled by the word RAIDZ.&lt;/p>
&lt;p>For the wider stack decision, including whether ZFS should live on the hypervisor at all, read &lt;a href="https://techfuelhq.com/homelab/proxmox-truenas-unraid-storage-backend-2026/">Proxmox vs TrueNAS vs Unraid as a storage backend&lt;/a> and the &lt;a href="https://techfuelhq.com/storage/unraid-vs-truenas-vs-omv-vs-proxmox-2026/">four-way NAS OS comparison&lt;/a>. If you have already committed to a ZFS pool, the &lt;a href="https://techfuelhq.com/tutorials/zfs-proxmox-pool-setup-arc-tuning-2026/">pool setup and ARC tuning walkthrough&lt;/a> covers the commands, and drive selection is covered in &lt;a href="https://techfuelhq.com/homelab/best-nas-hard-drives-2026/">best NAS hard drives&lt;/a>.&lt;/p></description></item><item><title>Pi-hole vs AdGuard Home: Which DNS Filter for 2026?</title><link>https://techfuelhq.com/homelab/pihole-vs-adguard-home-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/homelab/pihole-vs-adguard-home-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Pi-hole vs AdGuard Home&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Want encrypted upstreams without extra moving parts?&lt;/strong> AdGuard Home. DoH, DoT and DoQ are documented as built in.&lt;/li>
&lt;li>&lt;strong>Want the biggest pile of community guides and blocklists?&lt;/strong> Pi-hole. It is the default answer for a reason.&lt;/li>
&lt;li>&lt;strong>Need a DHCP server in the same tool?&lt;/strong> AdGuard Home, as long as the host is not Windows.&lt;/li>
&lt;li>&lt;strong>Care about per-device rules?&lt;/strong> Both support it. AdGuard Home via a client record, Pi-hole via group management.&lt;/li>
&lt;li>&lt;strong>Neither one blocks first-party ads.&lt;/strong> Both are DNS filters, not browser extensions, and neither can see inside a page.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>These two do the same core job: answer DNS queries for your network and return nothing for the domains on your blocklists. Everything past that is a design choice about which conveniences are built in and which you assemble yourself.&lt;/p>
&lt;p>I run a DNS filter for one narrow reason: a single place to stop known tracking and advertising domains before any device on the LAN resolves them. If that is also your reason, the feature differences below decide it quickly, because the blocklist part is genuinely equivalent.&lt;/p>
&lt;h2 id="what-both-of-them-actually-do">What both of them actually do&lt;/h2>
&lt;p>Both act as a recursive or forwarding resolver for your LAN. Pi-hole&amp;rsquo;s resolver is FTL, and the project describes it as a &amp;ldquo;lightweight but powerful inbuilt DNS / DHCP / TFTP&amp;rdquo; server (&lt;a href="https://docs.pi-hole.net/ftldns/dns-resolver/" rel="noopener">Pi-hole FTL documentation&lt;/a>). AdGuard Home is distributed as a self-contained binary that the project documents as a DNS server with filtering built in (&lt;a href="https://adguard-dns.io/kb/adguard-home/overview/" rel="noopener">AdGuard Home overview&lt;/a>).&lt;/p>
&lt;p>Both intercept at the domain. That sentence is the limit of the entire category, so it is worth dwelling on for one paragraph.&lt;/p>
&lt;p>A DNS filter answers a question about a hostname. It does not parse a page. When an advertisement is served from the same domain as the content you asked for, blocking the domain blocks the content, so neither tool touches it. In-page slots sold by the publisher are invisible to both. Cosmetic filtering and element hiding belong to browser extensions, and neither of these projects is one. If your complaint is banner ads on a news site, a DNS filter will disappoint you no matter which one you choose, and that is not a configuration problem.&lt;/p>
&lt;h2 id="blocklists-formats-and-management">Blocklists, formats and management&lt;/h2>
&lt;p>This is where Pi-hole&amp;rsquo;s maturity shows, and where the two projects diverge most in daily use.&lt;/p>
&lt;p>Pi-hole stores domains in an SQLite database. The project documents a &lt;code>domainlist&lt;/code> table where the type field distinguishes exact allowlist, exact denylist, regex allowlist and regex denylist, plus an &lt;code>adlist&lt;/code> table for subscribed list URLs which &lt;code>pihole -g&lt;/code> processes (&lt;a href="https://docs.pi-hole.net/database/domain-database/" rel="noopener">Pi-hole domain database&lt;/a>). It also documents &lt;code>gravity&lt;/code> and &lt;code>antigravity&lt;/code> tables that are flushed and rebuilt on each gravity run, which is why a backup has to capture the database rather than a generated file.&lt;/p>
&lt;p>The evaluation order is published too: exact allowlist, regex allowlist, exact denylist, subscribed allowlists, subscribed denylists, regex denylist (&lt;a href="https://docs.pi-hole.net/database/domain-database/" rel="noopener">Pi-hole domain database&lt;/a>). That ordering is the answer to about half the &amp;ldquo;why is this domain still resolving&amp;rdquo; questions I have seen, and Pi-hole is unusual for writing it down explicitly.&lt;/p>
&lt;p>AdGuard Home accepts three syntaxes. Its filtering documentation says: &amp;ldquo;There are three different approaches to writing hosts blocklists: Adblock-style syntax, /etc/hosts syntax, and Domains-only syntax,&amp;rdquo; and recommends Adblock-style when you are authoring one (&lt;a href="https://adguard-dns.io/kb/general/dns-filtering-syntax/" rel="noopener">AdGuard filtering syntax&lt;/a>). That recommendation matters in practice, because Adblock-style syntax is what most public list maintainers already write in.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Blocklist concern&lt;/th>
&lt;th scope="col">Pi-hole&lt;/th>
&lt;th scope="col">AdGuard Home&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Blocklist concern">Storage&lt;/td>
&lt;td data-label="Pi-hole">SQLite database&lt;/td>
&lt;td data-label="AdGuard Home">Configuration file and filter URLs&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Blocklist concern">Subscriptions&lt;/td>
&lt;td data-label="Pi-hole">&lt;code>adlist&lt;/code> table, rebuilt by &lt;code>pihole -g&lt;/code>&lt;/td>
&lt;td data-label="AdGuard Home">Filter URL list, refreshed on a schedule&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Blocklist concern">Rule types&lt;/td>
&lt;td data-label="Pi-hole">Exact and regex, allow and deny&lt;/td>
&lt;td data-label="AdGuard Home">Adblock-style, hosts, domains-only&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Blocklist concern">Order of precedence&lt;/td>
&lt;td data-label="Pi-hole">Published, six tiers&lt;/td>
&lt;td data-label="AdGuard Home">Exception rules, which &lt;code>$important&lt;/code> overrides&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Blocklist concern">Per-group lists&lt;/td>
&lt;td data-label="Pi-hole">Yes, via group management&lt;/td>
&lt;td data-label="AdGuard Home">Yes, via clients&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The practical consequence: if you already maintain Adblock-syntax lists, AdGuard Home ingests them directly. On Pi-hole, an Adblock-syntax list is not the native format — its native lists are domains and regexes — so verify a list&amp;rsquo;s format before subscribing.&lt;/p>
&lt;h2 id="encrypted-upstreams-are-where-they-diverge">Encrypted upstreams are where they diverge&lt;/h2>
&lt;p>This is the single most consequential difference for a homelab, and it is a packaging difference rather than a capability one.&lt;/p>
&lt;p>AdGuard Home supports encryption out of the box. Its documentation states that it &amp;ldquo;supports all modern DNS encryption protocols out-of-the-box: DNS-over-HTTPS, DNS-over-TLS, DNS-over-QUIC,&amp;rdquo; and that it supports both client-side and server-side DNSCrypt (&lt;a href="https://adguard-dns.io/kb/adguard-home/encryption/" rel="noopener">AdGuard encryption&lt;/a>). That covers both directions: encrypted queries leaving your network and encrypted queries arriving from a device that uses your server directly.&lt;/p>
&lt;p>Pi-hole does not ship an encrypted upstream in the resolver. Its own upstream configuration accepts &amp;ldquo;an array of IP addresses and/or hostnames, optionally with a port (&lt;code>#...&lt;/code>)&amp;rdquo; (&lt;a href="https://docs.pi-hole.net/ftldns/configfile/" rel="noopener">Pi-hole configuration file&lt;/a>) — an address, not a URL scheme. To get DoH you put something in front of it, and the project publishes guides for doing exactly that: &lt;a href="https://docs.pi-hole.net/guides/dns/cloudflared/" rel="noopener">cloudflared&lt;/a> for DoH and &lt;a href="https://docs.pi-hole.net/guides/dns/unbound/" rel="noopener">unbound&lt;/a> for local recursion. There is also a page on &lt;a href="https://docs.pi-hole.net/guides/dns/upstream-dns-providers/" rel="noopener">upstream DNS providers&lt;/a> if you would rather change who you forward to than encrypt the path.&lt;/p>
&lt;p>Read the cloudflared guide&amp;rsquo;s own warning before you commit to it. The page carries a notice dated November 2025 stating that the proxy-dns feature the guide relies on is deprecated by Cloudflare, that existing installations continue to work and are supported for twelve months after their release date, and that a cloudflared updated after 2 February 2026 will no longer function as the guide describes. New installations &amp;ldquo;via this method are not recommended.&amp;rdquo;&lt;/p>
&lt;p>That is not a reason to avoid Pi-hole. It is a reason to plan the encrypted path deliberately rather than pasting a guide from 2021. The unbound route has no such third-party dependency.&lt;/p>
&lt;h2 id="per-client-rules-and-how-each-identifies-a-device">Per-client rules and how each identifies a device&lt;/h2>
&lt;p>Both let you apply different rules to different devices. The models differ enough to matter if you have kids&amp;rsquo; devices, a work laptop, or an IoT VLAN.&lt;/p>
&lt;p>AdGuard Home treats a client as a record. Its client documentation says the product &amp;ldquo;offers flexible configuration options for connected devices&amp;rdquo; and &amp;ldquo;allows you to apply different rules depending on the client&amp;rdquo; (&lt;a href="https://adguard-dns.io/kb/adguard-home/clients/" rel="noopener">AdGuard clients&lt;/a>). Identification is the interesting part: the runtime determines which client made a query using hosts files, reverse DNS lookups, the ARP table, WHOIS, and DHCP leases. That means a device with a stable name resolves to the right profile even without a fixed IP, though a fixed IP or a DHCP reservation is still the reliable way to guarantee it.&lt;/p>
&lt;p>Pi-hole treats a client as a member of a group. Clients are identified by IP address in the &lt;code>client&lt;/code> table of its database, and groups then determine which blocklists apply (&lt;a href="https://docs.pi-hole.net/group_management/" rel="noopener">Pi-hole group management&lt;/a>, &lt;a href="https://docs.pi-hole.net/database/domain-database/" rel="noopener">Pi-hole domain database&lt;/a>). The model is more explicit — you build the group, then populate it — and it makes a &amp;ldquo;kids&amp;rdquo; or &amp;ldquo;IoT&amp;rdquo; group easy to reason about when you have several devices in each.&lt;/p>
&lt;p>The practical difference: AdGuard Home&amp;rsquo;s per-client model is quicker for one-off exceptions. Pi-hole&amp;rsquo;s group model scales better when you have six devices that should share one policy. Neither requires you to know anything you cannot see in its interface, and both reward fixed addressing — which is why VLAN planning and DHCP reservations come before filter tuning. If you are segmenting the network at the same time, the &lt;a href="https://techfuelhq.com/tutorials/vlans-homelab-2026/">VLAN walkthrough&lt;/a> and the &lt;a href="https://techfuelhq.com/tools/subnet-cidr-calculator/">subnet calculator&lt;/a> settle the addressing before the filter gets a say.&lt;/p>
&lt;h2 id="dhcp-query-logs-and-the-web-interface">DHCP, query logs and the web interface&lt;/h2>
&lt;p>&lt;strong>DHCP.&lt;/strong> AdGuard Home includes a DHCP server, and its documentation is specific: it &amp;ldquo;can be used as a DHCP server,&amp;rdquo; it currently does not support DHCP on Windows, it sets itself as the DNS server for DHCP clients by default, and the default lease time is 24 hours (&lt;a href="https://adguard-dns.io/kb/adguard-home/dhcp/" rel="noopener">AdGuard DHCP&lt;/a>). Pi-hole also offers DHCP, and documents the Docker-specific considerations separately (&lt;a href="https://docs.pi-hole.net/docker/dhcp/" rel="noopener">Pi-hole Docker DHCP&lt;/a>).&lt;/p>
&lt;p>If both your router and your Pi already hand out addresses, turn one off. Two DHCP servers on one broadcast domain is the classic way to spend a Saturday.&lt;/p>
&lt;p>&lt;strong>Query logs.&lt;/strong> Pi-hole records queries in a database documented separately from the domain database (&lt;a href="https://docs.pi-hole.net/database/query-database/" rel="noopener">Pi-hole query database&lt;/a>), and its web interface reads from it. AdGuard Home configures its query log in the &lt;code>querylog&lt;/code> object of &lt;code>AdGuardHome.yaml&lt;/code>, including whether the log is enabled, whether it is written to a file, a retention interval, and a memory size (&lt;a href="https://adguard-dns.io/kb/adguard-home/configuration/" rel="noopener">AdGuard configuration&lt;/a>).&lt;/p>
&lt;p>That configuration file detail is the one thing to internalise about AdGuard Home: everything lives in &lt;code>AdGuardHome.yaml&lt;/code>, and the documentation warns that you can modify the file only while the service is not running, &amp;ldquo;otherwise, any changes to the file will be lost because the running program will overwrite them.&amp;rdquo; Edit it with the service stopped, or not at all.&lt;/p>
&lt;p>&lt;strong>Blocking behaviour.&lt;/strong> Pi-hole documents its blocking modes explicitly, which is where you choose what a blocked query actually receives — an answer the client can deal with quickly rather than a timeout (&lt;a href="https://docs.pi-hole.net/ftldns/blockingmode/" rel="noopener">Pi-hole blocking modes&lt;/a>). If pages feel slow when a blocked domain is on them, that setting is usually the reason.&lt;/p>
&lt;h2 id="running-a-second-instance">Running a second instance&lt;/h2>
&lt;p>Redundancy is the part people skip and then regret, because a DNS filter is a single point of failure for the whole house. When it goes down, nothing resolves, and every complaint in the house is addressed to you.&lt;/p>
&lt;p>Neither project ships built-in clustering. The working pattern is the same on both: run a second instance on a second host, keep its configuration identical, and hand both addresses to DHCP as primary and secondary DNS. Clients fall back to the second when the first stops answering, though how quickly depends on the client.&lt;/p>
&lt;p>On Pi-hole that means maintaining two databases. Subscribed lists can be re-fetched with &lt;code>pihole -g&lt;/code> on each node, but hand-written rules and group assignments have to be copied. On AdGuard Home it means two &lt;code>AdGuardHome.yaml&lt;/code> files kept in sync — one file per node, which is easier to diff but easier to forget.&lt;/p>
&lt;p>Two warnings from experience, offered as pattern rather than measurement. First, a second instance on the same physical host or the same SD card is not redundancy; it is the same failure with a second IP. Second, if you are virtualising, put the pair on different hosts — the &lt;a href="https://techfuelhq.com/tutorials/adguard-home-local-dns-proxmox-2026/">AdGuard Home on Proxmox walkthrough&lt;/a> covers the container setup and the second-instance step in detail, and the &lt;a href="https://techfuelhq.com/homelab/proxmox-truenas-unraid-storage-backend-2026/">Proxmox storage backend comparison&lt;/a> is the right place to settle where that container&amp;rsquo;s disk lives.&lt;/p>
&lt;h2 id="which-one-should-you-pick">Which one should you pick&lt;/h2>
&lt;p>&lt;strong>Pick AdGuard Home if&lt;/strong> you want encrypted DNS without a second daemon, a DHCP server in the same tool, and a configuration you can version-control as a single file. It is the shorter path from &amp;ldquo;I want DoH&amp;rdquo; to &amp;ldquo;DoH is running,&amp;rdquo; and its per-client model is the more convenient of the two for a handful of devices.&lt;/p>
&lt;p>&lt;strong>Pick Pi-hole if&lt;/strong> you want the largest body of existing guides, a large catalogue of published blocklists already written in hosts format, and a documented precedence order that makes debugging predictable. It is the safer answer when you are learning the category, because almost every problem you hit has already been written up.&lt;/p>
&lt;p>&lt;strong>Run neither alone if&lt;/strong> the household depends on the network. Add the second instance at build time, not after the first outage.&lt;/p>
&lt;p>&lt;strong>Do not expect either to replace a browser extension.&lt;/strong> Third-party ad and tracker domains are what these tools see. First-party advertising, in-page slots, and anything served from the content domain are outside their reach by construction, and no amount of list tuning changes that.&lt;/p>
&lt;p>For the storage decision underneath whichever you choose, &lt;a href="https://techfuelhq.com/homelab/zfs-vs-btrfs-2026/">ZFS vs Btrfs&lt;/a> covers the pool your container or VM will sit on, and the &lt;a href="https://techfuelhq.com/homelab/caddy-vs-nginx-proxy-manager-vs-traefik-2026/">reverse proxy comparison&lt;/a> covers how you put a certificate and hostname in front of the admin interface so you are not managing it over plain HTTP on port 80.&lt;/p></description></item><item><title>NVIDIA Shader Cache Size: Disabled, Unlimited, or 10GB?</title><link>https://techfuelhq.com/gaming/shader-cache-size-nvidia-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gaming/shader-cache-size-nvidia-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · NVIDIA Shader Cache Size&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Default action: leave it where it is.&lt;/strong> You are trading disk space against repeated shader compilation, not buying frame rate.&lt;/li>
&lt;li>&lt;strong>Raise it only if&lt;/strong> you rotate through a large library of demanding games and you can afford the space. NVIDIA's own guidance is a size big enough for your normal games and small enough not to crowd your drive.&lt;/li>
&lt;li>&lt;strong>Do not leave it Disabled.&lt;/strong> That is a step in the cache-clearing procedure, not a permanent setting.&lt;/li>
&lt;li>&lt;strong>Clear the cache when&lt;/strong> games crash on launch, artifacts appear, or performance drops after a corrupted cache. NVIDIA documents that exact failure mode.&lt;/li>
&lt;li>&lt;strong>Where it lives:&lt;/strong> NVIDIA App → Graphics → Global Settings → Shader Cache Size, or the older NVIDIA Control Panel under Manage 3D settings.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>The Shader Cache Size control is the only entry in NVIDIA&amp;rsquo;s 3D settings list that people change for a problem it does not solve. It does not make a game render faster. It decides how much disk space the driver may spend keeping compiled shaders around, so that a game you launched last week does not have to compile them all again.&lt;/p>
&lt;p>That makes the decision narrower than the forum threads suggest. Leave it on the default unless you have a specific reason to move it, raise it if you own a large library of demanding titles and have the space, and touch it at all only to clear a damaged cache. The rest of this page is the reasoning and the exact paths.&lt;/p>
&lt;h2 id="what-a-shader-cache-actually-holds">What a shader cache actually holds&lt;/h2>
&lt;p>A shader is a small program the GPU runs, and the driver has to compile it for your specific card and driver version before the game can use it. NVIDIA&amp;rsquo;s Control Panel reference describes the problem in one line: shader compiles &amp;ldquo;are normally performed each time a game runs and are a common cause of game-play stuttering&amp;rdquo; (&lt;a href="https://www.nvidia.com/content/Control-Panel-Help/vLatest/en-us/mergedProjects/nv3d/Manage_3D_Settings_%28reference%29.htm" rel="noopener">NVIDIA Control Panel Help&lt;/a>).&lt;/p>
&lt;p>The cache exists to skip that repeat work. The same reference says the cache &amp;ldquo;stores these compiled shaders so that subsequent runs of the same game do not need to perform the shader compilation.&amp;rdquo; That is the whole promise: the second launch is cheaper than the first.&lt;/p>
&lt;p>Two things follow, and they matter more than any benchmark.&lt;/p>
&lt;p>First, the cache helps the second run, not the first. Nothing in NVIDIA&amp;rsquo;s description says the cache accelerates the initial compile. If your complaint is &amp;ldquo;this game hitches every time I start it, every session,&amp;rdquo; a bigger cache is not the fix, because the cache is not what you are waiting on.&lt;/p>
&lt;p>Second, the cache is a disk cost. Compiled GPU code is not small, and NVIDIA&amp;rsquo;s guidelines note that higher-end games &amp;ldquo;may require several hundred megabytes&amp;rdquo; each. Multiply that across a library and you understand why the setting has a ceiling at all.&lt;/p>
&lt;h2 id="the-option-list-as-nvidia-documents-it">The option list, as NVIDIA documents it&lt;/h2>
&lt;p>The Control Panel reference lists the values as: &amp;ldquo;Disabled, Unlimited, or one of the following values: 128 MB, 256 MB, 512 MB, 1 GB, 5 GB, 10 GB, 100 GB.&amp;rdquo; It also notes the control was introduced in Release 495. It does not state a default size anywhere on that page, so I am not going to quote one from that source.&lt;/p>
&lt;p>The NVIDIA App exposes a different label. NVIDIA&amp;rsquo;s support article on &lt;a href="https://nvidia.custhelp.com/app/answers/detail/a_id/5735" rel="noopener">deleting shader cache files&lt;/a> tells you to set the control back to &amp;ldquo;Driver Default (currently 16GB)&amp;rdquo; when you are finished clearing it. That sentence is the only place either document names a numeric default, and it describes the NVIDIA App&amp;rsquo;s entry rather than the Control Panel list.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Option&lt;/th>
&lt;th scope="col">What it means in practice&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Option">Disabled / Off&lt;/td>
&lt;td data-label="What it means in practice">No persistent shader cache. Every launch recompiles. This is the clearing state, not a tuning state.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Option">Driver Default&lt;/td>
&lt;td data-label="What it means in practice">NVIDIA&amp;rsquo;s chosen size; the support article names it as currently 16 GB. The sane starting point.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Option">128 MB to 1 GB&lt;/td>
&lt;td data-label="What it means in practice">Small ceilings. Fine for a couple of old titles, tight for anything modern.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Option">5 GB and 10 GB&lt;/td>
&lt;td data-label="What it means in practice">Room for a working library of demanding games without unbounded growth.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Option">100 GB&lt;/td>
&lt;td data-label="What it means in practice">A ceiling large enough that you will hit free-space limits before you hit it.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Option">Unlimited&lt;/td>
&lt;td data-label="What it means in practice">No ceiling of its own. The constraint becomes your free disk space.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The mechanical consequence of a small ceiling is the interesting part, and NVIDIA spells it out: &amp;ldquo;On approaching the size limit, the driver will remove older shaders from the cache to make space for newer shaders; setting a size limit too small may cause the driver to remove shaders you still make use of and cause game play stutters.&amp;rdquo;&lt;/p>
&lt;p>Read that twice, because it inverts the usual advice. A too-small cache does not merely fail to help. It can actively churn, evicting the shaders for the game you play nightly in favour of the one you installed last weekend.&lt;/p>
&lt;h2 id="why-stutter-spikes-after-a-purge-or-a-driver-update">Why stutter spikes after a purge or a driver update&lt;/h2>
&lt;p>The single most useful sentence in NVIDIA&amp;rsquo;s documentation is the note attached to this setting: &amp;ldquo;Installing a new driver will delete the cache; you may experience game play stutters the first time you run a game after installing a driver.&amp;rdquo;&lt;/p>
&lt;p>That explains a whole category of support thread. You update your driver, launch your main game, and it hitches for the first minutes. Nothing is broken. The cache that was saving you that work was just deleted, and you are paying the first-run compilation cost again.&lt;/p>
&lt;p>It also means the stutter is self-limiting. Play the game once and the cache rebuilds. If the hitch persists across many launches with no driver change, the cache is not your explanation and you should stop looking at this setting.&lt;/p>
&lt;p>The same logic covers the manual case. NVIDIA&amp;rsquo;s article describes what a damaged cache actually does: &amp;ldquo;If the NVIDIA Shader Cache files are damaged, it may cause applications or games to crash on launch, exhibit lower performance, or display visual artifacts.&amp;rdquo; Note the word damaged. Corrupt compiled code being replayed is a different failure from a cache that is merely small, and only one of those is fixed by deleting it.&lt;/p>
&lt;h2 id="why-unlimited-is-not-free">Why Unlimited is not free&lt;/h2>
&lt;p>Unlimited sounds like the option that removes a problem, and it is the option most likely to be recommended in a comment thread. It is not free, and the cost is not subtle.&lt;/p>
&lt;p>The disk cost grows with your library and your settings, because every game you launch deposits its compiled output. NVIDIA&amp;rsquo;s own guideline for this control is a limit &amp;ldquo;large enough to cover the set of games you normally use, but not too large that it exceeds your available hard drive disk space.&amp;rdquo; Unlimited deletes the first half of that sentence and keeps the second, leaving your free space as the only thing standing between the driver and a full drive.&lt;/p>
&lt;p>There is a second cost that people miss. The cache only pays back while its contents are valid, and a driver install resets that clock no matter how much room you allocated. Unlimited does not exempt you from the invalidation; it just means more stored shaders are discarded when the wipe happens.&lt;/p>
&lt;p>And a third: nothing about a larger ceiling speeds up the game you are about to play for the first time. That is the first-run cost again, and it is unaffected by how much room you have allocated.&lt;/p>
&lt;h2 id="when-to-clear-the-cache">When to clear the cache&lt;/h2>
&lt;p>Clear it when the symptoms are cache-shaped: a game crashes on launch, artifacts appear, or performance drops in a way that started recently and follows a driver change. NVIDIA&amp;rsquo;s article lists exactly those outcomes as the damaged-cache signature.&lt;/p>
&lt;p>NVIDIA&amp;rsquo;s own procedure is a five-step sequence, and the order matters:&lt;/p>
&lt;ol>
&lt;li>Open the &lt;strong>NVIDIA App&lt;/strong>, select &lt;strong>Graphics&lt;/strong> in the left column, then &lt;strong>Global Settings&lt;/strong> at the top.&lt;/li>
&lt;li>Search for and select &lt;strong>Shader Cache Size&lt;/strong>, choose &lt;strong>Off&lt;/strong> under Cache Size, and click &lt;strong>Apply&lt;/strong>.&lt;/li>
&lt;li>Reboot the PC.&lt;/li>
&lt;li>Delete the cache files. Open the Run dialog (Win + R) and enter &lt;code>%USERPROFILE%\AppData\Local&lt;/code>, open the &lt;code>NVIDIA&lt;/code> directory, and delete all contents from both the &lt;code>DXCache&lt;/code> and &lt;code>GLCache&lt;/code> folders. Then go back to the Local folder, open &lt;code>NVIDIA Corporation&lt;/code>, and delete the contents of &lt;code>NV_Cache&lt;/code>.&lt;/li>
&lt;li>Reopen the NVIDIA App, set Shader Cache Size back to &lt;strong>Driver Default&lt;/strong>, click &lt;strong>Apply&lt;/strong>, and restart once more.&lt;/li>
&lt;/ol>
&lt;p>Delete the contents of those folders, not the folders themselves. NVIDIA also documents an alternative route: the third-party Display Driver Uninstaller has a &lt;strong>Clean Shader Cache (Only)&lt;/strong> button, reached by selecting GPU as the device type and NVIDIA as the device. Its article says to restore the Driver Default setting afterwards either way.&lt;/p>
&lt;p>Two reboots rather than one is not ceremony. The first gets the driver out of the way of the files you are about to remove; the second settles the restored setting. If you skip straight to deleting while the cache is still enabled, you are racing the driver for the same files.&lt;/p>
&lt;h2 id="driver-cache-versus-per-game-pipeline-caches">Driver cache versus per-game pipeline caches&lt;/h2>
&lt;p>The folders above are NVIDIA&amp;rsquo;s cache. They are not the only shader cache on your machine, and confusing the two leads to a lot of wasted effort.&lt;/p>
&lt;p>Direct3D 12 gives applications their own shader cache. Microsoft&amp;rsquo;s &lt;a href="https://microsoft.github.io/DirectX-Specs/d3d/ShaderCache.html" rel="noopener">D3D12 Shader Cache specification&lt;/a> defines disk-backed cache sessions as being &amp;ldquo;backed by files on disk, that will persist from run to run, unless cleared,&amp;rdquo; and separately defines a driver-managed cache kind that &amp;ldquo;refers to the cache which is managed by the driver,&amp;rdquo; where &amp;ldquo;operations for this cache are hints.&amp;rdquo; Two caches, two owners.&lt;/p>
&lt;p>Games can also cache compiled pipeline state objects directly. Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/samples/microsoft/directx-graphics-samples/d3d12-pipeline-state-cache-sample-win32" rel="noopener">pipeline state cache sample&lt;/a> describes exactly why they do: &amp;ldquo;An app can use PSO libraries to cache compiled PSOs to disk and avoid costly shader compilation during subsequent runs.&amp;rdquo;&lt;/p>
&lt;p>Practically, this means a game that still hitches after you clear the NVIDIA folders may be reloading its own pipeline cache instead. It also means a game that hitches on first launch after a driver update may be recompiling PS states that the driver&amp;rsquo;s cache never held in the first place. If you are chasing a specific title, check whether it exposes its own shader or pipeline cache option before you touch the NVIDIA setting again.&lt;/p>
&lt;h2 id="leave-it-alone-change-it-or-clear-it">Leave it alone, change it, or clear it&lt;/h2>
&lt;p>&lt;strong>Leave it alone if&lt;/strong> your games settle within a session or two of launching, or after a driver update. That is the system working. This setting is not the reason a game stutters in hour three.&lt;/p>
&lt;p>&lt;strong>Change it if&lt;/strong> you keep a large library of demanding titles installed and you see repeat compilation cost as you rotate through them. Go to 10 GB, or one step at a time from Driver Default, and watch your free space. There is no reason to jump straight to Unlimited, and no evidence that it helps a library that already fits.&lt;/p>
&lt;p>&lt;strong>Clear it if&lt;/strong> a game crashes at launch, shows artifacts, or lost performance right after something changed on the system. Follow NVIDIA&amp;rsquo;s sequence in the order written, and put the setting back when you are done.&lt;/p>
&lt;p>&lt;strong>Stop tuning it&lt;/strong> the moment the symptom survives a cleared cache. A cache that has been deleted and rebuilt cannot be the cause of a hitch that is still there afterwards, and this control has nothing to say about a problem that lives in the game, the driver&amp;rsquo;s per-game profile, or the rest of the machine. The &lt;a href="https://techfuelhq.com/articles/pc-stuttering-in-games-2026/">stuttering guide&lt;/a> sorts those by pattern, and if you are choosing between driver branches rather than cache sizes, the &lt;a href="https://techfuelhq.com/articles/game-ready-vs-studio-driver-2026/">Game Ready versus Studio driver comparison&lt;/a> covers that decision.&lt;/p>
&lt;p>One last boundary. This setting governs shaders the driver compiles for your games. It is not a way to buy frame rate, and on a system where the &lt;a href="https://techfuelhq.com/tools/fps-calculator/">FPS calculator&lt;/a> already tells you the GPU is the limit, no cache size will change the answer.&lt;/p></description></item><item><title>Discord Hardware Acceleration: On or Off? (2026)</title><link>https://techfuelhq.com/gaming/discord-hardware-acceleration-on-or-off-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/gaming/discord-hardware-acceleration-on-or-off-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Discord hardware acceleration&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Default: leave it on.&lt;/strong> It moves compositing and video work onto the GPU, which is usually the cheaper place for it.&lt;/li>
&lt;li>&lt;strong>Turn it off for a symptom, not for a feeling:&lt;/strong> broken screen shares, video that will not render, crashes that line up with a driver event, or lost frames while streaming.&lt;/li>
&lt;li>&lt;strong>Where it lives:&lt;/strong> User Settings &amp;gt; Voice and Video &amp;gt; Video tab, then scroll to Hardware Acceleration. Older guides say User Settings &amp;gt; Advanced.&lt;/li>
&lt;li>&lt;strong>Relaunch the client&lt;/strong> and retest the exact thing that failed. One change, one observation.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>Discord runs on Chromium, and Chromium draws its interface with the GPU by default. That is the whole point of the hardware acceleration switch: when it is on, the client hands compositing and video decoding to the graphics card instead of doing that work on the CPU. It is a good default, and most people should never touch it.&lt;/p>
&lt;p>The exceptions are real, though, and they are specific. When the picture breaks in a particular way, or when the client is fighting a driver for the same GPU you are trying to game on, the switch is the first thing worth changing. What it is not is a general performance setting to flip because a video said so.&lt;/p>
&lt;h2 id="what-the-switch-actually-changes">What the switch actually changes&lt;/h2>
&lt;p>Discord describes itself as &amp;ldquo;based on chromium which has a multi-process model&amp;rdquo;, and lists the processes you will see in Task Manager: a main process, a renderer, a crash reporter, a GPU process and the overlay. That lineage matters because it tells you what the toggle controls. This is Chromium&amp;rsquo;s GPU compositing being turned on or off inside a chat application, not a Discord-specific graphics feature.&lt;/p>
&lt;p>Chromium&amp;rsquo;s own &lt;a href="https://www.chromium.org/developers/design-documents/gpu-accelerated-compositing-in-chrome/" rel="noopener">design document on GPU accelerated compositing&lt;/a> explains the architecture: renderers are sandboxed and cannot call the operating system&amp;rsquo;s 3D APIs directly, so a separate GPU process receives commands, parses them, and executes them through OpenGL or Direct3D. Content is split into layers, tiled, and rasterized either by software rasterizers in worker threads or directly on the GPU. Turning acceleration off moves that work to the software path.&lt;/p>
&lt;p>Two consequences follow, and both are practical:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>The GPU process does not disappear.&lt;/strong> Discord&amp;rsquo;s article on its processes says so explicitly: the GPU Process is listed &amp;ldquo;even with hardware acceleration turned off&amp;rdquo;. If you disable the option and still see a GPU process, the setting applied. Do not use that as evidence that nothing changed.&lt;/li>
&lt;li>&lt;strong>The work moves rather than vanishing.&lt;/strong> Software compositing keeps CPU cores busy. On a machine that is already CPU-limited, that is a worse trade than a GPU that has headroom.&lt;/li>
&lt;/ul>
&lt;p>Electron, the framework that packages Chromium into desktop apps like this one, exposes the same thing as an application-level switch in its &lt;a href="https://www.electronjs.org/docs/latest/api/app" rel="noopener">API reference&lt;/a>. The label in the settings menu is friendlier than the mechanism, but it is the same mechanism.&lt;/p>
&lt;h2 id="turn-it-off-when-the-picture-breaks">Turn it off when the picture breaks&lt;/h2>
&lt;p>Discord&amp;rsquo;s own troubleshooting documents recommend disabling hardware acceleration for a fairly narrow set of failures, and they are worth reading as a list rather than a slogan.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Symptom&lt;/th>
&lt;th scope="col">What Discord&amp;rsquo;s guides say&lt;/th>
&lt;th scope="col">What it suggests&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Symptom">Screen share tears, goes green, or shows black blocks&lt;/td>
&lt;td data-label="What Discord&amp;rsquo;s guides say">Disable hardware acceleration under the Video tab when screen sharing fails&lt;/td>
&lt;td data-label="What it suggests">The capture and encode path is the suspect&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom">Video inside the client will not render&lt;/td>
&lt;td data-label="What Discord&amp;rsquo;s guides say">Disable it under Voice and Video, Video tab, Advanced section&lt;/td>
&lt;td data-label="What it suggests">Decode path rather than network&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom">Stream lags while you play&lt;/td>
&lt;td data-label="What Discord&amp;rsquo;s guides say">&amp;ldquo;If you have Hardware Acceleration on, and you find your stream is lagging, please try disabling this setting&amp;rdquo;&lt;/td>
&lt;td data-label="What it suggests">The game and the stream are competing for the GPU&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom">Client freezes on the loading screen&lt;/td>
&lt;td data-label="What Discord&amp;rsquo;s guides say">The general guide lists disabling it under User Settings, Advanced&lt;/td>
&lt;td data-label="What it suggests">Older UI location, same switch&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>That third row is the one that matters most on a mid-range or older graphics card. Streaming a game means the encoder, the game renderer and the client&amp;rsquo;s compositor all want the same GPU. Discord&amp;rsquo;s &lt;a href="https://support.discord.com/hc/en-us/articles/33030151293079-Discord-Voice-Video-Streaming-Guide" rel="noopener">Voice, Video and Streaming guide&lt;/a> treats disabling the setting as a legitimate step when a stream lags, and the same guide walks the path: the cogwheel at the bottom left, then Voice and Video, then the Video tab, then the Hardware Acceleration row.&lt;/p>
&lt;p>The second row belongs to the &lt;a href="https://support.discord.com/hc/en-us/articles/360045138471-Discord-Voice-and-Video-Troubleshooting-Guide" rel="noopener">Voice and Video troubleshooting guide&lt;/a>, which sends video problems to the same place and describes the option as sitting in an Advanced section of that Video tab. If your build shows it there rather than under a top-level Advanced page, that is why.&lt;/p>
&lt;p>Crashes deserve their own paragraph, because the evidence standard is higher. A client that closes at the same moment the Windows log records a display driver recovery is a reasonable case for turning acceleration off — the &lt;a href="https://techfuelhq.com/articles/gpu-driver-crash-fix-2026/">TDR pattern&lt;/a> is that the driver was reset, and a renderer that was mid-composite does not always survive it. A client that crashes with acceleration off as well is a different fault, and the &lt;a href="https://techfuelhq.com/gaming/discord-not-opening-2026/">Discord not opening guide&lt;/a> is the better lane.&lt;/p>
&lt;h2 id="leave-it-on-unless-something-is-wrong">Leave it on unless something is wrong&lt;/h2>
&lt;p>There are four good reasons to leave the setting alone.&lt;/p>
&lt;p>&lt;strong>Your GPU has headroom.&lt;/strong> Compositing a chat window is trivial work for any discrete card and for most integrated ones. Moving it to the CPU buys nothing you can see and spends cycles you might want elsewhere.&lt;/p>
&lt;p>&lt;strong>Your CPU is the limit.&lt;/strong> On an older quad-core, or on any machine running a game that already pins the processor, software compositing adds work to the component that is already the bottleneck. That is the opposite of what you want.&lt;/p>
&lt;p>&lt;strong>The UI stays smoother.&lt;/strong> Scrolling a long channel list, animating the member sidebar, and playing an embedded video all use the same path. Chromium&amp;rsquo;s document notes that hardware compositing is skipped when drivers are blocklisted or no GPU exists, which is the situation the software path is designed for — not a normal desktop.&lt;/p>
&lt;p>&lt;strong>Laptops.&lt;/strong> Turning acceleration off shifts work to the CPU, and on a laptop that trade can cost battery life. Whether it does on your machine is worth measuring rather than assuming, because the result depends on the panel, the refresh rate and the power plan as much as on the client.&lt;/p>
&lt;p>None of this means the setting is sacred. It means the default is right until a symptom says otherwise.&lt;/p>
&lt;h2 id="the-exact-path-in-the-current-client">The exact path in the current client&lt;/h2>
&lt;ol>
&lt;li>Click the &lt;strong>cogwheel&lt;/strong> next to your name at the bottom left of the window to open &lt;strong>User Settings&lt;/strong>.&lt;/li>
&lt;li>Open &lt;strong>Voice and Video&lt;/strong>.&lt;/li>
&lt;li>Select the &lt;strong>Video&lt;/strong> tab and scroll down to the &lt;strong>Hardware Acceleration&lt;/strong> row.&lt;/li>
&lt;li>Clear the check box to turn it off. Tick it to turn it back on.&lt;/li>
&lt;li>&lt;strong>Quit Discord completely&lt;/strong> — from the tray, not just the window — and reopen it.&lt;/li>
&lt;/ol>
&lt;p>Step 5 is not optional. Discord&amp;rsquo;s streaming sequence lists restarting the app and the device immediately before the hardware acceleration step, and a running client keeps using whatever it started with. If you toggle the box and immediately retest, you are testing the old configuration.&lt;/p>
&lt;p>The path has moved over the client&amp;rsquo;s life, which is why guides disagree. Discord&amp;rsquo;s &lt;a href="https://support.discord.com/hc/en-us/articles/31623498041623-Discord-Troubleshooting-Guide" rel="noopener">general troubleshooting guide&lt;/a> still tells readers to &amp;ldquo;Disable hardware acceleration in User Settings &amp;gt; Advance&amp;rdquo; for loading-screen freezes. That is not wrong so much as old: it describes where the option sat in earlier builds. The Video-tab path is what the current guides describe, and it is what I would look for first.&lt;/p>
&lt;h2 id="test-the-change-instead-of-guessing">Test the change instead of guessing&lt;/h2>
&lt;p>A settings toggle is only useful if you can tell whether it helped, and the way to do that is to reproduce the original failure deliberately.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Write down the symptom&lt;/strong> in observable terms: &amp;ldquo;screen share of a full-screen game shows green blocks after about two minutes&amp;rdquo;, not &amp;ldquo;streaming is bad&amp;rdquo;.&lt;/li>
&lt;li>&lt;strong>Record the client version&lt;/strong> and the driver version. Both change often, and a fix that depends on one of them is worth knowing about.&lt;/li>
&lt;li>&lt;strong>Reproduce it once&lt;/strong> before you touch anything, so you know it still happens.&lt;/li>
&lt;li>&lt;strong>Change only the hardware acceleration setting&lt;/strong>, then relaunch.&lt;/li>
&lt;li>&lt;strong>Reproduce the same scenario&lt;/strong> with the same game, resolution and window mode.&lt;/li>
&lt;li>&lt;strong>Revert if nothing changed.&lt;/strong> A setting you changed without evidence is a variable you will trip over later.&lt;/li>
&lt;/ol>
&lt;p>If the symptom clears with acceleration off and returns when you switch it back on, you have a usable answer and a clean trade to make. If it behaves the same either way, the switch is not involved, and the next suspects are the game&amp;rsquo;s display mode, the capture path and the driver.&lt;/p>
&lt;h2 id="when-the-toggle-is-not-the-answer">When the toggle is not the answer&lt;/h2>
&lt;p>Three other problems get mistaken for this one.&lt;/p>
&lt;p>&lt;strong>A client that will not start.&lt;/strong> If Discord never reaches the login screen, or closes during its own launch, hardware acceleration cannot be the cause — the setting is loaded later. Follow the &lt;a href="https://techfuelhq.com/gaming/discord-not-opening-2026/">launch failure guide&lt;/a> instead.&lt;/p>
&lt;p>&lt;strong>Stutter in the game rather than in the stream.&lt;/strong> If your frame times wobble whether or not Discord is running, the client is not your problem. The &lt;a href="https://techfuelhq.com/articles/pc-stuttering-in-games-2026/">stuttering guide&lt;/a> sorts frame pacing from low frame rate, and hardware-accelerated GPU scheduling has its own &lt;a href="https://techfuelhq.com/gaming/hardware-accelerated-gpu-scheduling-on-or-off-2026/">on-or-off decision&lt;/a> that is separate from this one.&lt;/p>
&lt;p>&lt;strong>A picture problem that only appears in the game.&lt;/strong> Tearing and sync behaviour are governed by your display settings, not by Discord. The &lt;a href="https://techfuelhq.com/gaming/vsync-on-or-off-2026/">V-Sync decision&lt;/a> covers that, and it is a different set of switches in a different place.&lt;/p>
&lt;p>My rule is simple: leave the box ticked, and change it only when you can name the symptom it is supposed to fix. If you cannot name the symptom, you do not have a reason yet.&lt;/p></description></item><item><title>Windows 11 Black Screen With a Cursor: What Still Works</title><link>https://techfuelhq.com/articles/windows-11-black-screen-with-cursor-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/windows-11-black-screen-with-cursor-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Black screen with a cursor&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>A cursor that moves is good news.&lt;/strong> It means the graphics card, cable and panel are all still doing their jobs.&lt;/li>
&lt;li>&lt;strong>Restart the shell first:&lt;/strong> Ctrl+Shift+Esc, then right-click Windows Explorer and pick Restart, or File &amp;gt; Run new task and type explorer.exe.&lt;/li>
&lt;li>&lt;strong>No picture but a live cursor after a blink:&lt;/strong> Win+Ctrl+Shift+B resets the display driver, and a Windows log entry records the recovery.&lt;/li>
&lt;li>&lt;strong>Stop at Safe Mode.&lt;/strong> Black there too, or no cursor anywhere, and the fault is below Windows.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>A Windows 11 desktop that goes black while the pointer still glides across it is one of the more misleading failures in PC troubleshooting. Nothing is frozen. The fans are running, the disk light blinks, and the mouse moves, but every window, icon and taskbar button is gone. What you are looking at is a session where Explorer, the process that draws the desktop, has stopped painting, while the rest of the display pipeline keeps working.&lt;/p>
&lt;p>That single observation decides everything after it. A pointer that tracks your hand is drawn on top of whatever the desktop is producing, so the graphics card is scanning out an image and the panel is displaying it. The fault is above the hardware. Work it in this order, and you will usually be back on the desktop in under a minute without touching a driver.&lt;/p>
&lt;h2 id="what-a-visible-cursor-tells-you">What a visible cursor tells you&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">What you see&lt;/th>
&lt;th scope="col">What it points at&lt;/th>
&lt;th scope="col">First check&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="What you see">Cursor moves, everything else is black&lt;/td>
&lt;td data-label="What it points at">Explorer stopped painting&lt;/td>
&lt;td data-label="First check">Restart the desktop process&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you see">Picture blinks and returns on its own&lt;/td>
&lt;td data-label="What it points at">The display driver timed out and recovered&lt;/td>
&lt;td data-label="First check">Driver log, then a clean install&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you see">Cursor moves, black only since a specific update&lt;/td>
&lt;td data-label="What it points at">A change in that update&lt;/td>
&lt;td data-label="First check">Uninstall that update&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you see">Cursor moves, black only with a dock attached&lt;/td>
&lt;td data-label="What it points at">The external display path&lt;/td>
&lt;td data-label="First check">Undock and test the panel alone&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you see">Cursor frozen, or no cursor at all&lt;/td>
&lt;td data-label="What it points at">The display path itself&lt;/td>
&lt;td data-label="First check">The monitor&amp;rsquo;s own menu and a second source&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The last row is the one people skip. A frozen pointer is not a shell problem wearing a disguise; it means Windows is not delivering a usable image, and no amount of Explorer restarting will change that. Take it to the &lt;a href="https://techfuelhq.com/articles/monitor-no-signal-2026/">no-signal guide&lt;/a> and start with the monitor&amp;rsquo;s built-in menu.&lt;/p>
&lt;h2 id="restart-the-shell-from-task-manager">Restart the shell from Task Manager&lt;/h2>
&lt;p>Microsoft&amp;rsquo;s &lt;a href="https://support.microsoft.com/en-us/windows/hardware/display-graphics/troubleshooting-blank-screens-in-windows" rel="noopener">blank-screen troubleshooting article&lt;/a> gives this as the fix for exactly the symptom you are looking at. Press &lt;strong>Ctrl+Shift+Esc&lt;/strong> to open Task Manager, find &lt;strong>Windows Explorer&lt;/strong> in the Processes list, right-click it and choose &lt;strong>Restart&lt;/strong>. If the entry is missing, the same page says to &amp;ldquo;go to File &amp;gt; Run new task, type explorer.exe, and press Enter&amp;rdquo;.&lt;/p>
&lt;p>Two details make the difference between this working and this looking broken:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Task Manager opens on top of a black screen.&lt;/strong> It draws its own window, so it appears even when the desktop does not. If it does not open at all, skip to Safe Mode below.&lt;/li>
&lt;li>&lt;strong>Ctrl+Alt+Delete is the alternate door.&lt;/strong> Microsoft&amp;rsquo;s guidance is that if you see the security screen, launch Task Manager from there and restart Windows Explorer. That route works when the Ctrl+Shift+Esc shortcut is swallowed.&lt;/li>
&lt;/ul>
&lt;p>If the taskbar and icons return, note how long they survive. A desktop that stays up means you had a one-off crash of the shell. A desktop that dies again within minutes means the process is being killed by something that loads with it, and the Safe Mode test later in this article is how you find out whether that something is a startup program, a shell extension or the driver.&lt;/p>
&lt;p>This fix does not survive a reboot, and it is not meant to. It gets you a working desktop so the rest of the checks can be run from Windows instead of from a recovery menu.&lt;/p>
&lt;h2 id="reset-the-display-driver-and-read-the-log">Reset the display driver and read the log&lt;/h2>
&lt;p>Press &lt;strong>Win+Ctrl+Shift+B&lt;/strong>. It resets the graphics driver in place. Microsoft&amp;rsquo;s page describes the expected result precisely: you &amp;ldquo;should hear a beep or see a screen flicker if successful&amp;rdquo;. If your picture returns on that blink, you have learned something specific. The black screen was consistent with a timeout detection and recovery event, which is Windows detecting that the GPU did not finish an operation and resetting the graphics stack to keep the machine responsive.&lt;/p>
&lt;p>Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery" rel="noopener">WDDM driver documentation&lt;/a> explains the default behaviour: the operating system waits two seconds for the GPU to complete or preempt a task, and if it cannot, the OS diagnoses the GPU as frozen and resets it. When that completes, the OS displays an informational message, &amp;ldquo;Display driver stopped responding and has recovered&amp;rdquo;, and logs that message in Event Viewer.&lt;/p>
&lt;p>That log line is worth finding, because it is the difference between a theory and a record:&lt;/p>
&lt;ol>
&lt;li>Open &lt;strong>Event Viewer&lt;/strong> (press Win+R, type &lt;code>eventvwr.msc&lt;/code>, press Enter).&lt;/li>
&lt;li>Go to &lt;strong>Windows Logs &amp;gt; Application&lt;/strong>.&lt;/li>
&lt;li>Press &lt;strong>Ctrl+F&lt;/strong> and search for &lt;code>Display driver stopped responding&lt;/code>.&lt;/li>
&lt;/ol>
&lt;p>Read the timestamp. If it matches the moment your screen went black, you have a driver recovery on record, and the clean reinstall further down is the right repair. If the log is empty at that time, that is not proof of anything by itself. It only means this particular mechanism left no entry you can find.&lt;/p>
&lt;p>One more line from Microsoft&amp;rsquo;s documentation explains a symptom that confuses people after a successful recovery: &amp;ldquo;Some legacy DirectX applications might just render black at the end of this recovery, which requires the end user to restart these applications.&amp;rdquo; So if the desktop comes back but one game or one window is still a black rectangle, close and reopen that application before you conclude anything about the GPU.&lt;/p>
&lt;h2 id="safe-mode-is-the-test-that-separates-shell-from-firmware">Safe Mode is the test that separates shell from firmware&lt;/h2>
&lt;p>Safe Mode answers one question and answers it well: does this still happen with a minimal Windows? Microsoft&amp;rsquo;s &lt;a href="https://support.microsoft.com/en-us/windows/experience/startup-boot/windows-startup-settings" rel="noopener">Startup Settings page&lt;/a> states that &amp;ldquo;Safe mode starts Windows in a basic state, using a limited set of files and drivers&amp;rdquo;, and adds that a problem which does not occur there is likely not caused by default settings or basic drivers.&lt;/p>
&lt;p>You can reach it two ways, depending on whether you have a desktop to click on:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>From a working desktop, or from Task Manager&amp;rsquo;s File &amp;gt; Run new task if you can reach Settings:&lt;/strong> go to &lt;strong>Settings &amp;gt; System &amp;gt; Recovery &amp;gt; Advanced startup&lt;/strong> and select &lt;strong>Restart now&lt;/strong>, which Microsoft documents on its &lt;a href="https://support.microsoft.com/en-us/windows/experience/backup-recovery/recovery-options-in-windows" rel="noopener">recovery options page&lt;/a>.&lt;/li>
&lt;li>&lt;strong>When the desktop is dead:&lt;/strong> hold the power button for ten seconds, repeat two or three times until Windows enters Recovery Mode, then choose &lt;strong>Troubleshoot &amp;gt; Advanced Options &amp;gt; Startup Settings &amp;gt; Restart&lt;/strong>. On the Startup Settings screen, &lt;strong>F5&lt;/strong> starts Safe Mode with Networking according to Microsoft&amp;rsquo;s blank-screen page, while &lt;strong>4&lt;/strong> or &lt;strong>F4&lt;/strong> selects plain Safe Mode on the Startup Settings page.&lt;/li>
&lt;/ul>
&lt;p>Read the result carefully:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Safe Mode result&lt;/th>
&lt;th scope="col">What it means&lt;/th>
&lt;th scope="col">Next step&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Safe Mode result">Desktop draws normally&lt;/td>
&lt;td data-label="What it means">The shell works with a minimal driver set&lt;/td>
&lt;td data-label="Next step">The conflict loads with the normal driver set or a startup program&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Safe Mode result">Black screen, cursor still moves&lt;/td>
&lt;td data-label="What it means">Not a third-party startup app&lt;/td>
&lt;td data-label="Next step">Roll back or reinstall the display driver&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Safe Mode result">Black screen, no cursor&lt;/td>
&lt;td data-label="What it means">Not a Windows shell problem&lt;/td>
&lt;td data-label="Next step">Stop and test the display path&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>In the middle case, roll the driver back before you remove it. Microsoft&amp;rsquo;s blank-screen page says that if the issue started after an update, select &lt;strong>Roll back driver&lt;/strong> — you reach it through &lt;strong>Device Manager &amp;gt; Display adapters &amp;gt; your GPU &amp;gt; Properties &amp;gt; Driver&lt;/strong>. If no previous driver is stored, the clean install below is the alternative.&lt;/p>
&lt;h2 id="disconnect-docks-and-extra-displays">Disconnect docks and extra displays&lt;/h2>
&lt;p>A dock or an external monitor can leave a laptop panel dark while Windows happily believes it is drawing to a working screen. Microsoft&amp;rsquo;s page is blunt about the test: &amp;ldquo;If using a laptop, disconnect external displays and peripherals.&amp;rdquo; It also suggests cycling display modes with &lt;strong>Win+P&lt;/strong>, which is faster than unplugging and often enough to bring the internal panel back.&lt;/p>
&lt;p>If the internal panel lights up the moment the dock is out, you are not troubleshooting Windows any more. The desktop is fine; the external path is not. Work that with the &lt;a href="https://techfuelhq.com/articles/windows-11-not-detecting-second-monitor-2026/">second-monitor detection checks&lt;/a>, and if the external screen drops and returns rather than staying dark, the &lt;a href="https://techfuelhq.com/articles/monitor-keeps-going-black-2026/">random blackout guide&lt;/a> matches the symptom better.&lt;/p>
&lt;p>The inverse is also worth stating, because it sends people down the wrong path: if one monitor is black and the other shows your desktop, this article does not apply. A shell failure blanks every display at once.&lt;/p>
&lt;h2 id="remove-the-update-that-started-it">Remove the update that started it&lt;/h2>
&lt;p>If the timeline points at an update, undo that update rather than the whole system. Microsoft&amp;rsquo;s &lt;a href="https://support.microsoft.com/en-us/windows/deployment/updates-lifecycle/how-to-uninstall-a-windows-update" rel="noopener">uninstall guide&lt;/a> gives the Windows 11 route: &lt;strong>Start &amp;gt; Settings &amp;gt; Windows Update&lt;/strong>, then under &lt;strong>More options&lt;/strong> choose &lt;strong>Update history&lt;/strong>, and under &lt;strong>Related settings&lt;/strong> choose &lt;strong>Uninstall updates&lt;/strong>, select the update and choose &lt;strong>Uninstall&lt;/strong>.&lt;/p>
&lt;p>When you cannot get into Settings far enough to click anything, the same page documents the recovery-environment equivalent: reach &lt;strong>Windows RE&lt;/strong>, then &lt;strong>Troubleshoot &amp;gt; Advanced options &amp;gt; Uninstall updates&lt;/strong>, and select the option for the latest quality update.&lt;/p>
&lt;p>Two cautions come from the same page and are easy to skip in a hurry. Some updates cannot be uninstalled, and Microsoft warns that you should understand the risks of removing a security update, recommending that Windows 11 users try reinstalling Windows before going that route. I would add a practical one: write down the KB number and the date before you remove anything, because if the black screen returns you will want to know exactly which change you reversed.&lt;/p>
&lt;p>Unlike the shell restart, this one survives a reboot. That is the point of doing it.&lt;/p>
&lt;h2 id="clean-driver-reinstall-and-when-to-stop">Clean driver reinstall, and when to stop&lt;/h2>
&lt;p>A clean install is the right repair when you have a driver recovery on record, a black desktop that began after a driver update, or a shell that fails in Safe Mode with a normal driver set loaded. The sequence:&lt;/p>
&lt;ol>
&lt;li>Download the current driver for your exact card from the vendor&amp;rsquo;s site and leave the installer on the desktop.&lt;/li>
&lt;li>Boot to Safe Mode using the path above.&lt;/li>
&lt;li>Run &lt;a href="https://www.wagnardsoft.com/" rel="noopener">Display Driver Uninstaller&lt;/a> to remove the existing driver, choosing the clean-and-restart option for your vendor.&lt;/li>
&lt;li>Install the downloaded driver after the reboot, then test the desktop for a full session.&lt;/li>
&lt;/ol>
&lt;p>Do not stack a driver reinstall on top of three other changes. One change, one observation, recorded. The &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">Diagnostic Workbench&lt;/a> keeps those observations in order if you expect to hand the machine to someone else.&lt;/p>
&lt;h3 id="when-to-stop">When to stop&lt;/h3>
&lt;p>Stop testing software the moment one of these is true.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>The screen is black in Safe Mode.&lt;/strong> Safe Mode strips the startup programs and third-party drivers, so a failure that follows you there is not a shell extension problem.&lt;/li>
&lt;li>&lt;strong>There is no cursor at any point, or it freezes.&lt;/strong> The pointer is your proof that the display is working. Without it, the cable, the output, the panel or the firmware is the suspect, and &lt;a href="https://techfuelhq.com/articles/monitor-no-signal-2026/">monitor says no signal&lt;/a> is the right guide.&lt;/li>
&lt;li>&lt;strong>The motherboard logo never appears at power-on.&lt;/strong> If the firmware splash does not show, Windows has not started drawing anything yet, so no Windows repair can be the answer.&lt;/li>
&lt;li>&lt;strong>The same driver recovery repeats at stock clocks with a clean install.&lt;/strong> Repeated recoveries point at hardware, power delivery or thermals rather than the driver, and the &lt;a href="https://techfuelhq.com/articles/gpu-driver-crash-fix-2026/">GPU driver crash guide&lt;/a> covers that lane.&lt;/li>
&lt;/ul>
&lt;p>At that point the useful thing to carry to a repair desk is a short record: the Safe Mode result, whether a cursor was present, the driver log entry and its timestamp, and the update history around the date the problem started. That is worth more than a list of settings you changed.&lt;/p></description></item><item><title>Ryzen 7 9700X vs 9800X3D: Which One Should You Buy?</title><link>https://techfuelhq.com/articles/ryzen-7-9700x-vs-9800x3d-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/ryzen-7-9700x-vs-9800x3d-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Ryzen 7 9700X vs Ryzen 7 9800X3D&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Gaming-first build, fast GPU, 1080p or high-refresh 1440p:&lt;/strong> the Ryzen 7 9800X3D. TechSpot's 14-game suite put it 30% ahead of the 9700X on average.&lt;/li>
&lt;li>&lt;strong>Fixed total budget, mid-range GPU, or 1440p/4K gaming:&lt;/strong> the Ryzen 7 9700X. Same socket, same eight cores, 65 W instead of 120 W.&lt;/li>
&lt;li>&lt;strong>The one structural difference is cache:&lt;/strong> 96 MB of L3 on the 9800X3D against 32 MB on the 9700X.&lt;/li>
&lt;li>&lt;strong>Neither ships a cooler.&lt;/strong> AMD asks for a premium air cooler on the 9700X and a liquid cooler on the 9800X3D.&lt;/li>
&lt;li>&lt;strong>Already own either one?&lt;/strong> Keep it. Nothing here justifies a sideways swap.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>These two processors are the same chip wearing different hats. Both are eight-core, sixteen-thread Zen 5 parts on socket AM5, both take DDR5-5600 and the same motherboards, and both are unlocked. Only one of them has a 96 MB stack of cache sitting where the heat used to go, and only one of them costs real money for it.&lt;/p>
&lt;p>The short version: the Ryzen 7 9800X3D is the gaming answer and the Ryzen 7 9700X is the budget answer, and the gap between those two statements is 30% in the suite everyone quotes and close to 0% in the situations many people actually play in.&lt;/p>
&lt;h2 id="what-actually-differs-between-the-9700x-and-9800x3d">What actually differs between the 9700X and 9800X3D&lt;/h2>
&lt;p>Everything below is from AMD&amp;rsquo;s two specification pages. There is no guesswork in this table.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Specification&lt;/th>
&lt;th scope="col">Ryzen 7 9700X&lt;/th>
&lt;th scope="col">Ryzen 7 9800X3D&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Specification">Architecture&lt;/td>
&lt;td data-label="Ryzen 7 9700X">Zen 5&lt;/td>
&lt;td data-label="Ryzen 7 9800X3D">Zen 5, second-gen 3D V-Cache&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Cores / threads&lt;/td>
&lt;td data-label="Ryzen 7 9700X">8 / 16&lt;/td>
&lt;td data-label="Ryzen 7 9800X3D">8 / 16&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Base clock&lt;/td>
&lt;td data-label="Ryzen 7 9700X">3.8 GHz&lt;/td>
&lt;td data-label="Ryzen 7 9800X3D">4.7 GHz&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Max boost&lt;/td>
&lt;td data-label="Ryzen 7 9700X">Up to 5.5 GHz&lt;/td>
&lt;td data-label="Ryzen 7 9800X3D">Up to 5.2 GHz&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">L2 cache&lt;/td>
&lt;td data-label="Ryzen 7 9700X">8 MB&lt;/td>
&lt;td data-label="Ryzen 7 9800X3D">8 MB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">L3 cache&lt;/td>
&lt;td data-label="Ryzen 7 9700X">32 MB&lt;/td>
&lt;td data-label="Ryzen 7 9800X3D">96 MB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Default TDP&lt;/td>
&lt;td data-label="Ryzen 7 9700X">65 W&lt;/td>
&lt;td data-label="Ryzen 7 9800X3D">120 W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">AMD&amp;rsquo;s cooler guidance&lt;/td>
&lt;td data-label="Ryzen 7 9700X">Premium air cooler&lt;/td>
&lt;td data-label="Ryzen 7 9800X3D">Liquid cooler&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Cooler in the box&lt;/td>
&lt;td data-label="Ryzen 7 9700X">None&lt;/td>
&lt;td data-label="Ryzen 7 9800X3D">None&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Socket / memory&lt;/td>
&lt;td data-label="Ryzen 7 9700X">AM5 / DDR5-5600&lt;/td>
&lt;td data-label="Ryzen 7 9800X3D">AM5 / DDR5-5600&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Max memory&lt;/td>
&lt;td data-label="Ryzen 7 9700X">256 GB&lt;/td>
&lt;td data-label="Ryzen 7 9800X3D">256 GB&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">PCIe 5.0 lanes (total / usable)&lt;/td>
&lt;td data-label="Ryzen 7 9700X">28 / 24&lt;/td>
&lt;td data-label="Ryzen 7 9800X3D">28 / 24&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Max operating temperature&lt;/td>
&lt;td data-label="Ryzen 7 9700X">95 °C&lt;/td>
&lt;td data-label="Ryzen 7 9800X3D">95 °C&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Launch date&lt;/td>
&lt;td data-label="Ryzen 7 9700X">August 8, 2024&lt;/td>
&lt;td data-label="Ryzen 7 9800X3D">November 7, 2024&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Read the clock rows again, because they are the part people get backwards. The 9700X boosts higher on paper, 5.5 GHz against 5.2 GHz, yet &lt;a href="https://www.amd.com/en/products/processors/desktops/ryzen/9000-series/amd-ryzen-7-9800x3d.html" rel="noopener">AMD&amp;rsquo;s 9800X3D page&lt;/a> and &lt;a href="https://www.amd.com/en/products/processors/desktops/ryzen/9000-series/amd-ryzen-7-9700x.html" rel="noopener">its 9700X page&lt;/a> list the X3D part with a much higher base clock, 4.7 GHz versus 3.8 GHz.&lt;/p>
&lt;p>That is not a typo, and it is the direct consequence of how AMD built the second generation of 3D V-Cache. In the first generation the cache sat on top of the cores and acted as a blanket over them. AMD flipped the stack so the cores sit above the cache, and &lt;a href="https://www.techspot.com/review/2915-amd-ryzen-7-9800x3d/" rel="noopener">TechSpot reports&lt;/a> that AMD puts the reduction in thermal resistance at 46%. Cooler cores clock higher, which is why the gaming chip has the fatter base clock despite the lower ceiling.&lt;/p>
&lt;p>Everything else in the table is a wash. Same core count, same L2, same memory controller, same PCIe lane budget, same maximum capacity, same motherboards. You are not buying a bigger platform when you buy the 9800X3D. You are buying 64 MB more cache and a 55 W higher power limit.&lt;/p>
&lt;h2 id="what-the-extra-cache-does-in-games">What the extra cache does in games&lt;/h2>
&lt;p>The cleanest number I can give you comes from &lt;a href="https://www.techspot.com/review/2915-amd-ryzen-7-9800x3d/" rel="noopener">TechSpot&amp;rsquo;s 14-game CPU suite&lt;/a>, run on an RTX 4090 with both chips on the same motherboard, the same Windows build and the same DDR5-6000 memory. Across that per-game comparison the 9800X3D averaged 30% faster than the 9700X. Half the games moved by 30% or more, and a handful moved by around 45%.&lt;/p>
&lt;p>The spread is the useful part:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">TechSpot test&lt;/th>
&lt;th scope="col" style="text-align: right">9800X3D lead over the 9700X&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="TechSpot test">Homeworld 3&lt;/td>
&lt;td style="text-align: right" data-label="9800X3D lead over the 9700X">46%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="TechSpot test">Cyberpunk 2077&lt;/td>
&lt;td style="text-align: right" data-label="9800X3D lead over the 9700X">35% (for 11% more power)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="TechSpot test">Counter-Strike 2&lt;/td>
&lt;td style="text-align: right" data-label="9800X3D lead over the 9700X">27%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="TechSpot test">Remnant II&lt;/td>
&lt;td style="text-align: right" data-label="9800X3D lead over the 9700X">25%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="TechSpot test">A Plague Tale: Requiem&lt;/td>
&lt;td style="text-align: right" data-label="9800X3D lead over the 9700X">20%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="TechSpot test">The Last of Us Part 1&lt;/td>
&lt;td style="text-align: right" data-label="9800X3D lead over the 9700X">16% (at the same 95 W as the 9700X)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="TechSpot test">Star Wars Outlaws&lt;/td>
&lt;td style="text-align: right" data-label="9800X3D lead over the 9700X">10%&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="TechSpot test">14-game average&lt;/td>
&lt;td style="text-align: right" data-label="9800X3D lead over the 9700X">30%&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Two details in that table matter more than the headline. Star Wars Outlaws is the floor at 10%, and TechSpot labels it a CPU-limited title with a dense NPC area capped around 142 fps. Homeworld 3 is the ceiling at 46%, and it is the kind of simulation that lives inside a big cache. If your library looks like the ceiling, the 9800X3D is a large upgrade. If it looks like the floor, it is a small one.&lt;/p>
&lt;p>Tom&amp;rsquo;s Hardware&amp;rsquo;s own &lt;a href="https://www.tomshardware.com/pc-components/cpus/amd-ryzen-7-9800x3d-review-devastating-gaming-performance/2" rel="noopener">13-game 1080p suite on an RTX 4090&lt;/a> lands in the same place from the other direction. It measured the 9800X3D running at an average of 5.2 GHz with 1% lows of 148 fps, and it is careful to say that not every game benefits from 3D V-Cache, either because of the game code or because the GPU is the limit. Even in GPU-limited scenes it credits the bigger cache with better 1% lows, which is the stutter metric rather than the average.&lt;/p>
&lt;p>A single aggregate ranking hides how much the cache advantage depends on the game and settings. I would use the per-game results above as a better guide than treating one overall score as a promise for every title.&lt;/p>
&lt;h2 id="the-resolution-question-answered-honestly">The resolution question, answered honestly&lt;/h2>
&lt;p>A 30% average is a number from a 1080p CPU test bed with a flagship graphics card, and it does not transfer to every machine.&lt;/p>
&lt;p>The mechanism is simple. The 9800X3D wins by feeding the GPU faster, so the gain only appears where the GPU is waiting on the CPU. Drop to a mid-range card, raise the resolution to 1440p or 4K, and most games become GPU-bound. At that point both processors deliver the same frame rate because the limit moved. TechSpot&amp;rsquo;s tests are built to expose CPU limits, and Tom&amp;rsquo;s Hardware says the same thing in different words when it explains that some titles gain nothing from the cache.&lt;/p>
&lt;p>So the resolution plays a role, but the graphics card plays the bigger one. A 9700X paired with an RTX 5080 at 4K is not leaving meaningful performance on the table. A 9700X paired with an RTX 5080 at 1080p on a 360 Hz monitor is leaving a lot on the table, and that is the configuration where the 9800X3D earns its price.&lt;/p>
&lt;p>My rule is to spend on the cache only after the GPU is settled. If you are choosing between a 9700X plus a better graphics card and a 9800X3D plus a worse one, take the graphics card every time. The &lt;a href="https://techfuelhq.com/tools/pc-bottleneck-calculator/">CPU and GPU balance check in our bottleneck calculator&lt;/a> is built for exactly that comparison, and the &lt;a href="https://techfuelhq.com/articles/cpu-hierarchy-2026/">2026 CPU hierarchy&lt;/a> shows where both chips sit against everything else.&lt;/p>
&lt;h2 id="power-cooling-and-the-rest-of-the-build">Power, cooling and the rest of the build&lt;/h2>
&lt;p>The 9800X3D is the thirstier part, but not dramatically so in games.&lt;/p>
&lt;p>TechSpot measured 118 W of average package power in Cinebench 2024, and separately 128 W drawn through the EPS12V rails for the same multi-core run, with the compute dies never exceeding 79 °C and the cache sitting at 56 °C on a 360 mm liquid cooler. In games the picture is milder: 93 W in Cyberpunk 2077, where it delivered 35% more performance than the 9700X for 11% more power, and 95 W in The Last of Us Part 1, exactly what the 9700X drew in the same test while going 16% faster.&lt;/p>
&lt;p>That efficiency story is the argument for the X3D part beyond raw frame rate. It does more work per watt in games than the chip with the higher boost clock.&lt;/p>
&lt;p>The 9700X, for its part, is a 65 W part that AMD says will run on a premium air cooler, and that is a real budget line. A quiet tower cooler is enough, and the whole build can stay small. The 9800X3D wants liquid cooling according to AMD, though a large dual-tower air cooler is what many builders actually use. Neither box includes a heatsink, so the cooler is a line item either way.&lt;/p>
&lt;p>Motherboards are identical. AMD lists the same chipset support for both, from B650 through X870E, so there is no platform tax for the gaming chip. If you are building around the 9800X3D specifically, our &lt;a href="https://techfuelhq.com/articles/best-motherboard-ryzen-7-9800x3d-2026/">motherboard shortlist for that chip&lt;/a> covers which boards are worth the money, and the &lt;a href="https://techfuelhq.com/articles/ddr5-6000-cl30-explained-2026/">DDR5-6000 CL30 explainer&lt;/a> covers the memory kit question. Tom&amp;rsquo;s measured DDR5-6000 against DDR5-5600 on the 9800X3D and found a 1.8% average gain, which is a cheap 1.8% compared with the cost of the CPU upgrade itself.&lt;/p>
&lt;p>One more power note. Enabling Precision Boost Overdrive on the 9800X3D netted Tom&amp;rsquo;s Hardware about 2.6% more performance and TechSpot a 2.5% Cinebench gain for a 20% increase in power draw. I would leave it off. The cache is doing the work; the overclock is not.&lt;/p>
&lt;h2 id="who-should-buy-which">Who should buy which&lt;/h2>
&lt;p>&lt;strong>Buy the Ryzen 7 9800X3D if:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>Your graphics card is at or above the RTX 5070 / RX 9070 tier and you game at 1080p or on a 1440p high-refresh panel.&lt;/li>
&lt;li>Your library is CPU-heavy: simulation, strategy, MMO crowds, esports at high frame rates.&lt;/li>
&lt;li>You care about 1% lows and frame-time consistency as much as the average.&lt;/li>
&lt;li>The CPU is not competing with the GPU for the same money.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Buy the Ryzen 7 9700X if:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>You are building to a fixed total and the CPU savings buy a better graphics card.&lt;/li>
&lt;li>You game at 1440p or 4K on a mid-range GPU, where the CPU difference largely disappears.&lt;/li>
&lt;li>You want a 65 W part that runs quietly in a small case.&lt;/li>
&lt;li>You need eight cores for general work and gaming is secondary.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Keep what you own if&lt;/strong> you already have either chip. A 9700X owner gains nothing by swapping sideways, and a 9800X3D owner has no reason to move at all. If you are coming from AM4 or an older AM5 part, the &lt;a href="https://techfuelhq.com/articles/ryzen-5-9600x-vs-ryzen-7-9700x/">9600X versus 9700X comparison&lt;/a> covers the cheaper entry point, and the &lt;a href="https://techfuelhq.com/reviews/ryzen-7-9800x3d-review-2026/">full 9800X3D review&lt;/a> covers the chip in isolation.&lt;/p>
&lt;p>For the build this page is really about, the gaming-first machine with a fast card and a high-refresh display, the cache is the part that pays you back every session. That is the configuration where I would spend the extra.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=AMD&amp;#43;Ryzen&amp;#43;7&amp;#43;9800X3D&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/ryzen-7-9700x-vs-9800x3d-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DAMD%2BRyzen%2B7%2B9800X3D" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/ryzen-7-9700x-vs-9800x3d-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>If you landed on the other side of the decision, the 9700X is selectable in the &lt;a href="https://techfuelhq.com/tools/cpu-comparison/">CPU comparison tool&lt;/a> against any chip in our dataset, and the &lt;a href="https://techfuelhq.com/tools/pc-builder/">PC Builder&lt;/a> will hold the rest of the parts list while you decide where the money goes.&lt;/p></description></item><item><title>RTX 5060 Ti 8GB vs 16GB: The VRAM Cliff Tested</title><link>https://techfuelhq.com/articles/rtx-5060-ti-8gb-vs-16gb-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/rtx-5060-ti-8gb-vs-16gb-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · RTX 5060 Ti 8GB vs 16GB&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Want high textures or 1440p headroom?&lt;/strong> Choose the 16GB model; a real capacity shortfall can cause major frame-time drops.&lt;/li>
&lt;li>&lt;strong>Have a hard budget and mostly play at 1080p?&lt;/strong> The 8GB version can work if you are comfortable reducing texture settings when needed.&lt;/li>
&lt;li>&lt;strong>The graphics processor is the same.&lt;/strong> Both versions have 4,608 CUDA cores, GDDR7 and a 128-bit memory bus.&lt;/li>
&lt;li>&lt;strong>Do not mistake one bad out-of-memory result for a universal average.&lt;/strong> The difference depends on the game, settings and whether the local VRAM limit is reached.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>If you are looking at an RTX 5060 Ti, you are choosing between two cards with the same name, nearly the same board design, and one difference that can turn into a massive performance gap. The 16GB model costs more in stores; I am not quoting a live price here because it changes by vendor and date. What matters is whether your games can stay inside 8GB of local memory.&lt;/p>
&lt;p>My short answer is the 16GB card for anyone who wants to run high textures, play new releases at 1440p, or keep the card for several years. The 8GB version makes sense only when the lower purchase cost is important and you are willing to adjust graphics settings. It is not a faster-or-slower GPU contest in the usual sense. The capacity wall is the deciding factor.&lt;/p>
&lt;h2 id="what-is-different-between-the-8gb-and-16gb-versions">What is different between the 8GB and 16GB versions&lt;/h2>
&lt;p>NVIDIA&amp;rsquo;s &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5060-family/" rel="noopener">RTX 5060 family specification page&lt;/a> lists two memory configurations for the RTX 5060 Ti. The important GPU-side specifications remain the same.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Specification&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5060 Ti 8GB&lt;/th>
&lt;th scope="col" style="text-align: right">RTX 5060 Ti 16GB&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Specification">CUDA cores&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5060 Ti 8GB">4,608&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5060 Ti 16GB">4,608&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Boost clock&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5060 Ti 8GB">2.57 GHz&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5060 Ti 16GB">2.57 GHz&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Video memory&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5060 Ti 8GB">8GB GDDR7&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5060 Ti 16GB">16GB GDDR7&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Memory interface&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5060 Ti 8GB">128-bit&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5060 Ti 16GB">128-bit&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Memory bandwidth&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5060 Ti 8GB">448 GB/s&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5060 Ti 16GB">448 GB/s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">PCIe interface&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5060 Ti 8GB">PCIe 5.0 x8&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5060 Ti 16GB">PCIe 5.0 x8&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Total graphics power&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5060 Ti 8GB">180 W&lt;/td>
&lt;td style="text-align: right" data-label="RTX 5060 Ti 16GB">180 W&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>This is not like comparing an RTX 5060 to an RTX 5060 Ti, where the GPU itself changes. The two 5060 Ti versions have the same listed cores and memory bus. The 16GB board does not double the memory bandwidth; it doubles the amount of memory available to keep textures, geometry and other game assets close to the GPU.&lt;/p>
&lt;p>That difference is normally invisible while a game&amp;rsquo;s active data fits inside 8GB. Once it does not, the driver and game engine must find somewhere else to put assets. Some data can be evicted, textures can be streamed, or assets can move through system memory. Those workarounds keep the game running, but they are not free. The frame rate can fall and frame delivery can become uneven, even when the average looks passable.&lt;/p>
&lt;p>NVIDIA&amp;rsquo;s &lt;a href="https://www.nvidia.com/en-us/geforce/news/rtx-5060-desktop-family-laptop-5060-coming-soon/" rel="noopener">April 2025 RTX 5060 family announcement&lt;/a> introduced the product family, while Tom&amp;rsquo;s Hardware&amp;rsquo;s &lt;a href="https://www.tomshardware.com/pc-components/gpus/nvidia-geforce-rtx-5060-ti-16gb-review" rel="noopener">RTX 5060 Ti 16GB review&lt;/a> covers the card as a conventional gaming GPU. The capacity-specific evidence is more revealing: TechSpot tested both versions directly in workloads that stress memory.&lt;/p>
&lt;h2 id="when-the-8gb-limit-becomes-a-performance-cliff">When the 8GB limit becomes a performance cliff&lt;/h2>
&lt;p>The clearest example comes from &lt;a href="https://www.techspot.com/review/3004-nvidia-rtx-5060-ti-pcie-benchmark/" rel="noopener">TechSpot&amp;rsquo;s six-game 8GB-versus-16GB test&lt;/a>. In Dragon Age: The Veilguard, both models were tested on PCIe 3.0. The 16GB card averaged 66 frames per second with a 47 fps 1% low. The 8GB card averaged 27 fps, and its 1% low dropped to 9 fps. That is not a normal, small difference between two GPU models; it is a memory-capacity limit showing up as lost performance and rough frame pacing.&lt;/p>
&lt;p>The same review shows why the conclusion needs a boundary. On some games and settings, the 8GB card remained playable, especially when PCIe bandwidth was higher or the settings did not push as hard against the memory limit. In The Last of Us Part II, the 8GB version could reach the 16GB model&amp;rsquo;s average with PCIe 5.0, although the review notes frame-time inconsistency for the smaller-memory card. These are game-specific results, not a guarantee that PCIe 5.0 or a particular setting will rescue every title.&lt;/p>
&lt;p>Monster Hunter Wilds made the point at high visual quality. TechSpot found that its ultra preset needed more than 8GB even at 1080p; the 16GB card averaged 84 fps in that test, compared with 34 fps for the 8GB card, whose 1% lows fell to 16 fps. The resolution is not the only variable. Texture quality and the game engine&amp;rsquo;s memory footprint can matter more than whether the display is 1080p or 1440p.&lt;/p>
&lt;p>When VRAM fills, extra system memory bandwidth can help only at the margins. TechSpot explains that the RTX 5060 Ti has an eight-lane PCIe interface. When the GPU must move assets through system memory, the bandwidth available over that link is far below the 448 GB/s of its local video memory, and system memory also adds latency. A faster PCIe generation improves that fallback path but does not make it equivalent to having enough VRAM on the card.&lt;/p>
&lt;p>Tom&amp;rsquo;s Hardware&amp;rsquo;s &lt;a href="https://www.tomshardware.com/reviews/gpu-hierarchy,4388.html" rel="noopener">GPU hierarchy&lt;/a> and 16GB review help set the broader performance context, but averages across games can hide the capacity-specific outliers. If your library contains games where the 8GB model falls off a cliff, an overall ranking is not the most useful buying signal. The direct memory-pressure tests are.&lt;/p>
&lt;h2 id="what-the-extra-memory-does-and-does-not-buy">What the extra memory does and does not buy&lt;/h2>
&lt;p>The 16GB model does not make every game run twice as fast. It does not change the shader count, turn the card into a higher-tier GPU, or guarantee higher averages when 8GB is sufficient. In ordinary workloads that fit inside local memory, these two configurations should behave much more alike than a pair of GPUs with different core counts.&lt;/p>
&lt;p>The 16GB version buys margin. It lets a game keep larger texture sets resident and reduces the chance that the driver has to shuffle data back and forth between local video memory and system memory. That margin can show up as better 1% lows, fewer sudden frame-time spikes, or the ability to keep a higher texture preset enabled. The benefit depends on a workload actually using the space.&lt;/p>
&lt;p>That distinction also explains why the same game can produce different advice at different settings. A low or medium texture preset may fit within 8GB; a higher preset can exceed it. A reviewer can therefore report a respectable average for the 8GB card in one run and a severe slowdown in a more demanding run without either result being contradictory. The setting changed the memory footprint.&lt;/p>
&lt;p>Do not use a VRAM meter alone as proof that a game needs more memory. Some titles reserve memory aggressively, and allocation is not the same as active use. Look for corroborating behavior: a large gap against the 16GB model at matching settings, poor 1% lows, visible texture pop-in, or stutter that improves when you lower texture quality. TechSpot&amp;rsquo;s controlled side-by-side tests are valuable because the rest of the card is so similar.&lt;/p>
&lt;p>The 16GB option is most useful when the card needs to serve as a general-purpose gaming GPU rather than a narrow esports card. New single-player games, high-resolution texture packs and long ownership periods all increase the odds that you will meet a memory-heavy workload. The 8GB version is less fragile in older games, competitive titles and lower settings. None of those are promises about every new release; they are the reason to match capacity to the games you actually play.&lt;/p>
&lt;h2 id="which-one-should-you-buy">Which one should you buy?&lt;/h2>
&lt;p>&lt;strong>Choose the RTX 5060 Ti 16GB if:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>You want to use high or ultra texture settings without checking every game&amp;rsquo;s memory use first.&lt;/li>
&lt;li>You play demanding new releases at 1440p, or you prefer a card with more room for future games.&lt;/li>
&lt;li>You would rather pay once for extra capacity than troubleshoot stutter by lowering settings later.&lt;/li>
&lt;li>The cost difference is manageable within the build budget.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Choose the RTX 5060 Ti 8GB only if:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>The lower purchase cost matters more than a safety margin for future games.&lt;/li>
&lt;li>Your usual games are esports, older releases, or titles you are happy to run at lower texture settings.&lt;/li>
&lt;li>You understand that a game can be GPU-fast enough but still struggle when its memory footprint exceeds 8GB.&lt;/li>
&lt;li>You are comfortable adjusting settings after a game update or a new release exposes the limit.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Do not replace an 8GB card just because the 16GB model exists.&lt;/strong> If your current games run smoothly at the settings you like, there is no universal average-rate bonus waiting for you. Upgrade when you can point to a real problem: sustained stutter, a texture preset you cannot use, or a title that repeatedly runs out of local memory. Our &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5060-ti-vs-rtx-5070-2026/">RTX 5060 Ti vs RTX 5070 comparison&lt;/a> helps with the next GPU tier, and the &lt;a href="https://techfuelhq.com/articles/gpu-hierarchy-2026/">GPU hierarchy&lt;/a> shows where the card sits in broader testing.&lt;/p>
&lt;p>For a new build where the RTX 5060 Ti is the target, I would pick the 16GB model unless the cheaper 8GB version is the difference between completing the build and not. More memory is not a substitute for a faster GPU, but on this specific card it is the version that avoids the sharpest failure mode.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=RTX&amp;#43;5060&amp;#43;Ti&amp;#43;16GB&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/rtx-5060-ti-8gb-vs-16gb-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DRTX%2B5060%2BTi%2B16GB" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/rtx-5060-ti-8gb-vs-16gb-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>Before picking a board partner, compare the exact card dimensions and power connector against your case and power supply. For other value options, use our &lt;a href="https://techfuelhq.com/articles/best-budget-gpu-2026/">best budget GPU guide&lt;/a> and the &lt;a href="https://techfuelhq.com/tools/gpu-comparison/">GPU comparison tool&lt;/a> to compare the 5060 Ti with cards at its level.&lt;/p></description></item><item><title>RTX 5050 vs RTX 4060: Is the Newer 8GB Card Worth It?</title><link>https://techfuelhq.com/articles/rtx-5050-vs-rtx-4060-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/rtx-5050-vs-rtx-4060-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · RTX 5050 vs RTX 4060&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Already own an RTX 4060?&lt;/strong> Keep it. The RTX 5050 is not a meaningful gaming upgrade.&lt;/li>
&lt;li>&lt;strong>Building a new budget PC?&lt;/strong> Compare the two exact board prices and features; published 1080p suites place them in roughly the same performance class.&lt;/li>
&lt;li>&lt;strong>Both are 8GB cards.&lt;/strong> Neither escapes texture-memory limits in demanding games.&lt;/li>
&lt;li>&lt;strong>The RTX 5050 is newer, not automatically faster.&lt;/strong> Blackwell features are its main differentiator; the RTX 4060 has more CUDA cores.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>The RTX 5050 is newer than the RTX 4060, but that does not make it a clear replacement. Both cards have 8GB of memory, and the published game tests put them in the same general performance tier. The RTX 5050 can make sense in a new entry-level build when you want its newer features, but I would not replace an RTX 4060 expecting a meaningful jump in frame rate.&lt;/p>
&lt;p>The short version: compare the actual cards available to you, including their prices, cooler sizes and outputs. If one is notably cheaper, the better buy depends on that live deal; I am not publishing stale price snapshots. If the two are close, choose based on the features you will use. Do not buy the RTX 5050 simply because the model number is higher.&lt;/p>
&lt;h2 id="what-changes-between-the-rtx-5050-and-rtx-4060">What changes between the RTX 5050 and RTX 4060&lt;/h2>
&lt;p>NVIDIA&amp;rsquo;s &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5050/" rel="noopener">RTX 5050 specification page&lt;/a> and &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/40-series/rtx-4060-4060ti/" rel="noopener">RTX 4060 family page&lt;/a> show a newer Blackwell GPU against the RTX 4060&amp;rsquo;s Ada generation. Their memory capacities are the same, but the core configuration, memory bandwidth and board-power rating differ.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Specification&lt;/th>
&lt;th scope="col" style="text-align: right">GeForce RTX 5050&lt;/th>
&lt;th scope="col" style="text-align: right">GeForce RTX 4060&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Specification">GPU generation&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 5050">Blackwell&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 4060">Ada Lovelace&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">CUDA cores&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 5050">2,560&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 4060">3,072&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Video memory&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 5050">8GB GDDR6&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 4060">8GB GDDR6&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Memory bus&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 5050">128-bit&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 4060">128-bit&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Memory bandwidth&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 5050">320 GB/s&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 4060">272 GB/s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">PCIe interface&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 5050">PCIe 5.0 x8&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 4060">PCIe 4.0 x8&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Total graphics power&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 5050">130 W&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 4060">115 W&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">DLSS generation at launch&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 5050">DLSS 4&lt;/td>
&lt;td style="text-align: right" data-label="GeForce RTX 4060">DLSS 3&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The RTX 5050 has faster memory bandwidth and a newer architecture, but the RTX 4060 has more CUDA cores. Neither specification alone predicts every game&amp;rsquo;s performance. Different games lean on different parts of the GPU, and driver changes can also move results. That is why the published benchmark suite matters more than one row in a spec table.&lt;/p>
&lt;p>The most important shared limit is 8GB of VRAM. A game that fits comfortably in 8GB can run well on either card. When a high-resolution texture set or another asset pushes past that capacity, the game may have to evict data or use system memory. That can lead to stutter or lower texture quality. The RTX 5050 does not solve that problem just by arriving later.&lt;/p>
&lt;p>NVIDIA presents the RTX 5050 as a Blackwell card with its latest DLSS features, while the RTX 4060 belongs to the Ada RTX 40 Series. Newer supported features can matter in games that implement them, especially if you value frame generation, but feature support is not the same as native rendering speed. I would treat it as a secondary reason to choose the 5050, not proof that it beats the 4060 in ordinary rasterized games.&lt;/p>
&lt;h2 id="what-the-1080p-benchmarks-say">What the 1080p benchmarks say&lt;/h2>
&lt;p>Tom&amp;rsquo;s Hardware&amp;rsquo;s &lt;a href="https://www.tomshardware.com/pc-components/gpus/nvidia-geforce-rtx-5050-review/4" rel="noopener">RTX 5050 raster testing&lt;/a> and &lt;a href="https://www.tomshardware.com/pc-components/gpus/nvidia-geforce-rtx-5050-review/7" rel="noopener">review conclusion&lt;/a> place the card near the RTX 4060 in its 1080p suite. The review&amp;rsquo;s summary describes the RTX 5050 as basically tying the RTX 4060 and reports an average above 60 frames per second across the tested games. That is a useful result for a low-cost card, but it does not establish a generational leap over the older model.&lt;/p>
&lt;p>&lt;a href="https://www.techspot.com/review/3011-nvidia-geforce-rtx-5050/" rel="noopener">TechSpot&amp;rsquo;s RTX 5050 review&lt;/a> reached a similar practical conclusion across its 18-game test. The 5050 averaged 66 fps at 1080p in that suite. TechSpot found it on par with the RTX 4060 in games such as Hogwarts Legacy, Space Marine 2 and Clair Obscur: Expedition 33, while some other titles favored different cards. The average should be read as that review&amp;rsquo;s test result, not as a frame rate you should expect in every game.&lt;/p>
&lt;p>The examples help explain why a single average can be misleading. In some games the 5050 and 4060 are effectively interchangeable; in others, one card&amp;rsquo;s architecture or memory behavior shifts the result. For the direct purchase question, however, the important point is that the 5050 does not deliver a reliable tier jump. A newer product number is not a benchmark result.&lt;/p>
&lt;p>The 5050&amp;rsquo;s modest position also appears in broader comparisons. Tom&amp;rsquo;s Hardware&amp;rsquo;s &lt;a href="https://www.tomshardware.com/reviews/gpu-hierarchy,4388.html" rel="noopener">GPU hierarchy&lt;/a> and &lt;a href="https://www.tomshardware.com/reviews/best-gpus,4380.html" rel="noopener">best graphics cards guide&lt;/a> help place it among competing products, but those lists are not substitutes for the two review suites above. Their main use here is to confirm that this is an entry-level buying decision, not a reason to pay extra for an automatic performance upgrade.&lt;/p>
&lt;h2 id="the-practical-differences-beyond-average-frame-rate">The practical differences beyond average frame rate&lt;/h2>
&lt;p>The RTX 5050&amp;rsquo;s strongest reason to exist is its newer feature set. NVIDIA associates the Blackwell generation with DLSS 4, including features that can create additional frames in supported games. The RTX 4060 remains capable of DLSS upscaling and frame generation as an RTX 40 Series card, but its generation does not support the same Blackwell-only feature set. If you play a specific title that supports a feature you want, that can tip a new-build decision toward the 5050.&lt;/p>
&lt;p>Keep the distinction clear: generated frames are not the same thing as rendering more frames natively. They can make supported games feel smoother, but they do not fix high latency, poor base performance, or insufficient VRAM. If you need a card for an unsupported game, the newer feature name does not help. I would check the game list and the specific mode you want before assigning much value to this advantage.&lt;/p>
&lt;p>Both cards carry 8GB of GDDR6, so the RTX 5050 does not improve the most obvious capacity limitation. In a title whose high-resolution texture set exceeds 8GB, the same broad warning applies to both: reduce texture quality or choose a card with more memory. The 5050&amp;rsquo;s 320 GB/s bandwidth is higher than the RTX 4060&amp;rsquo;s 272 GB/s, but it is still an 8GB card. Bandwidth and capacity solve different problems.&lt;/p>
&lt;p>Power is not a clear win for the newer model either. NVIDIA&amp;rsquo;s reference total graphics power is 130 W for the 5050 and 115 W for the 4060. Those ratings do not predict a card&amp;rsquo;s exact wall draw in a particular game, but they do rule out the claim that the 5050 automatically uses less power based on its published board rating. For a compact PC, look at the exact card&amp;rsquo;s length, thickness, fan design, connectors, and the system&amp;rsquo;s power supply rather than assuming the newer name means an easier fit.&lt;/p>
&lt;p>Tom&amp;rsquo;s Hardware&amp;rsquo;s &lt;a href="https://www.tomshardware.com/pc-components/gpus/nvidia-geforce-rtx-5050-review/4" rel="noopener">raster results&lt;/a> are the most useful baseline for conventional gaming, while its &lt;a href="https://www.tomshardware.com/pc-components/gpus/nvidia-geforce-rtx-5050-review/7" rel="noopener">review conclusion&lt;/a> reflects the broader trade-off. TechSpot&amp;rsquo;s &lt;a href="https://www.techspot.com/review/3065-nvidia-rtx-5050-vs-intel-b580-dlss-xess/" rel="noopener">RTX 5050 versus Arc B580 comparison&lt;/a> adds a useful check on how DLSS and XeSS features interact with the measured result, but it does not turn the 5050 into a higher class of GPU.&lt;/p>
&lt;h2 id="who-should-buy-the-rtx-5050">Who should buy the RTX 5050&lt;/h2>
&lt;p>&lt;strong>Choose the RTX 5050 when:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>You are buying a new graphics card and its exact board is a good match for your case, display outputs, and available power connectors.&lt;/li>
&lt;li>You want to use a Blackwell-specific feature in games you actually play, and its support matters more to you than a large raster-performance gain.&lt;/li>
&lt;li>Your target is 1080p, you are willing to tune demanding settings, and you understand that both cards have 8GB of memory.&lt;/li>
&lt;li>Its price is more attractive than the available RTX 4060 models after comparing the exact listings.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Choose the RTX 4060 when:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>You already own one and are considering a 5050 as an upgrade. The published tests do not support that swap as a meaningful speed improvement.&lt;/li>
&lt;li>The 4060 is the better deal in the listings you can buy, and its feature set covers the games you play.&lt;/li>
&lt;li>You are comparing a specific card whose cooler, connector layout or dimensions fit your build better.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Look beyond both cards when&lt;/strong> your priority is high texture quality in demanding releases, a long useful life without settings changes, or a substantial frame-rate increase. Neither option adds video memory over the other. The &lt;a href="https://techfuelhq.com/articles/gpu-hierarchy-2026/">GPU hierarchy&lt;/a> and &lt;a href="https://techfuelhq.com/tools/gpu-comparison/">GPU comparison tool&lt;/a> let you compare other candidates, and our &lt;a href="https://techfuelhq.com/articles/best-budget-gpu-2026/">budget graphics-card guide&lt;/a> covers more choices in the same shopping range.&lt;/p>
&lt;p>The newer RTX 5050 is not a bad card simply because it fails to beat the RTX 4060 by a clear margin. It is a newer entry-level option with the same 8GB capacity and similar gaming performance. The right reason to choose it is a feature, fit or live deal that matters to your build. If the reason is only that it is newer, I would keep the RTX 4060 or wait for a more meaningful step up.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=RTX&amp;#43;5050&amp;#43;8GB&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/rtx-5050-vs-rtx-4060-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DRTX%2B5050%2B8GB" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/rtx-5050-vs-rtx-4060-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>If you are choosing between these two for a fresh build, compare the exact listing, cooler, board dimensions and power connection before ordering. The &lt;a href="https://techfuelhq.com/gpu-reviews/rtx-5050-review-2026/">RTX 5050 review&lt;/a> covers one tested board in more detail, and the &lt;a href="https://techfuelhq.com/articles/best-graphics-card-2026/">best graphics card guide&lt;/a> provides a wider shortlist.&lt;/p></description></item><item><title>PTM7950 vs Thermal Paste: Which Lasts and When</title><link>https://techfuelhq.com/articles/ptm7950-vs-thermal-paste-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/ptm7950-vs-thermal-paste-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · PTM7950 vs thermal paste&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>PTM7950 is the right answer for a bare die that keeps pumping paste out&lt;/strong>, and for anything you do not want to open again. It holds its bond line through thermal cycling and Honeywell's sheet claims no pump-out, bleed-out or dry-out.&lt;/li>
&lt;li>&lt;strong>Paste is the right answer for a flat cold plate you might remove&lt;/strong>, for a quick remount, and for anything where you want to adjust mounting pressure by feel. Kryonaut is silicone-based, does not cure, and is easy to clean off.&lt;/li>
&lt;li>&lt;strong>Pressure decides the result.&lt;/strong> Honeywell wants 30 to 40 psi for PTM7950, with 10 psi as the point where anything measurable starts happening. A cooler mount that clamps by hand may not get there.&lt;/li>
&lt;li>&lt;strong>The conductivity labels are not comparable.&lt;/strong> PTM7950 is rated 8.5 W/m·K; Thermal Grizzly has not published a W/m·K figure since 2020. Buy on measured thermal resistance, not on the number on the tube.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>Thermal paste is a suspension of thermally conductive particles in a carrier fluid. PTM7950 is a phase-change material: a thin, firm sheet that is solid at room temperature and turns into a viscous, conformal layer once it passes about 45 °C. They are used in the same place, and they fail in different ways, which is the entire decision.&lt;/p>
&lt;p>I have re-pasted enough coolers to have an opinion, but the numbers below are Honeywell&amp;rsquo;s, Thermal Grizzly&amp;rsquo;s and Igor&amp;rsquo;s Lab&amp;rsquo;s, not my own bench results. What follows is what each material is specified to do, where the published figures are not comparable, and the two conditions that decide which one you should buy.&lt;/p>
&lt;h2 id="what-each-material-actually-is">What each material actually is&lt;/h2>
&lt;p>PTM7950 is silicone-free and supplied as a sheet in a 0.2 mm to 0.5 mm thickness range (&lt;a href="https://prod-edam.solstice.com/content/dam/honeywell-edam/pmt/oneam/en-us/electronic-materials/thermal-interface-materials/documents/100600-esm-tds-ptm7950-pcm-ltr-en.pdf" rel="noopener">Honeywell TDS&lt;/a>). Its selling point is a property list rather than a single number: no pump-out, no bleed-out, no dry-out. That is a direct claim about the failure modes that kill paste on hot, small dies.&lt;/p>
&lt;p>Kryonaut is a silicone-based paste with no curing step. Thermal Grizzly publishes its viscosity at 130 to 170 Pa·s, density at 3.7 g/cm³, operating range from −250 °C to +350 °C, and thermal resistance at 0.0032 K/W (&lt;a href="https://www.thermal-grizzly.com/media/56/c8/6a/1700224682/TG-Datasheet-Kryonaut-EN.pdf" rel="noopener">Kryonaut datasheet&lt;/a>). It is a conventional product, well understood, and it behaves the way paste is supposed to behave.&lt;/p>
&lt;p>The mechanical difference is what matters. Paste is applied as a blob or a line and spreads under mounting pressure until it fills the microscopic gaps between two surfaces. The pad is already a sheet of a known thickness, and it thins as it heats and is compressed. A pad is a manufactured bond line; a paste is a bond line you create on the day.&lt;/p>
&lt;h2 id="the-conductivity-numbers-are-not-comparable">The conductivity numbers are not comparable&lt;/h2>
&lt;p>This is where most comparisons go wrong, so it is worth being precise.&lt;/p>
&lt;p>Honeywell rates PTM7950 at 8.5 W/m·K with a thermal impedance of 0.04 °C·cm²/W, both by ASTM D5470 at 125 W and 40 psi with no shim. Thermal Grizzly does not publish a W/m·K figure at all. Its product page states that the company &amp;ldquo;has not published general W/(m·K) ratings since the end of 2020&amp;rdquo; (&lt;a href="https://www.thermal-grizzly.com/en/kryonaut/s-tg-k-100-r" rel="noopener">Thermal Grizzly&lt;/a>). That is not evasion. W/(m·K) is a bulk property, and a paste in service is a layer a few tens of micrometres thick where contact resistance dominates.&lt;/p>
&lt;p>Igor&amp;rsquo;s Lab measured PTM7950 with ASTM D5470-17 on their TIMA5 tester and reported 6.374 W/(m·K), with thermal resistance falling from 0.41913 cm²K/W to 0.03427 cm²K/W as the bond line was compressed (&lt;a href="https://www.igorslab.de/en/overhyped-solstice-ptm7950-in-lab-test-and-as-game-changer-for-graphics-cards/" rel="noopener">Igor&amp;rsquo;s Lab&lt;/a>). They also state that ordinary pastes &amp;ldquo;cannot achieve much more than 4 to 5 W/(m-K) under the usual conditions on a GPU or CPU.&amp;rdquo;&lt;/p>
&lt;p>Two things follow. First, the measured 6.374 is lower than Honeywell&amp;rsquo;s 8.5 because it is an effective value that includes the bond line and the contacts, not the bulk material. You can see that in the datasheet&amp;rsquo;s own numbers: 0.04 °C·cm²/W across a 25 µm layer works out to about 6.25 W/(m·K) if you divide thickness by resistance, which is the same neighbourhood Igor measured. Second, the comparison that matters is 6.4 against 4 to 5, and it is a real gap, not a marketing one — but it is a gap in effective conductivity under pressure, not in the number printed on the box.&lt;/p>
&lt;h2 id="pressure-is-the-deciding-variable">Pressure is the deciding variable&lt;/h2>
&lt;p>Honeywell is explicit that pressure drives performance. Its datasheet states that 30 to 40 psi is needed, and that &amp;ldquo;a minimum pressure of 10 psi is needed to observe a significant reduction in bondline thickness.&amp;rdquo; Below that, you are not getting the material the datasheet describes.&lt;/p>
&lt;p>That is a harder requirement than it sounds. Most CPU coolers use spring-loaded screws that bottom out against a standoff, and the actual pressure depends on the spring rate and how far it compresses. Most mounts are designed to work with paste, which needs far less pressure to spread. If your cooler is a stock boxed unit with plastic push-pins, or a laptop heatsink held by four small screws into a thin chassis, you may never reach the pressure Honeywell specifies.&lt;/p>
&lt;p>There is no published number from Thermal Grizzly for Kryonaut&amp;rsquo;s required pressure, which is the point. Paste is forgiving of a mediocre mount. PTM7950 is not. If you cannot control or verify the mounting pressure, paste is the lower-risk choice, and the &lt;a href="https://techfuelhq.com/articles/cpu-overheating-2026/">CPU overheating guide&lt;/a> covers how to tell whether the mount is the problem in the first place.&lt;/p>
&lt;h2 id="pump-out-drying-and-the-long-haul">Pump-out, drying, and the long haul&lt;/h2>
&lt;p>Pump-out is the mechanism that makes a good paste go bad. The die heats and expands, the cold plate heats and expands at a different rate, and the paste is squeezed out of the interface over hundreds or thousands of cycles. Thermal Grizzly&amp;rsquo;s own guidance acknowledges the failure: replace the paste if temperatures deteriorate or if the cooler has been removed.&lt;/p>
&lt;p>A phase-change material is designed around that cycle instead of fighting it. It liquefies at 45 °C, flows into the gaps, and re-solidifies as it cools, so it re-conforms on every thermal cycle rather than being progressively displaced. Honeywell&amp;rsquo;s reliability data is aimed squarely at this: the sheet lists passing a 150 °C bake for 1,000 hours, a double-85 (85 °C / 85% humidity) test for 1,000 hours, and 1,000 temperature cycles between −55 °C and +125 °C, with thermal impedance staying at or below 0.045 °C·cm²/W throughout (&lt;a href="https://prod-edam.solstice.com/content/dam/honeywell-edam/pmt/oneam/en-us/electronic-materials/thermal-interface-materials/documents/100600-esm-tds-ptm7950-pcm-ltr-en.pdf" rel="noopener">TDS&lt;/a>).&lt;/p>
&lt;p>Igor&amp;rsquo;s Lab&amp;rsquo;s real-world result is consistent with that. On a Manli RTX 4080 Gallardo, temperatures settled at 66 to 67 °C after burn-in. That is a single card and a single test, not a universal claim, and I would not quote it as a temperature win over paste on your specific card. It is evidence that the material performs in a real mount.&lt;/p>
&lt;p>The trade-off is handling. Igor describes the pad as firm and brittle, notes that the protective films can crack it if you are careless, and recommends the pre-assembled versions with adhesive strips for exactly that reason (&lt;a href="https://www.igorslab.de/en/overhyped-solstice-ptm7950-in-lab-test-and-as-game-changer-for-graphics-cards/3/" rel="noopener">page 3&lt;/a>). Paste does not have that problem. It has the opposite problem: it is easy to apply badly and easy to apply too much.&lt;/p>
&lt;h2 id="where-each-one-belongs">Where each one belongs&lt;/h2>
&lt;p>Buy PTM7950 for a bare die with a small contact area that runs hot and cycles constantly: a graphics card, a laptop, a handheld. Buy it for a machine you do not want to open again, and for any mount where you have already seen paste pump out once. Buy it when you can torque the cooler down properly.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Honeywell&amp;#43;PTM7950&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/ptm7950-vs-thermal-paste-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DHoneywell%2BPTM7950" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/ptm7950-vs-thermal-paste-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>Buy paste for a desktop CPU under a tower cooler with a proper spring mount, for a cold plate you expect to remove within a year, and for any situation where you want to adjust the mount and try again. Kryonaut&amp;rsquo;s published properties are unremarkable in a good way: it does not cure, it cleans up with isopropyl alcohol, and you can re-seat a cooler without destroying the interface.&lt;/p>
&lt;p>A word on buying the pad: the counterfeit and repackaged market for PTM7950 is real, and the material&amp;rsquo;s performance depends on it being the actual Honeywell product in the stated thickness. Buy a pre-cut sheet from a seller who states the thickness and the source, not a loose square of unknown provenance.&lt;/p>
&lt;h2 id="what-i-would-check-before-buying">What I would check before buying&lt;/h2>
&lt;p>Four checks, and the first two decide most of the answer.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Can you apply real pressure?&lt;/strong> Spring screws with standoffs, a proper backplate, and a cooler that is not held by push-pins. If the answer is no, paste is the safer choice regardless of the conductivity numbers.&lt;/li>
&lt;li>&lt;strong>Has this mount already pumped out once?&lt;/strong> If you have re-pasted the same card twice and the temperatures fell again both times, that is the signature case for a phase-change pad.&lt;/li>
&lt;li>&lt;strong>Is the die bare or under a heat spreader?&lt;/strong> A bare GPU die with a small contact patch is the strongest case for PTM7950. A large, flat CPU heat spreader is the strongest case for paste.&lt;/li>
&lt;li>&lt;strong>What does your sensor actually say?&lt;/strong> Measure before you change anything. The &lt;a href="https://techfuelhq.com/articles/how-to-check-cpu-temp-2026/">CPU temperature check&lt;/a> covers the tools, and the &lt;a href="https://techfuelhq.com/data/gpu-hotspot-delta-census/">GPU hotspot delta census&lt;/a> covers the edge-versus-hotspot split that tells you whether the problem is the interface or the mount.&lt;/li>
&lt;/ol>
&lt;p>If the temperatures are already fine, neither product will help. Repasting a healthy cooler is how people end up with a worse result than they started with. The &lt;a href="https://techfuelhq.com/articles/cpu-gpu-thermal-throttling-fix-2026/">thermal throttling fix guide&lt;/a> is the place to start when the machine is actually throttling, because airflow, fan curves and mount pressure all come before the material choice.&lt;/p></description></item><item><title>PC Won't POST: The Ordered Diagnostic Path (2026)</title><link>https://techfuelhq.com/articles/pc-wont-post-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/pc-wont-post-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;p>A no-POST machine is the most misdiagnosed failure in PC building, because the symptom is so unhelpful. The fans spin, the lights glow, and nothing appears. People respond by buying a power supply, then memory, then a motherboard, and often end up with a working machine and three spare parts.&lt;/p>
&lt;p>The board is already trying to tell you where it stopped. You just have to read the indicator and then work the checks in an order that removes the cheap possibilities before the expensive ones.&lt;/p>
&lt;h2 id="no-post-is-a-specific-failure-not-a-general-one">No POST is a specific failure, not a general one&lt;/h2>
&lt;p>I keep four states separate, because they lead to completely different pages:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>No power:&lt;/strong> nothing spins, nothing lights.&lt;/li>
&lt;li>&lt;strong>No POST:&lt;/strong> the machine powers on but never completes its firmware hardware check.&lt;/li>
&lt;li>&lt;strong>No boot:&lt;/strong> POST completed but no operating system loads.&lt;/li>
&lt;li>&lt;strong>No video:&lt;/strong> the machine boots but the display shows nothing.&lt;/li>
&lt;/ul>
&lt;p>This page is the second one. If nothing happens at all, the &lt;a href="https://techfuelhq.com/articles/computer-wont-turn-on-2026/">computer won&amp;rsquo;t turn on guide&lt;/a> is the right starting point, because the checks split almost immediately. If the machine reaches Windows and the screen is blank, that is a display fault and the &lt;a href="https://techfuelhq.com/articles/monitor-no-signal-2026/">no signal guide&lt;/a> covers it.&lt;/p>
&lt;p>A useful confirmation: connect a monitor to the output the machine should be using and watch for the firmware logo. No logo, no beep, no handoff, and the board&amp;rsquo;s own indicator lit is a POST failure. That is the machine telling you which stage it could not clear.&lt;/p>
&lt;h2 id="read-the-boards-own-diagnostic-light">Read the board&amp;rsquo;s own diagnostic light&lt;/h2>
&lt;p>Most modern boards carry four status LEDs for the stages that matter. ASUS calls them Q-LEDs, and the &lt;a href="https://www.asus.com/us/support/faq/1042678/" rel="noopener">Q-LED troubleshooting article&lt;/a> names them plainly: CPU, DRAM, VGA, BOOT. A light that stays lit means that stage did not clear.&lt;/p>
&lt;p>The &lt;a href="https://dlcdnets.asus.com/pub/ASUS/mb/Socket%20AM5/ROG%20STRIX%20B650-A%20GAMING%20WIFI/E20268_ROG_STRIX_B650-A_GAMING_WIFI_UM_WEB.pdf" rel="noopener">board manual for the ROG STRIX B650-A Gaming WiFi&lt;/a> adds the colour coding, which is handy when the inside of the case is dark and the labels are small:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">LED&lt;/th>
&lt;th scope="col">Colour on this board&lt;/th>
&lt;th scope="col">What ASUS says a lit LED means&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="LED">CPU&lt;/td>
&lt;td data-label="Colour on this board">Red&lt;/td>
&lt;td data-label="What ASUS says a lit LED means">No CPU detected, or a CPU fault&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="LED">DRAM&lt;/td>
&lt;td data-label="Colour on this board">Yellow&lt;/td>
&lt;td data-label="What ASUS says a lit LED means">No memory detected, or a memory fault&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="LED">VGA&lt;/td>
&lt;td data-label="Colour on this board">White&lt;/td>
&lt;td data-label="What ASUS says a lit LED means">No graphics card detected, or a graphics fault&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="LED">BOOT&lt;/td>
&lt;td data-label="Colour on this board">Yellow-green&lt;/td>
&lt;td data-label="What ASUS says a lit LED means">No boot device detected, or a boot device fault&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>One sentence in that manual matters more than the table: the LEDs &amp;ldquo;provide the most probable cause of an error code as a starting point for troubleshooting,&amp;rdquo; and &amp;ldquo;the actual cause may vary from case to case.&amp;rdquo; A lit CPU LED is a direction, not a replacement order. The processor is one of the last things I suspect, not the first.&lt;/p>
&lt;p>The same board has a second indicator worth knowing about. A separate LED marked PLUG_8PIN_PWR lights up when the 8-pin CPU power plug is not connected. If that one is on, you have found the problem without opening anything else.&lt;/p>
&lt;h2 id="build-the-minimum-configuration-first">Build the minimum configuration first&lt;/h2>
&lt;p>Once you know which stage is failing, reduce the machine to the parts POST actually requires. &lt;a href="https://www.asus.com/us/support/faq/1042632/" rel="noopener">ASUS&amp;rsquo;s No Power / No Boot / No Display article&lt;/a> walks through this in order: power supply, CPU, memory, graphics card, monitor, then minimal components, Clear CMOS, and the Q-LEDs again.&lt;/p>
&lt;p>The minimum set is the board, the CPU with its cooler installed and connected, one memory module in the slot the manual specifies for single-module operation, and power. Remove the graphics card if the processor has integrated graphics, and disconnect every drive and every external device.&lt;/p>
&lt;p>Two rules I do not bend. The CPU cooler stays installed and powered, because POST will not complete with a processor that has no thermal path. And you change one thing at a time, so that when the symptom changes you know which change did it.&lt;/p>
&lt;p>Before any of that, count the power connectors. ASUS&amp;rsquo;s article calls out that some boards carry an 8-pin EATX12V_1, a 4-pin EATX12V_2 and the 24-pin EATXPWR, and recommends connecting all of them. A missing auxiliary CPU connector produces a machine that lights up and never POSTs, and it is one of the most common causes I see.&lt;/p>
&lt;h2 id="ordered-checks-cheapest-first">Ordered checks, cheapest first&lt;/h2>
&lt;p>Work down the list and stop when the symptom changes.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Confirm the state.&lt;/strong> Firmware logo on screen or no? Listen for a beep, watch the keyboard lights, and note which LED stays lit. Write it down before you touch anything.&lt;/li>
&lt;li>&lt;strong>Check every power connector.&lt;/strong> 24-pin, 8-pin CPU, and the 4-pin auxiliary if the board has one. Seat both ends on a modular supply until the latches click.&lt;/li>
&lt;li>&lt;strong>Clear CMOS exactly as the manual describes.&lt;/strong> A settings problem, particularly after a memory change or a failed overclock, can stop POST with every part healthy.&lt;/li>
&lt;li>&lt;strong>Reduce to one memory module.&lt;/strong> Use the slot named for single-module operation in the manual, then rotate modules and slots one change at a time. If a module is not on the board&amp;rsquo;s qualified list, that is a suspect rather than proof.&lt;/li>
&lt;li>&lt;strong>Remove the graphics card and use integrated video.&lt;/strong> A card that is not seated, or a slot that is not receiving power, can hold the VGA stage indefinitely.&lt;/li>
&lt;li>&lt;strong>Recheck CPU power and cooler mounting.&lt;/strong> A cooler that is not tightened evenly, or a CPU power connector that is only half seated, will stop the machine before any other test matters.&lt;/li>
&lt;li>&lt;strong>Reseat the processor only after the above.&lt;/strong> ASUS&amp;rsquo;s Q-LED article lists reinstalling the CPU, checking for dirt or damaged pins, and trying another processor as the CPU-side steps. Bent pins are easy to create and hard to fix, so this is not a first move.&lt;/li>
&lt;li>&lt;strong>Verify the firmware supports the processor.&lt;/strong> Check the CPU support list and required BIOS version for your exact board. If the board will not start at all, USB BIOS FlashBack can reflash from a USB drive without a processor installed; &lt;a href="https://www.asus.com/us/support/faq/1038568/" rel="noopener">ASUS&amp;rsquo;s FlashBack article&lt;/a> specifies a USB drive of at least 1 GB in FAT16 or FAT32 with an MBR partition.&lt;/li>
&lt;li>&lt;strong>Substitute a power supply only with its own cable set.&lt;/strong> Corsair&amp;rsquo;s guidance is blunt: &amp;ldquo;never try to use one brand&amp;rsquo;s cables with another brand&amp;rsquo;s PSU,&amp;rdquo; because each maker wires the supply end differently. A borrowed supply with borrowed cables is not a controlled test.&lt;/li>
&lt;li>&lt;strong>Try the board outside the case.&lt;/strong> A misplaced standoff or loose metal can short the board and stop POST. This is the last free check, and it is a deliberate one.&lt;/li>
&lt;/ol>
&lt;p>If the machine repeatedly shuts down rather than sitting at a lit LED, the fault is different. Corsair&amp;rsquo;s &lt;a href="https://www.corsair.com/us/en/explorer/diy-builder/power-supply-units/psu-protections-explained/" rel="noopener">PSU protections explainer&lt;/a> describes short-circuit protection tripping when the 3.3 V, 5 V, or 12 V rails short to another rail or to ground, and over-power protection tripping between 115% and 135% of rated output. A supply that trips and resets is protecting itself from something. Stop provoking it and find the short.&lt;/p>
&lt;h2 id="what-survives-a-reboot-and-what-does-not">What survives a reboot, and what does not&lt;/h2>
&lt;p>This distinction saves a lot of wasted effort, because most of the evidence in a no-POST diagnosis is live and disappears the moment you power down.&lt;/p>
&lt;p>&lt;strong>Does not survive a reboot:&lt;/strong> the lit LED itself, a beep pattern, and the exact moment the machine stopped. These are live states. If you power off to reseat a cable, the evidence is gone. Photograph the LED pattern or write it down first.&lt;/p>
&lt;p>&lt;strong>Survives a reboot:&lt;/strong> the installed BIOS version, the memory configuration you left in place, a jumper or Clear CMOS result, and anything you saved to a file or a note. That is why I keep a sheet of paper next to the machine and record each change with the symptom that followed it.&lt;/p>
&lt;p>&lt;strong>Survives a reboot and is also a hardware fact:&lt;/strong> whether the PLUG_8PIN_PWR LED is lit with the supply connected and switched on. That is a wiring state, not a transient reading.&lt;/p>
&lt;p>The practical upshot: change one thing, note the LED, power down, change the next thing. The note is the only part of that loop that persists.&lt;/p>
&lt;h2 id="when-to-stop">When to stop&lt;/h2>
&lt;p>Stop when the free checks are exhausted, because the next step stops being free.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>A pop, a spark, or a burning smell.&lt;/strong> Unplug the machine and leave it off. Corsair&amp;rsquo;s article explains what the supply is protecting against; it does not make repeated retries safe.&lt;/li>
&lt;li>&lt;strong>The same LED after a correct minimum configuration.&lt;/strong> At that point the board, the CPU, and the firmware are the suspects, and separating them needs known-good spares. That is a technician job, not a shopping spree.&lt;/li>
&lt;li>&lt;strong>A BIOS FlashBack that will not complete on a board that will not start.&lt;/strong> Check the USB format and the exact port from the manual once, then stop. Repeated failed flashes on a dead board do not improve with volume.&lt;/li>
&lt;li>&lt;strong>A machine that will not POST with a processor the board&amp;rsquo;s support list does not cover.&lt;/strong> That is a compatibility problem, not a fault, and the answer is firmware, not hardware.&lt;/li>
&lt;li>&lt;strong>Anything involving a prebuilt with a proprietary board.&lt;/strong> The maker decides which checks are user-serviceable. Ask before opening it.&lt;/li>
&lt;/ul>
&lt;p>If you get as far as documenting the LED stage, the power connections, and the BIOS version, you already have more than most repair tickets contain. The &lt;a href="https://techfuelhq.com/data/post-time-census/">POST time census&lt;/a> tracks how long boards take to clear training on healthy systems, which is useful context when a machine feels slow rather than dead. And the &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">diagnostic workbench&lt;/a> lets you record each step and result so the next person starts where you stopped.&lt;/p></description></item><item><title>M.2 SSD Heatsink Guide: When Your Board Is Enough</title><link>https://techfuelhq.com/articles/m2-ssd-heatsink-guide-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/m2-ssd-heatsink-guide-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Do you need an M.2 heatsink&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Use the motherboard heatsink first.&lt;/strong> Modern boards ship one over the primary slot, and drive makers treat it as a supported configuration. Crucial says a T705 needs a motherboard or alternate heatsink to hit optimal performance, not that it needs a premium one.&lt;/li>
&lt;li>&lt;strong>Check thickness before you buy anything.&lt;/strong> A bare 9100 PRO is 2.38 mm; the same drive with Samsung's heatsink is 8.88 mm. That difference decides whether the slot under your GPU is usable.&lt;/li>
&lt;li>&lt;strong>Never stack heatsinks.&lt;/strong> One cooling path, one pad, no double-stacking, and do not peel the copper-clad label off a drive designed to be used under a board heatsink.&lt;/li>
&lt;li>&lt;strong>Buy a third-party heatsink only for a specific gap:&lt;/strong> a slot with no heatsink, a double-sided drive the board pad cannot reach, or sustained Gen5 writes in a case with poor airflow.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>The M.2 heatsink question is usually answered before you open the case. If your motherboard has a metal plate over the slot with a thermal pad underneath it, you already have the cooling solution the drive was designed around, and adding a second one is more likely to cause a clearance problem than to fix a temperature problem.&lt;/p>
&lt;p>Where the answer changes is at the edges: a board with a bare second or third slot, a double-sided drive that sits proud of the pad, a Gen5 drive doing sustained writes in a case with no airflow across the board. Those are real cases, and they are worth identifying precisely instead of buying a heatsink on principle.&lt;/p>
&lt;h2 id="what-the-motherboard-heatsink-actually-does">What the motherboard heatsink actually does&lt;/h2>
&lt;p>M.2 is a form-factor family defined by PCI-SIG, and the drives people call &amp;ldquo;2280&amp;rdquo; are 22 mm wide and 80 mm long. That is a mechanical standard, not a thermal one, and the standard says nothing about how much heat a given drive produces. The heat comes from the controller, and the amount depends on the generation and the workload.&lt;/p>
&lt;p>The manufacturer&amp;rsquo;s own numbers show the range. Samsung rates the 1 TB 990 PRO, a Gen4 drive, at 5.5 W average during an active read (&lt;a href="https://download.semiconductor.samsung.com/resources/data-sheet/samsung_nvme_ssd_990_pro_datasheet_rev.2.0.pdf" rel="noopener">990 PRO datasheet&lt;/a>). The 9100 PRO, which is Gen5, runs 7.6 W for 1 TB, 8.1 W for 2 TB, 9.0 W for 4 TB and 10.5 W for 8 TB during an active read (&lt;a href="https://download.semiconductor.samsung.com/resources/data-sheet/Samsung_NVMe_SSD_9100_PRO_Datasheet_Rev.2.0.pdf" rel="noopener">9100 PRO datasheet&lt;/a>). Both datasheets state the operating range as 0 °C to 70 °C, measured by S.M.A.R.T., with proper airflow recommended.&lt;/p>
&lt;p>Two details in those footnotes are worth more than any forum rule of thumb. Samsung measures its power figures with the drive installed as a secondary device in a fan-cooled desktop system, so a passively cooled case is outside the condition the number was taken under. And the temperature limit is a S.M.A.R.T. reading, which is a sensor inside the controller, not the surface temperature of the NAND.&lt;/p>
&lt;p>A motherboard heatsink works by giving the controller a larger surface to dump heat into and letting the case&amp;rsquo;s airflow carry it away. It does not refrigerate anything. That is why the difference between a good board heatsink and a great one is small under light load, and why both are limited by how much air moves through the case.&lt;/p>
&lt;h2 id="the-three-numbers-that-decide-the-fit">The three numbers that decide the fit&lt;/h2>
&lt;p>Before you buy any heatsink, get three numbers for your exact drive and your exact board.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Number&lt;/th>
&lt;th scope="col">Where to find it&lt;/th>
&lt;th scope="col">Why it decides the purchase&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Number">Drive thickness&lt;/td>
&lt;td data-label="Where to find it">The drive datasheet, in the form factor row&lt;/td>
&lt;td data-label="Why it decides the purchase">The board&amp;rsquo;s pad sits at a fixed height; a thicker drive lifts off it or fouls the plate&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Number">Slot length and key&lt;/td>
&lt;td data-label="Where to find it">The motherboard manual or spec page&lt;/td>
&lt;td data-label="Why it decides the purchase">Some slots are 2280 only, others take 22110; a heatsink has to match the slot it covers&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Number">Vertical clearance above the slot&lt;/td>
&lt;td data-label="Where to find it">Your eyes, with the GPU fitted&lt;/td>
&lt;td data-label="Why it decides the purchase">The slot under a thick graphics card is the one that catches people&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Samsung&amp;rsquo;s datasheets make the thickness point concrete. The 9100 PRO is listed at a maximum of 80.15 × 22.15 × 2.38 mm for the 1 TB to 4 TB models, and 80.15 × 22.15 × 3.88 mm for the 8 TB model. The 990 PRO is listed at a maximum of 80.0 × 22 × 2.3 mm. Nothing dramatic so far, but the same 9100 PRO with Samsung&amp;rsquo;s factory heatsink is listed at 80.15 × 25 × 8.88 mm for 1 TB to 4 TB and 80.15 × 25 × 11.25 mm for 8 TB (&lt;a href="https://download.semiconductor.samsung.com/resources/data-sheet/Samsung_NVMe_SSD_9100_PRO_with_Heatsink_Datasheet_Rev.2.0.pdf" rel="noopener">with-heatsink datasheet&lt;/a>).&lt;/p>
&lt;p>That is the number people skip. A factory heatsink costs you about 6.5 mm of height and about 2.85 mm of width over the bare drive. Under a triple-slot graphics card with a backplate, 8.88 mm can be the difference between a clean install and a drive you cannot seat.&lt;/p>
&lt;p>Slot layout varies too, and the published specs are the only reliable source. ASUS lists the ROG Strix X870-F with four M.2 slots, where M.2_1 takes 2242, 2260 and 2280 drives while M.2_2 also takes a 22110, and both run PCIe 5.0 x4 (&lt;a href="https://rog.asus.com/us/motherboards/rog-strix/rog-strix-x870-f-gaming-wifi/spec/" rel="noopener">ASUS spec page&lt;/a>). MSI lists the MAG B850 Tomahawk MAX WIFI with four M.2 connectors and a tool-less EZ M.2 Shield Frozr II design (&lt;a href="https://storage-asset.msi.com/datasheet/mb/global/MAG-B850-TOMAHAWK-MAX-WIFI.pdf" rel="noopener">MSI datasheet&lt;/a>). The slots are not interchangeable, and the primary slot is usually the one that already has the best heatsink on the board.&lt;/p>
&lt;h2 id="the-double-sided-pad-mistake">The double-sided pad mistake&lt;/h2>
&lt;p>The most common heatsink mistake is not buying the wrong one. It is buying the right one and mounting it wrong.&lt;/p>
&lt;p>A board heatsink has a thermal pad on the underside, and that pad is designed to contact the top face of a drive. A single-sided drive presents a flat top, so the contact is straightforward. A double-sided drive has components on both faces, and the bottom face has to sit on the board&amp;rsquo;s mounting standoff while the top face meets the pad. If the pad is too thick, the drive lifts. If it is too thin, the pad does not touch. Either way you get a heatsink that looks installed and is not conducting.&lt;/p>
&lt;p>The second mistake is stacking. A drive that ships with a factory heatsink, like Samsung&amp;rsquo;s 9100 PRO with Heatsink, should not go under a motherboard heatsink as well. Samsung states plainly that the pre-installed heatsink should not be removed because doing so can damage the device, and that the warranty is void if a heatsink is removed from that model. So the drive is a single cooling path by construction, and the board&amp;rsquo;s plate comes off.&lt;/p>
&lt;p>The third mistake is the label. Crucial&amp;rsquo;s footnote on the T705 is specific: to keep optimal performance and maintain the warranty when installing with an in-motherboard heatsink, &amp;ldquo;you must not remove the copper-clad label&amp;rdquo; (&lt;a href="https://www.crucial.com/ssd/t705/CT2000T705SSD5" rel="noopener">Crucial T705&lt;/a>). The label is part of the thermal path on a drive designed to be used this way. Peeling it off to &amp;ldquo;improve contact&amp;rdquo; removes a layer the manufacturer counted on.&lt;/p>
&lt;h2 id="when-a-third-party-heatsink-earns-its-money">When a third-party heatsink earns its money&lt;/h2>
&lt;p>There are four situations where buying a separate heatsink is the right call, and they are narrower than the market suggests.&lt;/p>
&lt;p>&lt;strong>The slot has no heatsink.&lt;/strong> Many boards put a plate over the primary slot and leave the secondary slots bare. If you are filling those, a heatsink is not optional for a Gen5 drive and is cheap insurance for a Gen4 one.&lt;/p>
&lt;p>&lt;strong>The drive is double-sided and the board pad cannot reach it.&lt;/strong> This is where the thickness table above matters. A board designed for a 2.3 mm drive may not close properly on a 3.88 mm one, and no amount of pad will fix a standoff that is the wrong height.&lt;/p>
&lt;p>&lt;strong>You write to a Gen5 drive for long periods.&lt;/strong> Crucial&amp;rsquo;s claim for its pre-installed heatsink is that it &amp;ldquo;allows the T705 Gen5 SSD to run at max workload without the need to thermal throttle&amp;rdquo; under typical airflow and ambient conditions, and that non-heatsink versions &amp;ldquo;must be installed with a motherboard or alternate heatsink to achieve optimal performance.&amp;rdquo; That is the manufacturer drawing the line for you: optimal performance assumes a heatsink.&lt;/p>
&lt;p>&lt;strong>The case has no airflow across the board.&lt;/strong> A heatsink in still air is a heat spreader, not a cooler. If the board sits in a sealed compartment, the fix is airflow before it is a bigger heatsink.&lt;/p>
&lt;p>If none of those apply, the money is better spent elsewhere. The &lt;a href="https://techfuelhq.com/data/ssd-price-index/">SSD price index&lt;/a> is a more useful place to look than the heatsink aisle.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Sabrent&amp;#43;M.2&amp;#43;2280&amp;#43;SSD&amp;#43;heatsink&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/m2-ssd-heatsink-guide-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DSabrent%2BM.2%2B2280%2BSSD%2Bheatsink" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/m2-ssd-heatsink-guide-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;/span>
&lt;h2 id="factory-heatsinks-warranty-and-the-label-trap">Factory heatsinks, warranty and the label trap&lt;/h2>
&lt;p>A drive that ships with a heatsink is a different product from the same drive without one, and the differences are not only thermal. Samsung lists the 9100 PRO with Heatsink as its own model line with its own part numbers, a wider 25 mm body, and a taller profile that it explicitly tells you to check against your host system before installation. It also warns against overtightening the drive to the motherboard.&lt;/p>
&lt;p>That is worth reading twice, because the obvious failure mode with a tall heatsink is not heat. It is mechanical stress on the connector. A plate that fouls a GPU backplate can push the drive out of its slot at an angle, and that is how people damage M.2 connectors.&lt;/p>
&lt;p>The warranty rules differ by maker and by model, and they are the part I would check before buying a factory-heatsink drive. Crucial&amp;rsquo;s five-year coverage is tied to the TBW limit as well as the date, counted from SMART data. Samsung voids coverage on the heatsink model if you remove the heatsink. Neither policy is unusual, and both mean the same thing: decide which cooling path you are using before you install the drive, not after.&lt;/p>
&lt;h2 id="what-i-would-check-before-buying">What I would check before buying&lt;/h2>
&lt;p>Five checks, in order, and most people stop at the first one.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Count the heatsinks you already own.&lt;/strong> Look at the board. If every slot you plan to use has a plate and a pad, you are done.&lt;/li>
&lt;li>&lt;strong>Read the drive&amp;rsquo;s form factor row.&lt;/strong> The maximum thickness and the maximum length are both there. Match them against the slot and the pad.&lt;/li>
&lt;li>&lt;strong>Look at the slot under the GPU.&lt;/strong> Measure or eyeball the gap with the card fitted. This is the slot that decides whether a tall heatsink is possible.&lt;/li>
&lt;li>&lt;strong>Confirm you are not double-stacking.&lt;/strong> A factory-heatsink drive gets no board plate. A board plate comes off before a third-party heatsink goes on.&lt;/li>
&lt;li>&lt;strong>Check the temperatures before spending.&lt;/strong> S.M.A.R.T. reports the drive&amp;rsquo;s own sensor, and the &lt;a href="https://techfuelhq.com/articles/ssd-health-check-2026/">SSD health check guide&lt;/a> walks through reading it. A drive sitting at 45 °C under load does not need anything. A drive pinned at 70 °C and dropping speed does.&lt;/li>
&lt;/ol>
&lt;p>The &lt;a href="https://techfuelhq.com/tools/nvme-expansion-checker/">NVMe expansion checker&lt;/a> is the faster path if the question is really about how many drives you can add and how they will share lanes. Heatsinks are the last decision in that chain, not the first. If the machine is a homelab box running sustained writes around the clock, the &lt;a href="https://techfuelhq.com/articles/best-nvme-ssd-homelab-2026/">homelab NVMe guide&lt;/a> covers the endurance and power side that matters more than a few millimetres of aluminium.&lt;/p></description></item><item><title>How to Tell If Your AIO Pump Is Working (2026)</title><link>https://techfuelhq.com/articles/how-to-tell-if-aio-pump-is-working-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/how-to-tell-if-aio-pump-is-working-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;p>A failed AIO pump is the quietest hardware failure in a PC. The fans keep spinning, the lighting stays on, nothing beeps, and the machine boots normally. The only thing that changes is that the processor starts running hot, and by the time most people notice, they have already blamed the paste, the case, or the weather.&lt;/p>
&lt;p>The good news is that the pump is not a mystery component. It reports its own speed, and that number is either inside the manufacturer&amp;rsquo;s range or it is not. Everything else on this page is about making sure you are reading the right number.&lt;/p>
&lt;h2 id="the-pump-tach-is-the-whole-diagnosis">The pump tach is the whole diagnosis&lt;/h2>
&lt;p>Every pump on a modern AIO has a tachometer output on its control connector. That is the third pin on a standard fan-type header, and it is what the motherboard reads to show you an RPM figure. If the pump is turning, the number is non-zero. If the number is zero or absent on the correct header, the pump is not turning or not reporting.&lt;/p>
&lt;p>Know what the range should be before you judge the reading:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Cooler&lt;/th>
&lt;th scope="col">Pump speed specification&lt;/th>
&lt;th scope="col">Connector&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Cooler">ARCTIC Liquid Freezer III 360&lt;/td>
&lt;td data-label="Pump speed specification">800–2800 rpm, PWM controlled, 12 V DC, 0.35 A&lt;/td>
&lt;td data-label="Connector">4-pin PWM&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Cooler">NZXT Kraken Plus (2026)&lt;/td>
&lt;td data-label="Pump speed specification">1,200–3,200 rpm ±300, Asetek Gen 9&lt;/td>
&lt;td data-label="Connector">4-pin PWM&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Cooler">NZXT Kraken Core (2025)&lt;/td>
&lt;td data-label="Pump speed specification">3,100 rpm ±310 (fixed)&lt;/td>
&lt;td data-label="Connector">3-pin DC fan header&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Those figures come straight from the manufacturers: Arctic&amp;rsquo;s &lt;a href="https://www.arctic.de/media/16/63/19/1708429821/Spec_Sheet_Liquid_Freezer_III_360_Black_EN.pdf" rel="noopener">Liquid Freezer III 360 specification sheet&lt;/a>, NZXT&amp;rsquo;s &lt;a href="https://support.nzxt.com/hc/en-us/articles/58318166453659-What-are-the-specs-of-the-pump-in-the-Kraken-Plus-2026" rel="noopener">Kraken Plus pump article&lt;/a>, and NZXT&amp;rsquo;s &lt;a href="https://support.nzxt.com/hc/en-us/articles/41097983638299-Kraken-Core-2025-Specs" rel="noopener">Kraken Core (2025) spec sheet&lt;/a>. Read yours before you test, because &amp;ldquo;500 rpm&amp;rdquo; means something different on a 3,100 rpm fixed pump than on an 800 rpm floor.&lt;/p>
&lt;p>A pump reading in range does not prove the loop is healthy, and a pump reading zero does not always mean the pump is dead. That is why the next two sections exist.&lt;/p>
&lt;h2 id="read-the-header-before-you-touch-the-tubes">Read the header before you touch the tubes&lt;/h2>
&lt;p>People squeeze the tubes first. It feels like evidence. It is not.&lt;/p>
&lt;p>The supply tube carries hot coolant away from the block, and the return tube warms partly by conduction along the fitting and the rubber even when the water inside is barely moving. A warm tube tells you the block is hot. It does not tell you the impeller is turning.&lt;/p>
&lt;p>Read the header instead. On an ASUS board the fan page lives in Advanced Mode (F7) under Monitor, then Q-Fan Configuration, per &lt;a href="https://dlcdnets.asus.com/pub/ASUS/mb/LGA1151/STRIX_B250F_GAMING/E12497_STRIX_B250F-GAMING_BIOS_UM_web_only_20170706.pdf" rel="noopener">ASUS&amp;rsquo;s BIOS user manual&lt;/a>. That page lists every header and the speed it currently reports, which is exactly the reading you need.&lt;/p>
&lt;p>Which header should the pump be on? If the board has a dedicated pump header, that is the one. ASUS&amp;rsquo;s manual for the &lt;a href="https://dlcdnets.asus.com/pub/ASUS/mb/Socket%20AM5/ROG%20STRIX%20B650-A%20GAMING%20WIFI/E20268_ROG_STRIX_B650-A_GAMING_WIFI_UM_WEB.pdf" rel="noopener">ROG STRIX B650-A Gaming WiFi&lt;/a> says to connect a water-cooling kit&amp;rsquo;s pump connector to the AIO_PUMP header, and its header table shows that AIO_PUMP defaults to full speed while CPU_FAN and CPU_OPT are Q-Fan controlled. NZXT&amp;rsquo;s guidance for the Kraken Plus points the same direction: use CPU_FAN or AIO_PUMP, and not a CAM-powered controller.&lt;/p>
&lt;p>If the pump is on a header that is switched off in the fan configuration page, you will see no reading at all and the pump may not be receiving what it needs. That is a settings failure masquerading as a hardware failure, and it costs nothing to rule out.&lt;/p>
&lt;h2 id="match-the-header-mode-to-the-connector">Match the header mode to the connector&lt;/h2>
&lt;p>This is the step that catches the most false alarms, and it is also the step most guides skip.&lt;/p>
&lt;p>Fan and pump headers can run in PWM mode or DC (voltage) mode. ASUS&amp;rsquo;s BIOS manual lists exactly that choice: PWM Mode for a 4-pin fan, DC Mode for a 3-pin fan. Pick the wrong one and the header either cannot modulate the device or cannot read it properly.&lt;/p>
&lt;p>That matters because AIO pumps are not uniform. The Arctic Liquid Freezer III and the NZXT Kraken Plus use 4-pin PWM connectors. The NZXT Kraken Core (2025) uses a 3-pin DC fan header. A 3-pin pump on a header configured for PWM has no control line to talk to, so check the mode against the connector before you decide anything is broken.&lt;/p>
&lt;p>While you are in that page, look at the low-speed warning setting. The same ASUS manual shows CPU Fan Speed Lower Limit defaulting to 200 RPM, which exists so the board can warn you that a fan or pump has stopped. If your pump can legitimately idle below that floor, the warning will fire on a healthy cooler. If your pump should never drop that low, the warning is a useful alarm you should leave on.&lt;/p>
&lt;h2 id="is-it-the-pump-the-mount-or-the-firmware">Is it the pump, the mount, or the firmware?&lt;/h2>
&lt;p>Three different faults produce the same headline symptom: a hot CPU. Separate them with the table below.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">What you observe&lt;/th>
&lt;th scope="col">Most likely cause&lt;/th>
&lt;th scope="col">First check&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="What you observe">Pump RPM zero, CPU hot within seconds of load&lt;/td>
&lt;td data-label="Most likely cause">Pump not powered or failed&lt;/td>
&lt;td data-label="First check">Pump power lead and header assignment&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you observe">Pump RPM in range, CPU still hot&lt;/td>
&lt;td data-label="Most likely cause">Mounting, contact, or airflow&lt;/td>
&lt;td data-label="First check">Cold plate contact and radiator airflow&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you observe">Pump RPM correct but drops to zero under load&lt;/td>
&lt;td data-label="Most likely cause">Header curve or power delivery&lt;/td>
&lt;td data-label="First check">Header mode, profile, and pump lead seating&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you observe">Pump RPM normal, temps changed after a BIOS flash&lt;/td>
&lt;td data-label="Most likely cause">Firmware reset header settings&lt;/td>
&lt;td data-label="First check">Monitor &amp;gt; Q-Fan Configuration&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you observe">Gurgling or intermittent RPM after moving the case&lt;/td>
&lt;td data-label="Most likely cause">Air trapped at the impeller&lt;/td>
&lt;td data-label="First check">Cooler manual&amp;rsquo;s orientation guidance&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The first row is the one that ends in a warranty claim. The second row is the one that ends in a repaste, and it is far more common than people expect. If the pump is turning and the radiator is getting hot, the loop is moving heat; the problem is that heat is not getting into the loop efficiently, or not leaving the radiator.&lt;/p>
&lt;p>The fourth row is worth dwelling on. A BIOS update or a CMOS clear can return fan and pump headers to defaults. A header you had set to full speed can come back on a quiet profile, and the pump slows without any hardware change. If your temperatures changed on the same day you flashed firmware, check the fan configuration page before you order parts.&lt;/p>
&lt;h2 id="ordered-checks-that-survive-a-reboot">Ordered checks that survive a reboot&lt;/h2>
&lt;p>Work top to bottom. The first four cost nothing and take minutes.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Boot into the BIOS and open the fan page.&lt;/strong> Advanced Mode (F7), then Monitor, then Q-Fan Configuration on ASUS boards. Write down the pump header&amp;rsquo;s RPM and mode.&lt;/li>
&lt;li>&lt;strong>Confirm the header assignment.&lt;/strong> Pump on AIO_PUMP if the board has one, otherwise CPU_FAN. Check that the header is not disabled.&lt;/li>
&lt;li>&lt;strong>Match the mode to the connector.&lt;/strong> PWM for 4-pin pumps, DC for 3-pin pumps.&lt;/li>
&lt;li>&lt;strong>Set the pump header to full speed and re-read.&lt;/strong> On the B650-A the AIO_PUMP header already defaults to full speed, so a pump that still reads zero after this has a power or hardware problem.&lt;/li>
&lt;li>&lt;strong>Check the pump&amp;rsquo;s own power lead.&lt;/strong> Some coolers take power from a separate connector or SATA lead in addition to the tach header. Seat both ends.&lt;/li>
&lt;li>&lt;strong>Watch the temperature response.&lt;/strong> If the pump is genuinely dead, the CPU climbs toward its limit quickly under light load. AMD lists 95 °C as the maximum operating temperature for the &lt;a href="https://www.amd.com/en/products/processors/desktops/ryzen/9000-series/amd-ryzen-7-9800x3d.html" rel="noopener">Ryzen 7 9800X3D&lt;/a> and 89 °C for the &lt;a href="https://www.amd.com/en/products/processors/desktops/ryzen/7000-series/amd-ryzen-7-7800x3d.html" rel="noopener">Ryzen 7 7800X3D&lt;/a>; a chip pinned there in a browser is not a fan-curve problem.&lt;/li>
&lt;li>&lt;strong>Confirm the radiator fans separately.&lt;/strong> They can run while the pump is still. On the Arctic unit the split cable lets you control pump, VRM fan, and radiator fans independently, which makes this easy to check and easy to misread.&lt;/li>
&lt;li>&lt;strong>Save your readings.&lt;/strong> A written record of header, mode, RPM, and temperature survives a reboot. Your memory of a number you saw once does not.&lt;/li>
&lt;/ol>
&lt;p>Two things survive a reboot and one does not. A change you make in the BIOS fan page persists. A record you saved to a file persists. A Windows-only fan utility curve may not survive a clean boot or a driver update, which is why I prefer to settle the pump question in firmware before involving software.&lt;/p>
&lt;p>If you want the temperature side in more depth, the &lt;a href="https://techfuelhq.com/articles/how-to-check-cpu-temp-2026/">CPU temperature check guide&lt;/a> covers the tools and the &lt;a href="https://techfuelhq.com/articles/safe-cpu-temp-2026/">safe CPU temperature guide&lt;/a> covers the ceilings by model. The &lt;a href="https://techfuelhq.com/articles/cpu-gpu-thermal-throttling-fix-2026/">thermal throttling guide&lt;/a> explains how to confirm the chip is actually being slowed rather than merely warm. If the machine also stops producing a picture, that is a separate display fault; the &lt;a href="https://techfuelhq.com/articles/cpu-overheating-2026/">CPU overheating guide&lt;/a> covers the cooling side from the top.&lt;/p>
&lt;h2 id="when-to-stop">When to stop&lt;/h2>
&lt;p>Stop troubleshooting and use the warranty when the evidence is unambiguous.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Zero pump RPM with the lead seated and the header configured correctly.&lt;/strong> That is a failed pump, not a settings problem.&lt;/li>
&lt;li>&lt;strong>Pump RPM outside its rated range and a CPU that still overheats.&lt;/strong> The impeller may be turning without moving coolant. Either way, the unit is not doing its job.&lt;/li>
&lt;li>&lt;strong>Repeated air-lock symptoms after you have followed the cooler manual&amp;rsquo;s orientation and tilt guidance.&lt;/strong> Do not keep power-cycling a loop that will not prime.&lt;/li>
&lt;li>&lt;strong>Any leak, smell, or audible grinding from the pump housing.&lt;/strong> Stop using the machine. Do not open the pump.&lt;/li>
&lt;li>&lt;strong>A pump that works and a CPU that still overheats.&lt;/strong> That is a mounting or airflow problem, and replacing the cooler without fixing contact will reproduce the symptom. Read the &lt;a href="https://techfuelhq.com/articles/cpu-overheating-2026/">CPU overheating guide&lt;/a> before you buy anything.&lt;/li>
&lt;/ul>
&lt;p>If you are still uncertain after the checks above, the &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">diagnostic workbench&lt;/a> lets you log each step and the reading beside it, so the next person to look at the machine starts from evidence instead of a description.&lt;/p></description></item><item><title>GPU Hotspot Temperature: Normal Delta and Fault Signs (2026)</title><link>https://techfuelhq.com/articles/gpu-hotspot-temperature-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/gpu-hotspot-temperature-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;p>A reader sends me an overlay screenshot about once a week. The GPU temperature line says something calm, the hotspot line says something alarming, and the question is always the same: is the card dying? Almost every time, the honest answer is that one number cannot tell you, because the useful measurement is the gap between the two.&lt;/p>
&lt;p>I am not going to hand you a magic delta threshold. Neither NVIDIA nor AMD publishes one, and any site that gives you a single number is guessing on your behalf. What the vendors do document is how to read the sensors and how to tell whether the card is actually being slowed down by heat. That is enough to make a real decision.&lt;/p>
&lt;h2 id="what-the-hotspot-reading-actually-is">What the hotspot reading actually is&lt;/h2>
&lt;p>The hotspot, which AMD&amp;rsquo;s software calls the junction temperature, is the hottest point on the graphics die. The ordinary GPU temperature line is a different, lower sensor, usually described as edge or core temperature. Our own &lt;a href="https://techfuelhq.com/data/gpu-hotspot-delta-census/">GPU hotspot delta census&lt;/a> defines it plainly: the hotspot is the highest reading among the temperature sensors on the die, and the delta is hotspot minus core from the same session.&lt;/p>
&lt;p>That definition matters because it tells you what the delta is measuring. It is not a verdict. It is a description of how evenly heat is crossing from silicon into the cold plate. A wide spread means one region of the die is much hotter than the part the edge sensor sees.&lt;/p>
&lt;p>NVIDIA does not expose the field in its own command-line tool. The &lt;a href="https://docs.nvidia.com/deploy/nvidia-smi/index.html" rel="noopener">nvidia-smi documentation&lt;/a> describes board temperature readings and a T.Limit sensor that reports the margin to the maximum operating temperature, and it does not list a hotspot reading anywhere. On RTX 50 cards the number comes from third-party software, which is exactly why tool version matters so much here.&lt;/p>
&lt;h2 id="edge-hotspot-and-memory-are-three-different-jobs">Edge, hotspot, and memory are three different jobs&lt;/h2>
&lt;p>People collapse these into one &amp;ldquo;GPU temp&amp;rdquo; and then argue about it. Keep them apart:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Reading&lt;/th>
&lt;th scope="col">What it describes&lt;/th>
&lt;th scope="col">What it is good for&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Reading">GPU temperature (edge)&lt;/td>
&lt;td data-label="What it describes">A core sensor, typically the cooler-running of the die readings&lt;/td>
&lt;td data-label="What it is good for">Tracking overall cooler performance and fan response&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Reading">Hotspot / junction&lt;/td>
&lt;td data-label="What it describes">The hottest die sensor&lt;/td>
&lt;td data-label="What it is good for">Judging how evenly the die is being cooled&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Reading">Memory junction&lt;/td>
&lt;td data-label="What it describes">GDDR package sensors&lt;/td>
&lt;td data-label="What it is good for">Judging memory cooling, separate from die contact&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The delta is computed from the first two, and only if both come from the same sustained run. Our census validator rejects a hotspot below core, a hotspot outside its documented 20–125 °C range, a core outside 20–100 °C, and any load shorter than ten minutes. Those rules exist because a ten-second screenshot of a menu is not a thermal measurement.&lt;/p>
&lt;p>This is the single most common mistake I see in forum threads: someone records a core maximum from one run and a hotspot maximum from another, subtracts them, and posts the result. Two session maxima are not a delta. They may have happened minutes apart under different loads.&lt;/p>
&lt;h2 id="the-bands-and-what-i-check-in-each">The bands, and what I check in each&lt;/h2>
&lt;p>Our census publishes exact-model distributions in five fixed bands rather than inventing a universal limit: 0–9 °C, 10–19 °C, 20–29 °C, 30–39 °C, and 40 °C or higher. The edges are part of the dataset version, so a row collected this year stays comparable to one collected next year.&lt;/p>
&lt;p>Here is how I use each band. This is a diagnostic posture, not a measurement I am claiming to have taken:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Delta band&lt;/th>
&lt;th scope="col">How I read it&lt;/th>
&lt;th scope="col">First thing I check&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Delta band">0–9 °C&lt;/td>
&lt;td data-label="How I read it">Unusually tight. Possible, but confirm the tool is not repeating one sensor.&lt;/td>
&lt;td data-label="First thing I check">Tool name and version; whether the hotspot field is supported on this card&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Delta band">10–19 °C&lt;/td>
&lt;td data-label="How I read it">The ordinary working range for a card with good contact&lt;/td>
&lt;td data-label="First thing I check">Nothing, if clocks and throttle flags are healthy&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Delta band">20–29 °C&lt;/td>
&lt;td data-label="How I read it">Worth watching. Often load, airflow, or fan-curve dependent&lt;/td>
&lt;td data-label="First thing I check">Sustained-load duration, case airflow, fan curve&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Delta band">30–39 °C&lt;/td>
&lt;td data-label="How I read it">A contact or mounting conversation is reasonable&lt;/td>
&lt;td data-label="First thing I check">Mounting pressure, paste or pad state, cooler seating&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Delta band">40 °C or higher&lt;/td>
&lt;td data-label="How I read it">The pattern I treat as a fault until proven otherwise&lt;/td>
&lt;td data-label="First thing I check">Full remount, or warranty service if the card is covered&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Two cautions before you act on that table. A zero-degree delta is valid in our schema, but a tool that is reading the wrong sensor can also produce one, so verify support before you celebrate. And a delta in the 20s on a hot day in a cramped case is not the same finding as the same delta in a ventilated tower at stock settings.&lt;/p>
&lt;h2 id="confirm-the-tool-before-you-believe-the-number">Confirm the tool before you believe the number&lt;/h2>
&lt;p>This is the step almost everyone skips, and it is where half the &amp;ldquo;my hotspot is broken&amp;rdquo; reports come from.&lt;/p>
&lt;p>On the NVIDIA side, CPUID&amp;rsquo;s &lt;a href="https://www.cpuid.com/softwares/hwmonitor.html" rel="noopener">HWMonitor changelog&lt;/a> records hotspot temperature on RTX 50 GPUs as fixed in version 1.65.1, and version 1.66 as improving the hotspot report on AMD Radeon RX 9000 cards. On Linux, &lt;a href="https://github.com/ilya-zlobintsev/LACT/releases/tag/v0.10.0" rel="noopener">LACT v0.10.0&lt;/a> says the hotspot sensor on Blackwell &amp;ldquo;now works with a Blackwell-specific path, instead of reporting bogus values,&amp;rdquo; and the project&amp;rsquo;s &lt;a href="https://github.com/ilya-zlobintsev/LACT/pull/1122" rel="noopener">pull request 1122&lt;/a> is where that path was added.&lt;/p>
&lt;p>&amp;ldquo;Instead of reporting bogus values&amp;rdquo; is the sentence to remember. A wrong sensor path does not usually throw an error. It hands you a plausible number that describes something else, and you build a whole theory on top of it.&lt;/p>
&lt;p>On AMD cards the driver exposes both readings directly. &lt;a href="https://www.amd.com/en/resources/support-articles/faqs/DH3-038.html" rel="noopener">AMD&amp;rsquo;s performance metrics article DH3-038&lt;/a> lists both GPU Current Temperature and GPU Junction Temperature among the metrics you can log, with a sampling interval adjustable from 0.25 to 5 seconds. &lt;a href="https://www.amd.com/en/resources/support-articles/faqs/DH3-020.html" rel="noopener">DH3-020&lt;/a> notes that GPU Hotspot Temperature is only available on Radeon VII, Radeon RX 5000 Series and newer products. If you are on an older card, the field may simply not exist on your hardware.&lt;/p>
&lt;p>So the first check is free and takes ten seconds: write down the tool name and exact version next to every reading you plan to compare. That record survives a reboot, and it is the one piece of evidence you will still have when the numbers stop making sense.&lt;/p>
&lt;h2 id="is-the-card-actually-being-slowed-down">Is the card actually being slowed down?&lt;/h2>
&lt;p>A wide delta is not proof of throttling. It is proof of an uneven thermal profile. Whether that costs you performance is a separate question, and both vendors expose a flag for it.&lt;/p>
&lt;p>On NVIDIA hardware, the &lt;a href="https://docs.nvidia.com/deploy/nvml-api/latest/api/group__nvmlClocksEventReasons.html" rel="noopener">NVML clocks event reasons&lt;/a> separate software and hardware thermal slowdown from power capping and other reasons for reduced clocks. In practice that means you can see whether the card is being held back by heat or by its wattage limit, which are completely different problems with completely different fixes.&lt;/p>
&lt;p>The T.Limit reading in &lt;a href="https://docs.nvidia.com/deploy/nvidia-smi/index.html" rel="noopener">nvidia-smi&lt;/a> is the quick version. It reports margin, not temperature, and the documentation says a T.Limit value of 0 °C or lower indicates the GPU may optimize its clock based on thermal conditions. A healthy margin that stays positive under load is a good sign.&lt;/p>
&lt;p>Run the query while the load is running, not after:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-powershell" data-lang="powershell">&lt;span style="display:flex;">&lt;span>nvidia-smi -q -d TEMPERATURE,POWER,CLOCK,PERFORMANCE
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Save that output to a file. A log on disk survives a reboot; a live overlay reading does not, and the moment you restart to reseat a cable you lose the evidence you were about to reason from.&lt;/p>
&lt;p>On AMD, the junction reading and the clock behavior in the same overlay give you the same comparison, with the 0.25-second sampling floor from DH3-038 fine enough to catch a spike.&lt;/p>
&lt;h2 id="ordered-checks-cheapest-first">Ordered checks, cheapest first&lt;/h2>
&lt;p>Work down this list and stop as soon as the pattern resolves. Each step is cheaper and less invasive than the one below it.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Take one honest reading.&lt;/strong> Same session, same load, at least ten minutes, both numbers recorded together. If you cannot satisfy that, you do not have data yet.&lt;/li>
&lt;li>&lt;strong>Verify the tool version.&lt;/strong> Check the changelog for your card family. On RTX 50, HWMonitor below 1.65.1 or LACT below 0.10.0 is not a reading you should build a decision on.&lt;/li>
&lt;li>&lt;strong>Check the throttle flag.&lt;/strong> Positive T.Limit margin and no thermal slowdown event means the delta is not costing you clocks, whatever it looks like.&lt;/li>
&lt;li>&lt;strong>Look at fan behavior.&lt;/strong> A curve that never ramps, or a zero-RPM mode that never exits under load, produces a wide delta for reasons that have nothing to do with paste. The &lt;a href="https://techfuelhq.com/articles/gpu-fans-stuck-at-100-percent/">GPU fans stuck at full speed guide&lt;/a> covers the opposite failure, where the controller reacts to a sensor you cannot see.&lt;/li>
&lt;li>&lt;strong>Test case airflow without changing hardware.&lt;/strong> Remove the side panel while the load runs and watch whether both readings fall together. If they do, the problem is the enclosure and the fan curves, not the card.&lt;/li>
&lt;li>&lt;strong>Only then consider the mount.&lt;/strong> If the delta stays wide with airflow and fans sorted, the remaining suspects are mounting pressure and the thermal interface. Even screw torque in an X pattern, verified contact, and a fresh interface are the correct sequence. Phase-change pads exist precisely because ordinary paste can migrate out of a bare-die joint over many heat cycles.&lt;/li>
&lt;li>&lt;strong>Undervolt last.&lt;/strong> Once the mechanical side is right, a flatter voltage-frequency curve reduces total heat. It does not repair contact, and applying it first just moves both numbers down and hides the fault.&lt;/li>
&lt;/ol>
&lt;p>If you want the full flag-by-flag walkthrough for both processors and graphics cards, the &lt;a href="https://techfuelhq.com/articles/cpu-gpu-thermal-throttling-fix-2026/">thermal throttling fix guide&lt;/a> goes deeper on the telemetry side, and the &lt;a href="https://techfuelhq.com/articles/gpu-overheating-2026/">GPU overheating guide&lt;/a> covers the physical checks. For a model-by-model ceiling reference, the &lt;a href="https://techfuelhq.com/articles/safe-gpu-temp-2026/">safe GPU temperature guide&lt;/a> is the companion piece.&lt;/p>
&lt;h2 id="when-to-stop">When to stop&lt;/h2>
&lt;p>Stop diagnosing and start deciding when one of these is true.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>The card is under warranty and the delta pattern points at contact.&lt;/strong> A support ticket is cheaper than a voided warranty. Policies vary by brand and region, so read the terms for your exact model before the screwdriver comes out.&lt;/li>
&lt;li>&lt;strong>The delta stays wide after a correct remount.&lt;/strong> One careful remount with verified contact and an even torque pattern is a reasonable attempt. A second and third are not diagnosis, they are hope. If the spread persists, the card needs service or replacement.&lt;/li>
&lt;li>&lt;strong>The hotspot reads below the edge temperature.&lt;/strong> That is not a hot card, that is a sensor or tool problem. Recheck the version before you touch hardware.&lt;/li>
&lt;li>&lt;strong>The throttle flag never fires and clocks hold.&lt;/strong> Then you have a cosmetic number, not a fault. Close the overlay and go use the machine.&lt;/li>
&lt;/ul>
&lt;p>If none of the checks resolve it, the &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">diagnostic workbench&lt;/a> lets you record each test result and the readings beside it so a technician gets a record instead of a story. And if you have a reading worth contributing, the &lt;a href="https://techfuelhq.com/data/gpu-hotspot-delta-census/">census intake&lt;/a> is open — that dataset is how the bands above get better over time.&lt;/p></description></item><item><title>Game Ready vs Studio Drivers: Which Should You Install?</title><link>https://techfuelhq.com/articles/game-ready-vs-studio-driver-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/game-ready-vs-studio-driver-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Game Ready vs Studio&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Game on that machine at all?&lt;/strong> Game Ready. NVIDIA ties its release cadence to major game launches.&lt;/li>
&lt;li>&lt;strong>Does the machine pay for itself in creative apps?&lt;/strong> Studio. It is tested against top creative applications and ships on a slower, app-driven cadence.&lt;/li>
&lt;li>&lt;strong>Both run everything.&lt;/strong> NVIDIA states all its drivers provide full feature and application support for top games and creative apps; this is a priority choice, not a capability switch.&lt;/li>
&lt;li>&lt;strong>Switching is one toggle&lt;/strong> in the NVIDIA App's three-dot menu, or a clean install via Custom (Advanced).&lt;/li>
&lt;li>&lt;strong>You cannot run both at once.&lt;/strong> One branch is installed at a time.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>NVIDIA ships two driver branches from one codebase, and the choice between them is about what you want tested on your behalf. Game Ready tracks game launches. Studio tracks creative-application releases and is validated against the tools people use to earn a living. Neither branch is crippled on the other&amp;rsquo;s workload.&lt;/p>
&lt;p>So the decision is small and practical: which of your two workloads is more expensive to have interrupted? If a stutter in a new release costs you an evening, stay on Game Ready. If a crashed render at 2 a.m. costs you a deadline, move to Studio.&lt;/p>
&lt;h2 id="what-actually-differs-between-the-two-branches">What actually differs between the two branches&lt;/h2>
&lt;p>NVIDIA&amp;rsquo;s &lt;a href="https://nvidia.custhelp.com/app/answers/detail/a_id/4931/~/nvidia-studio-faqs" rel="noopener">Studio FAQ&lt;/a> describes Studio Drivers as &amp;ldquo;drivers that are specially designed for creators,&amp;rdquo; released &amp;ldquo;on a regular, longer cadence that matches major app launches, typically every month,&amp;rdquo; and &amp;ldquo;extensively tested against the top creative apps.&amp;rdquo; The same page explains the other branch: &amp;ldquo;In 2014, NVIDIA created the Game Ready Driver program to provide the best day-0 gaming experience,&amp;rdquo; and &amp;ldquo;the release cadence for Game Ready Drivers is driven by the release of major new game content.&amp;rdquo;&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">&lt;/th>
&lt;th scope="col">Game Ready&lt;/th>
&lt;th scope="col">Studio&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="">Release trigger&lt;/td>
&lt;td data-label="Game Ready">Major new game content&lt;/td>
&lt;td data-label="Studio">Major creative app launches&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Cadence, per NVIDIA&lt;/td>
&lt;td data-label="Game Ready">Driven by game releases&lt;/td>
&lt;td data-label="Studio">Regular, longer, typically monthly&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Validation emphasis&lt;/td>
&lt;td data-label="Game Ready">Day-0 game experience&lt;/td>
&lt;td data-label="Studio">Stability across creative applications and workflows&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Feature set&lt;/td>
&lt;td data-label="Game Ready">Full, per NVIDIA&lt;/td>
&lt;td data-label="Studio">Full, per NVIDIA&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Can run games&lt;/td>
&lt;td data-label="Game Ready">Yes&lt;/td>
&lt;td data-label="Studio">Yes&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Can run creative apps&lt;/td>
&lt;td data-label="Game Ready">Yes&lt;/td>
&lt;td data-label="Studio">Yes&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Installable together&lt;/td>
&lt;td data-label="Game Ready">No&lt;/td>
&lt;td data-label="Studio">No&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="">Switch method&lt;/td>
&lt;td data-label="Game Ready">Toggle, or clean install&lt;/td>
&lt;td data-label="Studio">Toggle, or clean install&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The row that surprises people is the feature set. NVIDIA&amp;rsquo;s own wording on the FAQ is that &amp;ldquo;all NVIDIA drivers provide full features and application support for top games and creative applications.&amp;rdquo; Studio is not a stripped branch and Game Ready is not a gaming-only build. They are differently validated, differently scheduled builds.&lt;/p>
&lt;p>That difference in schedule is the real content of the decision. A branch cut more often is a branch with more opportunities to change something you depend on. A branch cut less often is a branch you spend more time on, between the changes you get.&lt;/p>
&lt;h2 id="what-nvidia-says-about-each-program">What NVIDIA says about each program&lt;/h2>
&lt;p>The &lt;a href="https://www.nvidia.com/en-us/geforce/game-ready-drivers/" rel="noopener">Game Ready page&lt;/a> describes a process built around launch deadlines rather than a general optimisation pass: &amp;ldquo;We work closely with game developers throughout development, providing prerelease drivers and test data. NVIDIA&amp;rsquo;s Game Ready process keeps optimizing up to the last moment to ensure the best possible experience at launch.&amp;rdquo; The same page states that each driver is &amp;ldquo;independently WHQL-Certified by Microsoft for maximum reliability.&amp;rdquo;&lt;/p>
&lt;p>That last point matters for people who assume Game Ready is the less stable branch. The gaming branch is separately WHQL-certified, and NVIDIA&amp;rsquo;s Studio material instead leads with its testing against creative applications. The practical difference is where the testing hours went, not which one passed a stability bar.&lt;/p>
&lt;p>The &lt;a href="https://www.nvidia.com/en-us/studio/" rel="noopener">Studio page&lt;/a> frames the other side in terms of reliability for production work: &amp;ldquo;Designed for creators, NVIDIA Studio Drivers are GPU-tuned updates that ensure rock-solid stability and peak performance for every creative workflow.&amp;rdquo; The FAQ adds that Studio Drivers &amp;ldquo;provide extensive testing against top creative applications and workflows for the best performance possible, and support any major creative app updates to ensure that you are ready to update any apps on Day 1.&amp;rdquo;&lt;/p>
&lt;p>Read those two quotes side by side and the design intent is unambiguous. Both branches are chasing day-one readiness, just for different day ones.&lt;/p>
&lt;h2 id="who-should-run-studio-drivers">Who should run Studio Drivers&lt;/h2>
&lt;p>Run Studio when the GPU&amp;rsquo;s main job is patching, grading, modelling, rendering, or streaming, and an interruption is a business cost rather than an annoyance.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Video editing and colour work.&lt;/strong> The branch is tested against the applications in that workflow, which is the useful part when a driver update lands mid-project.&lt;/li>
&lt;li>&lt;strong>3D, animation, and CAD-adjacent work.&lt;/strong> Same logic: validation against the tools, on a cadence that follows those tools&amp;rsquo; releases.&lt;/li>
&lt;li>&lt;strong>Photography and graphic design.&lt;/strong> If the machine exists to move pixels into deliverables, take the branch built for that.&lt;/li>
&lt;li>&lt;strong>Live-streaming rigs.&lt;/strong> NVIDIA&amp;rsquo;s FAQ names live-streaming among the creative workflows Studio is aimed at.&lt;/li>
&lt;li>&lt;strong>Machines that game sometimes.&lt;/strong> Studio does not remove that ability, and NVIDIA does not present it as doing so.&lt;/li>
&lt;/ul>
&lt;p>What Studio does not buy you is a promise about gaming. NVIDIA&amp;rsquo;s guidance is directional: if launch-day game support is your priority, Game Ready is the branch it points you to. It does not claim Studio fails at games, and it does not publish a gaming penalty for Studio either way, so I am not going to invent one.&lt;/p>
&lt;h2 id="who-should-stay-on-game-ready">Who should stay on Game Ready&lt;/h2>
&lt;p>Stay on Game Ready if new releases are what you actually care about.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>You buy games in their launch window.&lt;/strong> The branch exists because profiles ship with the releases, as the Game Ready page describes with its &amp;ldquo;optimizing up to the last moment&amp;rdquo; line.&lt;/li>
&lt;li>&lt;strong>You play competitive multiplayer where patches move the ground under you.&lt;/strong> A mid-season patch is a &amp;ldquo;major new game content&amp;rdquo; event in the sense that matters here.&lt;/li>
&lt;li>&lt;strong>You do creative work occasionally, not professionally.&lt;/strong> A crashed export on a hobby project is annoying; it is not a deadline, and the gaming side is where your hours go.&lt;/li>
&lt;li>&lt;strong>You are troubleshooting.&lt;/strong> When you are isolating a graphics fault, changing branches adds a variable. Settle the branch question first.&lt;/li>
&lt;/ul>
&lt;p>If you are mid-diagnosis rather than mid-decision, the &lt;a href="https://techfuelhq.com/articles/gpu-driver-crash-fix-2026/">GPU driver crash fix guide&lt;/a> sequences the repair work, and the &lt;a href="https://techfuelhq.com/gaming/shader-cache-size-nvidia-2026/">shader cache page&lt;/a> covers the post-update stutter that follows either branch.&lt;/p>
&lt;h2 id="how-to-switch-and-what-to-check-afterward">How to switch, and what to check afterward&lt;/h2>
&lt;p>NVIDIA documents two switch paths, and they do different things.&lt;/p>
&lt;p>&lt;strong>The toggle, for a normal switch.&lt;/strong> The &lt;a href="https://nvidia.custhelp.com/app/answers/detail/a_id/4851" rel="noopener">Studio installation article&lt;/a> says: &amp;ldquo;Within NVIDIA App, click the menu (three vertical dots in the top right corner) to reveal a toggle. Select your preference and that&amp;rsquo;s what you&amp;rsquo;ll download and install.&amp;rdquo; The Studio FAQ describes the identical control inside GeForce Experience for older installations. This downloads and installs the other branch over the current one.&lt;/p>
&lt;p>&lt;strong>The clean installation, when you want a bare base.&lt;/strong> NVIDIA&amp;rsquo;s &lt;a href="https://nvidia.custhelp.com/app/answers/detail/a_id/10" rel="noopener">clean-install article&lt;/a> gives the installer path: choose &lt;strong>Custom (Advanced)&lt;/strong>, then &lt;strong>NEXT&lt;/strong>; on the next screen &amp;ldquo;enable the option labeled Perform a clean installation,&amp;rdquo; then &lt;strong>Next&lt;/strong>; and once installation completes, &amp;ldquo;reboot your PC to finalize the installation process.&amp;rdquo;&lt;/p>
&lt;p>The clean option resets your 3D settings. If you keep hand-tuned per-game profiles, note them down first. It is the right call when you are switching branches to escape a fault, and unnecessary when you are simply changing preference.&lt;/p>
&lt;p>After the switch, three things are worth checking:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Confirm the branch.&lt;/strong> NVIDIA&amp;rsquo;s &lt;a href="https://nvidia.custhelp.com/app/answers/detail/a_id/4848" rel="noopener">driver-identification article&lt;/a> says you can check the type of driver installed from NVIDIA App on the &lt;strong>DRIVERS&lt;/strong> tab. Version numbers alone will not tell you.&lt;/li>
&lt;li>&lt;strong>Expect first-launch compile cost.&lt;/strong> A new driver installation deletes the shader cache, which NVIDIA&amp;rsquo;s Control Panel reference warns can cause stutter the first time you run a game afterwards. That is the branch change, not a bad driver.&lt;/li>
&lt;li>&lt;strong>Re-check anything that depended on the old settings.&lt;/strong> Custom colour, per-game profiles, and app-specific configurations can reset under a clean install.&lt;/li>
&lt;/ol>
&lt;h2 id="amd-splits-its-drivers-differently">AMD splits its drivers differently&lt;/h2>
&lt;p>If you are on Radeon, the same question exists but the shape is different, and it is worth stating plainly because a lot of advice imports NVIDIA&amp;rsquo;s toggle model onto AMD.&lt;/p>
&lt;p>AMD has &lt;a href="https://www.amd.com/en/products/software/adrenalin.html" rel="noopener">AMD Software: Adrenalin Edition&lt;/a>, which the company describes as the interface for software features, game stats, and driver updates, and it has &lt;a href="https://www.amd.com/en/products/software/pro-edition.html" rel="noopener">AMD Software: PRO Edition&lt;/a>, presented as driving &amp;ldquo;enterprise-grade quality through extensive OEM platform validation and comprehensive ISV certification testing,&amp;rdquo; on a page about Radeon PRO GPUs.&lt;/p>
&lt;p>The &lt;a href="https://www.amd.com/en/resources/support-articles/release-notes/RN-PRO-WIN-26-Q3.html" rel="noopener">PRO Edition 26.Q3 release notes&lt;/a> spell out the intent: &amp;ldquo;AMD Software: PRO Edition is engineered to deliver market-leading stability, reliability, and uptime for professional workflows. Each release undergoes rigorous multi-wave testing and extensive ISV certification.&amp;rdquo; The same document lists supported operating systems as workstation platforms and defines compatibility by product family, naming Radeon AI PRO and Radeon PRO cards alongside Ryzen AI PRO processors.&lt;/p>
&lt;p>That last detail is the one to carry away. PRO Edition is not a preference toggle you flip on any Radeon card. Check AMD&amp;rsquo;s compatibility list for your exact GPU before assuming the professional branch is available to you. If your card is not on it, the decision on an AMD system is between Adrenalin builds, not between two branches. The numbering also differs: PRO releases carry a quarter-style designation like 26.Q3 rather than a game-facing version number.&lt;/p>
&lt;h2 id="which-one-i-would-install">Which one I would install&lt;/h2>
&lt;p>&lt;strong>A gaming-first desktop:&lt;/strong> Game Ready, and I would stop thinking about it. That is the branch whose release schedule is tied to the thing you bought the card for.&lt;/p>
&lt;p>&lt;strong>A workstation that also games:&lt;/strong> Studio. The cost of an interruption during a render or a colour pass is higher than the cost of being a week behind on a game profile, and NVIDIA states the gaming support is still there.&lt;/p>
&lt;p>&lt;strong>A new build you have not characterised yet:&lt;/strong> Game Ready until something gives you a reason to move. Changing branches to chase a fault before you have established the baseline means you cannot tell what fixed it.&lt;/p>
&lt;p>&lt;strong>A machine you switched and then forgot about:&lt;/strong> check the DRIVERS tab. Two branches that both run everything are easy to lose track of, and the branch you are on is a fact about the machine, not a preference you remember setting.&lt;/p>
&lt;p>Whatever you pick, keep it stable while you diagnose anything else. The &lt;a href="https://techfuelhq.com/tools/gpu-comparison/">GPU comparison tool&lt;/a> settles which card you should be troubleshooting, and if the symptom is a hitch rather than a crash, the &lt;a href="https://techfuelhq.com/articles/pc-stuttering-in-games-2026/">stuttering guide&lt;/a> will tell you whether the driver branch is even a candidate cause.&lt;/p></description></item><item><title>Black Spot on a Monitor: Dead Pixel, Dust or Burn-In?</title><link>https://techfuelhq.com/articles/black-spot-on-monitor-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/black-spot-on-monitor-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Black spot on a monitor&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Test before you touch.&lt;/strong> Solid white, red, green and blue full screen; the spot that survives all four is a panel defect, not content.&lt;/li>
&lt;li>&lt;strong>A single sharp dot and a soft blotch are different faults&lt;/strong> with different outcomes. Photograph both before you call support.&lt;/li>
&lt;li>&lt;strong>Clean the outside with a dry microfiber cloth&lt;/strong> and no pressure. Never open the panel to chase a particle.&lt;/li>
&lt;li>&lt;strong>Vendors publish their own limits.&lt;/strong> LG asks you to contact the seller at six or more dark spots across the three colour tests; check your own model's policy.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>A black spot that stays in the same place through every window, webpage and game is a panel problem, not a software one. The useful question is not &amp;ldquo;how do I remove it&amp;rdquo; but &amp;ldquo;which of four things is it&amp;rdquo;, because only one of them is a warranty conversation and only one of them is your own doing.&lt;/p>
&lt;p>The four are a dead or stuck pixel, a cluster of damaged pixels, a trapped particle or surface mark, and OLED wear. Each leaves different evidence, and the tests that separate them cost nothing and take ten minutes. Run those first, in the order below, and keep a photograph of each result.&lt;/p>
&lt;h2 id="four-faults-one-black-dot">Four faults, one black dot&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">What you see&lt;/th>
&lt;th scope="col">Most likely fault&lt;/th>
&lt;th scope="col">What settles it&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="What you see">One sharp pixel, dark on white, no larger than a pixel&lt;/td>
&lt;td data-label="Most likely fault">Dead subpixel&lt;/td>
&lt;td data-label="What settles it">Colour fields show it on every background&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you see">One bright or coloured dot on a black field&lt;/td>
&lt;td data-label="Most likely fault">Stuck subpixel&lt;/td>
&lt;td data-label="What settles it">Black full screen test&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you see">Soft-edged speck, unchanged by colour, faintly visible with power off&lt;/td>
&lt;td data-label="Most likely fault">Trapped particle or surface mark&lt;/td>
&lt;td data-label="What settles it">Clean the surface, then recheck&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you see">Jagged cluster of dark or discoloured pixels&lt;/td>
&lt;td data-label="Most likely fault">Pressure or impact damage&lt;/td>
&lt;td data-label="What settles it">Shape and history; usually visible in a built-in test&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you see">Ghost of a taskbar, logo or window frame&lt;/td>
&lt;td data-label="Most likely fault">Image retention or burn-in&lt;/td>
&lt;td data-label="What settles it">Whether it fades when other content runs&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>A single dead subpixel is a point defect. A cluster is a physical injury, and it usually has a story: a thumb on the panel while mounting a monitor arm, a keyboard dropped against the screen, a laptop lid closed on a pen. If you cannot find that story, look again at the light: a cluster often has a slightly different sheen at an angle, because the cell structure around it has been deformed.&lt;/p>
&lt;h2 id="the-free-tests-in-this-order">The free tests, in this order&lt;/h2>
&lt;ol>
&lt;li>&lt;strong>White first.&lt;/strong> Fill the screen with solid white. A dead pixel is at its most obvious here, and so is a dust speck.&lt;/li>
&lt;li>&lt;strong>Red, green and blue.&lt;/strong> LG&amp;rsquo;s monitor troubleshooting page uses these three backgrounds because a subpixel can fail on one channel and not the others, which is why a spot can look black on white and coloured on red. Look for the spot on each field and note whether it disappears.&lt;/li>
&lt;li>&lt;strong>Black.&lt;/strong> LG&amp;rsquo;s page also asks you to display black and look for bright spots; a stuck pixel is brightest against black.&lt;/li>
&lt;li>&lt;strong>The window drag.&lt;/strong> Open a white document and drag it slowly across the spot. If the spot moves with the window, it is content or a rendering artifact, not the panel.&lt;/li>
&lt;li>&lt;strong>The input switch.&lt;/strong> Change to an input with nothing connected, or turn the monitor off and shine a light across the panel at an angle. A mark that is still visible with no signal is on the surface or inside the panel stack.&lt;/li>
&lt;li>&lt;strong>The built-in test.&lt;/strong> Use the monitor&amp;rsquo;s own diagnostics if it has them. Dell&amp;rsquo;s support article explains that its built-in self-test &amp;ldquo;helps determine if the screen abnormality is an inherent problem with the Dell monitor&amp;rdquo;, and directs you to the model&amp;rsquo;s user guide under Troubleshooting, then Built-in diagnostics.&lt;/li>
&lt;/ol>
&lt;p>Write down what you saw for each step. A support agent will ask for the model number, the test used and a photo, and the order of your answers matters more than their confidence.&lt;/p>
&lt;h2 id="prove-the-spot-is-fixed-to-the-panel">Prove the spot is fixed to the panel&lt;/h2>
&lt;p>The window drag is the test most people skip, and it is the one that saves a wasted warranty claim. If the black spot moves when you scroll, the panel is fine and something in the rendering path produced it. Capture it two ways to find out which: take a screenshot and a photograph of the same moment. Corruption that appears in the screenshot came from the rendering path; a spot in the photo that is missing from the screenshot lives in the display or the connection.&lt;/p>
&lt;p>Refresh rate belongs here, as a controlled test rather than a fix. The path in Windows 11 is &lt;strong>Settings &amp;gt; System &amp;gt; Display &amp;gt; Advanced display&lt;/strong>, where the refresh rate selector sits, as Microsoft documents on its &lt;a href="https://support.microsoft.com/en-us/windows/hardware/display-graphics/change-the-refresh-rate-on-your-monitor-in-windows" rel="noopener">refresh rate page&lt;/a>. Change only that, leave the cable and the resolution alone, and look again. A spot that vanishes at a lower refresh rate is a mode-dependent fault, which points at signal integrity or panel driving rather than a dead cell. A spot that ignores the mode change is a physical defect.&lt;/p>
&lt;p>For a monitor that shows nothing at all, rather than a spot, the &lt;a href="https://techfuelhq.com/articles/monitor-no-signal-2026/">no-signal guide&lt;/a> is the right starting point instead.&lt;/p>
&lt;h2 id="clean-the-surface-before-you-blame-the-panel">Clean the surface before you blame the panel&lt;/h2>
&lt;p>Turn the monitor off, so a lit white field does not hide a smudge, and look across the glass at a low angle. Most &amp;ldquo;black spots&amp;rdquo; that arrive by email are fingerprints, dried cleaning spray, or a fleck of something on the coating.&lt;/p>
&lt;p>My approach is a dry microfiber cloth and nothing else to start. Wipe once, gently, and look again with the screen on. If the mark is grease, use only what the monitor&amp;rsquo;s own manual approves, applied to the cloth rather than the panel, and never spray onto the screen. Two things I do not do: press hard on a spot to see if it moves, and use a paper towel. The first can convert a cosmetic mark into a permanent pressure cluster, and the second can leave fine scratches that look worse than the original defect under a bright field.&lt;/p>
&lt;p>One vendor note is worth quoting because it surprises people. LG&amp;rsquo;s page, describing particles trapped during manufacturing, states that a maximum of one particle per 0.4 mm or less is normal, and suggests that a trapped particle can be removed &amp;ldquo;by gently tapping the LCD screen&amp;rdquo;. I would not tap a panel. The tolerance claim is LG&amp;rsquo;s published position and useful in a warranty conversation; the tapping advice is not something I would risk on a display I had to pay for.&lt;/p>
&lt;h2 id="oled-retention-is-not-the-same-as-burn-in">OLED retention is not the same as burn-in&lt;/h2>
&lt;p>On an OLED monitor, a dark or discoloured patch needs a different test, because the panel ages unevenly rather than failing at one cell. LG&amp;rsquo;s burn-in page draws the line clearly: image retention &amp;ldquo;refers to any image that sticks on a screen, even when the content changes&amp;rdquo;, and &amp;ldquo;usually appears as a faint ghost, and with most TVs this fades after a moment or two&amp;rdquo;. Burn-in, in the same document, is &amp;ldquo;a form of image retention that lasts much longer, and it&amp;rsquo;s usually visible even when playing other content&amp;rdquo;.&lt;/p>
&lt;p>The practical test is time and shape. Run fifteen minutes of varied full-screen video, then look again. A ghost that fades was retention. A ghost that stays, in the shape of a static element you actually left on screen, is wear. A round black spot is usually neither, which is why I test the colour fields first.&lt;/p>
&lt;p>LG&amp;rsquo;s page also describes the panel-care routine that ships with its OLED sets: a Pixel Refresher that runs automatically after every four hours of cumulative use, plus a longer calibration cycle that starts when you turn the set off after roughly 2,000 hours. Monitor implementations differ, and yours may call it pixel shift, screen move or panel refresh. Follow the manual for your model rather than a forum recipe; running a manual refresh repeatedly is not a repair. Our &lt;a href="https://techfuelhq.com/data/oled-burn-in-census/">OLED burn-in census&lt;/a> collects what owners actually report by panel and hours, and it is a better guide to the odds than any single case.&lt;/p>
&lt;h2 id="what-a-dead-pixel-warranty-claim-needs">What a dead-pixel warranty claim needs&lt;/h2>
&lt;p>Vendors do not share one threshold, and any article that quotes a universal number is making it up. Some publish a count per million pixels, some exclude certain zones, some treat bright dots differently from dark ones, and most apply different rules to consumer and commercial lines. Read the policy for your exact model before you argue.&lt;/p>
&lt;p>LG&amp;rsquo;s published guidance is concrete enough to quote. Its monitor page instructs readers to contact the seller if &amp;ldquo;there are 6 or more dark spots including all red/green/blue colors&amp;rdquo;, and separately, after displaying a black background, to contact the seller if bright spots appear. That is one vendor&amp;rsquo;s rule for its own products, not a standard.&lt;/p>
&lt;p>Dell&amp;rsquo;s route runs through its diagnostics rather than a pixel count. Its article says that if the abnormality appears in the built-in self-test, the next step is to contact Dell technical support for repair options, and if it does not appear, to continue with display and video troubleshooting. That is why the built-in test in step 6 matters: it converts your observation into the vendor&amp;rsquo;s own evidence.&lt;/p>
&lt;p>Whatever the brand, the file you send should contain the model number, the colour field where the spot appears, a close photograph with a ruler or a coin for scale if the spot is large, the built-in test result, and the purchase date. The &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">Diagnostic Workbench&lt;/a> is a reasonable place to keep those observations together before you open a ticket.&lt;/p>
&lt;h2 id="when-to-stop">When to stop&lt;/h2>
&lt;p>Stop cleaning, testing and adjusting when any of these is true:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>The panel is physically damaged.&lt;/strong> A crack, a spider mark, or a dark blotch that grows after an impact is not a pixel defect. Photograph it and contact the vendor; do not press it to see whether it spreads.&lt;/li>
&lt;li>&lt;strong>The spot appears in the manufacturer&amp;rsquo;s built-in test.&lt;/strong> That is the vendor&amp;rsquo;s own evidence, and further home testing adds nothing.&lt;/li>
&lt;li>&lt;strong>The spots are multiplying.&lt;/strong> A growing cluster can indicate a failing panel driver rather than isolated cells, and it changes a repair into a replacement decision.&lt;/li>
&lt;li>&lt;strong>You are considering opening the enclosure.&lt;/strong> At that point the correct move is a service quote, not a toolkit.&lt;/li>
&lt;/ul>
&lt;p>Then get the quote before deciding. A single dark subpixel in the corner of a large panel is something plenty of people learn to ignore; a cluster in the centre of the screen is not. That judgement belongs to you and your warranty terms, not to a rule of thumb.&lt;/p></description></item><item><title>ATX 3.1 PSU Guide: 12V-2x6, Hold-Up and Sizing</title><link>https://techfuelhq.com/articles/atx-3-1-psu-guide-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/atx-3-1-psu-guide-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · ATX 3.1 power supplies&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>The headline change is a connector, not a wattage.&lt;/strong> ATX 3.1 aligns the PSU spec to PCIe CEM 5.1 and replaces 12VHPWR with 12V-2x6. Intel says new designs should mount only the new connector.&lt;/li>
&lt;li>&lt;strong>Check the cable, not the badge.&lt;/strong> The two sense pins in a 12V-2x6 connector tell the card how much power it may draw. A PSU that configures those pins properly is worth more than a higher wattage number.&lt;/li>
&lt;li>&lt;strong>Size for transients.&lt;/strong> A single add-in card may now be rated to 675 W and is allowed brief excursions above its sustained power. Average wattage is the wrong input.&lt;/li>
&lt;li>&lt;strong>The 3.1 badge says nothing about efficiency.&lt;/strong> The required floor is 70% at full load. 80 PLUS and Cybenetics ETA are separate voluntary certifications, and they are the ones worth reading.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>Most of what gets sold as &amp;ldquo;ATX 3.1&amp;rdquo; in 2026 is a rebadged power supply with a new cable in the box. That is not a scam, because the revision really is mostly about the cable, but it does mean the version number on the box tells you far less than the spec sheet does. The things that changed are specific, they are documented, and they are worth knowing before you spend money on a unit you will keep for a decade.&lt;/p>
&lt;p>Here is what Intel&amp;rsquo;s own document says changed, what it means when you plug a GPU in, and the two timing numbers that decide whether your machine survives a power flicker.&lt;/p>
&lt;h2 id="what-atx-31-actually-changed">What ATX 3.1 actually changed&lt;/h2>
&lt;p>Intel&amp;rsquo;s design guide states its scope in one line: &amp;ldquo;This document aligns to ATX Specification Version 3.1.&amp;rdquo; The revision exists to bring the power supply specification in line with the PCIe CEM 5.1 add-in card specification, and it lists four substantive changes (&lt;a href="https://cdrdv2-public.intel.com/336521/336521_Rev2p1a.pdf" rel="noopener">Intel, doc 336521 rev 2.1a&lt;/a>):&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Two new auxiliary power connectors at 600 W.&lt;/strong> The 12V-2x6 connector carries 600 W on the 12 V rail, and the 48VHPWR connector carries 600 W on a 48 V rail. Each has four sideband signal conductors so the card and PSU can negotiate configuration directly.&lt;/li>
&lt;li>&lt;strong>A power excursion allowance.&lt;/strong> Cards may make brief high-current demands while keeping average power inside the specified limit.&lt;/li>
&lt;li>&lt;strong>A higher single-card ceiling.&lt;/strong> The maximum power for a single PCIe add-in card rose from 300 W to 675 W.&lt;/li>
&lt;li>&lt;strong>An optional 48 V rail.&lt;/strong> Intel expects it mainly in data centres and does not require PSU support for it.&lt;/li>
&lt;/ol>
&lt;p>The fourth item is the one to ignore for a desktop. The first three are the ones that change what you should buy.&lt;/p>
&lt;p>What did not change is just as important. The document&amp;rsquo;s efficiency table still sets the required minimum at 70% at full load, 72% at typical (50%) load and 65% at light (20%) load. The low-load requirement is 60% at 10 W or 2% of rated output. If you assumed a 3.1 unit was inherently more efficient than a 3.0 unit, the specification does not say that.&lt;/p>
&lt;h2 id="12v-2x6-the-sense-pins-and-why-adapters-are-the-weak-link">12V-2x6, the sense pins, and why adapters are the weak link&lt;/h2>
&lt;p>The 12VHPWR connector introduced in PCIe CEM 5.0 has been deprecated. Intel&amp;rsquo;s wording is unusually direct: the 12V-2x6 connector &amp;ldquo;replaces the 12VHPWR connector introduced in PCIe CEM 5.0, to address reliability concerns that were observed in the 12VHPWR connector. New power supply designs should mount only the 12V-2x6 connector and the 12VHPWR connector should be deprecated.&amp;rdquo;&lt;/p>
&lt;p>The two connectors are close relatives, and Intel describes the 12V-2x6 as mechanically identical in most respects. Two changes matter in practice. First, in the PCB header, the power pins were lengthened and the sideband pins shortened so the power pins mate first and break last: the sense pins only engage once the power pins are seated. Second, the SENSE0 and SENSE1 definitions were rewritten.&lt;/p>
&lt;p>Those sense pins are the part almost nobody checks, and they are the part that decides whether your GPU is told the truth. Four power levels are encoded on them, 600, 450, 300 and 150 W, and Intel requires both the PSU and the card to support them. Three details from Table 3-6 and section 3.3.1 are worth memorising:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>The 150 W level is signalled by a short&lt;/strong> between SENSE0 and SENSE1 presenting 0 Ω at the cable plug. Those pins must remain floating with respect to ground; if they are also shorted to ground, Intel notes the card &amp;ldquo;would misread the available power as 600 watts instead of 150 watts.&amp;rdquo;&lt;/li>
&lt;li>&lt;strong>Open on both pins means no power may be drawn.&lt;/strong> Intel is explicit that in the Open-Open high-impedance state, no power may be drawn by the load.&lt;/li>
&lt;li>&lt;strong>A modular PSU must configure the sense pins inside the PSU&lt;/strong>, not in the detachable cable, so that interchangeable double-ended 12V-2x6 cables work correctly.&lt;/li>
&lt;/ul>
&lt;p>That last point is the practical test for an adapter. If you are running a new GPU on an older PSU through a third-party adapter, the sense-pin wiring is being decided by a part the PSU manufacturer never specified. A unit with a native 12V-2x6 cable removes the question entirely, and that is the single strongest reason to buy a 3.1 unit rather than cable your way around one. The &lt;a href="https://techfuelhq.com/articles/psu-tier-list/">PSU tier list&lt;/a> sorts units by build quality once the connector is settled.&lt;/p>
&lt;h2 id="transients-and-hold-up-the-two-timing-numbers-that-matter">Transients and hold-up: the two timing numbers that matter&lt;/h2>
&lt;p>Graphics cards do not draw a steady number of watts. They spike, and ATX 3.1 formalises how much they may spike. Table 3-1 sets the allowance at 3× the card&amp;rsquo;s maximum sustained power over a 100 µs interval, decaying logarithmically through the range until it reaches 1× at one second. A card rated at 450 W may therefore pull well over a kilowatt for a fraction of a millisecond, repeatedly.&lt;/p>
&lt;p>This is why a PSU that passes a steady-state load test can still shut down in a game. The protection circuit sees a transient it was not designed for and trips. Buying for transient behaviour is not a marketing story; it is the reason the excursion table exists in the specification at all.&lt;/p>
&lt;p>The second number is hold-up time, and it is the one I would put on every PSU box. Section 4.2.9 requires the PSU to maintain output regulation for &lt;strong>12 ms at 100% of full load&lt;/strong>, and recommends &lt;strong>17 ms at 80% of full load&lt;/strong> after a loss of input power. That is the window your machine has to ride through a gap.&lt;/p>
&lt;p>If you run a UPS, this is the number that decides whether the UPS actually protects you. Mains drops, the PSU holds for 12 ms, and the UPS has to detect the loss and transfer to battery inside that window. A UPS with a slow transfer and a PSU that only just meets the minimum is a machine that reboots during every brownout. The &lt;a href="https://techfuelhq.com/tools/ups-runtime-calculator/">UPS runtime calculator&lt;/a> covers the battery side; the hold-up side is the PSU&amp;rsquo;s job, and it is worth preferring a unit that meets the recommended figure rather than the required one.&lt;/p>
&lt;h2 id="efficiency-the-spec-floor-is-lower-than-you-think">Efficiency: the spec floor is lower than you think&lt;/h2>
&lt;p>The gap between the ATX minimum and the sticker on the box is enormous, and it confuses a lot of buyers. The specification&amp;rsquo;s required efficiency is 70% at full load. An 80 PLUS Gold unit is far above that. Both statements are true, and neither one is a lie, because the ATX figure is a compliance floor and 80 PLUS is a voluntary certification program run by CLEAResult that tests at 20%, 50% and 100% load and grades the result (&lt;a href="https://www.clearesult.com/80plus/program-details" rel="noopener">CLEAResult&lt;/a>).&lt;/p>
&lt;p>Cybenetics ETA is a second, independent certification with its own test methodology and its own grading (&lt;a href="https://www.cybenetics.com/index.php?option=eta" rel="noopener">Cybenetics&lt;/a>). Corsair&amp;rsquo;s own explainer is a fair summary of why the two schemes sometimes disagree on the same unit: they measure different things at different load points with different tolerances (&lt;a href="https://www.corsair.com/us/en/explorer/diy-builder/power-supply-units/80-plus-vs-cybenetics/" rel="noopener">Corsair&lt;/a>).&lt;/p>
&lt;p>What this means for a purchase is simple. Read the certification and the test report, not the ATX version, and not the wattage. Bel Fuse&amp;rsquo;s technical paper on the 80 PLUS tiers makes the same point from the enterprise side: the certification is a procurement shortcut, and the levels above Gold exist because the efficiency curve at low load is where the money actually goes (&lt;a href="https://www.belfuse.com/resource-library/tech-paper/80-plus-why-you-need-titanium-power-supplies-in-your-data-center" rel="noopener">Bel Fuse&lt;/a>).&lt;/p>
&lt;p>For a desktop that idles most of the day, the low-load number is the one that shows up on your bill. The &lt;a href="https://techfuelhq.com/tools/power-cost-calculator/">power cost calculator&lt;/a> will do the arithmetic with your own electricity rate.&lt;/p>
&lt;h2 id="how-to-size-a-psu-for-a-2026-gpu">How to size a PSU for a 2026 GPU&lt;/h2>
&lt;p>Size from the connector budget and the transient allowance, then round up. Three rules cover almost every build.&lt;/p>
&lt;p>&lt;strong>Rule one: one native 12V-2x6 cable per high-power card.&lt;/strong> The connector is rated to 600 W sustained, and the sense pins tell the card what the PSU can actually deliver. Do not plan a build that needs two 600 W cables unless the PSU genuinely provides two, with the sense pins configured for each.&lt;/p>
&lt;p>&lt;strong>Rule two: leave headroom above the card&amp;rsquo;s rating, not above its average.&lt;/strong> ATX 3.1 permits 3× excursions over 100 µs. A PSU with a healthy margin and good transient response handles those without tripping; a unit run at 90% of capacity does not have anywhere to go.&lt;/p>
&lt;p>&lt;strong>Rule three: treat 675 W as a ceiling, not a target.&lt;/strong> Intel raised the maximum for a single add-in card from 300 W to 675 W. That does not mean your card draws 675 W, but it does mean the specification now contemplates cards that would have been unthinkable on a 3.0 unit.&lt;/p>
&lt;p>The unit I would start from for a single-GPU build is Seasonic&amp;rsquo;s FOCUS GX-750. Seasonic states that the FOCUS GX series complies with the ATX 3.1 and PCIe 5.1 standards and covers 750 W to 1000 W, so the 750 W model sits at the bottom of a documented 3.1 range rather than at the top of a 3.0 one (&lt;a href="https://seasonic.com/focus-gx-atx-3/" rel="noopener">Seasonic&lt;/a>).&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Seasonic&amp;#43;FOCUS&amp;#43;GX-750&amp;#43;ATX&amp;#43;3.1&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/atx-3-1-psu-guide-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DSeasonic%2BFocus%2BGX-750%2BATX%2B3.1" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/atx-3-1-psu-guide-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>The &lt;a href="https://techfuelhq.com/tools/psu-wattage-calculator/">PSU wattage calculator&lt;/a> handles the sum for a specific parts list. Use it, then add the margin you are comfortable with rather than the margin a retailer suggests.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Situation&lt;/th>
&lt;th scope="col">What I would buy&lt;/th>
&lt;th scope="col">Why&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Situation">New build, one GPU with a 12V-2x6 input&lt;/td>
&lt;td data-label="What I would buy">750 W class unit with a native 12V-2x6 cable&lt;/td>
&lt;td data-label="Why">Native cable means the PSU configures the sense pins, per Intel&amp;rsquo;s modular-supply requirement&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Situation">Existing 3.0 PSU, new GPU&lt;/td>
&lt;td data-label="What I would buy">A 3.1 unit, not an adapter&lt;/td>
&lt;td data-label="Why">The adapter decides the sense-pin state, and a misread costs you either a shutdown or a 600 W assumption on a 150 W cable&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Situation">Small case, short cable runs&lt;/td>
&lt;td data-label="What I would buy">Check cable length before wattage&lt;/td>
&lt;td data-label="Why">A 12V-2x6 cable that will not reach is a 0 W cable&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Situation">Machine on a UPS&lt;/td>
&lt;td data-label="What I would buy">Prefer the recommended 17 ms hold-up over the 12 ms minimum&lt;/td>
&lt;td data-label="Why">The UPS transfer has to fit inside the hold-up window&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="what-i-would-check-before-buying">What I would check before buying&lt;/h2>
&lt;p>The order matters, because the first check eliminates most of the market.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Does the unit have a native 12V-2x6 cable, and does the manufacturer document its sense-pin configuration?&lt;/strong> If the answer is &amp;ldquo;we include an adapter&amp;rdquo;, keep looking.&lt;/li>
&lt;li>&lt;strong>What does the efficiency certification actually say?&lt;/strong> 80 PLUS level and, where available, a Cybenetics ETA rating. Ignore the ATX version here.&lt;/li>
&lt;li>&lt;strong>What is the hold-up specification?&lt;/strong> If the manufacturer publishes 12 ms at full load and nothing else, it meets the minimum. If it publishes a figure at 80% load, compare it to the 17 ms recommendation.&lt;/li>
&lt;li>&lt;strong>What is the warranty and who honours it?&lt;/strong> A ten-year warranty from a company that will still be answering email in ten years is worth more than a higher efficiency grade.&lt;/li>
&lt;li>&lt;strong>Does the physical unit fit?&lt;/strong> Length, cable clearance behind the motherboard tray, and the number of 12 V EPS connectors your board needs.&lt;/li>
&lt;/ol>
&lt;p>If the machine is already built and behaving badly rather than being planned, the &lt;a href="https://techfuelhq.com/articles/psu-failure-symptoms-2026/">PSU failure symptoms guide&lt;/a> covers the diagnostics, and the &lt;a href="https://techfuelhq.com/articles/what-psu-for-rtx-5080-2026/">RTX 5080 PSU guide&lt;/a> works through a single high-power card in detail. Neither one is a substitute for reading the label on the unit you already own, which is where most of these questions actually get answered.&lt;/p></description></item><item><title>Air Cooler vs AIO in 2026: Which Should You Buy?</title><link>https://techfuelhq.com/articles/air-cooler-vs-aio-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/air-cooler-vs-aio-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Air cooler vs AIO in 2026&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Buy the 360 mm AIO&lt;/strong> if your case takes one in the front or roof without starving it, and you are cooling a 200 W+ CPU. It is the only option with real thermal headroom in the published tests.&lt;/li>
&lt;li>&lt;strong>Buy a big tower cooler&lt;/strong> if the case is small, the RAM is tall, the budget is tight, or you want a part with no pump in it. The gap at gaming loads is smaller than the forum arithmetic suggests.&lt;/li>
&lt;li>&lt;strong>Do not buy either on the label.&lt;/strong> A 360 mm radiator behind a solid front panel loses to a 120 mm tower in a mesh case. Case airflow decides more than cooler class.&lt;/li>
&lt;li>&lt;strong>Check three numbers first:&lt;/strong> cooler height against the case spec, radiator length plus fan depth, and the GPU clearance you give up. Fractal's North drops from 355 mm to 300 mm of GPU room with a 360 mm front radiator.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>The honest version of this decision is shorter than most buying guides make it. A good 360 mm AIO beats the best tower cooler by roughly eight degrees at 200 W, and by a little more at 250 W. Eight degrees is real, and it is also not the difference between stable and throttling on most modern chips. The rest of the choice is mechanical: what fits, what you hear, and what you are willing to have fail in three years.&lt;/p>
&lt;p>I have not put either cooler on a thermal bench this month. The numbers below come from GamersNexus&amp;rsquo;s testing, and I have named the load, the chip and the measurement so you can check them yourself rather than take my word for a delta.&lt;/p>
&lt;h2 id="what-the-tested-numbers-actually-show">What the tested numbers actually show&lt;/h2>
&lt;p>GamersNexus runs CPU cooler tests in a hemi-anechoic chamber, which is a room built to remove reflected sound, and they report a temperature rise above ambient rather than an absolute number. That matters: 45 °C in their chart means 45 °C hotter than the air entering the case, so a 22 °C room gives you 67 °C, and a 30 °C room gives you 75 °C. If you read one of these figures as an absolute temperature you will draw the wrong conclusion about your own build.&lt;/p>
&lt;p>Their AMD test bed for the NH-D15 G2 review was a Ryzen 9 3950X at roughly 200 W. Their Intel bed for the 250 W comparison was a Core i9-14900KF. Here is what the two reviews report side by side.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Cooler&lt;/th>
&lt;th scope="col">200 W, full fan speed&lt;/th>
&lt;th scope="col">200 W, noise-normalized&lt;/th>
&lt;th scope="col">250 W, noise-normalized&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Cooler">ARCTIC Liquid Freezer III 360&lt;/td>
&lt;td data-label="200 W, full fan speed">45.0 °C above ambient at 39.8 dBA&lt;/td>
&lt;td data-label="200 W, noise-normalized">47.3 °C&lt;/td>
&lt;td data-label="250 W, noise-normalized">48.1 °C&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Cooler">Noctua NH-D15 G2 (standard)&lt;/td>
&lt;td data-label="200 W, full fan speed">53.5 °C&lt;/td>
&lt;td data-label="200 W, noise-normalized">about 55.5 °C&lt;/td>
&lt;td data-label="250 W, noise-normalized">9.7 °C behind the AIO (G2 HBC)&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The AIO wins both columns, and the noise-normalized comparison is the one that should decide your purchase. At full fan speed the tower is running louder to hold a worse temperature; once both coolers are normalized to the same noise level, the Liquid Freezer III 360 is still ahead by close to eight degrees. The &lt;a href="https://techfuelhq.com/reviews/arctic-liquid-freezer-iii-360-review-2026/">Liquid Freezer III 360 review&lt;/a> covers the mounting and tubing in detail, and the &lt;a href="https://techfuelhq.com/reviews/noctua-nh-d15-g2-review-2026/">NH-D15 G2 review&lt;/a> covers the air side.&lt;/p>
&lt;p>The number that gets left out of these arguments is the second-place air cooler. GamersNexus measured the NH-D15 G2 only 1.5 °C ahead of Thermalright&amp;rsquo;s Peerless Assassin at 200 W with the fans at full speed, and the Noctua is the best air cooler in their dataset. That means the air-cooling ceiling is essentially flat: once you are at a competent dual-tower, spending more on air buys you noise and mounting hardware, not temperature. If you want more than about 53 °C above ambient at 200 W, you need a radiator.&lt;/p>
&lt;h2 id="clearance-is-where-most-builds-actually-decide">Clearance is where most builds actually decide&lt;/h2>
&lt;p>Noctua publishes the NH-D15 G2 at 168 mm tall with the fans installed, 150 mm wide, 152 mm deep, and 1,525 g with both NF-A14x25r G2 fans fitted, against 1,180 g for the heatsink alone. Its two fans are rated to 1,500 RPM and 24.8 dB(A), and Noctua specifies a mean time to failure above 150,000 hours. The socket list covers AM5, AM4, LGA1851, LGA1700 and the older Intel desktop sockets, and the cooler carries a six-year warranty.&lt;/p>
&lt;p>That 168 mm height is the whole argument in a lot of cases. Fractal&amp;rsquo;s North lists a maximum CPU cooler height of 170 mm without the fan bracket, and 145 mm with it. The Noctua fits with two millimetres to spare in the first configuration and does not fit at all in the second. Two millimetres is not a margin you want to discover after the motherboard is in.&lt;/p>
&lt;p>The AIO trades that constraint for a different one. Arctic specifies the Liquid Freezer III 360&amp;rsquo;s radiator at 398 × 120 × 38 mm, with three P12 PWM fans running 200 to 1,800 RPM, a pump that runs 800 to 2,800 RPM on PWM, 450 mm of tubing, and 1,840 g for the assembly. Their 2D drawing puts the radiator plus fans at roughly 66 mm deep, which is the number that matters when you are counting clearance above the motherboard or in front of the drive cage.&lt;/p>
&lt;p>Radiator support and GPU clearance interact, and the case spec is the only place that tells you how. The same Fractal North that takes a 360 mm front radiator also drops its maximum GPU length from 355 mm to 300 mm when that radiator is fitted. A 300 mm card is fine. A 336 mm card is not, and no cooler review will warn you about it.&lt;/p>
&lt;p>There is a third clearance problem that only shows up on specific boards. Arctic maintains a per-board compatibility list for the Liquid Freezer III because the pump block and its mounting hardware can collide with a VRM heatsink or a shroud on some motherboards. Check your exact board against that list before you buy, not after.&lt;/p>
&lt;h2 id="noise-and-what-the-decibel-rating-does-not-tell-you">Noise, and what the decibel rating does not tell you&lt;/h2>
&lt;p>Noctua&amp;rsquo;s 24.8 dB(A) and GamersNexus&amp;rsquo;s 39.8 dBA are not the same measurement and should not be compared. The first is a single fan on a manufacturer&amp;rsquo;s test rig; the second is a complete cooler under a 200 W load in an anechoic chamber. What you can compare is the shape of the noise. A tower cooler produces broadband fan noise that rises smoothly with load. An AIO produces fan noise plus pump noise, and pump noise is tonal and does not always scale with load, which is why some people find a quiet AIO more annoying than a louder tower.&lt;/p>
&lt;p>The practical lever is the fan curve, and it is the same lever on both designs. Set the case fans to a fixed, tolerable speed and let the CPU cooler ramp, rather than letting both chase the same temperature sensor. On an AIO, run the pump at a fixed speed in the middle of its range and control only the radiator fans from the CPU header. On a tower, cap the fan at the speed where you stop hearing it and accept the couple of degrees you give back.&lt;/p>
&lt;p>This is also where the six-year warranties matter less than people think. Both companies stand behind the hardware for six years, but only one of them has a part that can seize. Fan failure on a tower cooler is a fan swap; pump failure on an AIO is a full replacement, and it usually announces itself as a temperature spike at idle rather than as a noise.&lt;/p>
&lt;h2 id="failure-modes-and-what-they-cost-you">Failure modes and what they cost you&lt;/h2>
&lt;p>An air cooler fails in ways you can see. A fan bearing goes dry and starts to tick, one fan stops and the other carries the load, or the mounting hardware loosens over years of thermal cycling. None of those is catastrophic. You will notice the noise or the temperature long before anything is damaged, and the fix is a fan or a re-mount.&lt;/p>
&lt;p>An AIO fails in ways that are quieter and then abruptly not. The pump slows as coolant permeates through the tubing over years, the cold plate slowly stops transferring heat, and the first symptom is often a higher idle temperature or a fan curve that never settles. A total pump failure gives you a CPU at thermal throttle within a minute of load, which most boards handle by throttling hard rather than dying, but it is not a good afternoon.&lt;/p>
&lt;p>That asymmetry is the real argument for air, and it is a stronger argument than the two or three degrees people usually cite. If the machine is a work machine, a NAS that also runs a desktop VM, or anything you are not standing next to, a tower cooler removes a failure mode. If it is a gaming box you sit at every day, the AIO&amp;rsquo;s failure will announce itself in time for you to order a replacement.&lt;/p>
&lt;h2 id="who-should-buy-which">Who should buy which&lt;/h2>
&lt;p>Buy the AIO if all four of these are true: the case takes a 360 mm radiator with a mesh or open front, the CPU is a 200 W-class part, the GPU is short enough to survive the clearance loss, and you want the eight-degree margin for a quiet fan curve. That is the build the Liquid Freezer III 360 was designed for, and it is the one place where the radiator earns its cost and its extra failure mode.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=ARCTIC&amp;#43;Liquid&amp;#43;Freezer&amp;#43;III&amp;#43;360&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/air-cooler-vs-aio-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DARCTIC%2BLiquid%2BFreezer%2BIII%2B360" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/air-cooler-vs-aio-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>Buy air if any of these is true: the case spec is under 168 mm, the RAM is a tall kit with RGB heat spreaders, the GPU is long enough that a front radiator would not fit, or you simply do not want a pump in the box. In that case a dual-tower like the NH-D15 G2 or a Peerless Assassin is the correct answer, and the 1.5 °C gap between them means the cheaper one is not a compromise on temperature.&lt;/p>
&lt;p>There is a third option worth naming, because it wins a lot of builds: a 240 mm or 280 mm AIO in a case that cannot take a 360. It will not match the 360&amp;rsquo;s numbers, but it moves the radiator off the motherboard and often fits where a 168 mm tower will not. I would take a 280 mm AIO over a cramped tower in a small case, and I would take a tower over a 120 mm AIO in almost any case.&lt;/p>
&lt;h2 id="what-i-would-check-before-ordering">What I would check before ordering&lt;/h2>
&lt;p>Four checks, in this order, take about ten minutes and prevent almost every bad cooler purchase.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Cooler height against the case spec.&lt;/strong> Look up your exact case model on the manufacturer&amp;rsquo;s product sheet, not a retailer listing. If the spec gives two numbers, one with an accessory bracket and one without, use the smaller one.&lt;/li>
&lt;li>&lt;strong>Radiator support plus the GPU clearance it costs.&lt;/strong> The case spec usually lists both. Subtract the radiator and fan depth from the GPU figure before you commit to a long card.&lt;/li>
&lt;li>&lt;strong>Board-level conflicts.&lt;/strong> For an AIO, check the manufacturer&amp;rsquo;s per-board compatibility list. For a tower, check the RAM height and the first PCIe slot spacing in your motherboard manual.&lt;/li>
&lt;li>&lt;strong>Your actual sustained load.&lt;/strong> If the CPU is a 65 W or 105 W part and you game rather than render, none of the eight-degree margin is doing anything for you. The &lt;a href="https://techfuelhq.com/articles/cpu-overheating-2026/">CPU overheating guide&lt;/a> covers what a healthy temperature actually looks like, and the &lt;a href="https://techfuelhq.com/articles/safe-cpu-temp-2026/">safe CPU temperature ranges&lt;/a> give you the throttle points per platform.&lt;/li>
&lt;/ol>
&lt;p>The one thing I would not do is buy the cooler last. Case, cooler and GPU are a single clearance problem, and the order you pick them decides whether the build goes together. Pick the case, read its sheet, then pick the cooler that fits it and the CPU that needs it.&lt;/p>
&lt;p>If the machine is already built and running hot, the cooler is not automatically the culprit. The &lt;a href="https://techfuelhq.com/articles/cpu-gpu-thermal-throttling-fix-2026/">thermal throttling fix guide&lt;/a> walks through mount pressure, paste condition and airflow before you spend anything. A re-mount with fresh paste has fixed more &amp;ldquo;bad cooler&amp;rdquo; complaints than any upgrade I can name.&lt;/p></description></item><item><title>990 EVO Plus vs 990 PRO: Which Samsung SSD to Buy</title><link>https://techfuelhq.com/articles/990-evo-plus-vs-990-pro-2026/</link><pubDate>Mon, 16 Nov 2026 12:00:00 +0000</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/990-evo-plus-vs-990-pro-2026/</guid><atom:updated>2026-11-16T12:00:00Z</atom:updated><description>&lt;div class="verdict-card">
&lt;p class="callout-label">TL;DR · Samsung 990 EVO Plus vs 990 PRO&lt;/p>
&lt;ul style="margin:0.25rem 0 0 0;padding-left:1.25rem;line-height:1.55;">
&lt;li>&lt;strong>Most desktop and gaming PCs:&lt;/strong> the 990 EVO Plus is fast enough for ordinary work and avoids paying for capacity you may not use.&lt;/li>
&lt;li>&lt;strong>Write-heavy workloads or highest rated throughput:&lt;/strong> the 990 PRO has onboard DRAM and higher peak sequential ratings.&lt;/li>
&lt;li>&lt;strong>Both are 2TB TLC PCIe 4.0-class drives&lt;/strong> with a 1,200 TBW rating and five-year warranty at this capacity.&lt;/li>
&lt;li>&lt;strong>Long transfers outlast either drive's cache.&lt;/strong> Do not treat peak write speeds as sustained speeds.&lt;/li>
&lt;/ul>
&lt;/div>
&lt;p>The Samsung 990 EVO Plus and 990 PRO look close on the box: both are fast NVMe drives, both use TLC NAND, and both hit high sequential numbers. The differences are in the controller memory, interface configuration, rated throughput, and how each behaves after its write cache fills.&lt;/p>
&lt;p>For most everyday PCs, I would start with the 990 EVO Plus. It has enough performance for a Windows drive, games, and ordinary creative work, and Tom&amp;rsquo;s Hardware found it close to the 990 PRO in PCMark 10. I would choose the 990 PRO when a workload is sensitive to write speed or when its onboard DRAM and higher rated peak speed solve a real need. For sustained transfers, neither drive behaves like its headline number forever.&lt;/p>
&lt;h2 id="the-2tb-specification-comparison">The 2TB specification comparison&lt;/h2>
&lt;p>The table below uses Samsung&amp;rsquo;s official &lt;a href="https://download.semiconductor.samsung.com/resources/data-sheet/samsung_nvme_ssd_990_evo_plus_datasheet_rev.1.0.pdf" rel="noopener">990 EVO Plus datasheet&lt;/a> and &lt;a href="https://download.semiconductor.samsung.com/resources/data-sheet/samsung_nvme_ssd_990_pro_datasheet_rev.2.0.pdf" rel="noopener">990 PRO datasheet&lt;/a>. Capacity matters: cache sizes and rated numbers can vary across 1TB, 2TB and 4TB models, so I am comparing 2TB against 2TB.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Specification&lt;/th>
&lt;th scope="col" style="text-align: right">Samsung 990 EVO Plus 2TB&lt;/th>
&lt;th scope="col" style="text-align: right">Samsung 990 PRO 2TB&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Specification">Interface&lt;/td>
&lt;td style="text-align: right" data-label="Samsung 990 EVO Plus 2TB">PCIe 4.0 x4 or 5.0 x2&lt;/td>
&lt;td style="text-align: right" data-label="Samsung 990 PRO 2TB">PCIe 4.0 x4&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">NAND&lt;/td>
&lt;td style="text-align: right" data-label="Samsung 990 EVO Plus 2TB">Samsung V-NAND TLC&lt;/td>
&lt;td style="text-align: right" data-label="Samsung 990 PRO 2TB">Samsung V-NAND TLC&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Controller memory&lt;/td>
&lt;td style="text-align: right" data-label="Samsung 990 EVO Plus 2TB">HMB&lt;/td>
&lt;td style="text-align: right" data-label="Samsung 990 PRO 2TB">2GB LPDDR4 DRAM&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Sequential read, up to&lt;/td>
&lt;td style="text-align: right" data-label="Samsung 990 EVO Plus 2TB">7,250 MB/s&lt;/td>
&lt;td style="text-align: right" data-label="Samsung 990 PRO 2TB">7,450 MB/s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Sequential write, up to&lt;/td>
&lt;td style="text-align: right" data-label="Samsung 990 EVO Plus 2TB">6,300 MB/s&lt;/td>
&lt;td style="text-align: right" data-label="Samsung 990 PRO 2TB">6,900 MB/s&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Endurance rating&lt;/td>
&lt;td style="text-align: right" data-label="Samsung 990 EVO Plus 2TB">1,200 TBW&lt;/td>
&lt;td style="text-align: right" data-label="Samsung 990 PRO 2TB">1,200 TBW&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Specification">Limited warranty&lt;/td>
&lt;td style="text-align: right" data-label="Samsung 990 EVO Plus 2TB">5 years&lt;/td>
&lt;td style="text-align: right" data-label="Samsung 990 PRO 2TB">5 years&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>The 990 EVO Plus&amp;rsquo;s Gen5 label needs context. It reaches PCIe 5.0 through a two-lane connection, not a full x4 Gen5 interface. Samsung also lists PCIe 4.0 x4 compatibility for the drive. The 990 PRO is PCIe 4.0 x4. In the workloads these drives are designed for, the maximum sequential throughput is around the Gen4 range, so the EVO Plus&amp;rsquo;s alternate lane configuration should not be read as proof that it is a faster Gen5 drive.&lt;/p>
&lt;p>The more consequential architecture difference is DRAM. The 990 PRO has dedicated onboard DRAM; the EVO Plus uses Host Memory Buffer, which can use part of the host system&amp;rsquo;s memory for mapping information. HMB lets the EVO Plus deliver strong everyday performance without an onboard DRAM package, but it is not identical to the PRO&amp;rsquo;s design. The difference matters most in sustained or unusual workloads, not simply because one line says HMB and another says DRAM.&lt;/p>
&lt;p>Samsung&amp;rsquo;s datasheets also state that the rated sequential write speeds are measured with Intelligent TurboWrite enabled. That note matters: the peak is a burst capability while cache is available, not a speed guarantee for a transfer of any size. For a typical application launch or game load, the burst speed can be more than enough. A long video archive copy or scratch-disk workload raises a different question: how quickly does the drive write after its cache is consumed?&lt;/p>
&lt;h2 id="everyday-work-and-game-storage">Everyday work and game storage&lt;/h2>
&lt;p>The 990 EVO Plus is not a budget SATA drive wearing a Samsung label. Tom&amp;rsquo;s Hardware&amp;rsquo;s &lt;a href="https://www.tomshardware.com/pc-components/ssds/samsung-990-evo-plus-ssd-review" rel="noopener">review and PCMark 10 testing&lt;/a> found it close to the 990 PRO in the everyday application and storage benchmark. The reviewer concluded that its performance is sufficient for most users and that it makes sense as an all-around desktop or laptop drive.&lt;/p>
&lt;p>That is the use case where raw sequential maximums matter least. Windows startup, application launches, game loading, and routine project work involve a mix of access patterns and often wait on the CPU, application code, or other components. A small difference in peak transfer numbers may not translate into a noticeable difference in daily use. If your current storage is healthy and fast enough, changing from one modern NVMe drive to another for a spec-sheet improvement is rarely the best use of a budget.&lt;/p>
&lt;p>The 990 PRO&amp;rsquo;s onboard DRAM and higher sequential ratings make it easier to justify for workloads that push more data through the drive, but the workload needs to be specific. A content creator who regularly writes large project files may value faster writes. A gaming PC with a large library may benefit more from capacity than from the small sequential speed difference. A system drive that mostly reads applications will not automatically feel different because the benchmark says a sequential read is faster by a few hundred megabytes per second.&lt;/p>
&lt;p>Samsung&amp;rsquo;s datasheets list the same 1,200 TBW endurance rating for the 2TB models and a five-year warranty for each. That makes the comparison simple at this capacity: the 990 PRO does not buy you a higher stated endurance limit. The 1,200 TBW figure is a warranty limit under Samsung&amp;rsquo;s terms, not a promise the drive stops working at that amount or a prediction of failure.&lt;/p>
&lt;p>If you are deciding whether to upgrade a healthy existing drive, compare the actual capacity gained and the work the new drive will do. Our &lt;a href="https://techfuelhq.com/articles/ssd-health-check-2026/">SSD health check&lt;/a> can help assess a drive you already own, and the &lt;a href="https://techfuelhq.com/tools/ssd-endurance-calculator/">SSD endurance calculator&lt;/a> can put a workload&amp;rsquo;s writes in context. For general system use, added capacity often matters more than moving from the EVO Plus to the PRO.&lt;/p>
&lt;h2 id="sustained-writes-where-the-spec-sheet-stops">Sustained writes: where the spec sheet stops&lt;/h2>
&lt;p>Tom&amp;rsquo;s Hardware tests sequential writes for an extended period to measure cache size and post-cache behavior. In its &lt;a href="https://www.tomshardware.com/pc-components/ssds/samsung-990-evo-plus-ssd-review/2" rel="noopener">990 EVO Plus sustained-write test&lt;/a>, the 2TB model wrote at almost 6.1 GB/s for more than 37 seconds before the cache was exhausted. The review estimates a total cache around 226GB, combining the dynamic portion with a static component. These figures are specific to the reviewed 2TB drive and the review&amp;rsquo;s test procedure.&lt;/p>
&lt;p>The &lt;a href="https://www.tomshardware.com/reviews/samsung-990-pro-ssd-review/2" rel="noopener">990 PRO 2TB sustained-write test&lt;/a> shows a similar burst window: up to 6.2 GB/s for about 39 seconds before the cache runs out. The numbers illustrate why the two drives can look close in short bursts even though their datasheets list different maximum write speeds. A small benchmark file may finish while either drive is still using its fast cache.&lt;/p>
&lt;p>After the cache fills, writes continue into TLC flash at lower speeds. That is normal behavior for consumer SSDs using a pseudo-SLC write cache, not evidence that the drive is broken. The practical question is how often a real job writes more data than the cache can absorb and how long you can let the transfer run. A one-time migration, several large media projects in a row, and everyday game installs are different workloads.&lt;/p>
&lt;p>The 990 EVO Plus can recover some cache during idle periods, and the review measured its longer transfer behavior over time rather than treating one short burst as the entire result. If your workflow repeatedly saturates the drive, use the sustained-write charts rather than comparing only the quoted 6,300 and 6,900 MB/s peaks. For a desktop that rarely writes hundreds of gigabytes in one session, the cache difference is unlikely to be a deciding issue.&lt;/p>
&lt;h2 id="firmware-cooling-and-compatibility">Firmware, cooling and compatibility&lt;/h2>
&lt;p>Both drives use the M.2 2280 NVMe format, but check the motherboard manual before ordering. Verify that the M.2 socket accepts PCIe NVMe storage, that the slot is available with your other installed devices, and that the motherboard heatsink clears the SSD. The 990 EVO Plus&amp;rsquo;s ability to operate at PCIe 5.0 x2 does not turn a PCIe 4.0-only slot into a Gen5 one; the drive negotiates according to the host slot.&lt;/p>
&lt;p>Samsung&amp;rsquo;s &lt;a href="https://semiconductor.samsung.com/consumer-storage/support/tools/" rel="noopener">Magician and support tools page&lt;/a> is the place to check the installed firmware and download the manufacturer&amp;rsquo;s SSD utility. Check for firmware updates before a major migration or when you are troubleshooting a drive. Back up important data before changing firmware or moving partitions, and follow Samsung&amp;rsquo;s current instructions rather than relying on an old forum post.&lt;/p>
&lt;p>For a PlayStation 5, confirm the console&amp;rsquo;s current requirements, the sequential-read recommendation, and the physical heatsink clearance. Tom&amp;rsquo;s Hardware notes that its tests did not find much benefit from a Gen5 SSD in the PS5 compared with a capable Gen4 drive. The EVO Plus&amp;rsquo;s single-sided layout can help with some M.2 clearances, but the exact console configuration and heatsink still matter. I would verify the physical fit before buying rather than assume that the interface label guarantees compatibility.&lt;/p>
&lt;h2 id="which-one-should-you-buy">Which one should you buy?&lt;/h2>
&lt;p>&lt;strong>Choose the 990 EVO Plus if:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>You need a responsive general-purpose system, gaming, or laptop drive.&lt;/li>
&lt;li>You value strong everyday performance more than the highest peak sequential write rating.&lt;/li>
&lt;li>You want a single-sided design or have a specific platform reason to use PCIe 5.0 x2.&lt;/li>
&lt;li>Your workload rarely writes more data in one go than the drive&amp;rsquo;s cache can absorb.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Choose the 990 PRO if:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>Your workload benefits from a dedicated onboard DRAM cache and its higher rated sequential throughput.&lt;/li>
&lt;li>You often move large files and have checked the sustained-write data for the size and pattern of those transfers.&lt;/li>
&lt;li>The PRO is close enough in the live listings that the difference makes sense for your use case.&lt;/li>
&lt;li>You want the highest rated performance of these two drives, while understanding that its cache also fills on long writes.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Choose neither as an automatic upgrade&lt;/strong> if your current SSD is healthy and the extra capacity or sustained performance will not solve a problem. Our &lt;a href="https://techfuelhq.com/articles/ssd-tier-list/">SSD tier list&lt;/a> compares other drive classes, and the existing &lt;a href="https://techfuelhq.com/reviews/samsung-990-pro-review-2026/">990 PRO review&lt;/a> covers that drive&amp;rsquo;s firmware, cooling and sustained behavior in more detail.&lt;/p>
&lt;p>For an ordinary build, I would spend on the 990 EVO Plus and put the savings toward capacity, backup storage, or another part that changes how the PC feels. I would select the PRO only when a workload calls for its specific strengths, not because the model name sounds more premium.&lt;/p>
&lt;p>&lt;em>I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/em>&lt;/p>
&lt;span class="buy-actions buy-actions--cell buy-actions--inline google-anno-skip" data-pagefind-ignore data-affiliate-component="table-row">&lt;a class="buy-action buy-action--primary buy-action--amazon"
href="https://www.amazon.com/s?k=Samsung&amp;#43;990&amp;#43;EVO&amp;#43;Plus&amp;#43;2TB&amp;amp;tag=techfuelhq-20" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/990-evo-plus-vs-990-pro-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Amazon" data-affiliate-position="primary" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Amazon&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;a class="buy-action buy-action--primary buy-action--newegg"
href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;amp;mid=44583&amp;amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3DSamsung%2B990%2BEVO%2BPlus%2B2TB" rel="nofollow sponsored noopener" target="_blank" data-affiliate-page="/articles/990-evo-plus-vs-990-pro-2026/" data-affiliate-slot="table-row" data-affiliate-retailer="Newegg" data-affiliate-position="alternate" data-google-vignette="false"
data-link-kind="search">
&lt;span class="buy-action__label">Search Newegg&lt;/span>&lt;small class="buy-action__meta buy-action__meta--checked">Link checked 2026-11-16&lt;/small>
&lt;/a>
&lt;/span>
&lt;p>If your use case is specifically scratch-disk or bulk transfer work, compare the capacity and sustained-write behavior first. The &lt;a href="https://techfuelhq.com/reviews/samsung-990-pro-review-2026/">Samsung 990 PRO review&lt;/a> and &lt;a href="https://techfuelhq.com/articles/ssd-tier-list/">SSD tier list&lt;/a> are useful next stops before choosing a drive.&lt;/p></description></item><item><title>UniFi vs an OPNsense Build: The IDS/IPS Ceiling</title><link>https://techfuelhq.com/networking/unifi-vs-opnsense-build-2026/</link><pubDate>Mon, 07 Sep 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/networking/unifi-vs-opnsense-build-2026/</guid><atom:updated>2026-11-14T10:50:00Z</atom:updated><description>&lt;p>Turning on threat management costs you throughput. Ubiquiti publishes how much. You just have to look elsewhere.&lt;/p>
&lt;p>I have run both a UniFi gateway appliance and an x86 OPNsense box I built myself. Before comparing gateway spec sheets or pricing out mini PCs, draw one architectural line across your homelab diagram: what stays inside your Layer 2 switch ASIC versus what hits your Layer 3 firewall CPU. Getting that boundary wrong makes people overspend on 10GbE routers they never saturate, or choke local NAS backups through a &lt;code>2.3 Gbps&lt;/code> firewall inspection queue.&lt;/p>
&lt;h2 id="draw-the-l2-switch-vs-l3-firewall-traffic-boundary-first">Draw the L2 switch vs L3 firewall traffic boundary first&lt;/h2>
&lt;p>Switches move local packets. Routers cross subnets. Ethernet frames between two machines in the same subnet and VLAN are forwarded in silicon by your switch chip at full wire speed, whereas packets only climb up to your UniFi gateway or OPNsense CPU when they cross a Layer 3 subnet boundary, hit NAT/PPPoE toward your ISP, or enter a VPN tunnel:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Traffic flow in your homelab&lt;/th>
&lt;th scope="col">Where packets flow&lt;/th>
&lt;th scope="col">Touches router / firewall CPU?&lt;/th>
&lt;th scope="col">Sizing impact&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Traffic flow in your homelab">&lt;strong>Same-VLAN 10GbE PC → NAS SMB/iSCSI&lt;/strong> (&lt;code>192.168.10.20&lt;/code> → &lt;code>192.168.10.50&lt;/code>)&lt;/td>
&lt;td data-label="Where packets flow">&lt;strong>Layer 2 switch ASIC only&lt;/strong>&lt;/td>
&lt;td data-label="Touches router / firewall CPU?">&lt;strong>No (&lt;code>0%&lt;/code> router load)&lt;/strong>&lt;/td>
&lt;td data-label="Sizing impact">A $130 &lt;a href="https://techfuelhq.com/networking/10gbe-home-networking-budget-2026/">10GbE switch&lt;/a> delivers full 10 Gbps local transfers even if your router only has &lt;code>1 GbE&lt;/code> or &lt;code>2.5 GbE&lt;/code> ports!&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Traffic flow in your homelab">&lt;strong>Inter-VLAN East-West routing&lt;/strong> (&lt;code>VLAN 10 Workstation&lt;/code> → &lt;code>VLAN 20 NAS&lt;/code> or &lt;code>VLAN 30 IoT&lt;/code>)&lt;/td>
&lt;td data-label="Where packets flow">Hairpins up trunk link (&lt;code>802.1Q&lt;/code>) into &lt;strong>L3 firewall&lt;/strong> and back down&lt;/td>
&lt;td data-label="Touches router / firewall CPU?">&lt;strong>Yes — every packet&lt;/strong>&lt;/td>
&lt;td data-label="Sizing impact">Putting your workstation on VLAN 10 and your 10GbE NAS on VLAN 20 forces every backup through the firewall&amp;rsquo;s routing + IPS ceiling (unless you give the PC a second direct storage-VLAN NIC).&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Traffic flow in your homelab">&lt;strong>Fiber / Cable WAN (&lt;code>DHCP&lt;/code> vs &lt;code>PPPoE&lt;/code>)&lt;/strong>&lt;/td>
&lt;td data-label="Where packets flow">&lt;strong>L3 firewall NAT + WAN interface&lt;/strong>&lt;/td>
&lt;td data-label="Touches router / firewall CPU?">&lt;strong>Yes — every packet&lt;/strong>&lt;/td>
&lt;td data-label="Sizing impact">Standard DHCP WAN scales easily; multi-gig &lt;strong>PPPoE&lt;/strong> adds per-packet encapsulation overhead that taxes weak ARM cores and single-queue FreeBSD NICs unless hardware-offloaded or paired with fast x86 cores + Intel RSS queues.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Traffic flow in your homelab">&lt;strong>Suricata IDS (alert) / Inline IPS (block)&lt;/strong>&lt;/td>
&lt;td data-label="Where packets flow">&lt;strong>L3 firewall CPU + RAM&lt;/strong> (&lt;code>netmap&lt;/code> / packet engine)&lt;/td>
&lt;td data-label="Touches router / firewall CPU?">&lt;strong>Yes — heavy CPU &amp;amp; RAM&lt;/strong>&lt;/td>
&lt;td data-label="Sizing impact">Scales with active signature count and packet rate. Note that over TLS 1.3 (&lt;code>HTTPS&lt;/code>), IDS/IPS inspects IP reputation, DNS, TLS SNI/JA4 metadata, and unencrypted flows rather than decrypting payloads.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Traffic flow in your homelab">&lt;strong>SQM / Smart Queues (&lt;code>FQ-CoDel&lt;/code>)&lt;/strong>&lt;/td>
&lt;td data-label="Where packets flow">&lt;strong>L3 firewall CPU&lt;/strong> (single-queue traffic shaper)&lt;/td>
&lt;td data-label="Touches router / firewall CPU?">&lt;strong>Yes — disables packet offload&lt;/strong>&lt;/td>
&lt;td data-label="Sizing impact">UniFi recommends Smart Queues only below &lt;code>300 Mbps&lt;/code>. OPNsense &lt;code>FQ-CoDel&lt;/code> scales to &lt;code>1–2.5+ Gbps&lt;/code> on modern Intel N100/i3 cores.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Traffic flow in your homelab">&lt;strong>WireGuard / OpenVPN remote access &amp;amp; site-to-site&lt;/strong>&lt;/td>
&lt;td data-label="Where packets flow">&lt;strong>L3 firewall CPU&lt;/strong> (unless terminated on an internal host)&lt;/td>
&lt;td data-label="Touches router / firewall CPU?">&lt;strong>Yes — ChaCha20-Poly1305 crypto&lt;/strong>&lt;/td>
&lt;td data-label="Sizing impact">Terminating multi-gigabit WireGuard on the gateway favors x86 AES/SIMD clock speed over entry ARM appliances.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Keep high-bandwidth storage clients and your NAS on the same storage subnet (or add a dedicated untagged storage NIC) so bulk 10GbE traffic stays on your switch ASIC. Size the firewall strictly for &lt;strong>WAN speed + inter-VLAN east-west traffic + VPN/IPS&lt;/strong>.&lt;/p>
&lt;h2 id="the-unifi-idsips-ceiling-is-published-one-page-away">The UniFi IDS/IPS ceiling is published, one page away&lt;/h2>
&lt;p>Ubiquiti&amp;rsquo;s help documentation on &lt;a href="https://help.ui.com/hc/en-us/articles/360006893234-UniFi-Gateway-Intrusion-Detection-and-Prevention-IDS-IPS" rel="noopener">Gateway Intrusion Detection and Prevention (IDS/IPS)&lt;/a> states plainly that enabling inspection &amp;ldquo;increases CPU and memory utilization&amp;rdquo; and that &amp;ldquo;maximum routing performance may be reduced,&amp;rdquo; directing buyers to &lt;a href="https://techspecs.ui.com/unifi/cloud-gateways" rel="noopener">techspecs.ui.com&lt;/a>. Inside the UniFi controller (&lt;code>Settings → CyberSecure → Protection&lt;/code>), the switch sits there with no throughput warning beside it.&lt;/p>
&lt;p>Here is how Ubiquiti&amp;rsquo;s cloud-gateway lineup compares when you place physical WAN port speed next to published IDS/IPS throughput (specifications from &lt;code>techspecs.ui.com&lt;/code> and USD baseline prices from &lt;code>store.ui.com&lt;/code>, verified September 7, 2026):&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Gateway&lt;/th>
&lt;th scope="col">Default WAN ports&lt;/th>
&lt;th scope="col" style="text-align: right">IDS/IPS throughput&lt;/th>
&lt;th scope="col" style="text-align: right">Store price (2026-09-07)&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Gateway">Cloud Gateway Ultra (&lt;code>UCG-Ultra&lt;/code>)&lt;/td>
&lt;td data-label="Default WAN ports">2.5 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>1 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price (2026-09-07)">$129&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Cloud Gateway Max (&lt;code>UCG-Max&lt;/code>)&lt;/td>
&lt;td data-label="Default WAN ports">2.5 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>2.3 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price (2026-09-07)">from $199&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">UniFi Express 7 (&lt;code>UX7&lt;/code>)&lt;/td>
&lt;td data-label="Default WAN ports">10 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>2.3 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price (2026-09-07)">from $199&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Dream Router 7 (&lt;code>UDR7&lt;/code>)&lt;/td>
&lt;td data-label="Default WAN ports">10G SFP+, 2.5 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>2.3 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price (2026-09-07)">$279&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Cloud Gateway Fiber (&lt;code>UCG-Fiber&lt;/code>)&lt;/td>
&lt;td data-label="Default WAN ports">10G SFP+, 10 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>5 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price (2026-09-07)">$279&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Dream Machine Pro (&lt;code>UDM-Pro&lt;/code>)&lt;/td>
&lt;td data-label="Default WAN ports">10G SFP+, 1 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>3.5 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price (2026-09-07)">$379&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Dream Machine SE (&lt;code>UDM-SE&lt;/code>)&lt;/td>
&lt;td data-label="Default WAN ports">10G SFP+, 2.5 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>3.5 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price (2026-09-07)">$499&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Dream Machine Pro Max (&lt;code>UDM-Pro-Max&lt;/code>)&lt;/td>
&lt;td data-label="Default WAN ports">10G SFP+, 2.5 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>5 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price (2026-09-07)">$599&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Dream Machine Beast (&lt;code>UDM-Beast&lt;/code>)&lt;/td>
&lt;td data-label="Default WAN ports">25G SFP28, 10 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>25 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price (2026-09-07)">$1,499&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gateway">Enterprise Firewall (&lt;code>EFG&lt;/code>)&lt;/td>
&lt;td data-label="Default WAN ports">25G SFP28, 2.5 GbE RJ45&lt;/td>
&lt;td style="text-align: right" data-label="IDS/IPS throughput">&lt;strong>12.5 Gbps&lt;/strong>&lt;/td>
&lt;td style="text-align: right" data-label="Store price (2026-09-07)">$1,999&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Read the first two columns against each other. &lt;strong>A UniFi Express 7 exposes a 10 GbE WAN port and inspects at 2.3 Gbps.&lt;/strong> A Cloud Gateway Ultra exposes a 2.5 GbE WAN port and inspects at 1 Gbps. The RJ45 or SFP+ port tells you the physical link speed negotiated with your ONT. The inspection column tells you the ceiling once Threat Management goes on.&lt;/p>
&lt;p>Price order does not match inspection order either. &lt;strong>The $279 Cloud Gateway Fiber (&lt;code>UCG-Fiber&lt;/code>) inspects at 5 Gbps&lt;/strong>, beating the $379 rackmount Dream Machine Pro (&lt;code>3.5 Gbps&lt;/code>) and matching the $599 Dream Machine Pro Max, as independent hardware testing in &lt;a href="https://www.servethehome.com/ubiquiti-unifi-cloud-gateway-fiber-ucg-fiber-review/3/" rel="noopener">ServeTheHome&amp;rsquo;s UCG-Fiber review&lt;/a> also highlights alongside its newer quad-core Cortex-A73 platform.&lt;/p>
&lt;h2 id="multi-gig-fiber--bufferbloat-are-where-appliances-bite-silently">Multi-gig fiber &amp;amp; bufferbloat are where appliances bite silently&lt;/h2>
&lt;p>On a symmetric &lt;code>500 Mbps&lt;/code> or &lt;code>1 Gbps&lt;/code> fiber plan, almost every modern gateway feels effortless. Threat management turns on, speed tests read &lt;code>940 Mbps&lt;/code>, and nothing complains.&lt;/p>
&lt;p>The trap springs when you upgrade to &lt;code>2 Gbps&lt;/code> or &lt;code>5 Gbps&lt;/code> fiber, or route NAS traffic across VLANs. Nothing throws an error banner. Your &lt;code>2.5 Gbps&lt;/code> or &lt;code>5 Gbps&lt;/code> line simply plateaus at the gateway&amp;rsquo;s inspection cap while you blame the ISP.&lt;/p>
&lt;p>Latency under load hits an even lower ceiling on UniFi. Ubiquiti&amp;rsquo;s &lt;a href="https://help.ui.com/hc/en-us/articles/12648661321367-UniFi-Gateway-Smart-Queues" rel="noopener">Smart Queues documentation&lt;/a> states Smart Queues are designed for low-bandwidth connections (&lt;code>&amp;lt;300 Mbps&lt;/code>) and explicitly advises against enabling them above &lt;code>300 Mbps&lt;/code> because QoS disables hardware packet offload. On an x86 OPNsense box, &lt;a href="https://docs.opnsense.org/manual/how-tos/shaper_bufferbloat.html" rel="noopener">FQ-CoDel traffic shaping&lt;/a> has no arbitrary firmware cutoff; ceiling speed depends strictly on your CPU&amp;rsquo;s single-thread clock.&lt;/p>
&lt;h2 id="hardware-sizing--operational-maintenance-comparison-ucg-max--ucg-fiber-vs-x86-opnsense">Hardware-sizing &amp;amp; operational-maintenance comparison: &lt;code>UCG-Max&lt;/code> / &lt;code>UCG-Fiber&lt;/code> vs x86 OPNsense&lt;/h2>
&lt;p>Do not compare &amp;ldquo;UniFi&amp;rdquo; in the abstract against &amp;ldquo;some old PC.&amp;rdquo; Compare the two compact UniFi sweet spots (&lt;code>UCG-Max&lt;/code> and &lt;code>UCG-Fiber&lt;/code>) directly against the two proven x86 OPNsense hardware tiers (&lt;code>Intel N100/N150&lt;/code> fanless &lt;code>i226-V&lt;/code> mini appliance vs &lt;code>Core i3 / N305&lt;/code> SFP+ box):&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Dimension&lt;/th>
&lt;th scope="col">UniFi Cloud Gateway Max (&lt;code>UCG-Max&lt;/code>)&lt;/th>
&lt;th scope="col">UniFi Cloud Gateway Fiber (&lt;code>UCG-Fiber&lt;/code>)&lt;/th>
&lt;th scope="col">Fanless N100 / N150 (&lt;code>4× Intel i226-V 2.5GbE&lt;/code>) + OPNsense&lt;/th>
&lt;th scope="col">Core &lt;code>i3&lt;/code> / &lt;code>N305&lt;/code> SFF (&lt;code>10G SFP+ Intel X550/X710&lt;/code>) + OPNsense&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Dimension">&lt;strong>Physical ports&lt;/strong>&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Max (UCG-Max)">5× &lt;code>2.5 GbE&lt;/code> RJ45 (1 WAN + 4 LAN)&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Fiber (UCG-Fiber)">&lt;code>10G SFP+&lt;/code> + &lt;code>10 GbE&lt;/code> RJ45 + 4× &lt;code>2.5 GbE&lt;/code> (1 PoE+)&lt;/td>
&lt;td data-label="Fanless N100 / N150 (4× Intel i226-V 2.5GbE) &amp;#43; OPNsense">4–6× &lt;code>2.5 GbE&lt;/code> RJ45 (&lt;code>Intel i226-V&lt;/code>)&lt;/td>
&lt;td data-label="Core i3 / N305 SFF (10G SFP&amp;#43; Intel X550/X710) &amp;#43; OPNsense">2× &lt;code>10G SFP+&lt;/code> + 2× &lt;code>2.5 GbE&lt;/code> Intel NICs&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">&lt;strong>Routed / IPS ceiling&lt;/strong>&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Max (UCG-Max)">&lt;code>2.5 Gbps&lt;/code> line / &lt;strong>2.3 Gbps&lt;/strong> published IPS&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Fiber (UCG-Fiber)">&lt;code>10 Gbps&lt;/code> line / &lt;strong>5 Gbps&lt;/strong> published IPS&lt;/td>
&lt;td data-label="Fanless N100 / N150 (4× Intel i226-V 2.5GbE) &amp;#43; OPNsense">&lt;code>2.5 Gbps&lt;/code> NAT/VLAN port limit; Suricata inline IPS scales with ruleset + N100/N150 boost&lt;/td>
&lt;td data-label="Core i3 / N305 SFF (10G SFP&amp;#43; Intel X550/X710) &amp;#43; OPNsense">&lt;code>10 Gbps&lt;/code> inter-VLAN &amp;amp; NAT; highest headroom for multi-gig PPPoE, FQ-CoDel, WireGuard &amp;amp; Suricata&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">&lt;strong>Suricata IDS/IPS control&lt;/strong>&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Max (UCG-Max)">Pre-packaged CyberSecure category toggles&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Fiber (UCG-Fiber)">Pre-packaged CyberSecure category toggles&lt;/td>
&lt;td data-label="Fanless N100 / N150 (4× Intel i226-V 2.5GbE) &amp;#43; OPNsense">Granular per-interface &lt;a href="https://docs.opnsense.org/manual/ips.html" rel="noopener">OPNsense Suricata &lt;code>netmap&lt;/code> IPS&lt;/a>, custom ET Open/Pro rules, per-SID drop/bypass&lt;/td>
&lt;td data-label="Core i3 / N305 SFF (10G SFP&amp;#43; Intel X550/X710) &amp;#43; OPNsense">Same full Suricata &lt;code>netmap&lt;/code> control + RAM/CPU headroom for multi-VLAN inspection&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">&lt;strong>Switch &amp;amp; Wi-Fi pane&lt;/strong>&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Max (UCG-Max)">&lt;strong>Built-in UniFi Network&lt;/strong> adopts switches &amp;amp; APs in one UI&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Fiber (UCG-Fiber)">&lt;strong>Built-in UniFi Network&lt;/strong> adopts switches &amp;amp; APs in one UI&lt;/td>
&lt;td data-label="Fanless N100 / N150 (4× Intel i226-V 2.5GbE) &amp;#43; OPNsense">Separate: run UniFi Network controller in Docker/LXC for APs/switches while OPNsense owns L3&lt;/td>
&lt;td data-label="Core i3 / N305 SFF (10G SFP&amp;#43; Intel X550/X710) &amp;#43; OPNsense">Separate: OPNsense owns L3; switches/APs managed independently&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">&lt;strong>Upgrade &amp;amp; rollback safety&lt;/strong>&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Max (UCG-Max)">Appliance firmware updates (cloud/local backup restore)&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Fiber (UCG-Fiber)">Appliance firmware updates (cloud/local backup restore)&lt;/td>
&lt;td data-label="Fanless N100 / N150 (4× Intel i226-V 2.5GbE) &amp;#43; OPNsense">&lt;strong>ZFS Boot Environments&lt;/strong>: snapshot before major FreeBSD/OPNsense upgrades and roll back at boot menu in 10 seconds&lt;/td>
&lt;td data-label="Core i3 / N305 SFF (10G SFP&amp;#43; Intel X550/X710) &amp;#43; OPNsense">&lt;strong>ZFS Boot Environments&lt;/strong> + portable encrypted &lt;code>config.xml&lt;/code> restore onto any spare x86 box in 5 minutes&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dimension">&lt;strong>Typical wall idle draw&lt;/strong>&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Max (UCG-Max)">~6–10W&lt;/td>
&lt;td data-label="UniFi Cloud Gateway Fiber (UCG-Fiber)">~9–15W (excluding PoE output)&lt;/td>
&lt;td data-label="Fanless N100 / N150 (4× Intel i226-V 2.5GbE) &amp;#43; OPNsense">~8–14W&lt;/td>
&lt;td data-label="Core i3 / N305 SFF (10G SFP&amp;#43; Intel X550/X710) &amp;#43; OPNsense">~15–28W (depends on 10G SFP+ optics vs DAC)&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Notice the operational trade-off honestly. With UniFi, creating VLAN &lt;code>30&lt;/code> automatically provisions the gateway subnet, DHCP server, 802.1Q switch trunk profiles, and Wi-Fi SSID mapping from one screen. With OPNsense + UniFi switches/APs, you create VLAN &lt;code>30&lt;/code> once in OPNsense (&lt;code>Interfaces → Assignments → VLANs&lt;/code> + DHCP) and create a matching &lt;strong>Third-Party Gateway&lt;/strong> VLAN &lt;code>30&lt;/code> network in the UniFi controller. That takes ninety extra seconds per VLAN, and in exchange you own every firewall state, NAT outbound rule, DNS unbound override, and boot snapshot outright.&lt;/p>
&lt;h2 id="rule-granularity--why-new-diy-builds-start-on-opnsense">Rule granularity &amp;amp; why new DIY builds start on OPNsense&lt;/h2>
&lt;p>UniFi Network 9.0 narrowed the gap with &lt;a href="https://help.ui.com/hc/en-us/articles/115003173168-Zone-Based-Firewalls-in-UniFi" rel="noopener">Zone-Based Firewalls&lt;/a>, offering custom zones up to thirty total alongside protocol, port, IP, MAC, and application matching. What remains fixed is the appliance floor underneath: UniFi&amp;rsquo;s six default zones and built-in system policies carry lock icons and cannot be edited or deleted (you place override rules above them), and each network maps to a single zone. On OPNsense&amp;rsquo;s &lt;code>pf&lt;/code> engine, nothing is hidden: floating rules, interface groups, policy-based multi-WAN / VPN gateway routing, live real-time firewall log filtering (&lt;code>Firewall → Log Files → Live View&lt;/code>), and NAT reflection are completely explicit.&lt;/p>
&lt;p>If you choose the DIY route, my &lt;a href="https://techfuelhq.com/networking/opnsense-vs-pfsense-2026/">OPNsense vs pfSense comparison&lt;/a> covers why I start every new box on OPNsense rather than pfSense:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Licensing trajectory:&lt;/strong> Netgate ended the free Home+Lab tier of pfSense Plus in &lt;a href="https://www.netgate.com/blog/addressing-changes-to-pfsense-plus-homelab" rel="noopener">October 2023&lt;/a>, moving third-party pfSense Plus installs to a &lt;a href="https://www.netgate.com/pricing-pfsense-plus" rel="noopener">$129/year subscription&lt;/a> while leaving pfSense CE on a slower release track.&lt;/li>
&lt;li>&lt;strong>Engineering governance:&lt;/strong> Netgate&amp;rsquo;s rushed in-kernel WireGuard rollout and emergency removal in &lt;a href="https://www.netgate.com/blog/wireguard-removed-from-pfsense-ce-and-pfsense-plus-software" rel="noopener">March 2021&lt;/a>, alongside the &lt;a href="https://www.wipo.int/amc/en/domains/decisions/text/2017/d2017-1828.html" rel="noopener">2017 WIPO panel decision (&lt;code>D2017-1828&lt;/code>)&lt;/a> ordering &lt;code>opnsense.com&lt;/code> transferred away from Netgate&amp;rsquo;s principal to OPNsense maintainer Deciso, cemented OPNsense as the cleaner open-source bet.&lt;/li>
&lt;/ol>
&lt;h2 id="use-intel-nics-on-opnsense-skip-realtek">Use Intel NICs on OPNsense (skip Realtek)&lt;/h2>
&lt;p>Nine out of ten &amp;ldquo;my DIY firewall dropped the WAN under load&amp;rdquo; complaints trace straight to a Realtek Ethernet chip (&lt;code>RTL8111&lt;/code> / &lt;code>RTL8125&lt;/code>) running under FreeBSD. Both &lt;a href="https://docs.opnsense.org/manual/hardware.html" rel="noopener">OPNsense&amp;rsquo;s official hardware guide&lt;/a> and &lt;a href="https://docs.netgate.com/pfsense/en/latest/hardware/index.html" rel="noopener">Netgate&amp;rsquo;s FreeBSD hardware docs&lt;/a> give identical guidance: buy &lt;strong>Intel NICs&lt;/strong> (&lt;code>i210&lt;/code>, &lt;code>i350&lt;/code>, &lt;code>i226-V&lt;/code> for 2.5GbE, and &lt;code>X550&lt;/code> or &lt;code>X710&lt;/code> for 10GbE). FreeBSD&amp;rsquo;s &lt;code>igc&lt;/code> and &lt;code>ix&lt;/code> drivers support clean multi-queue interrupts and native Suricata &lt;code>netmap&lt;/code> rings without watchdog timeouts. Check exact Ethernet controller silicon before ordering in our &lt;a href="https://techfuelhq.com/homelab/n150-mini-pc-2026/">N150 mini PC firewall hardware guide&lt;/a>.&lt;/p>
&lt;h2 id="bottom-line-which-box-belongs-at-your-edge">Bottom line: which box belongs at your edge?&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>Buy the UniFi Cloud Gateway Fiber (&lt;code>UCG-Fiber&lt;/code>) or &lt;code>UCG-Max&lt;/code>&lt;/strong> if you already run UniFi switches and Wi-Fi access points, want single-screen VLAN provisioning, and its published IDS/IPS ceiling (&lt;code>5 Gbps&lt;/code> on &lt;code>UCG-Fiber&lt;/code>, &lt;code>2.3 Gbps&lt;/code> on &lt;code>UCG-Max&lt;/code>) clears your WAN speed with room to spare.&lt;/li>
&lt;li>&lt;strong>Build OPNsense on an Intel &lt;code>i226-V&lt;/code> N100/N150 mini PC (for &lt;code>1–2.5 Gbps&lt;/code>) or Core &lt;code>i3&lt;/code> SFP+ SFF box (for &lt;code>5–10 Gbps&lt;/code>)&lt;/strong> if you want live &lt;code>pf&lt;/code> packet logs, policy-based WireGuard/Tailscale routing, high-speed &lt;code>FQ-CoDel&lt;/code> bufferbloat control above &lt;code>300 Mbps&lt;/code>, ZFS boot-environment rollbacks, and zero vendor-imposed inspection caps.&lt;/li>
&lt;li>&lt;strong>Keep 10GbE NAS traffic on Layer 2 either way:&lt;/strong> Put high-speed storage transfers on a dedicated switch VLAN/subnet so your workstation and NAS talk at 10 Gbps across the switch ASIC without turning your firewall into an expensive bottleneck.&lt;/li>
&lt;/ul></description></item><item><title>Docker Compose Environment Variables: .env vs env_file</title><link>https://techfuelhq.com/tutorials/docker-compose-environment-variables-2026/</link><pubDate>Sat, 15 Aug 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/docker-compose-environment-variables-2026/</guid><atom:updated>2026-11-14T10:50:00Z</atom:updated><description>&lt;p>By &lt;a href="https://techfuelhq.com/author/lk-wood-iv/">LK Wood IV&lt;/a> · 2026-08-15 · Updated 2026-11-14 · ~12 min read · St. Louis County, MO&lt;/p>
&lt;p>Drop a &lt;code>.env&lt;/code> file next to &lt;code>compose.yaml&lt;/code>, fill it with application settings, run &lt;code>docker compose up -d&lt;/code>, and exec into the container to inspect &lt;code>env&lt;/code>.&lt;/p>
&lt;p>Nothing from &lt;code>.env&lt;/code> is inside the container.&lt;/p>
&lt;p>That single surprise wastes more homelab debugging hours than almost anything else in Docker. It happens because two Compose features share nearly identical names while operating at completely separate stages of container startup:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Phase 1 — YAML Interpolation (&lt;code>.env&lt;/code> and &lt;code>--env-file&lt;/code>):&lt;/strong> Substitutes &lt;code>${VAR}&lt;/code> text placeholders &lt;strong>inside &lt;code>compose.yaml&lt;/code> itself&lt;/strong> before Docker creates anything. By itself, &lt;code>.env&lt;/code> injects zero variables into any container.&lt;/li>
&lt;li>&lt;strong>Phase 2 — Container Runtime Injection (&lt;code>env_file:&lt;/code> and &lt;code>environment:&lt;/code>):&lt;/strong> Passes key-value variables &lt;strong>into the running container process&lt;/strong>, and is never consulted to fill &lt;code>${VAR}&lt;/code> placeholders in &lt;code>compose.yaml&lt;/code>.&lt;/li>
&lt;/ul>
&lt;p>&lt;a href="https://docs.docker.com/compose/how-tos/environment-variables/envvars-precedence/" rel="noopener">Docker&amp;rsquo;s official precedence documentation&lt;/a> states that distinction outright: the Host OS environment and &lt;code>.env&lt;/code> file do not put a variable inside a container on their own unless &lt;code>compose.yaml&lt;/code> explicitly references or passes them through.&lt;/p>
&lt;h2 id="yaml-interpolation-env-vs-runtime-injection-env_file">YAML interpolation (&lt;code>.env&lt;/code>) vs runtime injection (&lt;code>env_file:&lt;/code>)&lt;/h2>
&lt;p>Before looking at precedence conflicts, separate the two mechanisms side by side. Mixing them up causes two silent bugs. Names look alike; directions stay opposite.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Property&lt;/th>
&lt;th scope="col">Project &lt;code>.env&lt;/code> (or CLI &lt;code>--env-file&lt;/code>)&lt;/th>
&lt;th scope="col">Service &lt;code>env_file:&lt;/code> attribute&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Property">&lt;strong>When Compose reads it&lt;/strong>&lt;/td>
&lt;td data-label="Project .env (or CLI --env-file)">&lt;strong>Phase 1:&lt;/strong> Parsing &lt;code>compose.yaml&lt;/code>&lt;/td>
&lt;td data-label="Service env_file: attribute">&lt;strong>Phase 2:&lt;/strong> Creating the container runtime environment&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Property">&lt;strong>Fills &lt;code>${VAR}&lt;/code> in &lt;code>compose.yaml&lt;/code>?&lt;/strong> (&lt;code>image:&lt;/code>, &lt;code>ports:&lt;/code>, &lt;code>volumes:&lt;/code>)&lt;/td>
&lt;td data-label="Project .env (or CLI --env-file)">&lt;strong>Yes&lt;/strong>&lt;/td>
&lt;td data-label="Service env_file: attribute">&lt;strong>No — completely ignored during YAML interpolation&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Property">&lt;strong>Injects variables into the container?&lt;/strong>&lt;/td>
&lt;td data-label="Project .env (or CLI --env-file)">&lt;strong>No&lt;/strong> (unless wired into &lt;code>environment:&lt;/code>)&lt;/td>
&lt;td data-label="Service env_file: attribute">&lt;strong>Yes — every &lt;code>KEY=VAL&lt;/code> line enters the container&lt;/strong>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Property">&lt;strong>Relative path base directory&lt;/strong>&lt;/td>
&lt;td data-label="Project .env (or CLI --env-file)">&lt;code>--env-file&lt;/code> resolves from &lt;strong>your current shell working directory&lt;/strong>; default &lt;code>.env&lt;/code> lives in the project directory&lt;/td>
&lt;td data-label="Service env_file: attribute">Resolves from &lt;strong>&lt;code>compose.yaml&lt;/code>&amp;rsquo;s parent folder&lt;/strong>, regardless of your shell &lt;code>pwd&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Property">&lt;strong>If the file is missing&lt;/strong>&lt;/td>
&lt;td data-label="Project .env (or CLI --env-file)">Default &lt;code>.env&lt;/code>: &lt;strong>silent no-op&lt;/strong>; explicit &lt;code>--env-file&lt;/code>: &lt;strong>hard error&lt;/strong>&lt;/td>
&lt;td data-label="Service env_file: attribute">&lt;strong>Hard error&lt;/strong> by default (unless &lt;code>required: false&lt;/code> on Compose 2.24+)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Property">&lt;strong>Visible in &lt;code>docker compose config&lt;/code>?&lt;/strong>&lt;/td>
&lt;td data-label="Project .env (or CLI --env-file)">Shows interpolated values inside the rendered YAML&lt;/td>
&lt;td data-label="Service env_file: attribute">Expands and merges &lt;code>env_file:&lt;/code> keys into the service&amp;rsquo;s rendered &lt;code>environment:&lt;/code> block&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Here are both failure directions in ten lines of YAML:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># .env (Phase 1: YAML interpolation source ONLY)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">POSTGRES_TAG=17-alpine&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># compose.yaml&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">db&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">postgres:${POSTGRES_TAG} &lt;/span> &lt;span style="color:#75715e"># Works: .env turns this into postgres:17-alpine&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">env_file&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">./app.env # Works&lt;/span>: &lt;span style="color:#ae81ff">every line in app.env enters the container&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">TZ=America/Chicago # Works&lt;/span>: &lt;span style="color:#ae81ff">TZ enters the container&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>In that file, &lt;code>POSTGRES_TAG&lt;/code> never enters the &lt;code>db&lt;/code> container&amp;rsquo;s &lt;code>env&lt;/code> output. Now look at the mirror-image mistake:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">web&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;nginx:${NGINX_TAG}&amp;#34;&lt;/span> &lt;span style="color:#75715e"># BROKEN: env_file is NOT read for ${NGINX_TAG}!&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">env_file&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">./web.env &lt;/span> &lt;span style="color:#75715e"># Even if NGINX_TAG=1.27 is inside web.env, image becomes &amp;#34;nginx:&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Listing &lt;code>./web.env&lt;/code> (or even &lt;code>./.env&lt;/code>) under &lt;code>env_file:&lt;/code> dumps every key into the container process at runtime, while &lt;code>${NGINX_TAG}&lt;/code> on the &lt;code>image:&lt;/code> line still evaluates before &lt;code>env_file:&lt;/code> is ever opened.&lt;/p>
&lt;h2 id="complete-6-level-docker-compose-variable-precedence-table">Complete 6-level Docker Compose variable precedence table&lt;/h2>
&lt;p>When the same variable name appears in more than one place, &lt;a href="https://docs.docker.com/compose/how-tos/environment-variables/envvars-precedence/" rel="noopener">Docker&amp;rsquo;s environment variable precedence specification&lt;/a> resolves what actually lands &lt;strong>inside the container&lt;/strong> from &lt;strong>Level 1 (highest)&lt;/strong> down to &lt;strong>Level 6 (lowest)&lt;/strong>:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Priority&lt;/th>
&lt;th scope="col">Mechanism&lt;/th>
&lt;th scope="col">Example&lt;/th>
&lt;th scope="col">Critical edge case to watch&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Priority">&lt;strong>1 (Highest)&lt;/strong>&lt;/td>
&lt;td data-label="Mechanism">&lt;strong>&lt;code>docker compose run -e&lt;/code> CLI flag&lt;/strong>&lt;/td>
&lt;td data-label="Example">&lt;code>docker compose run --rm -e APP_ENV=cli_run web env&lt;/code>&lt;/td>
&lt;td data-label="Critical edge case to watch">Applies only to &lt;code>docker compose run&lt;/code> one-off containers (&lt;code>docker compose up&lt;/code> has no &lt;code>-e&lt;/code> flag). Bare &lt;code>-e VAR&lt;/code> pulls from host shell.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Priority">&lt;strong>2&lt;/strong>&lt;/td>
&lt;td data-label="Mechanism">&lt;strong>Host shell environment&lt;/strong> (passed or interpolated into service)&lt;/td>
&lt;td data-label="Example">&lt;code>APP_ENV=host_shell docker compose up -d&lt;/code> with &lt;code>environment: [APP_ENV]&lt;/code> or &lt;code>APP_ENV=${APP_ENV}&lt;/code>&lt;/td>
&lt;td data-label="Critical edge case to watch">Host shell beats &lt;code>.env&lt;/code> during &lt;code>${VAR}&lt;/code> interpolation AND beats &lt;code>env_file:&lt;/code> when bare &lt;code>environment: - APP_ENV&lt;/code> is listed. Unexported shell vars are invisible!&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Priority">&lt;strong>3&lt;/strong>&lt;/td>
&lt;td data-label="Mechanism">&lt;strong>Service &lt;code>environment:&lt;/code> attribute&lt;/strong> in &lt;code>compose.yaml&lt;/code>&lt;/td>
&lt;td data-label="Example">&lt;code>environment: [APP_ENV=compose_attr]&lt;/code> (literal or &lt;code>.env&lt;/code>-interpolated)&lt;/td>
&lt;td data-label="Critical edge case to watch">&lt;strong>Beats &lt;code>env_file:&lt;/code> even when empty!&lt;/strong> A stray &lt;code>APP_ENV=&lt;/code> or &lt;code>APP_ENV: &amp;quot;${UNSET}&amp;quot;&lt;/code> under &lt;code>environment:&lt;/code> wipes out a valid &lt;code>APP_ENV&lt;/code> in &lt;code>env_file:&lt;/code>.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Priority">&lt;strong>4&lt;/strong>&lt;/td>
&lt;td data-label="Mechanism">&lt;strong>Service &lt;code>env_file:&lt;/code> attribute&lt;/strong> in &lt;code>compose.yaml&lt;/code>&lt;/td>
&lt;td data-label="Example">&lt;code>env_file: [./base.env, ./local.env]&lt;/code>&lt;/td>
&lt;td data-label="Critical edge case to watch">Evaluated top-to-bottom when multiple files are listed; &lt;strong>the last file in the &lt;code>env_file:&lt;/code> list wins&lt;/strong> (&lt;code>local.env&lt;/code> beats &lt;code>base.env&lt;/code>).&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Priority">&lt;strong>5&lt;/strong>&lt;/td>
&lt;td data-label="Mechanism">&lt;strong>Container image &lt;code>Dockerfile&lt;/code> &lt;code>ENV&lt;/code>&lt;/strong>&lt;/td>
&lt;td data-label="Example">&lt;code>ENV APP_ENV=image_default&lt;/code> baked into image layers&lt;/td>
&lt;td data-label="Critical edge case to watch">Pure fallback. Evaluates &lt;strong>only&lt;/strong> if Levels 1–4 have zero entry for &lt;code>APP_ENV&lt;/code>. Any Compose entry replaces it completely.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Priority">&lt;strong>6 (Lowest)&lt;/strong>&lt;/td>
&lt;td data-label="Mechanism">&lt;strong>Unset / undefined&lt;/strong>&lt;/td>
&lt;td data-label="Example">Variable omitted everywhere&lt;/td>
&lt;td data-label="Critical edge case to watch">Absent from container &lt;code>env&lt;/code>. If referenced via unguarded &lt;code>${VAR}&lt;/code> in YAML, silently becomes empty string &lt;code>&amp;quot;&amp;quot;&lt;/code>!&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Keep &lt;strong>Phase 1 YAML interpolation precedence&lt;/strong> distinct in your head too (&lt;a href="https://docs.docker.com/compose/how-tos/environment-variables/variable-interpolation/" rel="noopener">variable interpolation docs&lt;/a>). When Compose fills &lt;code>${VAR}&lt;/code> inside &lt;code>compose.yaml&lt;/code>, it checks three sources in order:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Host OS shell environment&lt;/strong> (&lt;code>export VAR=...&lt;/code> or inline &lt;code>VAR=... docker compose ...&lt;/code>)&lt;/li>
&lt;li>&lt;strong>CLI &lt;code>--env-file&lt;/code> file(s)&lt;/strong> (or &lt;code>COMPOSE_ENV_FILES&lt;/code>; if passed multiple times, the last &lt;code>--env-file&lt;/code> wins)&lt;/li>
&lt;li>&lt;strong>Default &lt;code>.env&lt;/code> file&lt;/strong> in the project directory (unless disabled via &lt;code>COMPOSE_DISABLE_ENV_FILE=1&lt;/code>)&lt;/li>
&lt;/ol>
&lt;h2 id="verify-all-6-levels-yourself-with-docker-compose-config">Verify all 6 levels yourself with &lt;code>docker compose config&lt;/code>&lt;/h2>
&lt;p>Never guess what Compose resolved. Never test with live database passwords either. Create a disposable lab directory with distinct, non-secret marker strings (&lt;code>FROM_DOTENV&lt;/code>, &lt;code>FROM_ENV_FILE&lt;/code>, &lt;code>FROM_COMPOSE_ENV&lt;/code>, &lt;code>FROM_HOST_SHELL&lt;/code>, &lt;code>FROM_RUN_CLI&lt;/code>) and inspect the merged model using &lt;a href="https://docs.docker.com/reference/cli/docker/compose/config/" rel="noopener">&lt;code>docker compose config&lt;/code>&lt;/a>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>mkdir -p /tmp/compose-env-lab &lt;span style="color:#f92672">&amp;amp;&amp;amp;&lt;/span> cd /tmp/compose-env-lab
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &amp;gt; .env &lt;span style="color:#e6db74">&amp;lt;&amp;lt;&amp;#39;EOF&amp;#39;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">IMAGE_TAG=3.20
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">TEST_INTERPOLATED=FROM_DOTENV
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">EOF&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &amp;gt; runtime.env &lt;span style="color:#e6db74">&amp;lt;&amp;lt;&amp;#39;EOF&amp;#39;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">TEST_FILE_ONLY=FROM_ENV_FILE
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">TEST_CONFLICT=FROM_ENV_FILE
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">TEST_EMPTY_TRAP=GOOD_VALUE_IN_ENV_FILE
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">EOF&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &amp;gt; compose.yaml &lt;span style="color:#e6db74">&amp;lt;&amp;lt;&amp;#39;EOF&amp;#39;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">services:
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> probe:
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> image: alpine:${IMAGE_TAG}
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> env_file:
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> - ./runtime.env
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> environment:
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> TEST_CONFLICT: FROM_COMPOSE_ENV
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> TEST_SHELL_BRIDGE: ${TEST_INTERPOLATED}
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74"> TEST_EMPTY_TRAP: &amp;#34;&amp;#34;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">EOF&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Run &lt;code>docker compose config&lt;/code> before starting any container:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker compose config
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Look at the rendered &lt;code>environment:&lt;/code> block Compose prints for &lt;code>probe&lt;/code>:&lt;/p>
&lt;ul>
&lt;li>&lt;code>image&lt;/code> resolved to &lt;code>alpine:3.20&lt;/code>, while &lt;code>IMAGE_TAG&lt;/code> itself is &lt;strong>absent&lt;/strong> from &lt;code>environment:&lt;/code> (proving &lt;code>.env&lt;/code> alone stays out of the container).&lt;/li>
&lt;li>&lt;code>TEST_FILE_ONLY&lt;/code> equals &lt;code>FROM_ENV_FILE&lt;/code> (Level 4).&lt;/li>
&lt;li>&lt;code>TEST_CONFLICT&lt;/code> equals &lt;code>FROM_COMPOSE_ENV&lt;/code> (Level 3 beat Level 4).&lt;/li>
&lt;li>&lt;code>TEST_SHELL_BRIDGE&lt;/code> equals &lt;code>FROM_DOTENV&lt;/code> (&lt;code>.env&lt;/code> interpolated &lt;code>${TEST_INTERPOLATED}&lt;/code> into Level 3).&lt;/li>
&lt;li>&lt;code>TEST_EMPTY_TRAP&lt;/code> equals &lt;code>&amp;quot;&amp;quot;&lt;/code> (an empty string in Level 3 wiped out &lt;code>GOOD_VALUE_IN_ENV_FILE&lt;/code> from Level 4 with zero warnings!).&lt;/li>
&lt;/ul>
&lt;p>Now watch Levels 2 and 1 override that same stack live without editing a file:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Level 2: Host shell overrides .env interpolation -&amp;gt; prints TEST_SHELL_BRIDGE=FROM_HOST_SHELL&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>TEST_INTERPOLATED&lt;span style="color:#f92672">=&lt;/span>FROM_HOST_SHELL docker compose run --rm probe sh -c &lt;span style="color:#e6db74">&amp;#39;env | grep ^TEST_ | sort&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Level 1: run -e beats everything -&amp;gt; prints TEST_CONFLICT=FROM_RUN_CLI&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose run --rm -e TEST_CONFLICT&lt;span style="color:#f92672">=&lt;/span>FROM_RUN_CLI probe sh -c &lt;span style="color:#e6db74">&amp;#39;env | grep ^TEST_ | sort&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Clean up the scratch folder when finished&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>rm -rf /tmp/compose-env-lab
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Whenever a stack behaves strangely on your server (whether managed from the CLI or via &lt;a href="https://techfuelhq.com/tutorials/dockge-docker-compose-manager-2026/">Dockge&lt;/a>), &lt;code>docker compose config&lt;/code> and &lt;code>docker compose config --environment&lt;/code> show the exact post-interpolation truth in two seconds. Keep &lt;code>docker compose config&lt;/code> output out of public GitHub issues or screenshots if real credentials sit in your env files, because Compose prints every resolved value inline!&lt;/p>
&lt;h2 id="env_file-multi-file-layering-required-false-and-format-raw">&lt;code>env_file:&lt;/code> multi-file layering, &lt;code>required: false&lt;/code>, and &lt;code>format: raw&lt;/code>&lt;/h2>
&lt;p>Modern Compose v2 (&lt;a href="https://docs.docker.com/reference/compose-file/services/#env_file" rel="noopener">services &lt;code>env_file&lt;/code> reference&lt;/a>) supports a structured mapping syntax under &lt;code>env_file:&lt;/code> that solves two classic parser headaches:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">webapp&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">env_file&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">./defaults.env&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">path&lt;/span>: &lt;span style="color:#ae81ff">./local-overrides.env&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">required: false # Compose 2.24.0+&lt;/span>: &lt;span style="color:#ae81ff">silent skip if missing&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">path&lt;/span>: &lt;span style="color:#ae81ff">./literal-hashes.env&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">format: raw # Compose 2.30.0+&lt;/span>: &lt;span style="color:#66d9ef">no&lt;/span> &lt;span style="color:#ae81ff">quote stripping or $ expansion!&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Pay close attention to &lt;code>format: raw&lt;/code> (added in Compose &lt;code>2.30.0&lt;/code>). In standard &lt;code>.env&lt;/code> and &lt;code>env_file&lt;/code> syntax, double-quoted and unquoted values expand &lt;code>$&lt;/code> signs—so a bcrypt password hash like &lt;code>$2a$12$R9h/cIPz0gi...&lt;/code> gets mangled into &lt;code>$R9h/cIPz0gi...&lt;/code> unless wrapped in single quotes (&lt;code>'$2a$12...'&lt;/code>), escaped as &lt;code>$$&lt;/code>, or loaded via &lt;code>format: raw&lt;/code>. Also watch inline comments: &lt;code>PORT=8080 # web&lt;/code> sets &lt;code>8080&lt;/code>, whereas &lt;code>PORT=8080# web&lt;/code> (missing the space before &lt;code>#&lt;/code>) sets the literal string &lt;code>8080# web&lt;/code>.&lt;/p>
&lt;h2 id="guarding-defaults-var-default-vs-var-default-vs-varerror">Guarding defaults: &lt;code>${VAR:-default}&lt;/code> vs &lt;code>${VAR-default}&lt;/code> vs &lt;code>${VAR:?error}&lt;/code>&lt;/h2>
&lt;p>Never leave critical image tags or database usernames as bare &lt;code>${VAR}&lt;/code> placeholders. An unset &lt;code>${POSTGRES_VERSION}&lt;/code> turns &lt;code>postgres:${POSTGRES_VERSION}&lt;/code> into &lt;code>postgres:&lt;/code>, producing a cryptic registry parse error instead of telling you which variable was missing.&lt;/p>
&lt;p>The colon inside parameter expansion controls whether &lt;strong>empty strings (&lt;code>VAR=&amp;quot;&amp;quot;&lt;/code>)&lt;/strong> trigger the fallback alongside &lt;strong>unset&lt;/strong> variables:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Syntax&lt;/th>
&lt;th scope="col">Variable is &lt;strong>unset&lt;/strong>&lt;/th>
&lt;th scope="col">Variable is &lt;strong>empty (&lt;code>VAR=&lt;/code>)&lt;/strong>&lt;/th>
&lt;th scope="col">Variable is &lt;strong>&lt;code>VAR=custom&lt;/code>&lt;/strong>&lt;/th>
&lt;th scope="col">Best use in &lt;code>compose.yaml&lt;/code>&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Syntax">&lt;code>${VAR:-default}&lt;/code>&lt;/td>
&lt;td data-label="Variable is unset">&lt;code>&amp;quot;default&amp;quot;&lt;/code>&lt;/td>
&lt;td data-label="Variable is empty (VAR=)">&lt;code>&amp;quot;default&amp;quot;&lt;/code>&lt;/td>
&lt;td data-label="Variable is VAR=custom">&lt;code>&amp;quot;custom&amp;quot;&lt;/code>&lt;/td>
&lt;td data-label="Best use in compose.yaml">Safe defaults for image tags, ports, and optional settings&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Syntax">&lt;code>${VAR-default}&lt;/code>&lt;/td>
&lt;td data-label="Variable is unset">&lt;code>&amp;quot;default&amp;quot;&lt;/code>&lt;/td>
&lt;td data-label="Variable is empty (VAR=)">&lt;code>&amp;quot;&amp;quot;&lt;/code> (stays empty!)&lt;/td>
&lt;td data-label="Variable is VAR=custom">&lt;code>&amp;quot;custom&amp;quot;&lt;/code>&lt;/td>
&lt;td data-label="Best use in compose.yaml">Rare cases where an explicit empty string is intentional&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Syntax">&lt;code>${VAR:?error msg}&lt;/code>&lt;/td>
&lt;td data-label="Variable is unset">&lt;strong>Fails fast with &lt;code>error msg&lt;/code>&lt;/strong>&lt;/td>
&lt;td data-label="Variable is empty (VAR=)">&lt;strong>Fails fast with &lt;code>error msg&lt;/code>&lt;/strong>&lt;/td>
&lt;td data-label="Variable is VAR=custom">&lt;code>&amp;quot;custom&amp;quot;&lt;/code>&lt;/td>
&lt;td data-label="Best use in compose.yaml">Required paths, hostnames, and non-default usernames&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Syntax">&lt;code>${VAR?error msg}&lt;/code>&lt;/td>
&lt;td data-label="Variable is unset">&lt;strong>Fails fast with &lt;code>error msg&lt;/code>&lt;/strong>&lt;/td>
&lt;td data-label="Variable is empty (VAR=)">&lt;code>&amp;quot;&amp;quot;&lt;/code> (allowed!)&lt;/td>
&lt;td data-label="Variable is VAR=custom">&lt;code>&amp;quot;custom&amp;quot;&lt;/code>&lt;/td>
&lt;td data-label="Best use in compose.yaml">Required key that is allowed to be blank&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">db&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;postgres:${POSTGRES_VERSION:-17}&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">POSTGRES_DB&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;${DB_NAME:-app}&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">POSTGRES_USER&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;${DB_USER:?Set DB_USER in .env before starting}&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Also note the warning difference on pass-through lines: writing bare &lt;code>- DEBUG&lt;/code> under &lt;code>environment:&lt;/code> emits &lt;strong>zero warning&lt;/strong> when &lt;code>DEBUG&lt;/code> is unset in your shell, whereas writing &lt;code>- DEBUG=${DEBUG}&lt;/code> prints an explicit &lt;code>WARN[0000] The &amp;quot;DEBUG&amp;quot; variable is not set. Defaulting to a blank string.&lt;/code> Use the explicit &lt;code>${VAR:?...}&lt;/code> or &lt;code>${VAR:-...}&lt;/code> forms so missing &lt;code>.env&lt;/code> files on a new server fail loud at &lt;code>docker compose up&lt;/code> time rather than half-starting a broken container.&lt;/p>
&lt;h2 id="keep-real-secrets-out-of-environment-variables">Keep real secrets out of environment variables&lt;/h2>
&lt;p>Everything injected via &lt;code>environment:&lt;/code> or &lt;code>env_file:&lt;/code> is stored in container metadata and returned in plaintext by &lt;code>docker inspect&lt;/code>. On Linux, &lt;a href="https://techfuelhq.com/tutorials/add-user-to-docker-group-2026/">anyone in the &lt;code>docker&lt;/code> group&lt;/a> can inspect every running container—and crashed apps routinely dump &lt;code>process.env&lt;/code> or &lt;code>os.environ&lt;/code> into stack traces. Build-time &lt;code>ARG&lt;/code> tokens are even worse, remaining baked into &lt;code>docker history&lt;/code> image metadata unless handled via BuildKit secret mounts.&lt;/p>
&lt;p>Where official images support the &lt;code>_FILE&lt;/code> convention (&lt;code>postgres&lt;/code>, &lt;code>mariadb&lt;/code>, &lt;code>mysql&lt;/code>, &lt;code>wordpress&lt;/code>, &lt;code>authelia&lt;/code>, &lt;code>vaultwarden&lt;/code> admin tokens), mount file-based Compose secrets into &lt;code>/run/secrets/&amp;lt;name&amp;gt;&lt;/code> as recommended in &lt;a href="https://docs.docker.com/compose/how-tos/environment-variables/best-practices/" rel="noopener">Docker&amp;rsquo;s environment-variable best practices&lt;/a>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">db&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">postgres:17&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">POSTGRES_USER&lt;/span>: &lt;span style="color:#ae81ff">appuser&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">POSTGRES_PASSWORD_FILE&lt;/span>: &lt;span style="color:#ae81ff">/run/secrets/db_password&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">secrets&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">db_password&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">secrets&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">db_password&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">file&lt;/span>: &lt;span style="color:#ae81ff">./secrets/db_password.txt &lt;/span> &lt;span style="color:#75715e"># chmod 600 on host, gitignored&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="my-three-rule-house-standard">My three-rule house standard&lt;/h2>
&lt;p>After getting burned once at 1 a.m. by an empty &lt;code>environment:&lt;/code> key overriding a valid &lt;code>env_file:&lt;/code> entry, I stick to three non-negotiable habits on every homelab stack:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>&lt;code>.env&lt;/code> shapes &lt;code>compose.yaml&lt;/code> only:&lt;/strong> Pinned image versions (&lt;code>IMMICH_VERSION&lt;/code>), published host ports, and host bind-mount paths (&lt;code>UPLOAD_LOCATION&lt;/code>) live in &lt;code>.env&lt;/code>, guarded by &lt;code>:-&lt;/code> defaults or &lt;code>:?&lt;/code> checks.&lt;/li>
&lt;li>&lt;strong>&lt;code>env_file:&lt;/code> feeds application config:&lt;/strong> App-internal flags go into a dedicated &lt;code>./app.env&lt;/code> (with &lt;code>chmod 600&lt;/code>), while actual credentials use &lt;code>/run/secrets/&lt;/code> &lt;code>_FILE&lt;/code> mounts wherever supported.&lt;/li>
&lt;li>&lt;strong>Never define the same variable name in both &lt;code>environment:&lt;/code> and &lt;code>env_file:&lt;/code>:&lt;/strong> Precedence tables are for diagnosing bugs—not for intentionally defining conflicting values across two files and hoping future-you remembers Level 3 beats Level 4. While tidying up old stacks, check unused volumes and dangling images with our &lt;a href="https://techfuelhq.com/tutorials/docker-cleanup-disk-space-2026/">Docker disk-space cleanup guide&lt;/a>.&lt;/li>
&lt;/ol>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://docs.docker.com/compose/how-tos/environment-variables/envvars-precedence/" rel="noopener">Docker Compose Environment Variables Precedence&lt;/a> — official 6-level container precedence table and &lt;code>.env&lt;/code> / host OS illustration boundary.&lt;/li>
&lt;li>&lt;a href="https://docs.docker.com/compose/how-tos/environment-variables/set-environment-variables/" rel="noopener">Set Environment Variables in Docker Compose&lt;/a> and &lt;a href="https://docs.docker.com/reference/compose-file/services/#env_file" rel="noopener">Compose &lt;code>env_file&lt;/code> Reference&lt;/a> — &lt;code>environment:&lt;/code> vs &lt;code>env_file:&lt;/code>, &lt;code>required: false&lt;/code> (2.24+), and &lt;code>format: raw&lt;/code> (2.30+).&lt;/li>
&lt;li>&lt;a href="https://docs.docker.com/compose/how-tos/environment-variables/variable-interpolation/" rel="noopener">Variable Interpolation in Docker Compose&lt;/a> and &lt;a href="https://docs.docker.com/compose/how-tos/environment-variables/envvars/" rel="noopener">Pre-defined Environment Variables&lt;/a> — &lt;code>${VAR:-default}&lt;/code>, &lt;code>${VAR:?err}&lt;/code>, &lt;code>COMPOSE_ENV_FILES&lt;/code>, and &lt;code>COMPOSE_DISABLE_ENV_FILE&lt;/code>.&lt;/li>
&lt;li>&lt;a href="https://docs.docker.com/reference/cli/docker/compose/config/" rel="noopener">&lt;code>docker compose config&lt;/code> CLI Reference&lt;/a> and &lt;a href="https://docs.docker.com/compose/how-tos/environment-variables/best-practices/" rel="noopener">Environment Variables Best Practices&lt;/a>.&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Where to buy the A host that can hold the whole stack:&lt;/strong> &lt;a href="https://www.amazon.com/s?k=mini+pc+32gb&amp;tag=techfuelhq-20" rel="nofollow sponsored">Search Amazon&lt;/a> &amp;middot; &lt;a href="https://click.linksynergy.com/deeplink?id=CW4UrCo/56I&amp;mid=44583&amp;murl=https%3A%2F%2Fwww.newegg.com%2Fp%2Fpl%3Fd%3Dmini%2520pc%252032gb" rel="nofollow sponsored">Search Newegg&lt;/a>. Affiliate links. As an Amazon Associate I earn from qualifying purchases.&lt;/p></description></item><item><title>Proxmox vs Docker (2026): The Real Homelab Stack</title><link>https://techfuelhq.com/articles/proxmox-vs-docker-2026/</link><pubDate>Thu, 02 Jul 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/proxmox-vs-docker-2026/</guid><atom:updated>2026-11-14T10:50:00Z</atom:updated><description>&lt;p>Search &amp;ldquo;Proxmox vs Docker&amp;rdquo; and you will wade through years of forum threads arguing a false binary. They sit at different layers of the stack. Stop treating them like rivals.&lt;/p>
&lt;p>In my own homelab, I run both together. Proxmox VE 9 owns the bare metal, and one dedicated Debian 13 VM runs Docker Engine and Docker Compose on top of it.&lt;/p>
&lt;p>Proxmox carves physical CPU, RAM, NVMe storage, and NICs into isolated virtual machines and LXC system containers. Docker packages applications inside a single Linux OS. Once you see the boundary, only two architecture questions remain:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Should bare metal run Proxmox VE or plain Linux + Docker?&lt;/strong>&lt;/li>
&lt;li>&lt;strong>If Proxmox owns the metal, why put Docker inside a QEMU VM instead of an unprivileged LXC container?&lt;/strong>&lt;/li>
&lt;/ol>
&lt;p>If you are also weighing system containers against full VMs for non-Docker services like Pi-hole or WireGuard, read our &lt;a href="https://techfuelhq.com/homelab/lxc-vs-vm-proxmox-2026/">LXC vs VM on Proxmox breakdown&lt;/a> alongside this guide.&lt;/p>
&lt;h2 id="the-production-homelab-pattern-proxmox--one-debian-docker-vm">The production homelab pattern: Proxmox + one Debian Docker VM&lt;/h2>
&lt;p>Almost every self-hosted project ships a &lt;code>compose.yaml&lt;/code> file first. Hand-building 25 separate LXC containers wastes weekends. Conversely, installing Ubuntu + Docker straight onto bare metal forfeits instant hypervisor rollbacks, Home Assistant OS appliances, Windows test guests, and bare-metal-independent restores.&lt;/p>
&lt;p>Layering Proxmox VE 9 on bare metal with one Debian VM for Docker Compose solves both problems at once:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>One guest kernel boundary:&lt;/strong> All 15 or 30 Compose containers share one VM (&lt;code>~600–900 MB&lt;/code> of base guest RAM overhead once, not per app), with standard &lt;code>ext4&lt;/code> filesystem semantics regardless of whether Proxmox uses ZFS, LVM-thin, or Ceph underneath.&lt;/li>
&lt;li>&lt;strong>Five-second incremental backups:&lt;/strong> Running VMs backed up to &lt;a href="https://www.proxmox.com/en/products/proxmox-backup-server/overview" rel="noopener">Proxmox Backup Server (PBS)&lt;/a> track changed 4 MiB blocks in memory via QEMU dirty bitmaps. After the first full backup, nightly snapshots of a 200 GB Docker VM take a few seconds without stopping a single container.&lt;/li>
&lt;li>&lt;strong>Zero host-upgrade breakage:&lt;/strong> Proxmox kernel, &lt;code>AppArmor&lt;/code>, &lt;code>lxcfs&lt;/code>, and &lt;code>systemd&lt;/code> point-release updates never break &lt;code>runc&lt;/code> or &lt;code>containerd&lt;/code> inside a QEMU VM.&lt;/li>
&lt;/ul>
&lt;p>When bare-metal Debian + Docker wins instead: Pick bare metal when an 8 GB mini PC or single-board computer serves one isolated job (for example, an off-site Restic target or a standalone edge proxy) and will never host a second VM or PBS backup agent. Plain Debian + Docker Engine is clean, fast, and avoids hypervisor memory overhead. On any 16 GB+ multi-service home server, Proxmox underneath pays for itself the first time an update goes sideways. (Moving off VMware? See &lt;a href="https://techfuelhq.com/articles/proxmox-vs-esxi-2025/">Proxmox vs ESXi&lt;/a>.)&lt;/p>
&lt;h2 id="backup-kernel-isolation--gpu-sharing-comparison">Backup, kernel isolation &amp;amp; GPU-sharing comparison&lt;/h2>
&lt;p>Proxmox&amp;rsquo;s official &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pct.html" rel="noopener">Linux Container documentation (&lt;code>chapter-pct&lt;/code>)&lt;/a> explicitly advises running application containers like Docker inside a QEMU VM:&lt;/p>
&lt;blockquote>
&lt;p>&amp;ldquo;If you want to run application containers, for example, Docker images, it is recommended that you run them inside a Proxmox QEMU VM. This will give you all the advantages of application containerization, while also providing the benefits that VMs offer, such as strong isolation from the host and the ability to live-migrate.&amp;rdquo;&lt;/p>&lt;/blockquote>
&lt;p>Here is the concrete operational engineering behind that recommendation across every failure mode homelabbers hit:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Operational dimension&lt;/th>
&lt;th scope="col">Docker in a Debian VM (Recommended)&lt;/th>
&lt;th scope="col">Docker in Unprivileged LXC (&lt;code>nesting=1&lt;/code>)&lt;/th>
&lt;th scope="col">Native Proxmox LXC (No Docker)&lt;/th>
&lt;th scope="col">Bare-Metal Linux + Docker&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Operational dimension">&lt;strong>Kernel &amp;amp; upgrade isolation&lt;/strong>&lt;/td>
&lt;td data-label="Docker in a Debian VM (Recommended)">&lt;strong>Full guest kernel.&lt;/strong> Immune to Proxmox host AppArmor, &lt;code>cgroup2&lt;/code>, or &lt;code>runc&lt;/code> regressions.&lt;/td>
&lt;td data-label="Docker in Unprivileged LXC (nesting=1)">&lt;strong>Shared host kernel.&lt;/strong> Host &lt;code>AppArmor&lt;/code> / &lt;code>lxc&lt;/code> package updates periodically break &lt;code>containerd&lt;/code> or &lt;code>sysctl&lt;/code> calls inside nested containers.&lt;/td>
&lt;td data-label="Native Proxmox LXC (No Docker)">&lt;strong>Shared host kernel&lt;/strong>, single userspace init (&lt;code>systemd&lt;/code>). Very stable for standard Debian packages.&lt;/td>
&lt;td data-label="Bare-Metal Linux &amp;#43; Docker">&lt;strong>Single bare-metal kernel.&lt;/strong> Stable, but zero hypervisor rollback if a bad kernel or driver fails to boot.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Operational dimension">&lt;strong>PBS backup speed &amp;amp; mechanism&lt;/strong>&lt;/td>
&lt;td data-label="Docker in a Debian VM (Recommended)">&lt;strong>QEMU dirty-bitmap block backup.&lt;/strong> Incremental nightly runs finish in &lt;strong>~5 seconds&lt;/strong> without scanning millions of files.&lt;/td>
&lt;td data-label="Docker in Unprivileged LXC (nesting=1)">&lt;strong>Filesystem &lt;code>pxar&lt;/code> archive walk.&lt;/strong> PBS must &lt;code>stat()&lt;/code> hundreds of thousands of tiny Docker &lt;code>overlay2&lt;/code> layer files every run.&lt;/td>
&lt;td data-label="Native Proxmox LXC (No Docker)">&lt;strong>Fast &lt;code>pxar&lt;/code> walk&lt;/strong> (low file count per single-app LXC).&lt;/td>
&lt;td data-label="Bare-Metal Linux &amp;#43; Docker">&lt;strong>DIY (&lt;code>restic&lt;/code> / &lt;code>borg&lt;/code> / scripts).&lt;/strong> Full host recovery requires OS reinstall + Compose redeploy.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Operational dimension">&lt;strong>ZFS storage behavior&lt;/strong>&lt;/td>
&lt;td data-label="Docker in a Debian VM (Recommended)">&lt;strong>Guest sees plain &lt;code>ext4&lt;/code> on a ZFS &lt;code>zvol&lt;/code>.&lt;/strong> Zero &lt;code>overlay2&lt;/code> driver edge cases on any ZFS version.&lt;/td>
&lt;td data-label="Docker in Unprivileged LXC (nesting=1)">Native &lt;code>overlay2&lt;/code> works on OpenZFS 2.2+ (PVE 8.1+/9), &lt;strong>broke on older ZFS pools&lt;/strong> (&lt;code>fuse-overlayfs&lt;/code> fallback), and churns dataset POSIX metadata.&lt;/td>
&lt;td data-label="Native Proxmox LXC (No Docker)">Native ZFS dataset (&lt;code>subvol&lt;/code>) per container with instant ZFS snapshots.&lt;/td>
&lt;td data-label="Bare-Metal Linux &amp;#43; Docker">Native &lt;code>overlay2&lt;/code> on &lt;code>ext4&lt;/code>/&lt;code>xfs&lt;/code> (or ZFS 2.2+).&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Operational dimension">&lt;strong>NFS / SMB NAS mounts&lt;/strong>&lt;/td>
&lt;td data-label="Docker in a Debian VM (Recommended)">&lt;strong>Standard &lt;code>/etc/fstab&lt;/code> kernel mounts&lt;/strong> inside the VM (&lt;code>nfs4&lt;/code>, &lt;code>cifs&lt;/code>) with zero host coupling.&lt;/td>
&lt;td data-label="Docker in Unprivileged LXC (nesting=1)">&lt;strong>Blocked in unprivileged LXC&lt;/strong> (&lt;code>Operation not permitted&lt;/code>). Requires mounting on the Proxmox host first and passing &lt;code>mp0:&lt;/code> bind mounts.&lt;/td>
&lt;td data-label="Native Proxmox LXC (No Docker)">Blocked in unprivileged LXC; uses host mount + &lt;code>mp0:&lt;/code> bind mount.&lt;/td>
&lt;td data-label="Bare-Metal Linux &amp;#43; Docker">Standard &lt;code>/etc/fstab&lt;/code> kernel mounts.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Operational dimension">&lt;strong>GPU access &amp;amp; multi-app sharing&lt;/strong>&lt;/td>
&lt;td data-label="Docker in a Debian VM (Recommended)">&lt;strong>PCIe &lt;code>VFIO&lt;/code> passthrough to the VM.&lt;/strong> Every Docker container &lt;em>inside&lt;/em> that VM shares the GPU cleanly via NVIDIA Toolkit or &lt;code>/dev/dri&lt;/code>.&lt;/td>
&lt;td data-label="Docker in Unprivileged LXC (nesting=1)">&lt;strong>Host &lt;code>/dev/dri&lt;/code> or &lt;code>/dev/nvidia*&lt;/code> bind mount.&lt;/strong> Allows sharing one GPU &lt;em>across multiple LXCs&lt;/em>, but locks guest NVIDIA libraries to the exact host driver version.&lt;/td>
&lt;td data-label="Native Proxmox LXC (No Docker)">Host &lt;code>/dev/dri&lt;/code> or &lt;code>/dev/nvidia*&lt;/code> bind mount (popular for standalone Plex/Jellyfin LXC when sharing iGPU across guests).&lt;/td>
&lt;td data-label="Bare-Metal Linux &amp;#43; Docker">Native host GPU access for all containers; no VM sharing.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Operational dimension">&lt;strong>Cluster live migration&lt;/strong>&lt;/td>
&lt;td data-label="Docker in a Debian VM (Recommended)">&lt;strong>Online live migration&lt;/strong> with zero container downtime.&lt;/td>
&lt;td data-label="Docker in Unprivileged LXC (nesting=1)">&lt;strong>Offline / restart migration only&lt;/strong> (containers stop and restart on target node).&lt;/td>
&lt;td data-label="Native Proxmox LXC (No Docker)">Offline / restart migration only.&lt;/td>
&lt;td data-label="Bare-Metal Linux &amp;#43; Docker">None.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="why-docker-in-lxc-bites-months-later-not-on-day-one">Why Docker-in-LXC bites months later (not on day one)&lt;/h2>
&lt;p>Docker inside an unprivileged LXC with &lt;code>features: nesting=1,keyctl=1&lt;/code> starts in two seconds and uses almost zero idle RAM. That initial success is why so many weekend tutorials recommend it.&lt;/p>
&lt;p>The pain arrives six months later during routine maintenance:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>AppArmor and &lt;code>procfs&lt;/code> collisions on host updates:&lt;/strong> Enabling &lt;code>nesting=1&lt;/code> exposes host &lt;code>procfs&lt;/code> and &lt;code>sysfs&lt;/code> paths so Docker can create nested namespaces, while unprivileged user-namespace mapping restricts kernel calls. Minor updates to &lt;code>pve-container&lt;/code>, &lt;code>lxc-pve&lt;/code>, or Docker&amp;rsquo;s bundled &lt;code>containerd.io&lt;/code> have repeatedly triggered &lt;code>apparmor=&amp;quot;DENIED&amp;quot;&lt;/code> or &lt;code>permission denied: sysctl net.ipv4.ip_unprivileged_port_start&lt;/code> failures that prevent every container from starting after a routine &lt;code>apt full-upgrade&lt;/code>.&lt;/li>
&lt;li>&lt;strong>Kernel NFS and CIFS mounts fail inside unprivileged LXC:&lt;/strong> Stacks like Jellyfin, Immich, Paperless-ngx, and the &lt;code>*arr&lt;/code> suite frequently mount NAS shares. Inside an unprivileged LXC, &lt;code>mount -t nfs&lt;/code> fails immediately. You either weaken isolation by creating a privileged container (which Proxmox warns against outside strictly trusted testing) or maintain brittle &lt;code>/etc/fstab&lt;/code> mounts on the Proxmox hypervisor itself. Inside a Debian VM, &lt;code>/etc/fstab&lt;/code> or Docker NFS volumes just work.&lt;/li>
&lt;li>&lt;strong>Backup metadata amplification:&lt;/strong> Every pulled Docker image unpacks thousands of tiny files across &lt;code>overlay2&lt;/code> lowerdirs. When Proxmox Backup Server backs up an LXC container, &lt;code>proxmox-backup-client&lt;/code> walks the entire filesystem tree to build a &lt;code>.pxar&lt;/code> archive. On a QEMU VM, PBS reads only the dirty 4 MiB extents recorded by the hypervisor&amp;rsquo;s block layer since the last run.&lt;/li>
&lt;/ol>
&lt;h2 id="compose-data-location--proxmox-backup-server-worksheet">Compose data-location &amp;amp; Proxmox Backup Server worksheet&lt;/h2>
&lt;p>A backup only counts if it captures your actual state—and plenty of Docker users accidentally store volumes somewhere Proxmox skips! As Proxmox staff explain in the &lt;a href="https://forum.proxmox.com/threads/backing-up-docker-volumes-in-lxc-proxmox-container.139411/" rel="noopener">Proxmox forum thread on Docker volume backups (&lt;code>139411&lt;/code>)&lt;/a>, backup inclusion depends on which virtual disk or mount point holds &lt;code>/var/lib/docker&lt;/code> and your bind mounts:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Data type&lt;/th>
&lt;th scope="col">Recommended path inside Debian Docker VM&lt;/th>
&lt;th scope="col">Included in PBS VM snapshot?&lt;/th>
&lt;th scope="col">Restore &amp;amp; consistency rule&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Data type">&lt;strong>Compose YAML &amp;amp; &lt;code>.env&lt;/code> files&lt;/strong>&lt;/td>
&lt;td data-label="Recommended path inside Debian Docker VM">&lt;code>/opt/stacks/&amp;lt;stack&amp;gt;/compose.yaml&lt;/code> on &lt;code>scsi0&lt;/code>&lt;/td>
&lt;td data-label="Included in PBS VM snapshot?">&lt;strong>Yes&lt;/strong>&lt;/td>
&lt;td data-label="Restore &amp;amp; consistency rule">Keep all stack definitions under one &lt;code>/opt/stacks&lt;/code> tree so a single VM restore recovers config and containers together.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Data type">&lt;strong>Docker named volumes &amp;amp; images&lt;/strong>&lt;/td>
&lt;td data-label="Recommended path inside Debian Docker VM">&lt;code>/var/lib/docker/volumes/&lt;/code> on &lt;code>scsi0&lt;/code>&lt;/td>
&lt;td data-label="Included in PBS VM snapshot?">&lt;strong>Yes&lt;/strong>&lt;/td>
&lt;td data-label="Restore &amp;amp; consistency rule">Captured automatically on the VM disk. (Warning: in an LXC, if you move &lt;code>/var/lib/docker&lt;/code> onto a separate &lt;code>mp0:&lt;/code> mount point without ticking &lt;strong>&lt;code>Backup&lt;/code> (&lt;code>backup=1&lt;/code>)&lt;/strong>, PBS skips it completely!)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Data type">&lt;strong>Local SSD app data bind mounts&lt;/strong>&lt;/td>
&lt;td data-label="Recommended path inside Debian Docker VM">&lt;code>/srv/appdata/&amp;lt;stack&amp;gt;&lt;/code> on &lt;code>scsi0&lt;/code> (or &lt;code>scsi1&lt;/code> with Backup enabled)&lt;/td>
&lt;td data-label="Included in PBS VM snapshot?">&lt;strong>Yes&lt;/strong>&lt;/td>
&lt;td data-label="Restore &amp;amp; consistency rule">Keep SQLite databases (Jellyfin, Vaultwarden, Uptime Kuma) on local &lt;code>ext4&lt;/code> virtual disks, never over NFS/SMB.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Data type">&lt;strong>Transactional SQL databases&lt;/strong> (Postgres / MariaDB)&lt;/td>
&lt;td data-label="Recommended path inside Debian Docker VM">Local disk + &lt;code>/srv/backups/sql/&lt;/code> dump cron&lt;/td>
&lt;td data-label="Included in PBS VM snapshot?">&lt;strong>Yes (&lt;code>fsfreeze&lt;/code> + dump)&lt;/strong>&lt;/td>
&lt;td data-label="Restore &amp;amp; consistency rule">Enable &lt;strong>&lt;code>qemu-guest-agent&lt;/code>&lt;/strong> so PBS runs &lt;code>fsfreeze&lt;/code> before snapshotting, AND run a nightly &lt;code>pg_dumpall&lt;/code> into &lt;code>/srv/backups/sql/&lt;/code> on the backed-up VM disk.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Data type">&lt;strong>Multi-terabyte NAS media shares&lt;/strong>&lt;/td>
&lt;td data-label="Recommended path inside Debian Docker VM">&lt;code>/mnt/nas/media&lt;/code> mounted via NFSv4 / SMB&lt;/td>
&lt;td data-label="Included in PBS VM snapshot?">&lt;strong>No (by design)&lt;/strong>&lt;/td>
&lt;td data-label="Restore &amp;amp; consistency rule">Remote network mounts are never swept into VM block backups, keeping your nightly PBS snapshots small and fast while your NAS protects bulk media separately.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Always verify disaster recovery once: restore yesterday&amp;rsquo;s PBS VM snapshot to a spare VM ID (such as &lt;code>901&lt;/code>) with its network NIC temporarily disconnected, boot into the console, and confirm &lt;code>docker compose ps&lt;/code> brings every database and volume up cleanly.&lt;/p>
&lt;h2 id="setting-up-the-debian-13-docker-vm-cleanly">Setting up the Debian 13 Docker VM cleanly&lt;/h2>
&lt;p>Create one QEMU VM in Proxmox (&lt;code>VirtIO SCSI single&lt;/code>, &lt;code>scsi0&lt;/code> with &lt;code>Discard&lt;/code> and &lt;code>SSD emulation&lt;/code> enabled, &lt;code>CPU type: host&lt;/code>, &lt;code>QEMU Guest Agent: Enabled&lt;/code>, and 4–16 GB fixed RAM depending on your &lt;a href="https://techfuelhq.com/tools/docker-ram-planner/">Docker RAM planner&lt;/a> estimate—avoid QEMU memory ballooning on database-heavy Docker hosts so Linux page cache behaves predictably).&lt;/p>
&lt;p>Inside the fresh Debian 13 (&lt;code>trixie&lt;/code>) VM, install the guest agent and official Docker Engine packages per &lt;a href="https://docs.docker.com/engine/install/debian/" rel="noopener">Docker&amp;rsquo;s Debian installation docs&lt;/a>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>sudo apt update
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo apt install -y qemu-guest-agent ca-certificates curl
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo systemctl enable --now qemu-guest-agent
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Add Docker&amp;#39;s official GPG key and deb822 repository&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo install -m &lt;span style="color:#ae81ff">0755&lt;/span> -d /etc/apt/keyrings
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo curl -fsSL https://download.docker.com/linux/debian/gpg -o /etc/apt/keyrings/docker.asc
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo chmod a+r /etc/apt/keyrings/docker.asc
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo tee /etc/apt/sources.list.d/docker.sources &amp;gt;/dev/null &lt;span style="color:#e6db74">&amp;lt;&amp;lt;EOF
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">Types: deb
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">URIs: https://download.docker.com/linux/debian
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">Suites: $(. /etc/os-release &amp;amp;&amp;amp; echo &amp;#34;$VERSION_CODENAME&amp;#34;)
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">Components: stable
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">Architectures: $(dpkg --print-architecture)
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">Signed-By: /etc/apt/keyrings/docker.asc
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">EOF&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo apt update
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo apt install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo docker run --rm hello-world
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Two important security notes come straight from Docker&amp;rsquo;s Debian documentation. Published container ports (&lt;code>ports: - &amp;quot;8080:80&amp;quot;&lt;/code>) manipulate &lt;code>nftables&lt;/code>/&lt;code>iptables&lt;/code> directly and bypass &lt;code>ufw&lt;/code> host firewall rules unless bound to &lt;code>127.0.0.1:8080:80&lt;/code> behind a local reverse proxy, and wiring secrets or &lt;code>.env&lt;/code> interpolation properly requires distinguishing &lt;code>.env&lt;/code> from &lt;code>env_file:&lt;/code> as detailed in our &lt;a href="https://techfuelhq.com/tutorials/docker-compose-environment-variables-2026/">Docker Compose environment variables guide&lt;/a>.&lt;/p>
&lt;h2 id="what-about-proxmox-ve-91-native-oci-image-support">What about Proxmox VE 9.1+ native OCI image support?&lt;/h2>
&lt;p>Starting in Proxmox VE 9.1, you can pull OCI container images directly into LXC templates. Per the &lt;a href="https://pve.proxmox.com/wiki/Roadmap" rel="noopener">Proxmox VE Roadmap&lt;/a> and &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pct.html" rel="noopener">container admin guide&lt;/a>, running &lt;em>application&lt;/em> containers via OCI is explicitly marked a &lt;strong>technology preview&lt;/strong>.&lt;/p>
&lt;p>It does not parse &lt;code>compose.yaml&lt;/code>, create isolated per-stack Docker bridge networks, or orchestrate multi-container dependencies (such as Immich&amp;rsquo;s four linked server, ML, Valkey, and VectorChord Postgres services). Treat native OCI in Proxmox VE 9 as an interesting way to spin up a single stateless utility container, not a replacement for your Docker Compose VM.&lt;/p>
&lt;h2 id="decision-checklist">Decision checklist&lt;/h2>
&lt;p>Run every workload through four rules:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Appliances with their own OS or kernel (&lt;code>OPNsense&lt;/code>, &lt;code>Home Assistant OS&lt;/code>, &lt;code>Windows&lt;/code>):&lt;/strong> Dedicated Proxmox QEMU VM per appliance.&lt;/li>
&lt;li>&lt;strong>Multi-container stacks or frequent upstream releases (&lt;code>Immich&lt;/code>, &lt;code>Paperless-ngx&lt;/code>, &lt;code>Nextcloud&lt;/code>, &lt;code>Jellyfin&lt;/code>, &lt;code>*arr&lt;/code>):&lt;/strong> Put them in your &lt;strong>Debian Docker Compose VM&lt;/strong> backed up nightly to PBS. Pass your discrete GPU into this VM via &lt;a href="https://techfuelhq.com/tutorials/gpu-passthrough-proxmox-vm-2026/">PCIe VFIO passthrough&lt;/a> if multiple containers need NVENC or CUDA.&lt;/li>
&lt;li>&lt;strong>Core LAN plumbing that must stay up while rebooting the Docker VM (&lt;code>Pi-hole&lt;/code> / &lt;code>AdGuard Home&lt;/code>, &lt;code>Tailscale&lt;/code> subnet router, &lt;code>UPS nut-server&lt;/code>):&lt;/strong> Native Proxmox LXC container (one tiny Debian LXC per service, zero Docker overhead, sub-second boot).&lt;/li>
&lt;li>&lt;strong>Need one Intel Quick Sync iGPU shared between two separate Proxmox guests simultaneously?&lt;/strong> Either co-locate all media/ML apps inside the single Docker VM, or use &lt;code>/dev/dri&lt;/code> bind mounts across two native LXCs knowing they share the host kernel driver.&lt;/li>
&lt;/ol>
&lt;p>Size your combined VM and LXC memory budget in the &lt;a href="https://techfuelhq.com/tools/proxmox-capacity-planner/">Proxmox capacity planner&lt;/a> before allocating RAM, and keep Proxmox doing hardware virtualization while Docker handles application stacks.&lt;/p></description></item><item><title>Tailscale vs WireGuard (2026): NAT, DERP &amp; Speed</title><link>https://techfuelhq.com/networking/tailscale-vs-wireguard-2026/</link><pubDate>Wed, 01 Jul 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/networking/tailscale-vs-wireguard-2026/</guid><atom:updated>2026-11-14T10:50:00Z</atom:updated><description>&lt;p>Most &amp;ldquo;Tailscale vs WireGuard&amp;rdquo; articles treat them like rival encryption protocols and wave away performance as identical. Both claims miss the mark.&lt;/p>
&lt;p>Tailscale uses the WireGuard protocol for its encrypted data plane (&lt;a href="https://tailscale.com/compare/wireguard" rel="noopener">Tailscale&amp;rsquo;s technical comparison&lt;/a>). What differs is how packets cross hostile NATs and whether WireGuard runs inside your OS kernel with static peer endpoints or inside &lt;code>tailscaled&lt;/code> userspace with STUN hole-punching and TCP relays. Topology decides the winner. In my own homelab, I map the WAN path between client and server first. For hands-on setup commands, see our guides to &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale remote access&lt;/a> and &lt;a href="https://techfuelhq.com/tutorials/wireguard-self-hosted-vpn-proxmox-2026/">self-hosted WireGuard on Proxmox&lt;/a>.&lt;/p>
&lt;h2 id="topology--nat-traversal-decision-table">Topology &amp;amp; NAT-traversal decision table&lt;/h2>
&lt;p>Before comparing setup screens, find your network path in the left column. Network topology dictates whether raw WireGuard can connect at all, and whether Tailscale runs at direct UDP speed or drops down to a TCP relay:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Network topology between client &amp;amp; homelab&lt;/th>
&lt;th scope="col">Raw Kernel WireGuard (&lt;code>wireguard.ko&lt;/code>)&lt;/th>
&lt;th scope="col">Tailscale (&lt;code>tailscaled&lt;/code> + Control Plane)&lt;/th>
&lt;th scope="col">Recommended pick&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Network topology between client &amp;amp; homelab">&lt;strong>Home has public IPv4 (static or DDNS) + &lt;code>51820/udp&lt;/code> forwarded&lt;/strong> (client on LTE or home Wi-Fi)&lt;/td>
&lt;td data-label="Raw Kernel WireGuard (wireguard.ko)">&lt;strong>Direct UDP.&lt;/strong> Lowest CPU overhead, &lt;code>1420&lt;/code> MTU, instant roaming handoff, zero third-party server.&lt;/td>
&lt;td data-label="Tailscale (tailscaled &amp;#43; Control Plane)">&lt;strong>Direct UDP&lt;/strong> after coordination check-in (&lt;code>1280&lt;/code> MTU userspace &lt;code>wireguard-go&lt;/code>).&lt;/td>
&lt;td data-label="Recommended pick">&lt;strong>Raw WireGuard&lt;/strong> for 1–5 devices &amp;amp; total independence; &lt;strong>Tailscale&lt;/strong> for 10+ devices or family sharing.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Network topology between client &amp;amp; homelab">&lt;strong>Home behind IPv4 CGNAT, client has reachable IPv6&lt;/strong>&lt;/td>
&lt;td data-label="Raw Kernel WireGuard (wireguard.ko)">&lt;strong>Direct UDP over IPv6&lt;/strong> if &lt;em>every&lt;/em> client network (including cellular/coffee-shop Wi-Fi) provides working IPv6. Fails immediately on IPv4-only guest Wi-Fi!&lt;/td>
&lt;td data-label="Tailscale (tailscaled &amp;#43; Control Plane)">&lt;strong>Direct UDP&lt;/strong> over IPv6 or hole-punched IPv4 automatically.&lt;/td>
&lt;td data-label="Recommended pick">&lt;strong>Tailscale&lt;/strong> (unless you control both networks and guarantee dual-stack IPv6 everywhere).&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Network topology between client &amp;amp; homelab">&lt;strong>Home behind IPv4 CGNAT (Starlink, 5G Home, apartment fiber) + client on standard cone NAT&lt;/strong>&lt;/td>
&lt;td data-label="Raw Kernel WireGuard (wireguard.ko)">&lt;strong>Cannot connect&lt;/strong> without renting a public VPS and building a hub-and-spoke WireGuard bounce tunnel yourself.&lt;/td>
&lt;td data-label="Tailscale (tailscaled &amp;#43; Control Plane)">&lt;strong>Direct P2P UDP&lt;/strong> via &lt;a href="https://tailscale.com/blog/how-nat-traversal-works" rel="noopener">STUN + coordinated UDP hole-punching&lt;/a> across NAT state tables (zero open router ports).&lt;/td>
&lt;td data-label="Recommended pick">&lt;strong>Tailscale&lt;/strong> wins decisively.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Network topology between client &amp;amp; homelab">&lt;strong>Both sides behind strict symmetric NAT, or hotel / corporate firewall blocking all UDP&lt;/strong>&lt;/td>
&lt;td data-label="Raw Kernel WireGuard (wireguard.ko)">&lt;strong>Completely blocked&lt;/strong> (UDP &lt;code>51820&lt;/code> dropped; WireGuard intentionally has no TCP transport mode).&lt;/td>
&lt;td data-label="Tailscale (tailscaled &amp;#43; Control Plane)">&lt;strong>Automatic fallback to &lt;a href="https://tailscale.com/kb/1232/derp-servers" rel="noopener">&lt;code>DERP&lt;/code> TCP-443 relay&lt;/a>.&lt;/strong> Connects reliably over TLS &lt;code>443&lt;/code>, with added relay hop latency and lower throughput.&lt;/td>
&lt;td data-label="Recommended pick">&lt;strong>Tailscale&lt;/strong> (only option that connects without external TCP-tunnel wrappers).&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Network topology between client &amp;amp; homelab">&lt;strong>Site-to-site LAN bridge between two routers with public IPs&lt;/strong>&lt;/td>
&lt;td data-label="Raw Kernel WireGuard (wireguard.ko)">&lt;strong>Line-rate kernel tunnel&lt;/strong> directly on OPNsense / Linux routers; survives SaaS outages indefinitely.&lt;/td>
&lt;td data-label="Tailscale (tailscaled &amp;#43; Control Plane)">Works via subnet routers (&lt;code>--advertise-routes&lt;/code>), adds userspace daemon and account dependency.&lt;/td>
&lt;td data-label="Recommended pick">&lt;strong>Raw WireGuard&lt;/strong> on the routers.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="kernel-wireguard-vs-tailscaled-userspace--derp-why-speeds-diverge">Kernel WireGuard vs &lt;code>tailscaled&lt;/code> userspace + &lt;code>DERP&lt;/code>: why speeds diverge&lt;/h2>
&lt;p>Saying &amp;ldquo;Tailscale is WireGuard so speed is identical&amp;rdquo; hides three real transport differences you can measure on your own hardware:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>In-kernel &lt;code>wireguard.ko&lt;/code> vs userspace &lt;code>wireguard-go&lt;/code>:&lt;/strong> Since Linux 5.6, native WireGuard lives inside the kernel networking stack. Packets move from NIC ring buffers through ChaCha20-Poly1305 encryption with zero userspace context switches and a standard &lt;code>1420&lt;/code> byte MTU. Tailscale runs &lt;code>tailscaled&lt;/code> in userspace (&lt;code>1280&lt;/code> byte MTU) so it can handle per-packet ACLs, &lt;a href="https://tailscale.com/kb/1081/magicdns" rel="noopener">MagicDNS (&lt;code>100.100.100.100&lt;/code>)&lt;/a>, and dynamic path switching. On modern Linux kernels (&lt;code>6.2+&lt;/code>), Tailscale leverages &lt;strong>UDP Generic Segmentation Offload (&lt;code>GSO&lt;/code>) and Generic Receive Offload (&lt;code>GRO&lt;/code>)&lt;/strong> to push multi-gigabit direct speeds, though raw kernel WireGuard still uses measurably less CPU and mobile battery per gigabyte moved.&lt;/li>
&lt;li>&lt;strong>Direct UDP vs &lt;code>DERP&lt;/code> TCP-443 relays:&lt;/strong> When a hotel firewall blocks UDP or both sides sit behind port-randomizing symmetric NATs (for example certain cellular carriers talking to certain enterprise firewalls), Tailscale wraps encrypted WireGuard packets inside HTTPS-like streams over TCP port &lt;code>443&lt;/code> through regional &lt;a href="https://tailscale.com/kb/1232/derp-servers" rel="noopener">DERP relay servers&lt;/a>. DERP saves the day for SSH, Home Assistant, and web dashboards when raw WireGuard is dead in the water, yet TCP-over-tunnel congestion + an out-of-state relay hop cuts SMB file-copy and 4K Jellyfin streaming throughput sharply compared with a direct link.&lt;/li>
&lt;li>&lt;strong>Verify your active path in two seconds:&lt;/strong> Never guess why a Tailscale transfer feels slow. Run two built-in commands from your terminal:&lt;/li>
&lt;/ol>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Check every peer&amp;#39;s active transport (&amp;#39;direct &amp;lt;ip&amp;gt;:&amp;lt;port&amp;gt;&amp;#39; vs &amp;#39;relay &amp;#34;ord&amp;#34;&amp;#39;)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>tailscale status
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Watch real-time UDP hole-punch upgrade from DERP to direct P2P latency&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>tailscale ping homelab-nas
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>If &lt;code>tailscale ping&lt;/code> stays stuck on &lt;code>via DERP(...)&lt;/code> across ten packets when you control the home router, enabling &lt;strong>UPnP / NAT-PMP&lt;/strong> on your gateway or opening UDP port &lt;code>41641&lt;/code> to your primary subnet router lets Tailscale upgrade stubborn symmetric-NAT peers back to direct WireGuard speed.&lt;/p>
&lt;h2 id="subnet-routers-magicdns-and-exit-nodes-vs-manual-wg0conf">Subnet routers, MagicDNS, and exit nodes vs manual &lt;code>wg0.conf&lt;/code>&lt;/h2>
&lt;p>Raw WireGuard deliberately stops at Layer 3 point-to-point packet crypto. Adding a new phone means running &lt;code>wg genkey | tee privkey | wg pubkey&lt;/code>, assigning the next &lt;code>/32&lt;/code> IP by hand, appending a &lt;code>[Peer]&lt;/code> block on the server, and scanning a QR code on the client. To reach twenty LAN devices that cannot install VPN software (IPMI BMC ports, network printers, NAS shares, Apple TV), you enable &lt;code>net.ipv4.ip_forward=1&lt;/code> and maintain &lt;code>PostUp&lt;/code> / &lt;code>PostDown&lt;/code> &lt;code>nftables&lt;/code> or &lt;code>iptables&lt;/code> NAT/forwarding rules yourself.&lt;/p>
&lt;p>Tailscale turns those exact chores into single commands:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Subnet Routers (&lt;code>tailscale up --advertise-routes=192.168.1.0/24&lt;/code>):&lt;/strong> One tiny Linux VM or Proxmox LXC bridges your entire home subnet onto your tailnet without installing Tailscale on every appliance.&lt;/li>
&lt;li>&lt;strong>MagicDNS (&lt;code>100.100.100.100&lt;/code>):&lt;/strong> Automatically resolves stable &lt;code>100.x.y.z&lt;/code> tailnet names (&lt;code>proxmox.tail-scale.ts.net&lt;/code>) identically on home Wi-Fi, LTE, or airport Wi-Fi, and integrates split-DNS forwarding to internal Pi-hole or AdGuard Home servers.&lt;/li>
&lt;li>&lt;strong>Declarative ACLs &amp;amp; Tailscale SSH:&lt;/strong> Replace per-host &lt;code>iptables&lt;/code> chains and static SSH key distribution with one audited JSON/HuJSON policy file.&lt;/li>
&lt;/ul>
&lt;p>For public Wi-Fi protection when traveling, check whether routing through your own home fiber makes more sense than paying a third party. &lt;a href="https://tailscale.com/docs/features/exit-nodes" rel="noopener">Tailscale&amp;rsquo;s exit-node feature&lt;/a> and &lt;a href="https://www.wireguard.com/quickstart/" rel="noopener">WireGuard&amp;rsquo;s &lt;code>0.0.0.0/0&lt;/code> full-tunnel peer config&lt;/a> both send DNS and web traffic through your chosen server. Configure full-tunnel routing deliberately when you want it rather than leaving it on permanently. The encrypted tunnel protects packets only as far as that exit, whose operator and internet provider remain part of the trust decision; websites beyond that exit simply see your home or VPS public IP.&lt;/p>
&lt;h2 id="trust-boundary-control-plane-independence-and-headscale">Trust boundary, control-plane independence, and Headscale&lt;/h2>
&lt;p>Encryption strength does not separate them because both run WireGuard cryptography end to end. What separates them is &lt;strong>control-plane sovereignty&lt;/strong>.&lt;/p>
&lt;p>With self-hosted WireGuard, zero external infrastructure participates. No SaaS outage, OAuth identity-provider lock, or coordination-server policy change can ever touch your tunnel. Your public keys, peer IP mappings, and connection timestamps exist strictly inside &lt;code>/etc/wireguard/wg0.conf&lt;/code> on machines you own.&lt;/p>
&lt;p>With standard Tailscale, your payload traffic remains end-to-end encrypted between your devices, while Tailscale Inc.&amp;rsquo;s proprietary coordination plane distributes public keys, pushes ACL rules, and logs which devices belong to your tailnet. Existing direct tunnels usually stay up through brief control-plane hiccups, yet onboarding a new machine or rotating expired node keys requires reaching &lt;code>controlplane.tailscale.com&lt;/code>.&lt;/p>
&lt;p>If you want Tailscale&amp;rsquo;s NAT traversal, MagicDNS, and polished iOS/Android clients without relying on Tailscale&amp;rsquo;s cloud control plane, self-host &lt;strong>&lt;a href="https://techfuelhq.com/networking/headscale-self-hosted-tailscale-2026/">Headscale&lt;/a>&lt;/strong> (or compare &lt;a href="https://techfuelhq.com/networking/netbird-vs-tailscale-2026/">NetBird&lt;/a> and &lt;a href="https://techfuelhq.com/networking/zerotier-vs-tailscale-2026/">ZeroTier&lt;/a>) on a small VPS you control.&lt;/p>
&lt;h2 id="practical-homelab-verdict-pick-one-or-layer-both">Practical homelab verdict: pick one or layer both&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>Deploy raw kernel WireGuard&lt;/strong> when your home router has a public IPv4 address (static or DDNS) where you can forward one UDP port, you manage a handful of personal devices, and you want peak multi-gigabit kernel efficiency with zero external account dependencies.&lt;/li>
&lt;li>&lt;strong>Deploy Tailscale&lt;/strong> when your ISP puts you behind CGNAT (Starlink, T-Mobile/Verizon 5G Home, apartment fiber), you roam across UDP-hostile hotel or campus networks where &lt;code>DERP&lt;/code> TCP-443 fallback keeps you connected, or you share specific services (&lt;code>Jellyfin&lt;/code>, &lt;code>Immich&lt;/code>) with family members without opening router ports.&lt;/li>
&lt;li>&lt;strong>Run the hybrid homelab setup I recommend most:&lt;/strong> Terminate raw kernel WireGuard on your OPNsense or router firewall as your primary zero-dependency tunnel, and keep one lightweight Tailscale subnet-router container running inside your lab as a zero-port backup door. When a hotel network blocks UDP &lt;code>51820&lt;/code> or your residential WAN IP changes mid-trip, your backup door still opens in one click.&lt;/li>
&lt;/ul></description></item><item><title>DisplayPort &amp; HDMI Bandwidth Calculator (2026)</title><link>https://techfuelhq.com/tools/displayport-hdmi-bandwidth-calculator/</link><pubDate>Mon, 29 Jun 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tools/displayport-hdmi-bandwidth-calculator/</guid><atom:updated>2026-11-14T10:50:00Z</atom:updated><description>&lt;p>Box numbers lie. Every display standard prints its raw physical signaling rate on the retail carton while spending part of that link budget on line-coding synchronization bits before a single pixel crosses the wire.&lt;/p>
&lt;p>I built this calculator around effective video payload bandwidth, not marketing link rates. Pick your resolution, refresh rate, color depth, and chroma format above to check whether a mode fits uncompressed, triggers VESA Display Stream Compression (&lt;code>DSC 1.2a&lt;/code>), or exceeds HDMI 2.0, DisplayPort 1.4 (&lt;code>HBR3&lt;/code>), HDMI 2.1 (&lt;code>FRL6&lt;/code>), and all three DisplayPort 2.1 &lt;code>UHBR&lt;/code> tiers. Using an ultrawide panel? Check exact dimensions in our &lt;a href="https://techfuelhq.com/tools/aspect-ratio-calculator/">aspect ratio calculator&lt;/a> and &lt;a href="https://techfuelhq.com/tools/ppi-calculator/">PPI calculator&lt;/a>.&lt;/p>
&lt;h2 id="raw-link-rate-vs-effective-payload-bandwidth-reference-table">Raw link rate vs effective payload bandwidth reference table&lt;/h2>
&lt;p>Encoding overhead eats raw bandwidth. Older &lt;code>8b/10b&lt;/code> links (&lt;code>HDMI 2.0&lt;/code> and &lt;code>DP 1.4&lt;/code>) spend 20% of every symbol on clock recovery. &lt;code>HDMI 2.1&lt;/code> Fixed Rate Link (&lt;code>FRL&lt;/code>) switches to &lt;code>16b/18b&lt;/code> coding (11.1% overhead), and &lt;code>DisplayPort 2.1 UHBR&lt;/code> moves to &lt;code>128b/132b&lt;/code> coding plus framing/FEC (roughly 3.3% total overhead):&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Standard &amp;amp; signaling tier&lt;/th>
&lt;th scope="col">Lanes × rate&lt;/th>
&lt;th scope="col" style="text-align: right">Raw link rate&lt;/th>
&lt;th scope="col">Encoding scheme&lt;/th>
&lt;th scope="col" style="text-align: right">Effective payload ceiling&lt;/th>
&lt;th scope="col">Supports DSC?&lt;/th>
&lt;th scope="col">Required certified cable&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Standard &amp;amp; signaling tier">&lt;strong>HDMI 2.0&lt;/strong> (&lt;code>TMDS&lt;/code>)&lt;/td>
&lt;td data-label="Lanes × rate">3 × 6.0 Gbps&lt;/td>
&lt;td style="text-align: right" data-label="Raw link rate">18.00 Gbps&lt;/td>
&lt;td data-label="Encoding scheme">&lt;code>8b/10b&lt;/code> (-20%)&lt;/td>
&lt;td style="text-align: right" data-label="Effective payload ceiling">&lt;strong>14.40 Gbps&lt;/strong>&lt;/td>
&lt;td data-label="Supports DSC?">No&lt;/td>
&lt;td data-label="Required certified cable">Premium High Speed HDMI (&lt;code>18G&lt;/code>)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Standard &amp;amp; signaling tier">&lt;strong>DisplayPort 1.4a&lt;/strong> (&lt;code>HBR3&lt;/code>)&lt;/td>
&lt;td data-label="Lanes × rate">4 × 8.1 Gbps&lt;/td>
&lt;td style="text-align: right" data-label="Raw link rate">32.40 Gbps&lt;/td>
&lt;td data-label="Encoding scheme">&lt;code>8b/10b&lt;/code> (-20%)&lt;/td>
&lt;td style="text-align: right" data-label="Effective payload ceiling">&lt;strong>25.92 Gbps&lt;/strong>&lt;/td>
&lt;td data-label="Supports DSC?">Yes (&lt;code>DSC 1.2a&lt;/code>)&lt;/td>
&lt;td data-label="Required certified cable">VESA HBR3 Certified DP&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Standard &amp;amp; signaling tier">&lt;strong>HDMI 2.1&lt;/strong> (&lt;code>FRL6&lt;/code> full port)&lt;/td>
&lt;td data-label="Lanes × rate">4 × 12.0 Gbps&lt;/td>
&lt;td style="text-align: right" data-label="Raw link rate">48.00 Gbps&lt;/td>
&lt;td data-label="Encoding scheme">&lt;code>16b/18b&lt;/code> (-11.1%)&lt;/td>
&lt;td style="text-align: right" data-label="Effective payload ceiling">&lt;strong>42.67 Gbps&lt;/strong> (&lt;code>42.60&lt;/code> in tool)&lt;/td>
&lt;td data-label="Supports DSC?">Yes (&lt;code>DSC 1.2a&lt;/code>)&lt;/td>
&lt;td data-label="Required certified cable">Ultra High Speed HDMI (&lt;code>48G&lt;/code>)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Standard &amp;amp; signaling tier">&lt;strong>DisplayPort 2.1 &lt;code>UHBR10&lt;/code>&lt;/strong>&lt;/td>
&lt;td data-label="Lanes × rate">4 × 10.0 Gbps&lt;/td>
&lt;td style="text-align: right" data-label="Raw link rate">40.00 Gbps&lt;/td>
&lt;td data-label="Encoding scheme">&lt;code>128b/132b&lt;/code> + FEC&lt;/td>
&lt;td style="text-align: right" data-label="Effective payload ceiling">&lt;strong>38.69 Gbps&lt;/strong>&lt;/td>
&lt;td data-label="Supports DSC?">Yes (&lt;code>DSC 1.2a&lt;/code>)&lt;/td>
&lt;td data-label="Required certified cable">VESA &lt;code>DP40&lt;/code> or &lt;code>DP80&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Standard &amp;amp; signaling tier">&lt;strong>DisplayPort 2.1 &lt;code>UHBR13.5&lt;/code>&lt;/strong>&lt;/td>
&lt;td data-label="Lanes × rate">4 × 13.5 Gbps&lt;/td>
&lt;td style="text-align: right" data-label="Raw link rate">54.00 Gbps&lt;/td>
&lt;td data-label="Encoding scheme">&lt;code>128b/132b&lt;/code> + FEC&lt;/td>
&lt;td style="text-align: right" data-label="Effective payload ceiling">&lt;strong>52.22 Gbps&lt;/strong>&lt;/td>
&lt;td data-label="Supports DSC?">Yes (&lt;code>DSC 1.2a&lt;/code>)&lt;/td>
&lt;td data-label="Required certified cable">VESA &lt;code>DP54&lt;/code> or &lt;code>DP80&lt;/code>&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Standard &amp;amp; signaling tier">&lt;strong>DisplayPort 2.1 &lt;code>UHBR20&lt;/code>&lt;/strong>&lt;/td>
&lt;td data-label="Lanes × rate">4 × 20.0 Gbps&lt;/td>
&lt;td style="text-align: right" data-label="Raw link rate">80.00 Gbps&lt;/td>
&lt;td data-label="Encoding scheme">&lt;code>128b/132b&lt;/code> + FEC&lt;/td>
&lt;td style="text-align: right" data-label="Effective payload ceiling">&lt;strong>77.37 Gbps&lt;/strong>&lt;/td>
&lt;td data-label="Supports DSC?">Yes (&lt;code>DSC 1.2a&lt;/code>)&lt;/td>
&lt;td data-label="Required certified cable">VESA &lt;code>DP80&lt;/code>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Two traps hide inside that table.&lt;/p>
&lt;p>First, read the &lt;code>UHBR&lt;/code> suffix on every &amp;ldquo;DisplayPort 2.1&amp;rdquo; monitor and GPU. VESA permits manufacturers to market a port as DisplayPort 2.1 even when it tops out at &lt;code>UHBR10&lt;/code> (&lt;code>38.69 Gbps&lt;/code>) or &lt;code>UHBR13.5&lt;/code> (&lt;code>52.22 Gbps&lt;/code>) rather than full &lt;code>UHBR20&lt;/code> (&lt;code>77.37 Gbps&lt;/code>). Labels mislead buyers constantly. A monitor wired for &lt;code>DP 2.1 UHBR10&lt;/code> carries less uncompressed payload capacity than a full &lt;code>48 Gbps&lt;/code> HDMI 2.1 port (&lt;code>42.67 Gbps&lt;/code>), and some TVs or laptop HDMI 2.1 ports cap FRL at &lt;code>24 Gbps&lt;/code> (&lt;code>FRL3&lt;/code>) or &lt;code>40 Gbps&lt;/code> (&lt;code>FRL5&lt;/code>).&lt;/p>
&lt;p>Second, check &lt;code>4:2:2&lt;/code> subsampling carefully. Cutting chroma to &lt;code>4:2:2&lt;/code> reduces raw color samples to two-thirds of &lt;code>4:4:4&lt;/code>, yet HDMI and DisplayPort pack &lt;code>4:2:2&lt;/code> pixel containers differently on the wire and not every GPU/OSD combination exposes every bit depth in &lt;code>4:2:2&lt;/code>. This tool marks &lt;code>4:2:2&lt;/code> rows Verify on purpose so you check both device manuals before relying on subsampling.&lt;/p>
&lt;h2 id="how-cvt-rbv2-blanking--dsc-12a-31-triggers-work">How &lt;code>CVT-RBv2&lt;/code> blanking &amp;amp; &lt;code>DSC 1.2a&lt;/code> 3:1 triggers work&lt;/h2>
&lt;p>Active pixels are only part of the frame. Multiplying &lt;code>width × height × Hz × bits_per_pixel&lt;/code> always underestimates real wire bandwidth because displays need horizontal and vertical blanking intervals between active scanouts for panel timing, audio packets, and metadata islands.&lt;/p>
&lt;p>This calculator models VESA CVT Reduced Blanking v2 (&lt;code>CVT-RBv2&lt;/code>), which adds &lt;code>80&lt;/code> horizontal blanking pixels per line (&lt;code>3840&lt;/code> becomes &lt;code>3920&lt;/code>) plus a fixed &lt;code>460 µs&lt;/code> minimum vertical blanking window per frame. Because &lt;code>460 µs&lt;/code> stays constant in wall-clock time while total frame time shrinks at higher refresh rates, blanking overhead climbs steeply as Hz rises: roughly 5% at &lt;code>4K 60Hz&lt;/code>, 9% at &lt;code>4K 144Hz&lt;/code>, 16% at &lt;code>1440p 240Hz&lt;/code>, and 19% at &lt;code>4K 240Hz&lt;/code>. Custom timings can shave that margin slightly — compare CVT-RBv1, CVT-RBv2, and CEA-861 line counts side by side in &lt;a href="https://tomverbeure.github.io/video_timings_calculator" rel="noopener">Tom Verbeure&amp;rsquo;s video timings reference&lt;/a>.&lt;/p>
&lt;p>Whenever your mode&amp;rsquo;s uncompressed &lt;code>CVT-RBv2&lt;/code> bit rate crosses a port&amp;rsquo;s effective ceiling (&lt;code>25.92 Gbps&lt;/code> on &lt;code>DP 1.4&lt;/code>, &lt;code>38.69 Gbps&lt;/code> on &lt;code>UHBR10&lt;/code>, &lt;code>42.60 Gbps&lt;/code> on &lt;code>HDMI 2.1&lt;/code>), the GPU and monitor negotiate VESA &lt;code>DSC 1.2a&lt;/code>. Compression kicks in automatically. DSC compresses scanlines on the fly with sub-millisecond latency down to VESA&amp;rsquo;s &lt;code>8 bpp&lt;/code> reference target:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>8-bit SDR (&lt;code>24 bpp&lt;/code> raw → &lt;code>8 bpp&lt;/code> DSC):&lt;/strong> &lt;code>3:1&lt;/code> compression ratio&lt;/li>
&lt;li>&lt;strong>10-bit HDR (&lt;code>30 bpp&lt;/code> raw → &lt;code>8 bpp&lt;/code> DSC):&lt;/strong> &lt;code>3.75:1&lt;/code> compression ratio&lt;/li>
&lt;li>&lt;strong>12-bit color (&lt;code>36 bpp&lt;/code> raw → &lt;code>8 bpp&lt;/code> DSC):&lt;/strong> &lt;code>4.5:1&lt;/code> compression ratio&lt;/li>
&lt;/ul>
&lt;p>VESA certifies &lt;code>DSC 1.2a&lt;/code> at &lt;code>8 bpp&lt;/code> as visually lossless in ISO/IEC flicker tests. Still, running uncompressed on &lt;code>UHBR20&lt;/code> or &lt;code>HDMI 2.1&lt;/code> avoids occasional DSC side effects on certain GPU drivers—such as brief black-screen alt-tab delays out of exclusive fullscreen or internal GPU display-head consumption when driving three or four high-refresh monitors simultaneously.&lt;/p>
&lt;h2 id="worked-examples">Worked examples&lt;/h2>
&lt;p>Every figure below comes directly from this calculator&amp;rsquo;s &lt;code>CVT-RBv2&lt;/code> engine so you can sanity-check real monitor upgrades immediately:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>&lt;code>4K 144Hz 10-bit HDR (4:4:4)&lt;/code> — default high-refresh 4K gaming mode&lt;/strong>
&lt;ul>
&lt;li>&lt;strong>Inputs:&lt;/strong> &lt;code>3840 × 2160&lt;/code>, &lt;code>144 Hz&lt;/code>, &lt;code>10-bit&lt;/code>, &lt;code>4:4:4&lt;/code>&lt;/li>
&lt;li>&lt;strong>Output:&lt;/strong> &lt;strong>39.2 Gbps&lt;/strong> uncompressed, &lt;strong>10.4 Gbps&lt;/strong> with DSC. &lt;code>HDMI 2.0&lt;/code>: No. &lt;code>DP 1.4 (HBR3)&lt;/code>: Needs DSC. &lt;code>DP 2.1 UHBR10&lt;/code>: Needs DSC. &lt;code>HDMI 2.1 (48G)&lt;/code>, &lt;code>DP 2.1 UHBR13.5&lt;/code>, and &lt;code>DP 2.1 UHBR20&lt;/code>: &lt;strong>Fits uncompressed&lt;/strong>.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>&lt;strong>&lt;code>1440p 240Hz 8-bit SDR (4:4:4)&lt;/code> — competitive esports monitor on DP 1.4&lt;/strong>
&lt;ul>
&lt;li>&lt;strong>Inputs:&lt;/strong> &lt;code>2560 × 1440&lt;/code>, &lt;code>240 Hz&lt;/code>, &lt;code>8-bit&lt;/code>, &lt;code>4:4:4&lt;/code>&lt;/li>
&lt;li>&lt;strong>Output:&lt;/strong> &lt;strong>24.6 Gbps&lt;/strong> uncompressed, &lt;strong>8.2 Gbps&lt;/strong> with DSC. &lt;code>HDMI 2.0&lt;/code>: No. &lt;code>DP 1.4 (HBR3)&lt;/code>, &lt;code>HDMI 2.1&lt;/code>, and all &lt;code>DP 2.1 UHBR&lt;/code> tiers: &lt;strong>Fits uncompressed&lt;/strong> (&lt;code>24.6 Gbps&lt;/code> clears &lt;code>DP 1.4&lt;/code>&amp;rsquo;s &lt;code>25.92 Gbps&lt;/code> payload limit with &lt;code>1.3 Gbps&lt;/code> to spare; flipping on &lt;code>10-bit HDR&lt;/code> raises demand to &lt;code>30.8 Gbps&lt;/code> and triggers DSC on &lt;code>DP 1.4&lt;/code>).&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>&lt;strong>&lt;code>4K 240Hz 10-bit HDR (4:4:4)&lt;/code> — flagship 4K QD-OLED / WOLED test&lt;/strong>
&lt;ul>
&lt;li>&lt;strong>Inputs:&lt;/strong> &lt;code>3840 × 2160&lt;/code>, &lt;code>240 Hz&lt;/code>, &lt;code>10-bit&lt;/code>, &lt;code>4:4:4&lt;/code>&lt;/li>
&lt;li>&lt;strong>Output:&lt;/strong> &lt;strong>68.6 Gbps&lt;/strong> uncompressed, &lt;strong>18.3 Gbps&lt;/strong> with DSC. Requires DSC on &lt;code>DP 1.4&lt;/code>, &lt;code>HDMI 2.1&lt;/code>, &lt;code>DP 2.1 UHBR10&lt;/code>, and &lt;code>DP 2.1 UHBR13.5&lt;/code>. Fits &lt;strong>uncompressed only on full &lt;code>DP 2.1 UHBR20&lt;/code> (&lt;code>77.37 Gbps&lt;/code>)&lt;/strong> when both GPU and display expose &lt;code>UHBR20&lt;/code> over a certified &lt;code>DP80&lt;/code> cable!&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ol>
&lt;h2 id="four-link-troubleshooting-check-when-a-mode-drops-or-flickers">Four-link troubleshooting check when a mode drops or flickers&lt;/h2>
&lt;p>Bandwidth math only clears the protocol. Your real link drops to the &lt;strong>slowest component&lt;/strong> anywhere between GPU silicon and panel TCON. If a refresh rate disappears from Windows/Linux display settings or blacks out under load (see our full &lt;a href="https://techfuelhq.com/articles/monitor-flickering-fix-2026/">monitor flickering &amp;amp; black-screen fix guide&lt;/a>), inspect all four hops in order:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>GPU output port spec:&lt;/strong> Check the exact port revision (for example, secondary ports or older GPUs limited to &lt;code>DP 1.4a HBR3&lt;/code> or &lt;code>UHBR13.5&lt;/code> vs &lt;code>UHBR20&lt;/code>).&lt;/li>
&lt;li>&lt;strong>KVM switches, USB-C docks, and MST hubs:&lt;/strong> USB-C Alt Mode docks splitting USB 3.x data onto two lanes halve DisplayPort bandwidth immediately, and many older KVMs strip DSC pass-through. Test GPU-to-monitor direct first.&lt;/li>
&lt;li>&lt;strong>Cable rating and physical length:&lt;/strong> Passive copper &lt;code>DP80&lt;/code> cables are short by necessity due to 20 Gbps-per-lane signal attenuation. Uncertified 3-meter or 5-meter cables routinely fail link training and silently downshift from &lt;code>UHBR20&lt;/code> or &lt;code>HBR3&lt;/code> to &lt;code>HBR2&lt;/code> (&lt;code>17.28 Gbps&lt;/code>).&lt;/li>
&lt;li>&lt;strong>Monitor OSD link setting:&lt;/strong> Many monitors ship with DisplayPort set to &lt;code>1.2&lt;/code> or &lt;code>DSC Off&lt;/code> in their on-screen menu for legacy compatibility; switch the monitor OSD to &lt;code>DP 1.4&lt;/code> / &lt;code>DP 2.1&lt;/code> with DSC enabled.&lt;/li>
&lt;/ol>
&lt;h2 id="assumptions-and-primary-sources">Assumptions and primary sources&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>HDMI 2.1 FRL (&lt;code>48 Gbps&lt;/code> raw → &lt;code>42.6 Gbps&lt;/code> effective after &lt;code>16b/18b&lt;/code> coding):&lt;/strong> Derived from the &lt;a href="https://www.hdmi.org/spec/hdmi2_1" rel="noopener">HDMI Forum HDMI 2.1b specification&lt;/a>. Note that &lt;code>HDMI 2.0&lt;/code> (&lt;code>TMDS&lt;/code>) uses &lt;code>8b/10b&lt;/code> coding (&lt;code>18.0 × 0.8 = 14.40 Gbps&lt;/code>) and does not support DSC.&lt;/li>
&lt;li>&lt;strong>DisplayPort 1.4 (&lt;code>25.92 Gbps&lt;/code>) &amp;amp; DisplayPort 2.1 (&lt;code>38.69 / 52.22 / 77.37 Gbps&lt;/code>):&lt;/strong> Per &lt;a href="https://vesa.org/press/vesa-releases-displayport-2-1-specification/" rel="noopener">VESA&amp;rsquo;s DisplayPort 2.1 specification release&lt;/a>, accounting for &lt;code>8b/10b&lt;/code> overhead on &lt;code>HBR3&lt;/code> and &lt;code>128b/132b&lt;/code> + link-layer framing on &lt;code>UHBR10&lt;/code>, &lt;code>UHBR13.5&lt;/code>, and &lt;code>UHBR20&lt;/code>.&lt;/li>
&lt;li>&lt;strong>VESA Display Stream Compression (&lt;code>DSC 1.2a&lt;/code> at &lt;code>8 bpp&lt;/code>):&lt;/strong> Ratios (&lt;code>3:1&lt;/code> at 24-bit, &lt;code>3.75:1&lt;/code> at 30-bit, &lt;code>4.5:1&lt;/code> at 36-bit) and visual-losslessness testing come from &lt;a href="https://vesa.org/vesa-display-compression-codecs/" rel="noopener">VESA&amp;rsquo;s Display Compression Codecs documentation&lt;/a>. Real links with spare bandwidth can negotiate higher bits-per-pixel than the &lt;code>8 bpp&lt;/code> floor modeled here.&lt;/li>
&lt;li>&lt;strong>Blanking model (&lt;code>CVT-RBv2&lt;/code>):&lt;/strong> Uses &lt;code>80&lt;/code> horizontal blanking pixels and a &lt;code>460 µs&lt;/code> minimum vertical blanking interval, matching published &lt;code>3920 × 2222&lt;/code> &lt;code>4K 60Hz&lt;/code> CVT-RBv2 timings (&lt;a href="https://tomverbeure.github.io/video_timings_calculator" rel="noopener">video timings calculator reference&lt;/a>) alongside &lt;a href="https://blurbusters.com/understanding-display-scanout-lag-with-high-speed-video/" rel="noopener">Blur Busters&amp;rsquo; high-speed scanout analysis&lt;/a>.&lt;/li>
&lt;/ul></description></item><item><title>Immich Setup and Google Photos Migration Guide (2026)</title><link>https://techfuelhq.com/tutorials/immich-google-photos-migration-2026/</link><pubDate>Thu, 11 Jun 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/immich-google-photos-migration-2026/</guid><atom:updated>2026-11-14T10:50:00Z</atom:updated><description>&lt;p>By &lt;a href="https://techfuelhq.com/author/lk-wood-iv/">LK Wood IV&lt;/a> · 2026-06-11 · Updated 2026-11-14 · ~16 min read · St. Louis County, MO&lt;/p>
&lt;p>Moving ten years of family photos off Google Photos is high-stakes homelab work. Broken media servers cost an evening. Lost family originals hurt forever.&lt;/p>
&lt;p>I treat every Google Photos migration as a non-destructive, staged pipeline. First I stand up a version-pinned Immich stack with PostgreSQL on local SSD storage. Next I feed the raw Takeout &lt;code>.zip&lt;/code> archives straight into &lt;code>immich-go&lt;/code> without unzipping hundreds of gigabytes of duplicate album copies. Cloud deletion waits until last. I keep every photo untouched in Google Photos until &lt;code>pg_dumpall&lt;/code> and &lt;code>UPLOAD_LOCATION&lt;/code> survive a real restore onto a separate test instance.&lt;/p>
&lt;p>Still weighing photo platforms before committing? Read our &lt;a href="https://techfuelhq.com/tutorials/self-hosted-photo-library-immich-photoprism-ente-2026/">Immich vs PhotoPrism vs Ente comparison&lt;/a>.&lt;/p>
&lt;h2 id="hardware--storage-layout-requirements">Hardware &amp;amp; storage layout requirements&lt;/h2>
&lt;p>Immich&amp;rsquo;s &lt;a href="https://docs.immich.app/install/requirements/" rel="noopener">official system requirements&lt;/a> specify 6 GB RAM and 2 CPU cores minimum, with 8 GB+ RAM and 4+ cores recommended because initial thumbnail generation, CLIP smart search, and facial recognition hammer CPU and memory concurrently.&lt;/p>
&lt;p>Follow two storage rules before deploying:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Run Docker inside a full Linux VM on Proxmox&lt;/strong> (Immich explicitly discourages nested LXC deployments due to AppArmor/cgroup and VectorChord Postgres permission issues).&lt;/li>
&lt;li>&lt;strong>Keep &lt;code>DB_DATA_LOCATION&lt;/code> on local NVMe/SSD (&lt;code>ext4&lt;/code> or &lt;code>xfs&lt;/code>):&lt;/strong> Never place PostgreSQL&amp;rsquo;s data directory on NFS or SMB network shares, which corrupt database pages under lock contention. Your bulk &lt;code>UPLOAD_LOCATION&lt;/code> library can live on a larger local ZFS/RAID pool or wired NAS mount.&lt;/li>
&lt;/ol>
&lt;h2 id="step-1-deploy-immich-with-docker-compose">Step 1: Deploy Immich with Docker Compose&lt;/h2>
&lt;p>Create a dedicated stack directory on your Docker host:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>mkdir -p /opt/stacks/immich &lt;span style="color:#f92672">&amp;amp;&amp;amp;&lt;/span> cd /opt/stacks/immich
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Pin a specific &lt;a href="https://github.com/immich-app/immich/releases" rel="noopener">Immich GitHub release&lt;/a> rather than tracking floating tags blindly, and always download the matching &lt;code>docker-compose.yml&lt;/code> and &lt;code>example.env&lt;/code> from that release:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>version&lt;span style="color:#f92672">=&lt;/span>v3.3.6
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>release&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#34;https://github.com/immich-app/immich/releases/download/&lt;/span>$version&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>wget -O docker-compose.yml &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$release&lt;span style="color:#e6db74">/docker-compose.yml&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>wget -O .env &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$release&lt;span style="color:#e6db74">/example.env&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Edit &lt;code>.env&lt;/code> (&lt;code>chmod 600 .env&lt;/code>) and set four core values before first boot:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>&lt;code>IMMICH_VERSION=v3.3.6&lt;/code>&lt;/strong>: Matches the Compose file you downloaded (follow the &lt;a href="https://docs.immich.app/install/upgrading/" rel="noopener">official upgrade notes&lt;/a> whenever bumping versions later).&lt;/li>
&lt;li>&lt;strong>&lt;code>UPLOAD_LOCATION=/mnt/photos/immich&lt;/code>&lt;/strong>: Directory for managed originals, generated thumbnails, encoded videos, and built-in &lt;code>backups/&lt;/code>. Create this directory ahead of startup.&lt;/li>
&lt;li>&lt;strong>&lt;code>DB_DATA_LOCATION=./postgres&lt;/code>&lt;/strong>: Local SSD path for PostgreSQL + VectorChord vector indexes.&lt;/li>
&lt;li>&lt;strong>&lt;code>DB_PASSWORD&lt;/code>&lt;/strong>: Generate a random alphanumeric string (&lt;code>openssl rand -hex 24&lt;/code>) with no &lt;code>$&lt;/code> or special shell characters that complicate &lt;code>.env&lt;/code> parsing.&lt;/li>
&lt;/ul>
&lt;p>Start the stack and verify all four containers (&lt;code>immich_server&lt;/code>, &lt;code>immich_machine_learning&lt;/code>, &lt;code>immich_redis&lt;/code> running Valkey, and &lt;code>immich_postgres&lt;/code>) report healthy:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>docker compose up -d
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose ps
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Open &lt;code>http://&amp;lt;your-host-ip&amp;gt;:2283&lt;/code> and register your admin account.&lt;/p>
&lt;h2 id="step-2-managed-upload_location-vs-read-only-external-libraries">Step 2: Managed &lt;code>UPLOAD_LOCATION&lt;/code> vs read-only external libraries&lt;/h2>
&lt;p>Immich supports two distinct storage modes, and picking the right one before importing saves painful migrations later:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Managed &lt;code>UPLOAD_LOCATION&lt;/code> (use this for Google Takeout + mobile phone auto-backup):&lt;/strong> Immich owns the folder hierarchy inside &lt;code>UPLOAD_LOCATION/upload&lt;/code> (and &lt;code>UPLOAD_LOCATION/library&lt;/code> if you enable the Storage Template engine). Never manually rename, move, or delete files inside &lt;code>UPLOAD_LOCATION&lt;/code> from the Linux shell!&lt;/li>
&lt;li>&lt;strong>&lt;a href="https://docs.immich.app/features/libraries/" rel="noopener">External Libraries&lt;/a> (use this for curated DSLR/Lightroom folders you organize yourself):&lt;/strong> Bind-mount your existing folder into &lt;code>immich-server&lt;/code> with &lt;code>:ro&lt;/code> (&lt;code>/mnt/nas/dslr-archive:/mnt/external/dslr:ro&lt;/code>) and register &lt;code>/mnt/external/dslr&lt;/code> under &lt;strong>Administration → External Libraries&lt;/strong>. The &lt;code>:ro&lt;/code> flag guarantees Immich cannot alter your folder layout.&lt;/li>
&lt;/ul>
&lt;h2 id="step-3-mobile-app-auto-backup-setup">Step 3: Mobile app auto-backup setup&lt;/h2>
&lt;p>Install the official Immich app from the iOS App Store or Google Play Store, connect to &lt;code>http://&amp;lt;your-host-ip&amp;gt;:2283&lt;/code> (or your HTTPS reverse-proxy domain from Step 6), open the cloud-upload icon, select the camera albums (&lt;code>Recents&lt;/code> / &lt;code>Camera&lt;/code>) to watch, and enable Background Backup on Wi-Fi. On Android, enable Ignore Battery Optimizations so OS doze rules do not kill background uploads; on iOS, grant Background App Refresh and open the app periodically after shooting large 4K video batches.&lt;/p>
&lt;h2 id="step-4-enable-hardware-ml-acceleration-cuda-or-intel-openvino">Step 4: Enable hardware ML acceleration (CUDA or Intel OpenVINO)&lt;/h2>
&lt;p>During a 100,000-photo Takeout migration, CLIP smart search and face recognition are the heaviest jobs on the server. Offloading &lt;code>immich-machine-learning&lt;/code> to an NVIDIA GPU (&lt;code>-cuda&lt;/code>) or an Intel iGPU/Arc card (&lt;code>-openvino&lt;/code>) cuts indexing time dramatically without touching your originals.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>NVIDIA CUDA&lt;/strong> (requires the &lt;a href="https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html" rel="noopener">NVIDIA Container Toolkit&lt;/a> inside your Docker host/VM):&lt;/li>
&lt;/ul>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">immich-machine-learning&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}-cuda&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">deploy&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">resources&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">reservations&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">devices&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">driver&lt;/span>: &lt;span style="color:#ae81ff">nvidia&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">count&lt;/span>: &lt;span style="color:#ae81ff">1&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">capabilities&lt;/span>: [&lt;span style="color:#ae81ff">gpu]&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;ul>
&lt;li>&lt;strong>Intel OpenVINO&lt;/strong> (8th-gen Core / N100 / Arc iGPU via &lt;code>/dev/dri&lt;/code>):&lt;/li>
&lt;/ul>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">immich-machine-learning&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}-openvino&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">devices&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">/dev/dri:/dev/dri&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Run &lt;code>docker compose pull &amp;amp;&amp;amp; docker compose up -d&lt;/code>, trigger a smart-search job, and inspect &lt;code>docker compose logs immich-machine-learning&lt;/code> to confirm &lt;code>CUDAExecutionProvider&lt;/code> or &lt;code>OpenVINOExecutionProvider&lt;/code> loads cleanly (&lt;a href="https://docs.immich.app/features/ml-hardware-acceleration/" rel="noopener">ML hardware acceleration docs&lt;/a>; configure video playback transcoding separately under &lt;a href="https://docs.immich.app/features/hardware-transcoding/" rel="noopener">hardware transcoding&lt;/a>).&lt;/p>
&lt;h2 id="step-5-migrate-google-photos-via-takeout">Step 5: Migrate Google Photos via Takeout&lt;/h2>
&lt;h3 id="why-google-takeout-splits-metadata-into-supplemental-metadatajson-sidecars">Why Google Takeout splits metadata into &lt;code>.supplemental-metadata.json&lt;/code> sidecars&lt;/h3>
&lt;p>Never unzip Takeout folders into browser uploads. Three Google Takeout quirks ruin naive folder uploads:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Split EXIF vs JSON sidecars:&lt;/strong> Whenever you adjust a capture date, add a GPS pin, type a description in Google Photos, or save WhatsApp/screenshot images that lack camera EXIF headers, Google &lt;strong>never writes those edits back into the JPEG/HEIC/MP4 file&lt;/strong>. Instead, Takeout puts them in an adjacent JSON file named &lt;code>IMG_1234.JPG.supplemental-metadata.json&lt;/code> (and because Google truncates sidecar filenames around 46–51 characters, long filenames turn into &lt;code>.supplemen.json&lt;/code>, &lt;code>.suppl.json&lt;/code>, or numbered &lt;code>(1).json&lt;/code> variants!).&lt;/li>
&lt;li>&lt;strong>Cross-archive splits:&lt;/strong> On multi-part exports (&lt;code>takeout-001.zip&lt;/code> through &lt;code>takeout-012.zip&lt;/code>), &lt;code>IMG_4092.MP4&lt;/code> frequently lands inside &lt;code>takeout-004.zip&lt;/code> while its &lt;code>.supplemental-metadata.json&lt;/code> lands inside &lt;code>takeout-005.zip&lt;/code>. Importing archives one at a time leaves thousands of files with missing sidecars and wrong dates!&lt;/li>
&lt;li>&lt;strong>500 GB duplicate album bloat:&lt;/strong> Takeout includes a photo once inside &lt;code>Photos from 2022/&lt;/code> &lt;strong>and a second full copy&lt;/strong> inside every album folder (&lt;code>Summer Trip/&lt;/code>, &lt;code>Favorites/&lt;/code>). Unzipping a 250 GB multi-album export can chew through 450–500 GB of scratch space immediately.&lt;/li>
&lt;/ol>
&lt;h3 id="export-takeout-cleanly-and-rehearse-on-a-small-sample-first">Export Takeout cleanly and rehearse on a small sample first&lt;/h3>
&lt;ol>
&lt;li>Open &lt;a href="https://takeout.google.com" rel="noopener">takeout.google.com&lt;/a>, click &lt;strong>Deselect all&lt;/strong>, and tick &lt;strong>Google Photos&lt;/strong> only.&lt;/li>
&lt;li>Click &lt;strong>Multiple formats / All photo albums included&lt;/strong> and leave every year and user album selected so &lt;code>immich-go&lt;/code> has both the master year files and album membership manifests.&lt;/li>
&lt;li>Choose &lt;strong>Export once&lt;/strong>, &lt;code>.zip&lt;/code> format, and &lt;strong>50 GB&lt;/strong> archive size (fewer split boundaries than 2 GB parts; check your ISP cap first with our &lt;a href="https://techfuelhq.com/tools/data-usage-calculator/">data usage calculator&lt;/a>). Google&amp;rsquo;s &lt;a href="https://support.google.com/accounts/answer/3024190" rel="noopener">Takeout help page&lt;/a> notes preparation can take hours to several days.&lt;/li>
&lt;/ol>
&lt;p>Before running a 300 GB import, see what metadata edge cases look like in our offline &lt;a href="https://techfuelhq.com/downloads/immich-takeout-check/v1/sample.zip" download type="application/zip">Takeout verification sample kit (ZIP)&lt;/a> (with full hashes in &lt;a href="https://techfuelhq.com/downloads/immich-takeout-check/v1/results.json" download type="application/json">&lt;code>results.json&lt;/code>&lt;/a>), tested with &lt;a href="https://github.com/simulot/immich-go/releases/tag/v0.32.0" rel="noopener">&lt;code>immich-go 0.32.0&lt;/code>&lt;/a>:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Takeout input edge case&lt;/th>
&lt;th scope="col">Verified &lt;code>immich-go&lt;/code> behavior&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Takeout input edge case">Two distinct photos both named &lt;code>IMG_0001.jpg&lt;/code> shot during DST fallback (&lt;code>01:30&lt;/code> at &lt;code>-05:00&lt;/code> vs &lt;code>-06:00&lt;/code>)&lt;/td>
&lt;td data-label="Verified immich-go behavior">Both originals preserved byte-for-byte (&lt;code>06:30&lt;/code> and &lt;code>07:30 UTC&lt;/code>) without overwriting same-name collisions.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Takeout input edge case">Originals duplicated across &lt;code>Photos from YYYY&lt;/code> plus three named albums&lt;/td>
&lt;td data-label="Verified immich-go behavior">Stored once via content hash while retaining all five album memberships.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Takeout input edge case">Photo shot &lt;code>Jan 2, 00:15 +05:30&lt;/code> whose Takeout JSON listed &lt;code>Jan 1, 12:45 -06:00&lt;/code>&lt;/td>
&lt;td data-label="Verified immich-go behavior">Preserved exact &lt;code>18:45 UTC&lt;/code> instant rather than shifting the calendar day by 11.5 hours.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h3 id="stream-takeout-zip-files-directly-with-immich-go--sha-1-deduplication">Stream Takeout &lt;code>.zip&lt;/code> files directly with &lt;code>immich-go&lt;/code> + SHA-1 deduplication&lt;/h3>
&lt;p>Download the current &lt;a href="https://github.com/simulot/immich-go/releases" rel="noopener">&lt;code>immich-go&lt;/code> binary&lt;/a> on your server or workstation, generate a scoped API key inside Immich (&lt;strong>Account Settings → API Keys&lt;/strong>), and pass &lt;strong>every &lt;code>.zip&lt;/code> part of your Takeout export together in a single command&lt;/strong> without unzipping them:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">(&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> read -rsp &lt;span style="color:#e6db74">&amp;#39;Immich API key: &amp;#39;&lt;/span> IMMICH_GO_UPLOAD_API_KEY; echo
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> export IMMICH_GO_UPLOAD_API_KEY
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> immich-go upload from-google-photos &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --server&lt;span style="color:#f92672">=&lt;/span>http://127.0.0.1:2283 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --sync-albums&lt;span style="color:#f92672">=&lt;/span>true &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --pause-immich-jobs&lt;span style="color:#f92672">=&lt;/span>true &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /mnt/staging/takeout-*.zip
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">)&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Why this exact invocation works so cleanly:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Zero 500 GB unzip step:&lt;/strong> &lt;code>immich-go&lt;/code> indexes the central directory across all &lt;code>/mnt/staging/takeout-*.zip&lt;/code> files simultaneously, pairs truncated &lt;code>.supplemental-metadata.json&lt;/code> sidecars across archive boundaries, and streams files straight to Immich over HTTP.&lt;/li>
&lt;li>&lt;strong>&lt;code>--pause-immich-jobs=true&lt;/code> during huge imports:&lt;/strong> Pauses heavy background face-recognition and video-transcode queues while uploading so your server does not thrash disk I/O and RAM simultaneously, then resumes processing cleanly when the upload completes.&lt;/li>
&lt;li>&lt;strong>SHA-1 server-side deduplication:&lt;/strong> Immich hashes every uploaded file with &lt;strong>SHA-1&lt;/strong>. When an identical &lt;code>IMG_2048.HEIC&lt;/code> sits in &lt;code>Photos from 2021/&lt;/code> and four Takeout album folders, Immich stores &lt;strong>one single copy&lt;/strong> on disk and attaches all four album links—making re-runs idempotent if your network drops halfway through! &lt;em>(Important nuance: if Takeout contains both &lt;code>IMG_2048.JPG&lt;/code> and &lt;code>IMG_2048-edited.JPG&lt;/code>, or a re-encoded copy with altered pixels, their SHA-1 hashes differ and both versions import as separate files.)&lt;/em>&lt;/li>
&lt;/ul>
&lt;p>Revoke the temporary migration API key in Immich once &lt;code>immich-go&lt;/code> finishes with zero fatal errors, and let background Thumbnail, Smart Search, and Face Detection jobs drain under &lt;strong>Administration → Jobs&lt;/strong>.&lt;/p>
&lt;h2 id="step-6-reverse-proxy-with-nginx-proxy-manager">Step 6: Reverse proxy with Nginx Proxy Manager&lt;/h2>
&lt;p>When exposing Immich on &lt;code>https://photos.yourdomain.com&lt;/code> (or internally over split-DNS + &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale&lt;/a>), forward HTTP traffic to &lt;code>immich_server:2283&lt;/code> with &lt;strong>Websockets Support ON&lt;/strong> and raise Nginx&amp;rsquo;s body-size ceiling so multi-gigabyte 4K phone videos never fail with &lt;code>413 Request Entity Too Large&lt;/code> (&lt;a href="https://docs.immich.app/administration/reverse-proxy/" rel="noopener">Immich reverse proxy docs&lt;/a>):&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-nginx" data-lang="nginx">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">client_max_body_size&lt;/span> &lt;span style="color:#e6db74">50000M&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">proxy_read_timeout&lt;/span> &lt;span style="color:#e6db74">600s&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">proxy_send_timeout&lt;/span> &lt;span style="color:#e6db74">600s&lt;/span>;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">send_timeout&lt;/span> &lt;span style="color:#e6db74">600s&lt;/span>;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="step-7-backup-strategy">Step 7: Backup strategy&lt;/h2>
&lt;p>Immich&amp;rsquo;s &lt;a href="https://docs.immich.app/administration/backup-and-restore/" rel="noopener">backup and restore documentation&lt;/a> splits your library across two inseparable halves:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>&lt;code>UPLOAD_LOCATION&lt;/code> (&lt;code>upload/&lt;/code>, &lt;code>library/&lt;/code>, &lt;code>profile/&lt;/code>, &lt;code>backups/&lt;/code>):&lt;/strong> Contains your actual original photos and videos (note that Immich 1.113+ also writes automated daily database dumps into &lt;code>UPLOAD_LOCATION/backups/&lt;/code>, while &lt;code>thumbs/&lt;/code> and &lt;code>encoded-video/&lt;/code> can be regenerated if desired).&lt;/li>
&lt;li>&lt;strong>PostgreSQL database dump (&lt;code>pg_dumpall&lt;/code> or &lt;code>pg_dump&lt;/code>):&lt;/strong> Stores users, albums, facial clusters, edited dates, captions, and every path mapping into &lt;code>UPLOAD_LOCATION&lt;/code>. &lt;strong>Never rely on copying raw &lt;code>./postgres&lt;/code> bind-mount files while PostgreSQL is running&lt;/strong>—hot file copies of active Postgres data directories frequently corrupt!&lt;/li>
&lt;/ol>
&lt;p>Dump the full PostgreSQL cluster cleanly using Immich&amp;rsquo;s documented &lt;code>pg_dumpall&lt;/code> command (or &lt;code>pg_dump --clean --if-exists&lt;/code>) with gzip verification before promoting the archive:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e">#!/bin/bash
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e">&lt;/span>set -euo pipefail
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>umask &lt;span style="color:#ae81ff">077&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>backup_dir&lt;span style="color:#f92672">=&lt;/span>/mnt/backups/immich-db
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>install -d -m &lt;span style="color:#ae81ff">0700&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$backup_dir&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>tmp&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>mktemp &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$backup_dir&lt;span style="color:#e6db74">/.immich-db-XXXXXX.sql.gz&amp;#34;&lt;/span>&lt;span style="color:#66d9ef">)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>trap &lt;span style="color:#e6db74">&amp;#39;rm -f -- &amp;#34;$tmp&amp;#34;&amp;#39;&lt;/span> EXIT
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker exec -t immich_postgres &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> pg_dumpall --clean --if-exists --username&lt;span style="color:#f92672">=&lt;/span>postgres | gzip &amp;gt; &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$tmp&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>gzip --test &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$tmp&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>final&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span>$backup_dir&lt;span style="color:#e6db74">/immich-pgdumpall-&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>date -u +%Y%m%dT%H%M%SZ&lt;span style="color:#66d9ef">)&lt;/span>&lt;span style="color:#e6db74">.sql.gz&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>mv -- &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$tmp&lt;span style="color:#e6db74">&amp;#34;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$final&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>trap - EXIT
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>printf &lt;span style="color:#e6db74">&amp;#39;Verified Immich DB dump: %s\n&amp;#39;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$final&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Pair that nightly SQL dump with an encrypted &lt;strong>3-2-1 backup&lt;/strong> (&lt;code>restic&lt;/code> or &lt;code>borg&lt;/code> backing up &lt;code>UPLOAD_LOCATION&lt;/code> + &lt;code>/mnt/backups/immich-db&lt;/code> to both a local NAS/PBS target and an off-site cloud or remote homelab disk).&lt;/p>
&lt;h3 id="mandatory-6-gate-checklist-before-deleting-a-single-google-photos-cloud-item">Mandatory 6-gate checklist before deleting a single Google Photos cloud item&lt;/h3>
&lt;p>Never delete cloud originals right after &lt;code>immich-go&lt;/code> finishes. Walk every row of this verification gate first:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Gate&lt;/th>
&lt;th scope="col">What to verify&lt;/th>
&lt;th scope="col">Pass criterion&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Gate">&lt;strong>1. &lt;code>immich-go&lt;/code> log audit&lt;/strong>&lt;/td>
&lt;td data-label="What to verify">Inspect upload summary and skipped/unmatched log lines&lt;/td>
&lt;td data-label="Pass criterion">&lt;code>0&lt;/code> failed uploads; any unmatched sidecars accounted for across all &lt;code>.zip&lt;/code> parts.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gate">&lt;strong>2. Admin job queues&lt;/strong>&lt;/td>
&lt;td data-label="What to verify">Check &lt;strong>Administration → Jobs&lt;/strong> in Immich web UI&lt;/td>
&lt;td data-label="Pass criterion">&lt;code>0&lt;/code> failed jobs across Metadata Extraction, Thumbnail Generation, Video Transcoding, and Smart Search.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gate">&lt;strong>3. Date &amp;amp; album spot-check&lt;/strong>&lt;/td>
&lt;td data-label="What to verify">Check 10 older pre-smartphone scans, WhatsApp/screenshot images, timezone travel photos, and 5 named albums&lt;/td>
&lt;td data-label="Pass criterion">Timeline dates match expected capture dates (not upload date!) and album counts match Google Photos.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gate">&lt;strong>4. Byte-hash spot-check&lt;/strong>&lt;/td>
&lt;td data-label="What to verify">Download 5 full-resolution originals from Immich web UI and run &lt;code>sha256sum&lt;/code> against the files inside Takeout &lt;code>.zip&lt;/code>&lt;/td>
&lt;td data-label="Pass criterion">Exact &lt;code>SHA-256&lt;/code> match confirming uncorrupted original storage.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gate">&lt;strong>5. 3-2-1 backup completion&lt;/strong>&lt;/td>
&lt;td data-label="What to verify">Verify local NAS backup + off-site &lt;code>restic&lt;/code>/cloud snapshot of both &lt;code>UPLOAD_LOCATION&lt;/code> and &lt;code>pg_dumpall&lt;/code> SQL dump&lt;/td>
&lt;td data-label="Pass criterion">Independent off-host copy exists and &lt;code>restic check&lt;/code> passes.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Gate">&lt;strong>6. Isolated restore drill&lt;/strong>&lt;/td>
&lt;td data-label="What to verify">Spin up a disposable test VM/stack with a copy of &lt;code>UPLOAD_LOCATION&lt;/code>, wipe &lt;code>DB_DATA_LOCATION&lt;/code>, run &lt;code>gunzip &amp;lt; dump.sql.gz | docker exec -i immich_postgres psql --dbname=postgres --username=postgres&lt;/code>, and start Immich&lt;/td>
&lt;td data-label="Pass criterion">Test instance opens on &lt;code>:2283&lt;/code> with intact albums, dates, faces, and playable original photos/videos!&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Even after all six gates pass, I archive the raw Google Takeout &lt;code>.zip&lt;/code> files onto a cold offline external hard drive on a shelf before deleting anything from Google&amp;rsquo;s cloud. Storage costs pennies per gigabyte. Twenty years of family photos cannot be re-shot.&lt;/p>
&lt;h2 id="common-issues">Common issues&lt;/h2>
&lt;p>Wrong timeline dates (hundreds of photos bunched on migration day): Usually caused by extracting Takeout folders and uploading JPEGs without their &lt;code>.supplemental-metadata.json&lt;/code> sidecars, or uploading &lt;code>takeout-001.zip&lt;/code> through &lt;code>takeout-010.zip&lt;/code> in separate runs when a photo and its JSON sidecar spanned adjacent archives. Re-run &lt;code>immich-go upload from-google-photos&lt;/code> passing &lt;code>/path/to/takeout-*.zip&lt;/code> in a single command.&lt;/p>
&lt;p>&lt;code>immich-machine-learning&lt;/code> container OOM-killed or restart-looping: Large imports running concurrent ML and video jobs on a 4–6 GB VM exhaust RAM. Give the VM 8–12 GB RAM, use &lt;code>--pause-immich-jobs=true&lt;/code> during &lt;code>immich-go&lt;/code> uploads, and lower concurrency under Administration → Settings → Job Settings (set Face Detection / Smart Search concurrency to &lt;code>1&lt;/code> or &lt;code>2&lt;/code>).&lt;/p>
&lt;p>Mobile app fails on large 4K video backups over HTTPS: Reverse proxy is rejecting uploads at Nginx&amp;rsquo;s default &lt;code>1M&lt;/code> or &lt;code>100M&lt;/code> limit. Set &lt;code>client_max_body_size 50000M;&lt;/code> on your proxy host (Step 6), or connect privately over &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale&lt;/a> or &lt;a href="https://techfuelhq.com/tutorials/wireguard-self-hosted-vpn-proxmox-2026/">self-hosted WireGuard&lt;/a>.&lt;/p>
&lt;p>&lt;code>VectorChord&lt;/code> / &lt;code>pgvecto.rs&lt;/code> extension error during database restore: You restored a database dump onto a mismatched &lt;code>immich_postgres&lt;/code> container tag or forgot to start from a completely empty &lt;code>DB_DATA_LOCATION&lt;/code> directory before piping &lt;code>psql&lt;/code> per the &lt;a href="https://docs.immich.app/administration/backup-and-restore/#restore-via-command-line" rel="noopener">official CLI restore steps&lt;/a>. Match your &lt;code>docker-compose.yml&lt;/code> version to the version that generated the dump first, verify login, and only then upgrade.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://docs.immich.app/install/docker-compose/" rel="noopener">Immich Docker Compose Installation&lt;/a> and &lt;a href="https://docs.immich.app/install/requirements/" rel="noopener">System Requirements&lt;/a> — official Compose stack, &lt;code>.env&lt;/code> variables, RAM/CPU sizing, and VM storage guidance.&lt;/li>
&lt;li>&lt;a href="https://docs.immich.app/administration/backup-and-restore/" rel="noopener">Immich Backup and Restore&lt;/a> — &lt;code>UPLOAD_LOCATION/backups&lt;/code>, &lt;code>pg_dumpall --clean --if-exists&lt;/code>, and clean-database restore verification.&lt;/li>
&lt;li>&lt;a href="https://github.com/simulot/immich-go" rel="noopener">&lt;code>immich-go&lt;/code> Repository &amp;amp; Google Photos Upload Docs&lt;/a> — direct multi-part Takeout &lt;code>.zip&lt;/code> streaming, &lt;code>.supplemental-metadata.json&lt;/code> matching, album reconstruction, and deduplication.&lt;/li>
&lt;li>&lt;a href="https://docs.immich.app/administration/reverse-proxy/" rel="noopener">Immich Reverse Proxy Configuration&lt;/a> and &lt;a href="https://docs.immich.app/features/ml-hardware-acceleration/" rel="noopener">ML Hardware Acceleration&lt;/a>.&lt;/li>
&lt;/ul></description></item><item><title>Proxmox Home Assistant: Install HAOS as a VM, No ISO (2026)</title><link>https://techfuelhq.com/tutorials/home-assistant-proxmox-2026/</link><pubDate>Sun, 31 May 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/home-assistant-proxmox-2026/</guid><atom:updated>2026-11-14T10:50:00Z</atom:updated><description>&lt;p>By &lt;a href="https://techfuelhq.com/author/lk-wood-iv/">LK Wood IV&lt;/a> · Published 2026-05-31 · Updated 2026-11-14 · ~16 min read · St. Louis County, MO&lt;/p>
&lt;p>Running Home Assistant on a separate Raspberry Pi made sense five years ago. If you already run a Proxmox host, a second box is just another power brick and SD card waiting to die.&lt;/p>
&lt;p>Looking for a HAOS ISO to upload into Proxmox? Stop searching. HAOS has no ISO. You create a blank UEFI VM with Secure Boot keys disabled, import the official &lt;code>.qcow2&lt;/code> disk image straight into Proxmox storage, and boot from &lt;code>scsi0&lt;/code>.&lt;/p>
&lt;p>If you do not have a server yet and want dedicated low-watt hardware first, start with my &lt;a href="https://techfuelhq.com/homelab/best-mini-pc-home-assistant-2026/">best mini PC for Home Assistant guide&lt;/a> and come back here for the setup.&lt;/p>
&lt;h2 id="haos-vm-vs-docker-vs-lxc-on-proxmox">HAOS VM vs Docker vs LXC on Proxmox&lt;/h2>
&lt;p>Every week someone tries to cram Home Assistant into an unprivileged Proxmox LXC to save 600 MB of RAM, then loses a Saturday fighting &lt;code>cgroup2&lt;/code> permissions when a Zigbee stick unplugs and re-enumerates on a new device node. Look at what each Proxmox deployment route gives you before you build.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Feature / Operational boundary&lt;/th>
&lt;th scope="col">HAOS VM (&lt;code>OVMF&lt;/code> UEFI, &lt;code>Pre-Enroll keys&lt;/code> off)&lt;/th>
&lt;th scope="col">Docker (&lt;code>Home Assistant Container&lt;/code> in a VM)&lt;/th>
&lt;th scope="col">Proxmox LXC (community scripts / manual Core)&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Feature / Operational boundary">&lt;strong>Official HA support status&lt;/strong>&lt;/td>
&lt;td data-label="HAOS VM (OVMF UEFI, Pre-Enroll keys off)">Tier-1 supported (&lt;code>haos_ova&lt;/code> &lt;code>.qcow2&lt;/code> appliance)&lt;/td>
&lt;td data-label="Docker (Home Assistant Container in a VM)">Supported (&lt;code>ghcr.io/home-assistant/home-assistant&lt;/code>)&lt;/td>
&lt;td data-label="Proxmox LXC (community scripts / manual Core)">Unsupported for HAOS; fragile for Core/Container&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Feature / Operational boundary">&lt;strong>One-click Apps (Add-ons) &amp;amp; Supervisor&lt;/strong>&lt;/td>
&lt;td data-label="HAOS VM (OVMF UEFI, Pre-Enroll keys off)">Included (Mosquitto, Zigbee2MQTT, Matter, Whisper, Tailscale)&lt;/td>
&lt;td data-label="Docker (Home Assistant Container in a VM)">Not available — you maintain separate Compose containers&lt;/td>
&lt;td data-label="Proxmox LXC (community scripts / manual Core)">Not available without unsupported hacks&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Feature / Operational boundary">&lt;strong>UEFI / kernel boot behavior&lt;/strong>&lt;/td>
&lt;td data-label="HAOS VM (OVMF UEFI, Pre-Enroll keys off)">Dedicated HAOS kernel with A/B rollback; &lt;strong>must uncheck &lt;code>Pre-Enroll keys&lt;/code>&lt;/strong> so Secure Boot does not block boot&lt;/td>
&lt;td data-label="Docker (Home Assistant Container in a VM)">Uses guest Linux VM kernel&lt;/td>
&lt;td data-label="Proxmox LXC (community scripts / manual Core)">Shares Proxmox host kernel; host &lt;code>systemd&lt;/code> or AppArmor updates can break startup&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Feature / Operational boundary">&lt;strong>Zigbee / Thread / Z-Wave USB passthrough&lt;/strong>&lt;/td>
&lt;td data-label="HAOS VM (OVMF UEFI, Pre-Enroll keys off)">Clean QEMU device passthrough; guest exposes stable &lt;code>/dev/serial/by-id/...&lt;/code> symlinks across host reboots&lt;/td>
&lt;td data-label="Docker (Home Assistant Container in a VM)">Requires passing USB to the Docker VM first, then &lt;code>--device&lt;/code> mapping into Compose&lt;/td>
&lt;td data-label="Proxmox LXC (community scripts / manual Core)">Host &lt;code>/dev/bus/usb&lt;/code> or &lt;code>/dev/ttyACM*&lt;/code> major/minor numbers shift on unplug or reboot unless custom &lt;code>udev&lt;/code> rules are maintained&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Feature / Operational boundary">&lt;strong>Native HA &lt;code>.tar&lt;/code> snapshots &amp;amp; restore&lt;/strong>&lt;/td>
&lt;td data-label="HAOS VM (OVMF UEFI, Pre-Enroll keys off)">Full encrypted backup of Core + every App + SSL certs; one-screen Onboarding restore&lt;/td>
&lt;td data-label="Docker (Home Assistant Container in a VM)">Backs up HA &lt;code>/config&lt;/code> only; external Mosquitto/Z2M containers need separate volume backups&lt;/td>
&lt;td data-label="Proxmox LXC (community scripts / manual Core)">Manual directory or container backup only&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Feature / Operational boundary">&lt;strong>Proxmox Backup Server (PBS) rollback&lt;/strong>&lt;/td>
&lt;td data-label="HAOS VM (OVMF UEFI, Pre-Enroll keys off)">Whole-VM dirty-bitmap incremental backup in seconds (&lt;code>scsi0&lt;/code> + &lt;code>efidisk0&lt;/code>)&lt;/td>
&lt;td data-label="Docker (Home Assistant Container in a VM)">Whole Docker VM backup covers all stacks together (blunt rollback radius)&lt;/td>
&lt;td data-label="Proxmox LXC (community scripts / manual Core)">Fast &lt;code>pct&lt;/code> backup, but excludes host-bound USB/mount state&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>I run the HAOS VM every time. The &lt;a href="https://techfuelhq.com/homelab/lxc-vs-vm-proxmox-2026/">LXC vs VM breakdown&lt;/a> covers the general hypervisor rule, and Home Assistant is the textbook VM case. It is an appliance operating system, not a single Linux daemon. You get one-click Apps (Home Assistant renamed Add-ons to Apps in 2026.2), isolated Supervisor updates, and radio passthrough that survives power outages without hand-editing container configs.&lt;/p>
&lt;h2 id="is-there-a-haos-iso-for-proxmox">Is there a HAOS ISO for Proxmox?&lt;/h2>
&lt;p>No. Home Assistant does not publish an installer ISO for HAOS. The &lt;a href="https://www.home-assistant.io/installation/alternative" rel="noopener">alternative installation page&lt;/a> ships pre-built virtual disks for VirtualBox (&lt;code>.vdi&lt;/code>), KVM/Proxmox (&lt;code>.qcow2&lt;/code>), and VMware (&lt;code>.ova&lt;/code>), while the &lt;a href="https://www.home-assistant.io/installation/generic-x86-64/" rel="noopener">generic x86-64 page&lt;/a> provides a raw &lt;code>.img.xz&lt;/code> image meant to be flashed directly onto bare-metal media.&lt;/p>
&lt;p>The official GitHub release assets list these x86-64 files, with no &lt;code>.iso&lt;/code> among them:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">File&lt;/th>
&lt;th scope="col">Use&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="File">&lt;code>haos_ova-&amp;lt;version&amp;gt;.qcow2.xz&lt;/code>&lt;/td>
&lt;td data-label="Use">KVM/Proxmox VM disk. This guide imports it.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="File">&lt;code>haos_ova-&amp;lt;version&amp;gt;.ova&lt;/code>&lt;/td>
&lt;td data-label="Use">VMware&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="File">&lt;code>haos_ova-&amp;lt;version&amp;gt;.vdi.zip&lt;/code>&lt;/td>
&lt;td data-label="Use">VirtualBox&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="File">&lt;code>haos_ova-&amp;lt;version&amp;gt;.vmdk.zip&lt;/code>, &lt;code>haos_ova-&amp;lt;version&amp;gt;.vhdx.zip&lt;/code>&lt;/td>
&lt;td data-label="Use">Other virtual disk formats&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="File">&lt;code>haos_generic-x86-64-&amp;lt;version&amp;gt;.img.xz&lt;/code>&lt;/td>
&lt;td data-label="Use">Generic x86-64 disk image for writing directly to a physical drive&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>That is why the Proxmox VM wizard below selects Do not use any media. The boot disk arrives in Step 3 via &lt;code>qm disk import&lt;/code>. Skip the ISO folder completely.&lt;/p>
&lt;h2 id="step-1-download-and-verify-the-haos-disk-image">Step 1: Download and verify the HAOS disk image&lt;/h2>
&lt;p>You can grab the KVM/Proxmox &lt;code>.qcow2.xz&lt;/code> link from &lt;a href="https://www.home-assistant.io/installation/alternative" rel="noopener">home-assistant.io/installation/alternative&lt;/a>, or pull and verify the latest stable release straight from your Proxmox host shell:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Run on the Proxmox host shell as root&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>set -euo pipefail
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cd /tmp
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Query the latest official HAOS release tag from GitHub&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>RELEASE_JSON&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>curl --fail --silent --show-error --location &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> https://api.github.com/repos/home-assistant/operating-system/releases/latest&lt;span style="color:#66d9ef">)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>HAOS_VERSION&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>printf &lt;span style="color:#e6db74">&amp;#39;%s\n&amp;#39;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$RELEASE_JSON&lt;span style="color:#e6db74">&amp;#34;&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> | sed -n &lt;span style="color:#e6db74">&amp;#39;s/.*&amp;#34;tag_name&amp;#34;: *&amp;#34;\([^&amp;#34;]*\)&amp;#34;.*/\1/p&amp;#39;&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> | head -n 1&lt;span style="color:#66d9ef">)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">if&lt;/span> &lt;span style="color:#f92672">[&lt;/span> -z &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$HAOS_VERSION&lt;span style="color:#e6db74">&amp;#34;&lt;/span> &lt;span style="color:#f92672">]&lt;/span>; &lt;span style="color:#66d9ef">then&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> echo &lt;span style="color:#e6db74">&amp;#34;No HAOS release tag found; check the official download page instead.&amp;#34;&lt;/span> &amp;gt;&amp;amp;&lt;span style="color:#ae81ff">2&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> exit &lt;span style="color:#ae81ff">1&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">fi&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>HAOS_ASSET&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#34;haos_ova-&lt;/span>&lt;span style="color:#e6db74">${&lt;/span>HAOS_VERSION&lt;span style="color:#e6db74">}&lt;/span>&lt;span style="color:#e6db74">.qcow2.xz&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>HAOS_URL&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#34;https://github.com/home-assistant/operating-system/releases/download/&lt;/span>&lt;span style="color:#e6db74">${&lt;/span>HAOS_VERSION&lt;span style="color:#e6db74">}&lt;/span>&lt;span style="color:#e6db74">/&lt;/span>&lt;span style="color:#e6db74">${&lt;/span>HAOS_ASSET&lt;span style="color:#e6db74">}&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>curl --fail --show-error --location --output &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$HAOS_ASSET&lt;span style="color:#e6db74">&amp;#34;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$HAOS_URL&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Verify archive integrity before decompressing&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>test -s &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$HAOS_ASSET&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>xz --test &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$HAOS_ASSET&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>xz --decompress --keep &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$HAOS_ASSET&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>test -s &lt;span style="color:#e6db74">&amp;#34;/tmp/haos_ova-&lt;/span>&lt;span style="color:#e6db74">${&lt;/span>HAOS_VERSION&lt;span style="color:#e6db74">}&lt;/span>&lt;span style="color:#e6db74">.qcow2&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ls -lh &lt;span style="color:#e6db74">&amp;#34;/tmp/haos_ova-&lt;/span>&lt;span style="color:#e6db74">${&lt;/span>HAOS_VERSION&lt;span style="color:#e6db74">}&lt;/span>&lt;span style="color:#e6db74">.qcow2&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Never import a wildcard like &lt;code>/tmp/haos*.qcow2&lt;/code> if older downloads sit in &lt;code>/tmp&lt;/code>. Keep &lt;code>HAOS_VERSION&lt;/code> open for Step 3.&lt;/p>
&lt;h2 id="step-2-create-the-ovmf-uefi-vm-with-pre-enroll-keys-unchecked">Step 2: Create the OVMF UEFI VM (with Pre-Enroll keys unchecked)&lt;/h2>
&lt;p>In the Proxmox web UI, click Create VM at the top right. One checkbox on the System tab makes or breaks first boot.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>General tab:&lt;/strong> Choose your Proxmox node, pick a free VM ID (such as &lt;code>200&lt;/code>), and name it &lt;code>home-assistant&lt;/code>.&lt;/li>
&lt;li>&lt;strong>OS tab:&lt;/strong> Select &lt;strong>Do not use any media&lt;/strong>. Leave Guest OS as Linux &lt;code>6.x - 2.6 Kernel&lt;/code>.&lt;/li>
&lt;li>&lt;strong>System tab:&lt;/strong>
&lt;ul>
&lt;li>Machine: &lt;code>q35&lt;/code>&lt;/li>
&lt;li>BIOS: &lt;code>OVMF (UEFI)&lt;/code> (HAOS will not boot on SeaBIOS)&lt;/li>
&lt;li>EFI Storage: &lt;code>local-lvm&lt;/code> (or your ZFS pool)&lt;/li>
&lt;li>&lt;strong>Pre-Enroll keys: UNCHECKED&lt;/strong> — this is critical. Proxmox checks &lt;code>Pre-Enroll keys&lt;/code> by default, which injects Microsoft/distribution Secure Boot certificates into the OVMF NVRAM (&lt;code>pre-enrolled-keys=1&lt;/code>) and turns Secure Boot on. Because HAOS uses an unsigned EFI boot stub, leaving &lt;code>Pre-Enroll keys&lt;/code> checked drops the VM straight to a dead &lt;code>Access Denied&lt;/code> / UEFI interactive shell on boot.&lt;/li>
&lt;li>SCSI Controller: &lt;code>VirtIO SCSI single&lt;/code>&lt;/li>
&lt;li>Qemu Agent: &lt;strong>Checked&lt;/strong> (HAOS ships &lt;code>qemu-guest-agent&lt;/code> preinstalled)&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>&lt;strong>Disks tab:&lt;/strong> Click the trash icon next to &lt;code>scsi0&lt;/code> to delete the placeholder disk. No disk should be listed.&lt;/li>
&lt;li>&lt;strong>CPU tab:&lt;/strong> 1 socket, &lt;code>2&lt;/code> cores minimum, Type &lt;code>host&lt;/code>.&lt;/li>
&lt;li>&lt;strong>Memory tab:&lt;/strong> &lt;code>2048&lt;/code> MiB minimum (&lt;code>4096&lt;/code> MiB recommended if you plan to run Zigbee2MQTT, Matter, and voice Apps; disable Ballooning if you pass through PCIe devices, otherwise default is fine).&lt;/li>
&lt;li>&lt;strong>Network tab:&lt;/strong> Bridge &lt;code>vmbr0&lt;/code>, Model &lt;code>VirtIO (paravirtualized)&lt;/code>.&lt;/li>
&lt;/ul>
&lt;p>Click Finish, and do not start the VM yet. Open VM 200 → Options and set Start at boot to Yes.&lt;/p>
&lt;p>Prefer building the EFI disk from the CLI instead of the wizard? If you left Add EFI Disk unchecked during creation, allocate the non-Secure-Boot 4M OVMF variables volume explicitly:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>qm set &lt;span style="color:#ae81ff">200&lt;/span> --efidisk0 local-lvm:1,efitype&lt;span style="color:#f92672">=&lt;/span>4m,pre-enrolled-keys&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#ae81ff">0&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Already booted with &lt;code>Pre-Enroll keys&lt;/code> checked by mistake? Stop the VM right away. Remove &lt;code>efidisk0&lt;/code> under Hardware, then re-add an EFI Disk with Pre-Enroll keys unchecked. No re-import of the main HAOS disk is required.&lt;/p>
&lt;h2 id="step-3-import-and-attach-the-haos-disk">Step 3: Import and attach the HAOS disk&lt;/h2>
&lt;p>From the same Proxmox root shell where &lt;code>HAOS_VERSION&lt;/code> is set, import the extracted &lt;code>.qcow2&lt;/code> into VM &lt;code>200&lt;/code> on your target storage (&lt;code>local-lvm&lt;/code> or &lt;code>local-zfs&lt;/code>):&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>qm disk import &lt;span style="color:#ae81ff">200&lt;/span> &lt;span style="color:#e6db74">&amp;#34;/tmp/haos_ova-&lt;/span>&lt;span style="color:#e6db74">${&lt;/span>HAOS_VERSION&lt;span style="color:#e6db74">}&lt;/span>&lt;span style="color:#e6db74">.qcow2&amp;#34;&lt;/span> local-lvm
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>(&lt;code>qm importdisk&lt;/code> is an alias for &lt;code>qm disk import&lt;/code> in current &lt;a href="https://pve.proxmox.com/pve-docs/qm.1.html" rel="noopener">Proxmox VE &lt;code>qm&lt;/code> docs&lt;/a>.) Once the import prints &lt;code>Successfully imported disk as 'unused0:local-lvm:vm-200-disk-1'&lt;/code>, attach it and lock the boot order. Two shell commands finish the job:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Attach unused0 to scsi0 with TRIM/discard and SSD emulation enabled&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>qm set &lt;span style="color:#ae81ff">200&lt;/span> --scsi0 local-lvm:vm-200-disk-1,discard&lt;span style="color:#f92672">=&lt;/span>on,ssd&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#ae81ff">1&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Boot strictly from scsi0&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>qm set &lt;span style="color:#ae81ff">200&lt;/span> --boot order&lt;span style="color:#f92672">=&lt;/span>scsi0
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Or do the exact same steps in the Proxmox UI: open VM 200 → Hardware, double-click Unused Disk 0, set Bus/Device to &lt;code>SCSI&lt;/code> &lt;code>0&lt;/code>, check Discard, click Add, then open Options → Boot Order, enable &lt;code>scsi0&lt;/code>, drag it to slot 1, and uncheck &lt;code>net0&lt;/code>. Remove &lt;code>/tmp/haos_ova-${HAOS_VERSION}.qcow2*&lt;/code> once the VM boots cleanly.&lt;/p>
&lt;h2 id="step-4-first-boot-and-onboarding">Step 4: First boot and onboarding&lt;/h2>
&lt;p>Start VM &lt;code>200&lt;/code> and open Console. HAOS resizes its data partition automatically on first boot, starts Docker/Supervisor internally, and prints its IPv4/IPv6 addresses above the &lt;code>ha &amp;gt;&lt;/code> prompt. With QEMU Guest Agent enabled, Proxmox also displays the live IP right on the VM&amp;rsquo;s Summary screen (or via &lt;code>qm guest cmd 200 network-get-interfaces&lt;/code>).&lt;/p>
&lt;p>Open &lt;code>http://homeassistant.local:8123&lt;/code> (or &lt;code>http://&amp;lt;vm-ip&amp;gt;:8123&lt;/code>) in your browser. Wait for the initial preparation screen to finish, then either click Create my smart home (saving your owner credentials in a password manager — local owner passwords have no cloud reset) or click Restore from backup if you are migrating an existing &lt;code>.tar&lt;/code> archive. Lock a static DHCP lease immediately. Bookmarks and reverse proxies never drift that way.&lt;/p>
&lt;h2 id="step-5-persistent-zigbee-thread-and-z-wave-usb-passthrough">Step 5: Persistent Zigbee, Thread, and Z-Wave USB passthrough&lt;/h2>
&lt;p>Plug your radio coordinator into a USB 2.0 port on a short shielded USB extension cable away from USB 3.0 SSDs and metal chassis walls — 2.4 GHz USB 3.0 noise deafens Zigbee and Thread receivers at the port. That physical rule applies equally to a Sonoff ZBDongle-P (&lt;code>10c4:ea60&lt;/code> CP2102N), a Sonoff ZBDongle-E (&lt;code>1a86:55d4&lt;/code> CH9102), a &lt;a href="https://www.home-assistant.io/connect/zbt-2/" rel="noopener">Home Assistant Connect ZBT-2&lt;/a> (our &lt;a href="https://techfuelhq.com/homelab/home-assistant-connect-zbt-2-2026/">ZBT-2 review and setup notes&lt;/a>), or a Z-Wave 800-series stick.&lt;/p>
&lt;p>Check how the Linux host sees the stick:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>lsusb
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ls -l /dev/serial/by-id/
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Pass the stick into the HAOS VM with the right Proxmox mapping rule (&lt;a href="https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_usb_passthrough" rel="noopener">Proxmox USB passthrough docs&lt;/a>):&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Unique Vendor/Product ID (95% of homelabs):&lt;/strong> Go to &lt;strong>VM 200 → Hardware → Add → USB Device → Use USB Vendor/Device ID&lt;/strong> and pick your stick. This survives both host reboots &lt;em>and&lt;/em> moving the USB extension cable to a different port on the Proxmox server.&lt;/li>
&lt;li>&lt;strong>Two identical Vendor/Product IDs (e.g., two &lt;code>10c4:ea60&lt;/code> CP2102N sticks, one for Zigbee and one for Thread/Z-Wave):&lt;/strong> Vendor/Product ID cannot tell them apart. Choose &lt;strong>Use USB Port&lt;/strong> (which maps the physical host bus/port topology, such as &lt;code>1-4.2&lt;/code>) and label the rear ports so nobody swaps cables during cleaning.&lt;/li>
&lt;/ol>
&lt;p>Inside Home Assistant, never configure &lt;code>/dev/ttyUSB0&lt;/code> or &lt;code>/dev/ttyACM0&lt;/code> in Zigbee2MQTT, ZHA, OpenThread Border Router, or Z-Wave JS. Kernel enumeration order flips those numbers unpredictably. Open Settings → System → Hardware → All Hardware, search &lt;code>by-id&lt;/code>, and copy the full &lt;code>/dev/serial/by-id/usb-...&lt;/code> path (for example &lt;code>/dev/serial/by-id/usb-Nabu_Casa_ZBT-2_...-if00&lt;/code> or &lt;code>/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_...-if00-port0&lt;/code>). That symlink encodes the chip&amp;rsquo;s descriptor and serial number, so it points at the exact physical radio across every guest and host reboot. See the &lt;a href="https://techfuelhq.com/tutorials/home-assistant-zigbee-zwave-2026/">Zigbee and Z-Wave integration guide&lt;/a> for channel selection and pairing.&lt;/p>
&lt;h2 id="step-6-off-host-backups-and-restore-verification-tar--pbs">Step 6: Off-host backups and restore verification (&lt;code>.tar&lt;/code> + PBS)&lt;/h2>
&lt;p>A backup stored only inside VM &lt;code>200&lt;/code>&amp;rsquo;s virtual disk vanishes if the host NVMe dies. A Proxmox VM snapshot (&lt;code>qm snapshot&lt;/code>) is a local pre-upgrade rollback point on the same pool, never a backup. Build two off-host layers and test restoring both before your household relies on wall switches and water-leak sensors:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Off-host Home Assistant &lt;code>.tar&lt;/code> backups (application layer):&lt;/strong>
&lt;ul>
&lt;li>Go to &lt;strong>Settings → System → Storage → Add network storage&lt;/strong> and mount an SMB or NFS share on a separate NAS (Usage: &lt;strong>Backup&lt;/strong>), or configure an off-site cloud backup integration (such as Google Drive Backup or Home Assistant Cloud/Link).&lt;/li>
&lt;li>Open &lt;strong>Settings → System → Backups&lt;/strong>, enable automatic daily backups retained on both local disk and your NAS/cloud target, and &lt;strong>download the Emergency Kit&lt;/strong> immediately. Store that kit in your password manager: without its encryption key, encrypted &lt;code>.tar&lt;/code> archives from 2025+ HAOS releases cannot be decrypted.&lt;/li>
&lt;li>&lt;strong>Verify the &lt;code>.tar&lt;/code> restore:&lt;/strong> Pull one &lt;code>.tar&lt;/code> file from your NAS or Google Drive onto your desktop. Create a temporary Proxmox test VM (&lt;code>VMID 299&lt;/code>) with &lt;strong>Disconnect&lt;/strong> checked on its VirtIO NIC (&lt;code>net0&lt;/code>) or placed on an isolated VLAN so it cannot fight your live instance for LAN integrations, attach a fresh HAOS &lt;code>.qcow2&lt;/code>, boot to port 8123 on that test network, choose &lt;strong>Restore from backup&lt;/strong> during onboarding, upload the &lt;code>.tar&lt;/code>, enter the Emergency Kit key, and verify your dashboards, automations, and App configs load cleanly. Destroy VM &lt;code>299&lt;/code> once verified.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>&lt;strong>Proxmox Backup Server (PBS) or &lt;code>vzdump&lt;/code> (hypervisor layer):&lt;/strong>
&lt;ul>
&lt;li>Schedule nightly incremental &lt;a href="https://pbs.proxmox.com/docs/backup-client.html" rel="noopener">Proxmox Backup Server&lt;/a> (or &lt;code>vzdump&lt;/code> to an NFS/SMB target) jobs covering VM &lt;code>200&lt;/code>. Because &lt;code>qemu-guest-agent&lt;/code> is active, Proxmox freezes guest filesystems cleanly (&lt;code>fsfreeze&lt;/code>) during snapshot creation and captures both &lt;code>scsi0&lt;/code> and your &lt;code>efidisk0&lt;/code> OVMF boot variables.&lt;/li>
&lt;li>&lt;strong>Verify the PBS restore:&lt;/strong> In the Proxmox UI under your PBS storage → &lt;strong>Backups&lt;/strong>, select last night&amp;rsquo;s &lt;code>vm/200&lt;/code> snapshot, click &lt;strong>Restore&lt;/strong>, set &lt;strong>VM&lt;/strong> to a new free ID (&lt;code>299&lt;/code>), leave &lt;strong>Start after restore&lt;/strong> unchecked, and disconnect &lt;code>net0&lt;/code> (and remove any duplicate USB passthrough entry on &lt;code>299&lt;/code>!) before starting it on console. Confirm it boots past OVMF straight to the &lt;code>ha &amp;gt;&lt;/code> banner without dropping to the UEFI shell.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ol>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Recovery check&lt;/th>
&lt;th scope="col">Passing verification state&lt;/th>
&lt;th scope="col">Failure caught early&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Recovery check">Host power-loss reboot&lt;/td>
&lt;td data-label="Passing verification state">&lt;code>Start at boot: Yes&lt;/code>, &lt;code>qemu-guest-agent&lt;/code> reports guest IP, &lt;code>/dev/serial/by-id/...&lt;/code> radio reconnects automatically&lt;/td>
&lt;td data-label="Failure caught early">Missing autostart, swapped USB port on duplicate-ID stick, or &lt;code>Pre-Enroll keys&lt;/code> Secure Boot hang&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Recovery check">Off-host &lt;code>.tar&lt;/code> + Emergency Kit&lt;/td>
&lt;td data-label="Passing verification state">Downloaded &lt;code>.tar&lt;/code> from NAS/Google Drive decrypts with saved Emergency Kit key on isolated test VM &lt;code>299&lt;/code>&lt;/td>
&lt;td data-label="Failure caught early">Corrupted SMB write, missing encryption key, or incomplete App backup exclusion&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Recovery check">PBS / &lt;code>vzdump&lt;/code> whole-VM restore&lt;/td>
&lt;td data-label="Passing verification state">Restores to spare VM ID &lt;code>299&lt;/code> (NIC/USB detached prior to start) and boots &lt;code>scsi0&lt;/code> cleanly via restored &lt;code>efidisk0&lt;/code>&lt;/td>
&lt;td data-label="Failure caught early">Broken datastore permissions, missing EFI disk in backup, or silent SSD corruption&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="step-7-remote-access-and-virtual-disk-expansion">Step 7: Remote access and virtual disk expansion&lt;/h2>
&lt;p>For remote phone access outside your LAN, pick one documented path:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Home Assistant Cloud / Link (Nabu Casa):&lt;/strong> Zero port forwarding, remote UI + Alexa/Google voice bridge ($6.50/month or $65/year US when checked October 2, 2026; transitioning branding to &lt;a href="https://www.nabucasa.com/link/" rel="noopener">Home Assistant Link&lt;/a> on December 2, 2026).&lt;/li>
&lt;li>&lt;strong>Tailscale App:&lt;/strong> Free zero-port-forward mesh access. Install &lt;strong>Tailscale&lt;/strong> from &lt;strong>Settings → Apps → App store&lt;/strong>, authenticate to your tailnet, and reach HA from any device on your &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale homelab setup&lt;/a>.&lt;/li>
&lt;li>&lt;strong>Reverse proxy (Nginx Proxy Manager / Caddy):&lt;/strong> Point &lt;code>ha.yourdomain.com&lt;/code> at &lt;code>http://&amp;lt;vm-ip&amp;gt;:8123&lt;/code> with &lt;strong>Websockets Support&lt;/strong> enabled, and declare the proxy&amp;rsquo;s exact IP under &lt;code>http: use_x_forwarded_for: true&lt;/code> and &lt;code>trusted_proxies:&lt;/code> in HA&amp;rsquo;s &lt;code>configuration.yaml&lt;/code> so Home Assistant doesn&amp;rsquo;t reject proxied requests with &lt;code>400 Bad Request&lt;/code>.&lt;/li>
&lt;/ul>
&lt;p>Need more than the default 32 GB virtual disk later for Music Assistant or recorder history? (Keep heavy NVR video outside HAOS or size it first with the &lt;a href="https://techfuelhq.com/tools/frigate-nvr-storage-calculator/">Frigate NVR storage calculator&lt;/a>.) Expand &lt;code>scsi0&lt;/code> online from the Proxmox shell:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>qm disk resize &lt;span style="color:#ae81ff">200&lt;/span> scsi0 +32G
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Reboot HAOS once (&lt;code>Settings → System → Hardware → ⋮ → Reboot system&lt;/code>). Its init scripts grow the &lt;code>hassos-data&lt;/code> filesystem automatically to fill the new space, which you can confirm under &lt;strong>Settings → System → Storage&lt;/strong>. To model host wall-power draw alongside other guests, plug your host meter reading into the &lt;a href="https://techfuelhq.com/tools/power-cost-calculator/">Power &amp;amp; Cost Calculator&lt;/a>.&lt;/p>
&lt;hr>
&lt;h2 id="next-steps">Next steps&lt;/h2>
&lt;ul>
&lt;li>Set up remote access with &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale&lt;/a> or &lt;a href="https://techfuelhq.com/tutorials/wireguard-self-hosted-vpn-proxmox-2026/">WireGuard&lt;/a>.&lt;/li>
&lt;li>Pair Zigbee and Z-Wave devices using the &lt;a href="https://techfuelhq.com/tutorials/home-assistant-zigbee-zwave-2026/">Zigbee and Z-Wave integration guide&lt;/a>.&lt;/li>
&lt;li>Build reliable triggers, conditions, and traces with the &lt;a href="https://techfuelhq.com/tutorials/home-assistant-automations-guide-2026/">Home Assistant automations guide&lt;/a>.&lt;/li>
&lt;li>Add local voice control with the &lt;a href="https://techfuelhq.com/tutorials/home-assistant-local-llm-voice-2026/">fully local LLM voice guide&lt;/a>.&lt;/li>
&lt;/ul>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://www.home-assistant.io/installation/alternative" rel="noopener">Home Assistant: Alternative installation methods&lt;/a> — official KVM/Proxmox &lt;code>.qcow2&lt;/code> image, 2 vCPU / 2 GB RAM / 32 GB disk minimums, and non-Secure-Boot UEFI requirement.&lt;/li>
&lt;li>&lt;a href="https://www.home-assistant.io/installation/" rel="noopener">Home Assistant: Installation methods overview&lt;/a> — official feature comparison between Home Assistant OS (VM/appliance) and Home Assistant Container (Docker).&lt;/li>
&lt;li>&lt;a href="https://www.home-assistant.io/installation/generic-x86-64/" rel="noopener">Home Assistant: Generic x86-64&lt;/a> and &lt;a href="https://github.com/home-assistant/operating-system/releases/latest" rel="noopener">HAOS GitHub releases&lt;/a> — official release artifacts confirming disk-image distribution with no installer ISO.&lt;/li>
&lt;li>&lt;a href="https://www.home-assistant.io/common-tasks/general/" rel="noopener">Home Assistant common tasks: Backups and restore&lt;/a> and &lt;a href="https://www.home-assistant.io/getting-started/onboarding/" rel="noopener">Onboarding&lt;/a> — encrypted &lt;code>.tar&lt;/code> automatic backups, Emergency Kit decryption key, and Onboarding restore workflow.&lt;/li>
&lt;li>&lt;a href="https://www.home-assistant.io/connect/zbt-2/" rel="noopener">Home Assistant Connect ZBT-2&lt;/a> and &lt;a href="https://www.zigbee2mqtt.io/guide/configuration/adapter-settings.html" rel="noopener">Zigbee2MQTT adapter settings&lt;/a> — Zigbee/Thread USB radio hardware and persistent &lt;code>/dev/serial/by-id/...&lt;/code> paths.&lt;/li>
&lt;li>&lt;a href="https://pve.proxmox.com/pve-docs/chapter-qm.html" rel="noopener">Proxmox VE QEMU/KVM Virtual Machines&lt;/a> and &lt;a href="https://pve.proxmox.com/pve-docs/qm.1.html" rel="noopener">&lt;code>qm&lt;/code> manual&lt;/a> — &lt;code>q35&lt;/code>, &lt;code>OVMF&lt;/code> EFI disk &lt;code>pre-enrolled-keys=0&lt;/code>, &lt;code>qm disk import&lt;/code>, &lt;code>qm disk resize&lt;/code>, and &lt;a href="https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_usb_passthrough" rel="noopener">USB passthrough&lt;/a>.&lt;/li>
&lt;li>&lt;a href="https://pve.proxmox.com/pve-docs/chapter-vzdump.html" rel="noopener">Proxmox VE backup and restore&lt;/a> and &lt;a href="https://pbs.proxmox.com/docs/backup-client.html" rel="noopener">Proxmox Backup Server client docs&lt;/a> — hypervisor whole-VM backups, &lt;code>fsfreeze&lt;/code>, and test restores.&lt;/li>
&lt;li>&lt;a href="https://www.home-assistant.io/blog/2026/02/04/release-20262/" rel="noopener">Home Assistant 2026.2 release notes&lt;/a>, &lt;a href="https://www.home-assistant.io/integrations/zwave_js/" rel="noopener">Z-Wave integration&lt;/a>, and &lt;a href="https://www.nabucasa.com/link/" rel="noopener">Nabu Casa Link&lt;/a> — Add-ons-to-Apps rename, Z-Wave JS architecture, and remote access pricing.&lt;/li>
&lt;/ul></description></item><item><title>ZFS on Proxmox: Pool Setup, ARC Cap, and SSD Wear (2026)</title><link>https://techfuelhq.com/tutorials/zfs-proxmox-pool-setup-arc-tuning-2026/</link><pubDate>Tue, 26 May 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/zfs-proxmox-pool-setup-arc-tuning-2026/</guid><atom:updated>2026-11-14T10:50:00Z</atom:updated><description>&lt;p>By &lt;a href="https://techfuelhq.com/author/lk-wood-iv/">LK Wood IV&lt;/a> · Published 2026-05-26 · Updated 2026-11-14 · ~15 min read · St. Louis County, MO&lt;/p>
&lt;p>The &lt;a href="https://techfuelhq.com/homelab/proxmox-truenas-unraid-storage-backend-2026/">ZFS storage backend comparison&lt;/a> covers when ZFS beats LVM-thin, TrueNAS, or Unraid. This guide covers the exact Proxmox VE 8 and 9 commands: creating an &lt;code>ashift=12&lt;/code> pool safely, tuning ARC memory caps across installer generations, picking &lt;code>lz4&lt;/code> vs &lt;code>zstd&lt;/code>, and avoiding the consumer QLC SSD wearout trap.&lt;/p>
&lt;p>Pick your starting point before running a single command:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Already have a running ZFS pool and only want to check or tune RAM / SSD wear?&lt;/strong> Jump straight to &lt;a href="#tune-zfs-arc-for-a-shared-host">Tune ZFS ARC: 10% installer cap vs historic 50%&lt;/a> or &lt;a href="#why-consumer-qlc-and-dram-less-nvme-ssds-burn-out-on-proxmox-zfs">Why consumer QLC NVMe drives burn out&lt;/a>. Do not touch &lt;code>zpool create&lt;/code>.&lt;/li>
&lt;li>&lt;strong>Adding brand-new or wiped drives for a fresh pool?&lt;/strong> Start right below at &lt;a href="#identify-your-drives">Identify your drives&lt;/a> and verify serial numbers before previewing with &lt;code>zpool create -n&lt;/code>.&lt;/li>
&lt;/ul>
&lt;h2 id="identify-your-drives">Identify your drives&lt;/h2>
&lt;p>Pool creation erases every target disk. Never run &lt;code>zpool create&lt;/code> on a Proxmox boot drive, a mounted filesystem, or a drive holding unbacked-up data. Stop immediately if a serial looks ambiguous. Double-check every serial twice.&lt;/p>
&lt;p>Match every physical drive&amp;rsquo;s model, capacity, and serial number before touching ZFS:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS,MODEL,SERIAL,WWN
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ls -la /dev/disk/by-id/ | grep -v part
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Always pass &lt;code>/dev/disk/by-id/&lt;/code> paths (never &lt;code>/dev/sda&lt;/code> or &lt;code>/dev/nvme0n1&lt;/code>) to &lt;code>zpool create&lt;/code>. Kernel enumeration shifts whenever PCIe cards move. While ZFS reads on-disk labels once a pool exists, passing &lt;code>/dev/sdX&lt;/code> during creation or &lt;code>zpool replace&lt;/code> is still the classic way admins wipe the wrong disk by mistake.&lt;/p>
&lt;p>Example inventory you want in front of you:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>ata-ST16000NM001G-2_ZR507B3X -&amp;gt; 16TB Seagate IronWolf (empty)
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ata-ST16000NM001G-2_ZR507B3Y -&amp;gt; 16TB Seagate IronWolf (empty)
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>nvme-Micron_7450_MTFDKBA960TFR_2319X1 -&amp;gt; 960GB Enterprise PLP NVMe (empty)
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>nvme-Micron_7450_MTFDKBA960TFR_2319X2 -&amp;gt; 960GB Enterprise PLP NVMe (empty)
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="why-consumer-qlc-and-dram-less-nvme-ssds-burn-out-on-proxmox-zfs">Why consumer QLC and DRAM-less NVMe SSDs burn out on Proxmox ZFS&lt;/h2>
&lt;p>Cheap QLC sticks die fast here. Before you build an SSD pool on whatever 2 TB M.2 stick was on sale last week, look at what Proxmox writes to disk when idle. I learned this lesson watching a budget consumer drive chew through wear percentage on an otherwise quiet test node.&lt;/p>
&lt;p>Even with zero active VMs, a Proxmox VE host is never write-idle. The &lt;a href="https://pve.proxmox.com/pve-docs/chapter-pmxcfs.html" rel="noopener">Proxmox Cluster File System (&lt;code>pmxcfs&lt;/code>)&lt;/a> mounts &lt;code>/etc/pve&lt;/code> in RAM and persists every configuration update, auth ticket rotation, cluster heartbeat, and RRD status graph into a local SQLite database (&lt;code>/var/lib/pve-cluster/config.db&lt;/code>) via frequent &lt;code>fsync&lt;/code> calls, alongside &lt;code>journald&lt;/code> and &lt;code>pveproxy&lt;/code> logs. Layer ZFS copy-on-write transaction groups (&lt;code>txg&lt;/code>) and ZFS Intent Log (&lt;code>ZIL&lt;/code>) synchronous writes on top, and tiny 200-byte synchronous commits turn into padded 4 KiB+ flash writes thousands of times an hour.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">SSD class&lt;/th>
&lt;th scope="col">Power-loss protection (PLP) &amp;amp; DRAM&lt;/th>
&lt;th scope="col">Behavior under Proxmox &lt;code>pmxcfs&lt;/code> + ZFS sync writes&lt;/th>
&lt;th scope="col">Homelab suitability&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="SSD class">&lt;strong>Consumer QLC / DRAM-less NVMe&lt;/strong> (e.g., Crucial P3, Kingston NV2/NV3)&lt;/td>
&lt;td data-label="Power-loss protection (PLP) &amp;amp; DRAM">No PLP capacitors; host-memory buffer (HMB) or tiny SLC cache over dense 4-bit QLC cells&lt;/td>
&lt;td data-label="Behavior under Proxmox pmxcfs &amp;#43; ZFS sync writes">Every ZIL/&lt;code>pmxcfs&lt;/code> &lt;code>fsync&lt;/code> forces a physical flash flush, bypassing write coalescing; write amplification spikes I/O wait (&lt;code>iowait&lt;/code>) and burns through 150–300 TBW ratings rapidly&lt;/td>
&lt;td data-label="Homelab suitability">&lt;strong>Avoid for ZFS pools or &lt;code>rpool&lt;/code>&lt;/strong> (fine for read-heavy scratch/game libraries, bad for ZFS)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="SSD class">&lt;strong>Prosumer TLC NVMe with DRAM&lt;/strong> (e.g., WD Black SN850X, Samsung 990 Pro)&lt;/td>
&lt;td data-label="Power-loss protection (PLP) &amp;amp; DRAM">Dedicated DRAM cache, 3-bit TLC NAND, &lt;strong>no PLP capacitors&lt;/strong>&lt;/td>
&lt;td data-label="Behavior under Proxmox pmxcfs &amp;#43; ZFS sync writes">Survives light homelab VM duty much better than QLC, but synchronous ZIL flushes remain slower than PLP drives; monitor SMART &lt;code>Percentage Used&lt;/code> monthly&lt;/td>
&lt;td data-label="Homelab suitability">Acceptable for non-critical single-node labs when mirrored and monitored&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="SSD class">&lt;strong>Enterprise TLC SSD / NVMe with PLP&lt;/strong> (e.g., Micron 7450 Pro/Max, Intel D3-S4510/S4610, Samsung PM9A3/PM893)&lt;/td>
&lt;td data-label="Power-loss protection (PLP) &amp;amp; DRAM">Hardware tantalum capacitors flush in-flight DRAM buffers on power cut; 1–3+ DWPD rating&lt;/td>
&lt;td data-label="Behavior under Proxmox pmxcfs &amp;#43; ZFS sync writes">Acknowledges &lt;code>fsync&lt;/code> / ZIL commits straight from capacitor-backed DRAM in microseconds with minimal NAND write amplification and multi-petabyte endurance&lt;/td>
&lt;td data-label="Homelab suitability">&lt;strong>Recommended by Proxmox&lt;/strong> for ZFS boot mirrors, VM pools, SLOG, and &lt;code>special&lt;/code> vdevs&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Check your existing NVMe wear right now with &lt;code>smartctl -a /dev/nvme0n1 | grep -E &amp;quot;Percentage Used|Data Units Written&amp;quot;&lt;/code>. Enterprise PLP SSDs solve this permanently. If you run a standalone single-node lab on consumer TLC SSDs, stopping unused cluster daemons (&lt;code>pve-ha-lrm&lt;/code>, &lt;code>pve-ha-crm&lt;/code>, &lt;code>corosync&lt;/code> on a non-clustered node only) reduces background &lt;code>pmxcfs&lt;/code> chatter noticeably.&lt;/p>
&lt;h2 id="create-a-pool-common-topologies-ashift12">Create a pool: common topologies (&lt;code>ashift=12&lt;/code>)&lt;/h2>
&lt;p>Never force a pool wipe. Replace every disk placeholder below with a verified &lt;code>/dev/disk/by-id/&lt;/code> whole-disk symlink, and keep &lt;code>-n&lt;/code> on the first run because &lt;a href="https://openzfs.github.io/openzfs-docs/man/v2.3/8/zpool-create.8.html" rel="noopener">OpenZFS &lt;code>zpool-create(8)&lt;/code>&lt;/a> treats &lt;code>-n&lt;/code> as a non-destructive dry-run preview that prints the exact vdev layout without writing a byte to disk. Only remove &lt;code>-n&lt;/code> once every serial matches your checklist, and never pass &lt;code>-f&lt;/code> to silence an active-filesystem warning.&lt;/p>
&lt;h3 id="two-disks-mirror-recommended-starting-vm-pool">Two disks: mirror (recommended starting VM pool)&lt;/h3>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>zpool create -n -o ashift&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#ae81ff">12&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O compression&lt;span style="color:#f92672">=&lt;/span>lz4 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O atime&lt;span style="color:#f92672">=&lt;/span>off &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O xattr&lt;span style="color:#f92672">=&lt;/span>sa &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O dnodesize&lt;span style="color:#f92672">=&lt;/span>auto &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> datapool mirror &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /dev/disk/by-id/nvme-EnterpriseDisk1 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /dev/disk/by-id/nvme-EnterpriseDisk2
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h3 id="four-disks-striped-mirrors-raid10--best-vm-random-iops">Four disks: striped mirrors (RAID10 — best VM random IOPS)&lt;/h3>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>zpool create -n -o ashift&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#ae81ff">12&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O compression&lt;span style="color:#f92672">=&lt;/span>lz4 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O atime&lt;span style="color:#f92672">=&lt;/span>off &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O xattr&lt;span style="color:#f92672">=&lt;/span>sa &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O dnodesize&lt;span style="color:#f92672">=&lt;/span>auto &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> datapool &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> mirror /dev/disk/by-id/ata-Disk1 /dev/disk/by-id/ata-Disk2 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> mirror /dev/disk/by-id/ata-Disk3 /dev/disk/by-id/ata-Disk4
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h3 id="four-disks-raidz1--raidz2-bulk-media--backups-not-iops-heavy-vms">Four disks: RAIDZ1 / RAIDZ2 (bulk media &amp;amp; backups, not IOPS-heavy VMs)&lt;/h3>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>zpool create -n -o ashift&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#ae81ff">12&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O compression&lt;span style="color:#f92672">=&lt;/span>lz4 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O atime&lt;span style="color:#f92672">=&lt;/span>off &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O xattr&lt;span style="color:#f92672">=&lt;/span>sa &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> -O dnodesize&lt;span style="color:#f92672">=&lt;/span>auto &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> datapool raidz2 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /dev/disk/by-id/ata-Disk1 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /dev/disk/by-id/ata-Disk2 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /dev/disk/by-id/ata-Disk3 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> /dev/disk/by-id/ata-Disk4
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Pool / dataset flag&lt;/th>
&lt;th scope="col">Why it belongs on Proxmox&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Pool / dataset flag">&lt;code>-o ashift=12&lt;/code>&lt;/td>
&lt;td data-label="Why it belongs on Proxmox">Locks vdev physical sector alignment to &lt;code>2^12 = 4,096 bytes&lt;/code> (4K). &lt;strong>Immutable per vdev after creation.&lt;/strong> Leaving a mis-reporting drive at &lt;code>ashift=9&lt;/code> (512B) causes severe read-modify-write amplification. Check enterprise NVMe datasheets: 8K-native drives use &lt;code>ashift=13&lt;/code>.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Pool / dataset flag">&lt;code>-O compression=lz4&lt;/code>&lt;/td>
&lt;td data-label="Why it belongs on Proxmox">Fast stream compression with early-abort on incompressible blocks; essentially free CPU overhead on modern x86 while shrinking OS blocks, logs, and sparse VM extents.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Pool / dataset flag">&lt;code>-O atime=off&lt;/code>&lt;/td>
&lt;td data-label="Why it belongs on Proxmox">Stops ZFS from writing a new metadata block every time a file is read.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Pool / dataset flag">&lt;code>-O xattr=sa&lt;/code> + &lt;code>-O dnodesize=auto&lt;/code>&lt;/td>
&lt;td data-label="Why it belongs on Proxmox">Stores Linux extended attributes directly inside system-attribute bonus buffers rather than hidden directory trees — major IOPS win for LXC containers and Samba shares.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Verify the created pool with &lt;code>zpool status datapool&lt;/code> and &lt;code>zpool get ashift datapool&lt;/code>.&lt;/p>
&lt;h2 id="add-the-pool-to-proxmox-storage">Add the pool to Proxmox storage&lt;/h2>
&lt;p>Register the pool with Proxmox (&lt;code>--sparse 1&lt;/code> enables thin provisioning so a 64 GiB virtual disk only consumes blocks actually written):&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>pvesm add zfspool datapool-storage &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --pool datapool &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --content rootdir,images &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --sparse &lt;span style="color:#ae81ff">1&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Or add it in the GUI under &lt;strong>Datacenter → Storage → Add → ZFS&lt;/strong> and tick &lt;strong>Thin provision&lt;/strong>.&lt;/p>
&lt;h2 id="tune-zfs-arc-for-a-shared-host">Tune ZFS ARC for a shared host&lt;/h2>
&lt;p>ARC (Adaptive Replacement Cache) is ZFS&amp;rsquo;s RAM read cache. Outdated forum posts still repeat &amp;ldquo;ZFS eats 50% of your RAM by default on Proxmox&amp;rdquo; as an unconditional fact. In 2026, what your host actually caps ARC at depends on &lt;strong>how and when Proxmox was installed&lt;/strong>. Check the three distinct regimes before editing anything:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Host installation history&lt;/th>
&lt;th scope="col">Default &lt;code>zfs_arc_max&lt;/code> ceiling&lt;/th>
&lt;th scope="col">Effective cap on a &lt;code>64 GiB&lt;/code> host&lt;/th>
&lt;th scope="col">Where it comes from&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Host installation history">&lt;strong>Fresh Proxmox VE 8.1+ or VE 9 ISO install&lt;/strong>&lt;/td>
&lt;td data-label="Default zfs_arc_max ceiling">&lt;strong>10% of physical RAM&lt;/strong>, clamped between &lt;code>1 GiB&lt;/code> min and &lt;code>16 GiB&lt;/code> max&lt;/td>
&lt;td data-label="Effective cap on a 64 GiB host">&lt;strong>&lt;code>6.4 GiB&lt;/code>&lt;/strong> (or &lt;code>16 GiB&lt;/code> on a &lt;code>256 GiB&lt;/code> host)&lt;/td>
&lt;td data-label="Where it comes from">Proxmox ISO installer writes &lt;code>options zfs zfs_arc_max=...&lt;/code> into &lt;code>/etc/modprobe.d/zfs.conf&lt;/code> (&lt;a href="https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_zfs" rel="noopener">Proxmox ZFS docs&lt;/a>)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Host installation history">&lt;strong>In-place upgrade from Proxmox VE 8.0 or 7.x&lt;/strong>&lt;/td>
&lt;td data-label="Default zfs_arc_max ceiling">Historic &lt;strong>50% of physical RAM&lt;/strong> (or whatever custom &lt;code>zfs.conf&lt;/code> existed)&lt;/td>
&lt;td data-label="Effective cap on a 64 GiB host">&lt;strong>&lt;code>32 GiB&lt;/code>&lt;/strong> unless manually edited&lt;/td>
&lt;td data-label="Where it comes from">Upgrades preserve existing &lt;code>/etc/modprobe.d/zfs.conf&lt;/code> (or lack of one under OpenZFS &amp;lt;= 2.2)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Host installation history">&lt;strong>Uncapped Linux OpenZFS 2.3+ (&lt;code>zfs_arc_max=0&lt;/code>)&lt;/strong> — e.g., Proxmox installed over Debian 12/13 without &lt;code>zfs.conf&lt;/code>&lt;/td>
&lt;td data-label="Default zfs_arc_max ceiling">&lt;code>max(RAM - 1 GiB, 5/8 × RAM)&lt;/code>&lt;/td>
&lt;td data-label="Effective cap on a 64 GiB host">&lt;strong>&lt;code>63 GiB&lt;/code>&lt;/strong> (&lt;code>64 - 1 GiB&lt;/code>)&lt;/td>
&lt;td data-label="Where it comes from">Upstream &lt;a href="https://openzfs.github.io/openzfs-docs/man/v2.3/4/zfs.4.html" rel="noopener">OpenZFS 2.3 &lt;code>zfs(4)&lt;/code>&lt;/a> raised the Linux default to match FreeBSD&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Never guess which row applies. Read the active kernel parameter directly:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># 0 means uncapped upstream default; non-zero is bytes&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat /sys/module/zfs/parameters/zfs_arc_max
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat /sys/module/zfs/parameters/zfs_arc_min
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>arc_summary | head -n &lt;span style="color:#ae81ff">35&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>grep -RnsE &lt;span style="color:#e6db74">&amp;#39;^[[:space:]]*options[[:space:]]+zfs[[:space:]]&amp;#39;&lt;/span> /etc/modprobe.d/
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Leave working caps alone. If a fresh VE 9 install already capped your &lt;code>64 GiB&lt;/code> box at &lt;code>~6.4 GiB&lt;/code> and your guests have plenty of free memory, leave it unchanged — or raise it to &lt;code>10–16 GiB&lt;/code> if &lt;code>arc_summary&lt;/code> shows hit rates below 85% on a storage-heavy host. Conversely, if an uncapped host (&lt;code>0&lt;/code>) or legacy &lt;code>50%&lt;/code> host is starving QEMU VMs and triggering the Linux OOM-killer (because wired KVM guest pages and ZFS ARC shrink too slowly when a VM boots fast), set an explicit byte ceiling in &lt;code>/etc/modprobe.d/zfs.conf&lt;/code>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Example: 64 GiB host running 44 GiB of VMs + 6 GiB OS headroom -&amp;gt; 12 GiB ARC&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># 12 * 1024^3 = 12884901888 bytes&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">if&lt;/span> &lt;span style="color:#f92672">[&lt;/span> -f /etc/modprobe.d/zfs.conf &lt;span style="color:#f92672">]&lt;/span>; &lt;span style="color:#66d9ef">then&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> cp -a /etc/modprobe.d/zfs.conf &lt;span style="color:#e6db74">&amp;#34;/etc/modprobe.d/zfs.conf.bak.&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>date -u +%Y%m%dT%H%M%SZ&lt;span style="color:#66d9ef">)&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">fi&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &amp;gt; /etc/modprobe.d/zfs.conf &lt;span style="color:#e6db74">&amp;lt;&amp;lt;&amp;#39;EOF&amp;#39;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">options zfs zfs_arc_max=12884901888
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">EOF&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># MANDATORY when Proxmox boots from ZFS (rpool), because zfs.ko loads inside initramfs!&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>update-initramfs -u -k all
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Two rules from &lt;a href="https://github.com/proxmox/pve-docs/blob/master/local-zfs.adoc" rel="noopener">Proxmox&amp;rsquo;s ZFS administration guide&lt;/a> prevent silent ignores:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>&lt;code>zfs_arc_min&lt;/code> trap on high-RAM servers:&lt;/strong> &lt;code>zfs_arc_min&lt;/code> defaults to &lt;code>1/32&lt;/code> of system RAM (&lt;code>8 GiB&lt;/code> on a &lt;code>256 GiB&lt;/code> server, &lt;code>16 GiB&lt;/code> on &lt;code>512 GiB&lt;/code>). If you set &lt;code>zfs_arc_max&lt;/code> &lt;em>equal to or below&lt;/em> &lt;code>zfs_arc_min&lt;/code>, OpenZFS ignores your &lt;code>zfs_arc_max&lt;/code> completely! Always set &lt;code>zfs_arc_min&lt;/code> lower (at most &lt;code>zfs_arc_max - 1&lt;/code>) when capping large-memory hosts tightly.&lt;/li>
&lt;li>&lt;strong>Apply live now, persist via &lt;code>initramfs&lt;/code>:&lt;/strong> Writing bytes straight to &lt;code>/sys/module/zfs/parameters/zfs_arc_max&lt;/code> (&lt;code>echo 12884901888 &amp;gt; /sys/module/zfs/parameters/zfs_arc_max&lt;/code>) adjusts the cap immediately without a reboot, while &lt;code>update-initramfs -u -k all&lt;/code> guarantees the next reboot keeps it. Model your exact VM + ARC split interactively in the &lt;a href="https://techfuelhq.com/tools/proxmox-capacity-planner/">Proxmox VM Capacity Planner&lt;/a>.&lt;/li>
&lt;/ol>
&lt;h2 id="create-datasets-with-lz4-vs-zstd-compression">Create datasets with &lt;code>lz4&lt;/code> vs &lt;code>zstd&lt;/code> compression&lt;/h2>
&lt;p>Never dump backups, ISOs, and media directly into the pool&amp;rsquo;s root dataset. Create child datasets so each workload gets the right &lt;code>compression&lt;/code> and &lt;code>recordsize&lt;/code>:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Dataset workload&lt;/th>
&lt;th scope="col">Recommended &lt;code>compression&lt;/code>&lt;/th>
&lt;th scope="col">Recommended &lt;code>recordsize&lt;/code>&lt;/th>
&lt;th scope="col">Why&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Dataset workload">VM zvols &amp;amp; LXC rootfs (&lt;code>datapool/vm-disks&lt;/code>)&lt;/td>
&lt;td data-label="Recommended compression">&lt;code>lz4&lt;/code>&lt;/td>
&lt;td data-label="Recommended recordsize">Pool default (&lt;code>8K&lt;/code>/&lt;code>16K&lt;/code> zvols, &lt;code>128K&lt;/code> LXC)&lt;/td>
&lt;td data-label="Why">Minimal latency and CPU cost; skips uncompressible blocks immediately&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dataset workload">Proxmox / PBS backups &amp;amp; logs (&lt;code>datapool/backups&lt;/code>)&lt;/td>
&lt;td data-label="Recommended compression">&lt;code>zstd-3&lt;/code>&lt;/td>
&lt;td data-label="Recommended recordsize">&lt;code>1M&lt;/code>&lt;/td>
&lt;td data-label="Why">Higher compression ratio on &lt;code>.vma&lt;/code>, &lt;code>.tar&lt;/code>, and structured text at modest CPU cost&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dataset workload">PostgreSQL / MariaDB bind mounts (&lt;code>datapool/db&lt;/code>)&lt;/td>
&lt;td data-label="Recommended compression">&lt;code>lz4&lt;/code> or &lt;code>zstd-3&lt;/code>&lt;/td>
&lt;td data-label="Recommended recordsize">&lt;code>16K&lt;/code> (match Postgres &lt;code>8K&lt;/code>/&lt;code>16K&lt;/code> page size)&lt;/td>
&lt;td data-label="Why">Prevents 128K read-modify-write amplification on random database commits&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Dataset workload">Movies, TV, &amp;amp; Lossless/HEVC media (&lt;code>datapool/media&lt;/code>)&lt;/td>
&lt;td data-label="Recommended compression">&lt;code>lz4&lt;/code> or &lt;code>off&lt;/code>&lt;/td>
&lt;td data-label="Recommended recordsize">&lt;code>1M&lt;/code>&lt;/td>
&lt;td data-label="Why">&lt;code>1M&lt;/code> blocks cut metadata overhead on multi-gigabyte MKVs; &lt;code>lz4&lt;/code> early-aborts cleanly on H.265 while still compressing &lt;code>.srt&lt;/code> subtitles and &lt;code>.nfo&lt;/code> sidecars&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>zfs create -o compression&lt;span style="color:#f92672">=&lt;/span>lz4 datapool/vm-disks
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>zfs create -o compression&lt;span style="color:#f92672">=&lt;/span>zstd-3 -o recordsize&lt;span style="color:#f92672">=&lt;/span>1M datapool/backups
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>zfs create -o compression&lt;span style="color:#f92672">=&lt;/span>lz4 -o recordsize&lt;span style="color:#f92672">=&lt;/span>1M datapool/media
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>zfs get compression,compressratio,recordsize,used,available datapool/vm-disks datapool/backups datapool/media
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Skip ZFS deduplication completely. Never set &lt;code>dedup=on&lt;/code> on a homelab host. In-RAM deduplication tables devour roughly 3–5 GiB of host memory per TiB of stored data and can stall pool imports entirely during an emergency recovery when system RAM runs tight, whereas &lt;code>lz4&lt;/code> and &lt;code>zstd-3&lt;/code> deliver nearly all of the real-world space savings at near-zero operational risk.&lt;/p>
&lt;h2 id="confirm-automatic-scrubs">Confirm automatic scrubs&lt;/h2>
&lt;p>Scrubs catch silent bit rot early. Debian and Proxmox ship &lt;code>/etc/cron.d/zfsutils-linux&lt;/code>, which invokes &lt;code>/usr/lib/zfs-linux/scrub&lt;/code> at &lt;code>00:24&lt;/code> on the second Sunday of every month across all healthy imported pools, so verify that cron file on your host rather than assuming a custom timer is active:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>cat /etc/cron.d/zfsutils-linux
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>zpool status datapool | grep scan
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Avoid running duplicate scrub schedules. If you prefer per-pool systemd timers (&lt;code>systemctl enable --now zfs-scrub-monthly@datapool.timer&lt;/code>), comment out the &lt;code>/etc/cron.d/zfsutils-linux&lt;/code> entry so both schedules never collide on the same Sunday night, and remember you can pause a long HDD scrub during daytime work with &lt;code>zpool scrub -p datapool&lt;/code> before resuming it later with &lt;code>zpool scrub datapool&lt;/code>.&lt;/p>
&lt;h2 id="snapshot-policy-and-off-host-replication">Snapshot policy and off-host replication&lt;/h2>
&lt;p>Local snapshots are not backups. While &lt;code>zfs snapshot datapool/vm-disks@$(date +%Y-%m-%d)&lt;/code> gives instant rollback before risky updates and &lt;a href="https://github.com/jimsalterjrs/sanoid" rel="noopener">&lt;code>sanoid&lt;/code>&lt;/a> (&lt;code>apt install sanoid&lt;/code>) automates hourly and daily retention pruning cleanly, local snapshots still live on the exact same physical pool and exclude &lt;code>/etc/pve/qemu-server/&amp;lt;vmid&amp;gt;.conf&lt;/code>.&lt;/p>
&lt;p>For full Proxmox guest recovery (VM disks + config + deduplication), run &lt;a href="https://pbs.proxmox.com/docs/introduction.html" rel="noopener">Proxmox Backup Server&lt;/a> on separate hardware. For raw dataset replication (&lt;code>datapool/media&lt;/code> to a remote ZFS NAS), use &lt;code>zfs send&lt;/code> / &lt;code>zfs receive&lt;/code> with &lt;code>set -o pipefail&lt;/code> (or &lt;code>syncoid&lt;/code>):&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>set -o pipefail
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>snapshot&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#34;replication-&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>date -u +%Y%m%dT%H%M%SZ&lt;span style="color:#66d9ef">)&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>zfs snapshot &lt;span style="color:#e6db74">&amp;#34;datapool/media@&lt;/span>$snapshot&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Initial full send to an empty remote target dataset&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>zfs send &lt;span style="color:#e6db74">&amp;#34;datapool/media@&lt;/span>$snapshot&lt;span style="color:#e6db74">&amp;#34;&lt;/span> | &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> ssh root@192.168.1.20 &lt;span style="color:#e6db74">&amp;#34;zfs receive backuppool/media-from-proxmox&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Subsequent runs send incrementals (&lt;code>zfs send -i &amp;quot;datapool/media@$previous&amp;quot; &amp;quot;datapool/media@$snapshot&amp;quot;&lt;/code>) per &lt;a href="https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-send.8.html" rel="noopener">OpenZFS &lt;code>zfs-send(8)&lt;/code>&lt;/a> and &lt;a href="https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-receive.8.html" rel="noopener">&lt;code>zfs-receive(8)&lt;/code>&lt;/a>, and you should never slap &lt;code>zfs receive -F&lt;/code> onto an unattended replication script to silence a snapshot mismatch before inspecting both datasets with &lt;code>zfs list -t snapshot&lt;/code>. Force flags destroy diverging snapshots.&lt;/p>
&lt;h2 id="monitor-pool-health-and-avoid-common-mistakes">Monitor pool health and avoid common mistakes&lt;/h2>
&lt;p>Check &lt;code>zpool status -v&lt;/code>, &lt;code>zpool list&lt;/code> (keep pool occupancy under 80% so ZFS copy-on-write block allocation never fragments into slow metaslab searches), and &lt;code>smartctl&lt;/code> SSD wear every month. Full pools crawl. Four mistakes cause nearly every homelab ZFS ticket:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Passing &lt;code>/dev/sdX&lt;/code> instead of &lt;code>/dev/disk/by-id/&lt;/code>.&lt;/strong> Verify model + serial every single time.&lt;/li>
&lt;li>&lt;strong>Building ZFS on consumer QLC NVMe sticks.&lt;/strong> Watch &lt;code>pmxcfs&lt;/code> + ZIL sync writes eat their endurance and stall VM I/O; buy used or new enterprise PLP SSDs instead.&lt;/li>
&lt;li>&lt;strong>Creating datasets per VM by hand.&lt;/strong> Register the parent dataset via &lt;code>pvesm&lt;/code> and let Proxmox manage &lt;code>vm-100-disk-0&lt;/code> zvols automatically.&lt;/li>
&lt;li>&lt;strong>Editing &lt;code>/etc/modprobe.d/zfs.conf&lt;/code> without &lt;code>update-initramfs -u -k all&lt;/code>.&lt;/strong> On a ZFS boot pool (&lt;code>rpool&lt;/code>), skipping initramfs regeneration means your next reboot silently reverts to the old ARC ceiling.&lt;/li>
&lt;/ul>
&lt;hr>
&lt;p>&lt;em>For topology math (mirrors vs RAIDZ, when a PLP SLOG or special vdev actually helps), read the &lt;a href="https://techfuelhq.com/homelab/proxmox-truenas-unraid-storage-backend-2026/">ZFS storage backend comparison&lt;/a>. To model guest RAM alongside your exact ARC cap, open the &lt;a href="https://techfuelhq.com/tools/proxmox-capacity-planner/">Proxmox VM Capacity Planner&lt;/a>.&lt;/em>&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_zfs" rel="noopener">Proxmox VE Administration Guide: ZFS on Linux&lt;/a> and &lt;a href="https://pve.proxmox.com/wiki/ZFS_on_Linux" rel="noopener">Proxmox Wiki: ZFS on Linux&lt;/a> — official 10% (max 16 GiB) installer ARC ceiling on PVE 8.1+/9, &lt;code>/etc/modprobe.d/zfs.conf&lt;/code>, &lt;code>zfs_arc_min&lt;/code> interaction, &lt;code>update-initramfs -u -k all&lt;/code>, &lt;code>ashift=12&lt;/code>, and enterprise PLP SSD recommendations.&lt;/li>
&lt;li>&lt;a href="https://pve.proxmox.com/pve-docs/chapter-pmxcfs.html" rel="noopener">Proxmox Cluster File System (&lt;code>pmxcfs&lt;/code>)&lt;/a> — official architecture of &lt;code>/etc/pve&lt;/code> backed by &lt;code>/var/lib/pve-cluster/config.db&lt;/code> SQLite synchronous disk persistence.&lt;/li>
&lt;li>&lt;a href="https://openzfs.github.io/openzfs-docs/man/v2.3/4/zfs.4.html" rel="noopener">OpenZFS 2.3 &lt;code>zfs(4)&lt;/code> manual&lt;/a> and &lt;a href="https://openzfs.github.io/openzfs-docs/Performance%20and%20Tuning/Module%20Parameters.html" rel="noopener">OpenZFS Module Parameters&lt;/a> — uncapped Linux &lt;code>zfs_arc_max&lt;/code> formula (&lt;code>max(allmem - 1 GiB, 5/8 × allmem)&lt;/code>), &lt;code>compression=lz4&lt;/code>/&lt;code>zstd&lt;/code>, and &lt;code>xattr=sa&lt;/code>.&lt;/li>
&lt;li>&lt;a href="https://openzfs.github.io/openzfs-docs/man/v2.3/8/zpool-create.8.html" rel="noopener">OpenZFS &lt;code>zpool-create(8)&lt;/code>&lt;/a>, &lt;a href="https://openzfs.github.io/openzfs-docs/man/master/8/zpool-scrub.8.html" rel="noopener">&lt;code>zpool-scrub(8)&lt;/code>&lt;/a>, &lt;a href="https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-send.8.html" rel="noopener">&lt;code>zfs-send(8)&lt;/code>&lt;/a>, and &lt;a href="https://openzfs.github.io/openzfs-docs/man/v2.3/8/zfs-receive.8.html" rel="noopener">&lt;code>zfs-receive(8)&lt;/code>&lt;/a> — dry-run &lt;code>-n&lt;/code>, &lt;code>ashift&lt;/code>, scrub pausing, and replication flags.&lt;/li>
&lt;li>&lt;a href="https://pbs.proxmox.com/docs/introduction.html" rel="noopener">Proxmox Backup Server documentation&lt;/a> and &lt;a href="https://github.com/jimsalterjrs/sanoid" rel="noopener">Sanoid / Syncoid&lt;/a> — VM backup integration and automated ZFS snapshot lifecycle management.&lt;/li>
&lt;/ul></description></item><item><title>Jellyfin Docker Compose Setup &amp; GPU Transcoding (2026)</title><link>https://techfuelhq.com/tutorials/jellyfin-setup-docker-homelab-2026/</link><pubDate>Mon, 25 May 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/tutorials/jellyfin-setup-docker-homelab-2026/</guid><atom:updated>2026-11-14T10:50:00Z</atom:updated><description>&lt;p>By &lt;a href="https://techfuelhq.com/author/lk-wood-iv/">LK Wood IV&lt;/a> · 2026-05-25 · Updated 2026-11-14 · ~14 min read · St. Louis County, MO&lt;/p>
&lt;p>Jellyfin gives you local media streaming and hardware-accelerated GPU transcoding without a subscription, mandatory cloud login, or external authentication check. Still deciding between platforms? Read our &lt;a href="https://techfuelhq.com/articles/jellyfin-vs-plex-2026/">Jellyfin vs Plex breakdown&lt;/a> first, then come back here to build it.&lt;/p>
&lt;p>Four mistakes break most Jellyfin containers.&lt;/p>
&lt;p>Unpinned &lt;code>:latest&lt;/code> tags upgrade SQLite schemas overnight without a backup, &lt;code>/config&lt;/code> folders on NAS shares lock up during scans, &lt;code>/dev/dri&lt;/code> lacks the host&amp;rsquo;s numeric &lt;code>render&lt;/code> group ID, and unconfigured reverse proxies mask remote WAN viewers as local LAN clients. I structure every homelab Jellyfin stack to prevent all four before adding a single movie library.&lt;/p>
&lt;h2 id="step-1-separate-fast-ssd-config-storage-from-bulk-hdd-media">Step 1: Separate fast SSD &lt;code>/config&lt;/code> storage from bulk HDD &lt;code>/media&lt;/code>&lt;/h2>
&lt;p>Split storage across two tiers first. Changing library paths inside the container later forces Jellyfin to rescan metadata and rebuild watch state from scratch.&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Fast local NVMe / SSD (&lt;code>/opt/stacks/jellyfin/config&lt;/code> and &lt;code>/opt/stacks/jellyfin/cache&lt;/code>):&lt;/strong> Holds SQLite databases (&lt;code>library.db&lt;/code>, &lt;code>jellyfin.db&lt;/code>), poster images, trickplay scrub previews, and temporary HLS transcode segments. Never place &lt;code>/config&lt;/code> on an NFS or SMB network mount; SQLite file locking over network filesystems triggers &lt;code>SQLite Error 5: 'database is locked'&lt;/code> crashes during library scans.&lt;/li>
&lt;li>&lt;strong>Bulk HDD array or NAS mount (&lt;code>/mnt/media/{movies,tv,music}&lt;/code>):&lt;/strong> Holds multi-terabyte video and audio files, mounted into the container &lt;strong>read-only (&lt;code>:ro&lt;/code>)&lt;/strong> unless you explicitly want Jellyfin deleting media or writing &lt;code>.nfo&lt;/code> sidecars back into your archive.&lt;/li>
&lt;/ol>
&lt;p>Create the local SSD directories and check the numeric &lt;code>render&lt;/code> group ID on your Linux host for Intel Quick Sync or AMD VAAPI hardware acceleration:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>sudo mkdir -p /opt/stacks/jellyfin/&lt;span style="color:#f92672">{&lt;/span>config,cache&lt;span style="color:#f92672">}&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sudo chown -R 1000:1000 /opt/stacks/jellyfin
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Check that the Linux kernel exposes your GPU render node&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ls -l /dev/dri
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Example output: crw-rw---- 1 root render 226, 128 ... renderD128&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Print the exact numeric GID for &amp;#39;render&amp;#39; (e.g. 105, 107, or 109) — copy this number!&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>getent group render | cut -d: -f3
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Write down that numeric GID (for example &lt;code>109&lt;/code>). Names fail across container boundaries. Docker&amp;rsquo;s &lt;code>group_add:&lt;/code> directive inside the official image needs the host&amp;rsquo;s numeric GID, because the container&amp;rsquo;s internal &lt;code>/etc/group&lt;/code> file may assign a different number (or none at all) to the name &lt;code>render&lt;/code>.&lt;/p>
&lt;h2 id="step-2-pinned-reproducible-composeyaml">Step 2: Pinned, reproducible &lt;code>compose.yaml&lt;/code>&lt;/h2>
&lt;p>Pinning a concrete release tag such as &lt;code>jellyfin/jellyfin:12.4&lt;/code> (rather than floating &lt;code>:latest&lt;/code>) ensures major server upgrades only run after you snapshot or back up &lt;code>/config&lt;/code>. &lt;a href="https://jellyfin.org/docs/general/installation/container/" rel="noopener">Jellyfin&amp;rsquo;s official container guide&lt;/a> recommends bind mounts for straightforward path inspection and clean backups.&lt;/p>
&lt;h3 id="option-a-official-jellyfinjellyfin-with-intel-quick-sync--amd-vaapi-recommended">Option A: Official &lt;code>jellyfin/jellyfin&lt;/code> with Intel Quick Sync / AMD VAAPI (Recommended)&lt;/h3>
&lt;p>Save &lt;code>/opt/stacks/jellyfin/compose.yaml&lt;/code>, replacing &lt;code>109&lt;/code> under &lt;code>group_add&lt;/code> with the exact number &lt;code>getent group render | cut -d: -f3&lt;/code> printed on your host:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># /opt/stacks/jellyfin/compose.yaml&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">jellyfin&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">jellyfin/jellyfin:12.4&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">container_name&lt;/span>: &lt;span style="color:#ae81ff">jellyfin&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">user&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;1000:1000&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">group_add&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#e6db74">&amp;#34;109&amp;#34;&lt;/span> &lt;span style="color:#75715e"># &amp;lt;-- Replace with output of: getent group render | cut -d: -f3&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">TZ=America/Chicago&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">JELLYFIN_PublishedServerUrl=https://jellyfin.yourdomain.com&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">volumes&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">./config:/config&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">./cache:/cache&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">type&lt;/span>: &lt;span style="color:#ae81ff">bind&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">source&lt;/span>: &lt;span style="color:#ae81ff">/mnt/media/movies&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">target&lt;/span>: &lt;span style="color:#ae81ff">/media/movies&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">read_only&lt;/span>: &lt;span style="color:#66d9ef">true&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">type&lt;/span>: &lt;span style="color:#ae81ff">bind&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">source&lt;/span>: &lt;span style="color:#ae81ff">/mnt/media/tv&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">target&lt;/span>: &lt;span style="color:#ae81ff">/media/tv&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">read_only&lt;/span>: &lt;span style="color:#66d9ef">true&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#f92672">type&lt;/span>: &lt;span style="color:#ae81ff">bind&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">source&lt;/span>: &lt;span style="color:#ae81ff">/mnt/media/music&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">target&lt;/span>: &lt;span style="color:#ae81ff">/media/music&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">read_only&lt;/span>: &lt;span style="color:#66d9ef">true&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">devices&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">/dev/dri:/dev/dri&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">ports&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#e6db74">&amp;#34;8096:8096/tcp&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#e6db74">&amp;#34;7359:7359/udp&amp;#34;&lt;/span> &lt;span style="color:#75715e"># Optional: local LAN client auto-discovery&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">restart&lt;/span>: &lt;span style="color:#ae81ff">unless-stopped&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Why each line earns its spot:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>&lt;code>image: jellyfin/jellyfin:12.4&lt;/code>&lt;/strong>: Locks the container to release &lt;code>12.4&lt;/code> instead of pulling breaking updates unattended (&lt;a href="https://docs.docker.com/reference/cli/docker/image/pull/" rel="noopener">Docker pull reference&lt;/a>).&lt;/li>
&lt;li>&lt;strong>&lt;code>group_add: [&amp;quot;109&amp;quot;]&lt;/code> + &lt;code>devices: [&amp;quot;/dev/dri:/dev/dri&amp;quot;]&lt;/code>&lt;/strong>: Grants UID &lt;code>1000&lt;/code> direct access to &lt;code>/dev/dri/renderD128&lt;/code> without running Jellyfin as &lt;code>root&lt;/code>.&lt;/li>
&lt;li>&lt;strong>&lt;code>JELLYFIN_PublishedServerUrl&lt;/code>&lt;/strong>: Tells Jellyfin the canonical external URL to advertise during client discovery and API redirects behind a reverse proxy.&lt;/li>
&lt;li>&lt;strong>&lt;code>read_only: true&lt;/code> media mounts&lt;/strong>: Prevents an accidental click in the web UI from deleting movies on your NAS while keeping &lt;code>./config&lt;/code> and &lt;code>./cache&lt;/code> writable on local SSD storage.&lt;/li>
&lt;/ul>
&lt;h3 id="option-b-linuxserverio-image-or-nvidia-nvenc-compose">Option B: LinuxServer.io image or NVIDIA NVENC Compose&lt;/h3>
&lt;p>If you prefer &lt;a href="https://docs.linuxserver.io/images/docker-jellyfin/" rel="noopener">LinuxServer&amp;rsquo;s Jellyfin image&lt;/a> (which maps &lt;code>PUID&lt;/code>/&lt;code>PGID&lt;/code> and adjusts &lt;code>/dev/dri&lt;/code> ACLs in its startup init) or you pass an NVIDIA GPU via the NVIDIA Container Toolkit (covered in our &lt;a href="https://techfuelhq.com/articles/best-gpu-plex-jellyfin-transcode-2026/">GPU transcoding guide&lt;/a>), pin LinuxServer&amp;rsquo;s release tag (&lt;code>version-12.4ubu2604&lt;/code>) and keep all variables under a single &lt;code>environment:&lt;/code> key (&lt;a href="https://yaml.org/spec/1.2.2/" rel="noopener">YAML 1.2.2&lt;/a> forbids duplicate mapping keys):&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">services&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">jellyfin&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">image&lt;/span>: &lt;span style="color:#ae81ff">lscr.io/linuxserver/jellyfin:version-12.4ubu2604&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">container_name&lt;/span>: &lt;span style="color:#ae81ff">jellyfin&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">restart&lt;/span>: &lt;span style="color:#ae81ff">unless-stopped&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">environment&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">PUID=1000&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">PGID=1000&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">TZ=America/Chicago&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">JELLYFIN_PublishedServerUrl=https://jellyfin.yourdomain.com&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">NVIDIA_VISIBLE_DEVICES=all&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">volumes&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">./config:/config&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">./cache:/transcode&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">/mnt/media/movies:/media/movies:ro&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#ae81ff">/mnt/media/tv:/media/tv:ro&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">ports&lt;/span>:
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> - &lt;span style="color:#e6db74">&amp;#34;8096:8096&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">runtime&lt;/span>: &lt;span style="color:#ae81ff">nvidia&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>&lt;em>(If attaching Jellyfin to an external reverse-proxy Docker network such as &lt;code>networks: [proxy]&lt;/code> with &lt;code>external: true&lt;/code>, create that network first with &lt;code>docker network create proxy&lt;/code>; &lt;a href="https://docs.docker.com/reference/compose-file/networks/" rel="noopener">Docker Compose networks&lt;/a> halt startup if an external network does not exist yet.)&lt;/em>&lt;/p>
&lt;p>Start the stack and watch initial database creation:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>cd /opt/stacks/jellyfin
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose up -d
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker compose logs -f jellyfin
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Open &lt;code>http://&amp;lt;your-host-ip&amp;gt;:8096&lt;/code> to complete the setup wizard: create your admin user, add &lt;code>/media/movies&lt;/code> and &lt;code>/media/tv&lt;/code> as libraries, and set Dashboard → Playback → Transcoding → &lt;strong>Transcode path&lt;/strong> to &lt;code>/cache&lt;/code> (official image) or &lt;code>/transcode&lt;/code> (LinuxServer image).&lt;/p>
&lt;h2 id="jellyfin-ports-8096-8920-7359--reverse-proxy-knownproxies-trust">Jellyfin ports (&lt;code>8096&lt;/code>, &lt;code>8920&lt;/code>, &lt;code>7359&lt;/code>) &amp;amp; reverse-proxy &lt;code>KnownProxies&lt;/code> trust&lt;/h2>
&lt;p>Per &lt;a href="https://jellyfin.org/docs/general/post-install/networking/" rel="noopener">Jellyfin&amp;rsquo;s official networking documentation&lt;/a>, &lt;code>8096/TCP&lt;/code> serves HTTP web UI and media traffic, &lt;code>8920/TCP&lt;/code> is Jellyfin&amp;rsquo;s optional built-in HTTPS port (leave disabled when terminating TLS on a reverse proxy), and &lt;code>7359/UDP&lt;/code> handles local-subnet client auto-discovery. Never expose &lt;code>8096/TCP&lt;/code> directly to the internet.&lt;/p>
&lt;p>When placing Nginx Proxy Manager, Caddy, or Traefik in front of Jellyfin (&lt;code>https://jellyfin.yourdomain.com&lt;/code> → &lt;code>http://jellyfin:8096&lt;/code> with Websockets Support ON), configure client-IP trust inside Dashboard → Networking:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Known proxies:&lt;/strong> Enter the exact IP address (or static container IP on your proxy bridge network, e.g. &lt;code>172.19.0.2&lt;/code> or &lt;code>192.168.1.20&lt;/code>) of your reverse proxy. Never enter &lt;code>0.0.0.0/0&lt;/code>, which lets external clients forge &lt;code>X-Forwarded-For&lt;/code> headers.&lt;/li>
&lt;li>&lt;strong>LAN networks:&lt;/strong> Explicitly enter your real home LAN subnet CIDR (for example &lt;code>192.168.1.0/24&lt;/code>), not &lt;code>172.16.0.0/12&lt;/code>.&lt;/li>
&lt;li>&lt;strong>Restart Jellyfin&lt;/strong> (&lt;code>docker compose restart jellyfin&lt;/code>) after saving &lt;code>Known proxies&lt;/code> so Kestrel reloads its forwarded-header middleware.&lt;/li>
&lt;/ol>
&lt;p>Skipping &lt;code>KnownProxies&lt;/code> breaks remote bitrate caps silently.&lt;/p>
&lt;p>Without &lt;code>Known proxies&lt;/code> configured, Jellyfin ignores &lt;code>X-Forwarded-For&lt;/code> and thinks every remote phone or hotel TV is connecting from your proxy&amp;rsquo;s local RFC1918 IP. Jellyfin then classifies remote internet viewers as unrestricted LAN sessions, bypassing Internet streaming bitrate limit (Mbps), hammering your home upload bandwidth with 60 Mbps 4K Blu-ray remuxes, and logging every login under the proxy&amp;rsquo;s IP instead of the real client IP. For private remote streaming without opening port &lt;code>443&lt;/code> on your router at all, advertise your LAN via &lt;a href="https://techfuelhq.com/tutorials/tailscale-remote-access-homelab-2026/">Tailscale subnet routing&lt;/a> (&lt;code>tailscale up --advertise-routes=192.168.1.0/24&lt;/code>), while smart TVs that cannot run Tailscale (Roku, LG webOS, Samsung Tizen) can follow our &lt;a href="https://techfuelhq.com/tutorials/jellyfin-remote-access-2026/">Jellyfin remote access decision guide&lt;/a>.&lt;/p>
&lt;h2 id="step-3-verify--enable-hardware-transcoding-vaapi--qsv--nvenc">Step 3: Verify &amp;amp; enable hardware transcoding (&lt;code>VAAPI&lt;/code> / &lt;code>QSV&lt;/code> / &lt;code>NVENC&lt;/code>)&lt;/h2>
&lt;p>Before toggling checkboxes in the Jellyfin web UI, confirm the container can actually open your GPU driver and uses Jellyfin&amp;rsquo;s custom &lt;code>jellyfin-ffmpeg&lt;/code> build. Per &lt;a href="https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/intel/" rel="noopener">Jellyfin&amp;rsquo;s Intel acceleration guide&lt;/a> and &lt;a href="https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/" rel="noopener">acceleration overview&lt;/a>, run both checks from the host shell:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># 1. Confirm Jellyfin&amp;#39;s bundled ffmpeg carries the &amp;#39;-Jellyfin&amp;#39; build suffix&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/ffmpeg -version | head -n &lt;span style="color:#ae81ff">1&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># 2. Verify VAAPI/QSV driver initialization and supported encode/decode profiles&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/vainfo --display drm --device /dev/dri/renderD128
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Only tick codec decode/encode boxes in &lt;strong>Dashboard → Playback → Transcoding&lt;/strong> that appear in your &lt;code>vainfo&lt;/code> output (&lt;code>VAEntrypointVLD&lt;/code> = decode; &lt;code>VAEntrypointEncSlice&lt;/code> / &lt;code>VAEntrypointEncSliceLP&lt;/code> = encode):&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Codec&lt;/th>
&lt;th scope="col">Supported Intel Quick Sync hardware per Jellyfin docs&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Codec">&lt;strong>H.264 8-bit&lt;/strong> decode &amp;amp; encode&lt;/td>
&lt;td data-label="Supported Intel Quick Sync hardware per Jellyfin docs">Broadwell (5th-gen Core) and newer&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Codec">&lt;strong>HEVC 8-bit&lt;/strong> decode &amp;amp; encode&lt;/td>
&lt;td data-label="Supported Intel Quick Sync hardware per Jellyfin docs">Skylake (6th-gen Core) and newer&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Codec">&lt;strong>HEVC 10-bit&lt;/strong> (4K HDR) decode &amp;amp; encode&lt;/td>
&lt;td data-label="Supported Intel Quick Sync hardware per Jellyfin docs">Kaby Lake (7th-gen Core), Apollo/Gemini Lake, N100/N150, and newer&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Codec">&lt;strong>AV1 decode&lt;/strong>&lt;/td>
&lt;td data-label="Supported Intel Quick Sync hardware per Jellyfin docs">Tiger Lake (11th-gen Core), Alder Lake-N (&lt;code>N100&lt;/code>/&lt;code>N150&lt;/code>), and newer&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Codec">&lt;strong>AV1 hardware encode&lt;/strong>&lt;/td>
&lt;td data-label="Supported Intel Quick Sync hardware per Jellyfin docs">&lt;strong>Intel Arc A/B-series&lt;/strong> and &lt;strong>Core Ultra (Meteor Lake+)&lt;/strong> only — &lt;strong>do NOT tick AV1 encode on N100 or 12th/13th/14th-gen desktop iGPUs!&lt;/strong>&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Trigger a test transcode by playing a 4K HEVC video and manually lowering playback quality to &lt;code>1080p - 8 Mbps&lt;/code>, then verify &lt;strong>Dashboard → Active Sessions&lt;/strong> shows &lt;code>(hw)&lt;/code> beside the video codec.&lt;/p>
&lt;h2 id="hardware-transcoding--reverse-proxy-troubleshooting-table">Hardware transcoding &amp;amp; reverse-proxy troubleshooting table&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Symptom in Dashboard or logs&lt;/th>
&lt;th scope="col">Root cause&lt;/th>
&lt;th scope="col">Exact fix&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Symptom in Dashboard or logs">&lt;code>av_hwdevice_ctx_create&lt;/code> / &lt;code>open /dev/dri/renderD128: Permission denied&lt;/code>&lt;/td>
&lt;td data-label="Root cause">Container UID &lt;code>1000&lt;/code> lacks host &lt;code>render&lt;/code> group membership, or unprivileged Proxmox LXC blocks device cgroup access.&lt;/td>
&lt;td data-label="Exact fix">Run &lt;code>getent group render | cut -d: -f3&lt;/code> on the Docker host, put that numeric GID in &lt;code>group_add:&lt;/code>, and run &lt;code>docker compose up -d&lt;/code>. (On Proxmox, run Docker inside a Debian VM with VFIO/iGPU or verify LXC &lt;code>dev0:&lt;/code> passthrough.)&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom in Dashboard or logs">&lt;code>Playback Error: This client isn't compatible with the media&lt;/code> right after enabling QSV/VAAPI&lt;/td>
&lt;td data-label="Root cause">Enabled hardware decoding or encoding for a codec your GPU silicon lacks (most commonly ticking &lt;strong>AV1 encode&lt;/strong> on Intel N100/12th-gen or &lt;strong>HEVC 10-bit&lt;/strong> on 6th-gen Skylake), or Low-Power HuC firmware missing.&lt;/td>
&lt;td data-label="Exact fix">Compare ticked boxes against &lt;code>vainfo&lt;/code> (&lt;code>VAEntrypointVLD&lt;/code> vs &lt;code>VAEntrypointEncSlice&lt;/code>). Untick unsupported codecs and only enable &lt;strong>Low-Power H.264/HEVC hardware encoders&lt;/strong> if host &lt;code>dmesg&lt;/code> confirms GuC/HuC firmware is loaded.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom in Dashboard or logs">CPU spikes to &lt;code>85–100%&lt;/code> even though &lt;code>/dev/dri&lt;/code> is mounted&lt;/td>
&lt;td data-label="Root cause">PGS/VobSub image subtitles are being burned into video frames on CPU, HDR tone-mapping lacks OpenCL runtime, or non-&lt;code>-Jellyfin&lt;/code> &lt;code>ffmpeg&lt;/code> binary is running.&lt;/td>
&lt;td data-label="Exact fix">Select external &lt;code>.srt&lt;/code> text subtitles to test without subtitle burn-in, verify &lt;code>/usr/lib/jellyfin-ffmpeg/ffmpeg&lt;/code> is selected, and install/enable VPP or OpenCL tone-mapping per GPU vendor docs.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom in Dashboard or logs">Remote mobile viewers stream at 60+ Mbps and stutter instead of respecting WAN bitrate cap&lt;/td>
&lt;td data-label="Root cause">Jellyfin sees the reverse proxy&amp;rsquo;s LAN/Docker IP instead of &lt;code>X-Forwarded-For&lt;/code> client IP.&lt;/td>
&lt;td data-label="Exact fix">Add the reverse proxy IP to &lt;strong>Dashboard → Networking → Known proxies&lt;/strong>, set &lt;strong>LAN networks&lt;/strong> to your home subnet CIDR (&lt;code>192.168.1.0/24&lt;/code>), and restart the &lt;code>jellyfin&lt;/code> container.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom in Dashboard or logs">WebSocket sync / real-time dashboard session status fails over HTTPS&lt;/td>
&lt;td data-label="Root cause">Reverse proxy drops &lt;code>Upgrade: websocket&lt;/code> headers.&lt;/td>
&lt;td data-label="Exact fix">Turn &lt;strong>Websockets Support ON&lt;/strong> on the &lt;code>jellyfin.yourdomain.com&lt;/code> proxy host in Nginx Proxy Manager (or pass &lt;code>Upgrade&lt;/code>/&lt;code>Connection&lt;/code> headers in Nginx).&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Symptom in Dashboard or logs">Slow library browsing or &lt;code>SQLite Error 5: 'database is locked'&lt;/code>&lt;/td>
&lt;td data-label="Root cause">&lt;code>/config&lt;/code> resides on an NFS/SMB network share or spinning HDD pool.&lt;/td>
&lt;td data-label="Exact fix">Stop Jellyfin, move &lt;code>./config&lt;/code> and &lt;code>./cache&lt;/code> onto local SSD/NVMe storage, and leave only &lt;code>/media/*&lt;/code> on the NAS share.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="library-naming--safe-container-upgrades">Library naming &amp;amp; safe container upgrades&lt;/h2>
&lt;p>Follow TMDB/TVDB folder conventions so metadata scrapes cleanly on the first scan (&lt;code>/media/movies/The Dark Knight (2008)/The Dark Knight (2008).mkv&lt;/code> and &lt;code>/media/tv/Breaking Bad/Season 01/Breaking Bad S01E01.mkv&lt;/code>, with matching &lt;code>Movie (Year).en.srt&lt;/code> external text subtitles).&lt;/p>
&lt;p>Before bumping your pinned &lt;code>jellyfin/jellyfin:12.4&lt;/code> tag to a newer release, follow &lt;a href="https://jellyfin.org/docs/general/administration/backup-and-restore/" rel="noopener">Jellyfin&amp;rsquo;s backup and restore guide&lt;/a>:&lt;/p>
&lt;ol>
&lt;li>Trigger an application backup under &lt;strong>Dashboard → Backups → Create Backup&lt;/strong>, or stop the container cleanly (&lt;code>docker compose stop jellyfin&lt;/code>) so SQLite WAL files flush and copy &lt;code>./config&lt;/code> to a dated backup archive.&lt;/li>
&lt;li>Update the version tag in &lt;code>compose.yaml&lt;/code>, then run &lt;code>docker compose pull &amp;amp;&amp;amp; docker compose up -d&lt;/code> (&lt;a href="https://docs.docker.com/reference/cli/docker/compose/up/" rel="noopener">Compose &lt;code>up&lt;/code> reference&lt;/a>). Keeping pinned tags means rollbacks only require restoring &lt;code>./config&lt;/code> and reverting the tag line.&lt;/li>
&lt;/ol>
&lt;h2 id="bounded-hardware-reference-intel-n100-quick-sync">Bounded hardware reference: Intel N100 Quick Sync&lt;/h2>
&lt;p>For sizing context on budget mini-PC homelabs, here is published Intel N100 Quick Sync throughput on &lt;code>4K HEVC → 1080p H.264&lt;/code> hardware transcoding (workload depends on source bitrate, HDR tone-mapping settings, and subtitle burn-in):&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Concurrent &lt;code>4K → 1080p&lt;/code> streams&lt;/th>
&lt;th scope="col">Host CPU load&lt;/th>
&lt;th scope="col">Transcode speed (&lt;code>fps&lt;/code>)&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Concurrent 4K → 1080p streams">1 stream&lt;/td>
&lt;td data-label="Host CPU load">~8%&lt;/td>
&lt;td data-label="Transcode speed (fps)">60–90 fps&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Concurrent 4K → 1080p streams">2 streams&lt;/td>
&lt;td data-label="Host CPU load">~14%&lt;/td>
&lt;td data-label="Transcode speed (fps)">55–80 fps each&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Concurrent 4K → 1080p streams">3 streams&lt;/td>
&lt;td data-label="Host CPU load">~20%&lt;/td>
&lt;td data-label="Transcode speed (fps)">45–70 fps each&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Concurrent 4K → 1080p streams">4 streams&lt;/td>
&lt;td data-label="Host CPU load">~28%&lt;/td>
&lt;td data-label="Transcode speed (fps)">40–60 fps each&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>By contrast, pure CPU software transcoding saturates all four N100 cores on a single 4K HEVC remux. Compare Intel Quick Sync, Intel Arc AV1, and NVIDIA NVENC cards in our &lt;a href="https://techfuelhq.com/articles/best-gpu-plex-jellyfin-transcode-2026/">Best GPU for Plex &amp;amp; Jellyfin Transcoding guide&lt;/a>, or pair Jellyfin with &lt;a href="https://techfuelhq.com/tutorials/audiobookshelf-docker-setup-2026/">AudioBookshelf in Docker&lt;/a> for audiobooks and podcasts.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://jellyfin.org/docs/general/installation/container/" rel="noopener">Jellyfin Container Installation&lt;/a> — official &lt;code>jellyfin/jellyfin&lt;/code> Compose specification, bind mounts, and &lt;code>/config&lt;/code> + &lt;code>/cache&lt;/code> layout.&lt;/li>
&lt;li>&lt;a href="https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/" rel="noopener">Jellyfin Hardware Acceleration&lt;/a> and &lt;a href="https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/intel/" rel="noopener">Intel QSV/VAAPI Guide&lt;/a> — &lt;code>/dev/dri&lt;/code> render permissions, &lt;code>-Jellyfin&lt;/code> ffmpeg requirement, &lt;code>vainfo&lt;/code> verification, and per-generation codec support.&lt;/li>
&lt;li>&lt;a href="https://jellyfin.org/docs/general/post-install/networking/" rel="noopener">Jellyfin Networking&lt;/a> — ports &lt;code>8096&lt;/code>/&lt;code>8920&lt;/code>/&lt;code>7359&lt;/code>, &lt;code>Known proxies&lt;/code>, &lt;code>LAN networks&lt;/code> CIDR configuration, and reverse-proxy security.&lt;/li>
&lt;li>&lt;a href="https://jellyfin.org/docs/general/administration/backup-and-restore/" rel="noopener">Jellyfin Backup and Restore&lt;/a> — cold &lt;code>/config&lt;/code> SQLite backup and built-in Dashboard Backups.&lt;/li>
&lt;li>&lt;a href="https://docs.linuxserver.io/images/docker-jellyfin/" rel="noopener">LinuxServer.io Jellyfin Image Docs&lt;/a> — &lt;code>lscr.io/linuxserver/jellyfin&lt;/code> tags, &lt;code>PUID&lt;/code>/&lt;code>PGID&lt;/code>, and NVIDIA runtime setup.&lt;/li>
&lt;li>&lt;a href="https://docs.docker.com/reference/cli/docker/compose/up/" rel="noopener">Docker Compose &lt;code>up&lt;/code> Reference&lt;/a>, &lt;a href="https://docs.docker.com/reference/compose-file/networks/" rel="noopener">Networks Reference&lt;/a>, and &lt;a href="https://docs.docker.com/reference/cli/docker/image/pull/" rel="noopener">Image Pull Reference&lt;/a>.&lt;/li>
&lt;/ul></description></item><item><title>Turn an Old Gaming PC Into a Proxmox Server (2026)</title><link>https://techfuelhq.com/articles/repurpose-gaming-pc-proxmox-server-2026/</link><pubDate>Fri, 01 May 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/repurpose-gaming-pc-proxmox-server-2026/</guid><atom:updated>2026-11-14T10:50:00Z</atom:updated><description>&lt;p>By &lt;a href="https://techfuelhq.com/author/lk-wood-iv/">LK Wood IV&lt;/a> · 2026-05-01 · Updated 2026-11-14 · 16 min read&lt;/p>
&lt;h2 id="key-takeaways">Key takeaways&lt;/h2>
&lt;ul>
&lt;li>A repurposed gaming PC makes a strong Proxmox VE 9.2 host when its headless idle power lands around 25–45W and you actually value its paid-for RAM, PCIe slots, or 3.5-inch drive bays. Check &lt;a href="https://techfuelhq.com/homelab/proxmox-hardware-requirements-2026/">Proxmox hardware requirements&lt;/a> first.&lt;/li>
&lt;li>Leaving a gaming rig on gaming BIOS defaults is why people see 70–110W at idle. Pulling an unneeded discrete GPU once headless, turning off RGB and unused SATA controllers, and enabling CPU Package C-States plus PCIe ASPM routinely cuts wall draw by 30–60W.&lt;/li>
&lt;li>Selling a spare midrange GPU for $100–$200 changes the math in both directions: you can pocket that cash while running the tuned tower at 30W, or apply it toward a $150–$220 N100/N150 mini PC that idles at 8–12W.&lt;/li>
&lt;li>Keep the discrete GPU installed only if a guest needs VFIO passthrough, hardware transcoding, or local LLM VRAM.&lt;/li>
&lt;li>If tuned headless idle stays above 75W without a multi-bay or PCIe workload justifying it, part the desktop out and start on a &lt;a href="https://techfuelhq.com/homelab/best-mini-pcs-homelab-2026/">low-idle mini PC&lt;/a>.&lt;/li>
&lt;/ul>
&lt;h2 id="tldr-keep-the-tower-or-buy-a-mini-pc">TL;DR: Keep the tower or buy a mini PC?&lt;/h2>
&lt;p>Free hardware is only free until the utility meter spins 8,760 hours a year. When I evaluate an old &lt;a href="https://techfuelhq.com/pc-builds/1500-dollar-rtx-5060-ti-1440p-build-2026/">gaming PC build&lt;/a> sitting in a closet, I do not guess from the processor&amp;rsquo;s box TDP. I plug it into a wall meter, strip out gaming-era idle waste, and compare the annual electricity bill against a $150–$220 Intel N100 or N150 mini PC.&lt;/p>
&lt;p>A 2018-or-newer desktop with an Intel Core i5-8400, i5-10400, or Ryzen 5 3600/5600, 16–64GB of DDR4, and a working wired NIC converts cleanly in 90 minutes. If you want pure network storage rather than VMs and containers, the same hardware guidelines apply to a &lt;a href="https://techfuelhq.com/homelab/nas-from-old-pc-2026/">dedicated NAS built from an old PC&lt;/a> or a &lt;a href="https://techfuelhq.com/homelab/proxmox-truenas-unraid-storage-backend-2026/">Proxmox vs TrueNAS vs Unraid storage stack&lt;/a>. For the hypervisor comparison itself, see &lt;a href="https://techfuelhq.com/articles/proxmox-vs-esxi-2025/">Proxmox vs ESXi&lt;/a> and &lt;a href="https://techfuelhq.com/articles/proxmox-vs-hyper-v-2026/">Proxmox vs Hyper-V&lt;/a>.&lt;/p>
&lt;h2 id="247-idle-watt-and-payback-worksheet">24/7 idle-watt and payback worksheet&lt;/h2>
&lt;p>Every continuous watt on a 24/7 server consumes &lt;code>8.76 kWh&lt;/code> per year (&lt;code>Watts ÷ 1,000 × 8,760 hours&lt;/code>). Multiply that annual kWh figure by the supply-plus-delivery rate on your electric bill, not just the generation line item.&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Host profile&lt;/th>
&lt;th scope="col">Typical 24/7 idle watts&lt;/th>
&lt;th scope="col">Annual energy (&lt;code>kWh/yr&lt;/code>)&lt;/th>
&lt;th scope="col">Cost @ &lt;code>$0.12/kWh&lt;/code>&lt;/th>
&lt;th scope="col">Cost @ &lt;code>$0.18/kWh&lt;/code>&lt;/th>
&lt;th scope="col">Cost @ &lt;code>$0.30/kWh&lt;/code>&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Host profile">&lt;strong>Untuned gaming tower&lt;/strong> (discrete GPU left in, RGB on, C-states/ASPM off)&lt;/td>
&lt;td data-label="Typical 24/7 idle watts">65–110W&lt;/td>
&lt;td data-label="Annual energy (kWh/yr)">569–964 kWh&lt;/td>
&lt;td data-label="Cost @ $0.12/kWh">$68–$116/yr&lt;/td>
&lt;td data-label="Cost @ $0.18/kWh">$102–$173/yr&lt;/td>
&lt;td data-label="Cost @ $0.30/kWh">$171–$289/yr&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Host profile">&lt;strong>Tuned headless 65W-class tower&lt;/strong> (GPU pulled, RGB/unused SATA off, C-states + ASPM on)&lt;/td>
&lt;td data-label="Typical 24/7 idle watts">25–40W&lt;/td>
&lt;td data-label="Annual energy (kWh/yr)">219–350 kWh&lt;/td>
&lt;td data-label="Cost @ $0.12/kWh">$26–$42/yr&lt;/td>
&lt;td data-label="Cost @ $0.18/kWh">$39–$63/yr&lt;/td>
&lt;td data-label="Cost @ $0.30/kWh">$66–$105/yr&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Host profile">&lt;strong>Enthusiast / GPU-active tower&lt;/strong> (105W+ chip, multi-chiplet Ryzen X, or dGPU kept for VM/AI)&lt;/td>
&lt;td data-label="Typical 24/7 idle watts">55–80W&lt;/td>
&lt;td data-label="Annual energy (kWh/yr)">482–701 kWh&lt;/td>
&lt;td data-label="Cost @ $0.12/kWh">$58–$84/yr&lt;/td>
&lt;td data-label="Cost @ $0.18/kWh">$87–$126/yr&lt;/td>
&lt;td data-label="Cost @ $0.30/kWh">$145–$210/yr&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Host profile">&lt;strong>New $150–$220 N100 / N150 mini PC&lt;/strong> (16GB RAM, single NVMe, headless)&lt;/td>
&lt;td data-label="Typical 24/7 idle watts">8–12W&lt;/td>
&lt;td data-label="Annual energy (kWh/yr)">70–105 kWh&lt;/td>
&lt;td data-label="Cost @ $0.12/kWh">$8–$13/yr&lt;/td>
&lt;td data-label="Cost @ $0.18/kWh">$13–$19/yr&lt;/td>
&lt;td data-label="Cost @ $0.30/kWh">$21–$32/yr&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Run two concrete payback scenarios before you buy anything:&lt;/p>
&lt;ol>
&lt;li>&lt;strong>Tuned 32W tower vs $180 mini PC (&lt;code>10W&lt;/code> idle = &lt;code>22W&lt;/code> gap, &lt;code>193 kWh/yr&lt;/code>):&lt;/strong> At &lt;code>$0.12/kWh&lt;/code>, that 22W gap costs &lt;code>$23/year&lt;/code>, meaning a $180 mini PC takes nearly &lt;strong>7.8 years&lt;/strong> to earn back its purchase price on electricity alone. Even at &lt;code>$0.18/kWh&lt;/code> (&lt;code>$35/yr&lt;/code> difference), payback stretches past &lt;strong>5 years&lt;/strong>. If you pull an unneeded GTX 1660 Super or RTX 3060 and sell it locally for &lt;code>$110–$170&lt;/code>, keeping the 32W tower puts cash in your pocket on day one while preserving four RAM slots and SATA bays.&lt;/li>
&lt;li>&lt;strong>Stubborn 85W tower vs $180 mini PC (&lt;code>10W&lt;/code> idle = &lt;code>75W&lt;/code> gap, &lt;code>657 kWh/yr&lt;/code>):&lt;/strong> A 75W delta burns &lt;code>$79/yr&lt;/code> at &lt;code>$0.12/kWh&lt;/code>, &lt;code>$118/yr&lt;/code> at &lt;code>$0.18/kWh&lt;/code>, and &lt;code>$197/yr&lt;/code> at &lt;code>$0.30/kWh&lt;/code>. At average US rates, the mini PC pays for itself inside &lt;strong>18 months&lt;/strong> on power alone. If you also sell the old GPU and motherboard/CPU combo for &lt;code>$180+&lt;/code>, swapping to the mini PC is cash-positive immediately.&lt;/li>
&lt;/ol>
&lt;p>Keep the gaming tower even at 45–65W idle when its physical expansion replaces a second box. Four DDR4 DIMM slots holding 64GB or 128GB, PCIe x16/x8 lanes for dual 10GbE SFP+ cards or an LSI HBA, four 3.5-inch HDD bays, or a 12GB+ GPU running Jellyfin NVENC and Ollama would cost far more than $200 to replicate outside an ATX case. Realistic low-power baselines across desktop and mini-PC generations are tracked in &lt;a href="https://www.servethehome.com/hp-elitedesk-800-g4-mini-tinyminimicro-guide-review/3/" rel="noopener">ServeTheHome&amp;rsquo;s TinyMiniMicro reviews&lt;/a>, while &lt;a href="https://www.techpowerup.com/cpu-specs/" rel="noopener">TechPowerUp&amp;rsquo;s CPU database&lt;/a> confirms socket, PCIe revision, and integrated-graphics specs.&lt;/p>
&lt;h2 id="before-you-start-hardware-sanity-check">Before you start: hardware sanity check&lt;/h2>
&lt;p>Check four items before flashing installer media. Five minutes here prevents a dead-end install.&lt;/p>
&lt;h3 id="cpu-virtualization-and-f-sku-headless-boot">CPU virtualization and F-sku headless boot&lt;/h3>
&lt;p>Proxmox VE 9 requires a 64-bit Intel or AMD processor with &lt;code>VT-x&lt;/code> (&lt;code>vmx&lt;/code>) or &lt;code>AMD-V&lt;/code> (&lt;code>svm&lt;/code>) enabled. &lt;code>VT-d&lt;/code> or &lt;code>AMD-Vi&lt;/code> (IOMMU) is required whenever you pass a PCIe GPU, HBA, or NIC directly into a VM. Boot a live Linux USB or inspect your existing Linux shell:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Intel: look for vmx; AMD: look for svm&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>grep -E &lt;span style="color:#e6db74">&amp;#39;vmx|svm&amp;#39;&lt;/span> /proc/cpuinfo | head -1
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Confirm CPU model and virtualization capability&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>lscpu | grep -E &lt;span style="color:#e6db74">&amp;#39;Model name|Virtualization&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Check whether your processor has integrated graphics before planning to pull the discrete GPU. Intel &lt;code>F&lt;/code>-suffix chips (such as &lt;code>i5-9400F&lt;/code> or &lt;code>i5-12400F&lt;/code>) and most non-&lt;code>G&lt;/code> Ryzen 1000–5000 desktop CPUs lack an iGPU. Leave the graphics card installed through Step 5. Once Proxmox answers on port &lt;code>8006&lt;/code> and SSH, most consumer motherboards will boot headless with no GPU installed as long as BIOS Halt On / Wait for F1 If Error is disabled (test this on your board in Step 9; a few boards require a headless UEFI toggle).&lt;/p>
&lt;h3 id="nic-compatibility">NIC compatibility&lt;/h3>
&lt;p>Onboard Intel Gigabit (&lt;code>I219-V&lt;/code>) works cleanly out of the box. Watch two common gaming-board controllers:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Realtek 2.5GbE (&lt;code>RTL8125B&lt;/code>)&lt;/strong>: Supported in Proxmox VE 9&amp;rsquo;s kernel, though certain board revisions exhibit link flaps or block deep PCIe ASPM states. Dropping in a $20 PCIe Intel &lt;code>I210&lt;/code> or &lt;code>I226-V&lt;/code> card solves driver quirks and unlocks cleaner C-state residency.&lt;/li>
&lt;li>&lt;strong>Wi-Fi onboard&lt;/strong>: Proxmox VE is meant for wired Ethernet bridges (&lt;code>vmbr0&lt;/code>). Disable unused onboard Wi-Fi/Bluetooth in BIOS so it stops drawing standby power.&lt;/li>
&lt;/ul>
&lt;p>Confirm your PCI network device IDs:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>lspci -nn | grep -iE &lt;span style="color:#e6db74">&amp;#39;ethernet|network&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h3 id="gpu-passthrough-viability">GPU passthrough viability&lt;/h3>
&lt;p>If you plan to keep the discrete GPU for a Windows gaming VM, Jellyfin transcode VM, or CUDA container host, verify four platform requirements covered in detail in our &lt;a href="https://techfuelhq.com/tutorials/gpu-passthrough-proxmox-vm-2026/">GPU Passthrough to a Proxmox VM guide&lt;/a>:&lt;/p>
&lt;ol>
&lt;li>Clean motherboard IOMMU group separation (Intel Z-series and AMD B550/X570 boards usually isolate the primary CPU x16 slot cleanly; older B350/B450 chipset slots often bundle devices together).&lt;/li>
&lt;li>Pure UEFI boot with CSM disabled.&lt;/li>
&lt;li>A UEFI-capable GPU vBIOS (GeForce GTX 900 / Radeon RX 400 series and newer).&lt;/li>
&lt;li>BIOS &lt;strong>Above 4G Decoding&lt;/strong> enabled.&lt;/li>
&lt;/ol>
&lt;h2 id="prerequisites">Prerequisites&lt;/h2>
&lt;ul>
&lt;li>Old gaming PC with 16GB+ RAM and a healthy PSU (note that an oversized 850W–1000W gaming PSU running at 3% load loses several watts in conversion efficiency compared with a 450W–550W unit)&lt;/li>
&lt;li>Dedicated 256GB+ SATA SSD or NVMe drive for the Proxmox boot OS&lt;/li>
&lt;li>8GB+ USB flash drive for &lt;a href="https://www.ventoy.net/" rel="noopener">Ventoy&lt;/a>&lt;/li>
&lt;li>Wired Ethernet cable to your switch or router&lt;/li>
&lt;li>Kill-A-Watt meter or calibrated energy-monitoring smart plug&lt;/li>
&lt;/ul>
&lt;h2 id="step-1--take-your-before-wattage-reading">Step 1 — Take your &amp;ldquo;before&amp;rdquo; wattage reading&lt;/h2>
&lt;p>Plug the gaming PC alone (not the monitor or speakers) into your Kill-A-Watt meter with its current OS sitting at an idle desktop. Wait three minutes for startup tasks to settle. Write down the idle watts alongside your CPU model, RAM stick count, drive count, and installed GPU.&lt;/p>
&lt;p>Photograph the meter if you want a permanent record. Guessing before-and-after numbers hides which change actually saved power. Step 10 measures the exact same wall outlet after Proxmox is tuned and headless.&lt;/p>
&lt;h2 id="step-2--flip-the-bios-virtualization-and-idle-power-toggles">Step 2 — Flip the BIOS virtualization and idle-power toggles&lt;/h2>
&lt;p>Reboot and press &lt;kbd>Delete&lt;/kbd> or &lt;kbd>F2&lt;/kbd> to enter UEFI setup. Load optimized defaults first if the PC still carries old all-core gaming overclocks or fixed core voltages, because manual voltage overrides frequently prevent idle clock and voltage drop.&lt;/p>
&lt;h3 id="2a-virtualization-and-iommu-vt-xamd-v--vt-damd-vi">2a. Virtualization and IOMMU (&lt;code>VT-x&lt;/code>/&lt;code>AMD-V&lt;/code> + &lt;code>VT-d&lt;/code>/&lt;code>AMD-Vi&lt;/code>)&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Intel:&lt;/strong> Enable &lt;strong>Intel Virtualization Technology&lt;/strong> under CPU Configuration, plus &lt;strong>VT-d&lt;/strong> under System Agent (SA) Configuration.&lt;/li>
&lt;li>&lt;strong>AMD:&lt;/strong> Enable &lt;strong>SVM Mode&lt;/strong> under CPU Configuration, plus &lt;strong>IOMMU&lt;/strong> under AMD CBS or NBIO Common Options.&lt;/li>
&lt;/ul>
&lt;h3 id="2b-above-4g-decoding-resizable-bar-and-sr-iov">2b. Above 4G Decoding, Resizable BAR, and SR-IOV&lt;/h3>
&lt;p>Under &lt;strong>Advanced → PCI Subsystem&lt;/strong>, enable &lt;strong>Above 4G Decoding&lt;/strong> (and &lt;strong>Re-Size BAR&lt;/strong> if offered) when keeping a GPU or high-BAR PCIe card. Enable &lt;strong>SR-IOV Support&lt;/strong> if you add an Intel I350 or X550 multi-queue NIC.&lt;/p>
&lt;h3 id="2c-cpu-package-c-states-and-pcie-aspm-the-idle-wattage-unlock">2c. CPU Package C-States and PCIe ASPM (the idle-wattage unlock)&lt;/h3>
&lt;p>Gaming motherboards routinely leave deep package sleep states on &lt;code>Auto&lt;/code>, which resolves to &lt;code>Disabled&lt;/code> or &lt;code>C2&lt;/code> on many desktop BIOSes! Set these explicitly:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Package C-State Limit (Intel) / Global C-state Control (AMD):&lt;/strong> Set to &lt;code>Enabled&lt;/code> or the deepest available state (&lt;code>C8&lt;/code> or &lt;code>C10&lt;/code>, rather than &lt;code>Auto&lt;/code> or &lt;code>C0/C1&lt;/code>). Keep &lt;strong>Intel SpeedStep / Speed Shift&lt;/strong> or &lt;strong>AMD Cool&amp;rsquo;n&amp;rsquo;Quiet / CPPC&lt;/strong> enabled.&lt;/li>
&lt;li>&lt;strong>PCIe ASPM (Active State Power Management):&lt;/strong> Enable &lt;strong>PCH ASPM&lt;/strong> and &lt;strong>CPU PCIe ASPM&lt;/strong> (&lt;code>L0sL1&lt;/code> or &lt;code>L1&lt;/code>, plus &lt;code>L1 Substates&lt;/code> where listed). Without ASPM, a single PCIe NVMe SSD or add-in card keeps the CPU&amp;rsquo;s root complex awake and blocks the entire processor package from dropping below &lt;code>PC2&lt;/code> or &lt;code>PC3&lt;/code>, adding 10–20W continuously.&lt;/li>
&lt;li>&lt;strong>Shut off parasitic onboard hardware:&lt;/strong> Turn motherboard &lt;strong>RGB / Aura / Mystic Light LEDs&lt;/strong> completely off (including in sleep/S5), disable unused third-party &lt;strong>ASMedia SATA controllers&lt;/strong>, &lt;strong>onboard Wi-Fi/Bluetooth&lt;/strong>, and &lt;strong>HD Audio&lt;/strong> if no VM uses them, and disable &lt;strong>Wait for F1 If Error&lt;/strong> so headless reboots never stall without a keyboard or GPU.&lt;/li>
&lt;li>&lt;strong>Restore AC Power Loss:&lt;/strong> Set to &lt;strong>Power On&lt;/strong> (or &lt;strong>Last State&lt;/strong>) so the server boots back up automatically after a power outage.&lt;/li>
&lt;/ul>
&lt;h3 id="2d-uefi-boot-mode--secure-boot">2d. UEFI boot mode + Secure Boot&lt;/h3>
&lt;p>Set Boot Mode to &lt;strong>UEFI only&lt;/strong> with &lt;strong>CSM (Compatibility Support Module) Disabled&lt;/strong>. CSM breaks clean IOMMU initialization and UEFI GOP framebuffer handoff. Current Proxmox VE supports Secure Boot out of the box; leave it enabled unless an unsigned out-of-tree driver requires turning it off. Save and exit.&lt;/p>
&lt;h2 id="step-3--build-the-ventoy-usb">Step 3 — Build the Ventoy USB&lt;/h2>
&lt;ol>
&lt;li>Install &lt;a href="https://www.ventoy.net/" rel="noopener">Ventoy&lt;/a> onto your 8GB+ USB stick (this formats the USB stick once).&lt;/li>
&lt;li>Download the official &lt;a href="https://www.proxmox.com/en/downloads" rel="noopener">Proxmox VE 9.2 ISO&lt;/a> and verify its &lt;code>SHA256SUMS&lt;/code> hash before copying.&lt;/li>
&lt;li>Copy the &lt;code>.iso&lt;/code> file straight onto the Ventoy data partition. You can drop a Debian live ISO or Memtest86+ onto the same stick later without reflashing.&lt;/li>
&lt;/ol>
&lt;h2 id="step-4--install-proxmox-ve-92">Step 4 — Install Proxmox VE 9.2&lt;/h2>
&lt;p>Plug the USB stick into a rear motherboard port, open the UEFI boot menu (&lt;kbd>F11&lt;/kbd>, &lt;kbd>F12&lt;/kbd>, or &lt;kbd>F8&lt;/kbd>), select the UEFI Ventoy entry, and boot the Proxmox VE installer in normal mode.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Target Harddisk:&lt;/strong> Select your dedicated 256GB+ boot SSD. Better yet, temporarily unplug SATA data cables from any old drives holding files you have not backed up yet.&lt;/li>
&lt;li>&lt;strong>Filesystem:&lt;/strong> Choose &lt;strong>&lt;code>ext4&lt;/code>&lt;/strong> (which creates &lt;code>local&lt;/code> plus &lt;code>local-lvm&lt;/code> thin provisioning) for a single consumer SSD. Only pick ZFS RAID1 when pairing two matching high-endurance SSDs; see our &lt;a href="https://techfuelhq.com/tutorials/zfs-proxmox-pool-setup-arc-tuning-2026/">Proxmox ZFS pool and ARC tuning guide&lt;/a> for why consumer QLC drives wear quickly under ZFS sync writes.&lt;/li>
&lt;li>&lt;strong>Management Network:&lt;/strong> Pick the active wired Ethernet port, give the node a hostname such as &lt;code>pve.home.arpa&lt;/code>, and assign a &lt;strong>static IPv4 address&lt;/strong> outside your router&amp;rsquo;s dynamic DHCP pool (for example &lt;code>192.168.1.50/24&lt;/code>) with your router IP as gateway and DNS.&lt;/li>
&lt;/ul>
&lt;p>Complete installation and remove the USB stick when the system reboots to the &lt;code>https://&amp;lt;your-static-ip&amp;gt;:8006/&lt;/code> login banner. For the full screen-by-screen walkthrough, see &lt;a href="https://techfuelhq.com/articles/how-to-install-proxmox-ve-2026/">How to Install Proxmox VE in 2026&lt;/a>.&lt;/p>
&lt;h2 id="step-5--post-install-configure-debian-13-repositories">Step 5 — Post-install: configure Debian 13 repositories&lt;/h2>
&lt;p>Open &lt;code>https://&amp;lt;your-static-ip&amp;gt;:8006&lt;/code> from another computer on your LAN, accept the self-signed TLS certificate, and log in as &lt;code>root&lt;/code>.&lt;/p>
&lt;p>Fresh Proxmox VE 9 installs enable the paid enterprise repository by default. On a homelab node without a subscription key, disable the enterprise stanza in &lt;code>/etc/apt/sources.list.d/pve-enterprise.sources&lt;/code> (and &lt;code>/etc/apt/sources.list.d/ceph.sources&lt;/code> if present) by setting &lt;code>Enabled: no&lt;/code>, then add the documented Debian 13 &lt;code>trixie&lt;/code> &lt;a href="https://pve.proxmox.com/wiki/Package_Repositories" rel="noopener">no-subscription repository&lt;/a>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Disable enterprise repo cleanly (or toggle it off under Node -&amp;gt; Updates -&amp;gt; Repositories)&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>sed -i &lt;span style="color:#e6db74">&amp;#39;s/^Enabled:.*/Enabled: no/&amp;#39;&lt;/span> /etc/apt/sources.list.d/pve-enterprise.sources 2&amp;gt;/dev/null &lt;span style="color:#f92672">||&lt;/span> true
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Add the official Proxmox VE 9 (Debian 13 Trixie) no-subscription deb822 source&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat &amp;gt; /etc/apt/sources.list.d/proxmox.sources &lt;span style="color:#e6db74">&amp;lt;&amp;lt;&amp;#39;EOF&amp;#39;
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">Types: deb
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">URIs: http://download.proxmox.com/debian/pve
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">Suites: trixie
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">Components: pve-no-subscription
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#e6db74">EOF&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>apt update
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>apt full-upgrade -y
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="step-6--verify-iommu-is-live">Step 6 — Verify IOMMU is live&lt;/h2>
&lt;p>Reboot if &lt;code>apt full-upgrade&lt;/code> installed a newer Proxmox kernel. Check IOMMU groups next. Run both commands from the node shell:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>dmesg | grep -e DMAR -e IOMMU -e AMD-Vi
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">for&lt;/span> d in /sys/kernel/iommu_groups/*/devices/*; &lt;span style="color:#66d9ef">do&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> n&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">${&lt;/span>d##*/iommu_groups/*/devices/&lt;span style="color:#e6db74">}&lt;/span>; g&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">${&lt;/span>d%/devices/*&lt;span style="color:#e6db74">}&lt;/span>; g&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">${&lt;/span>g##*/&lt;span style="color:#e6db74">}&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> printf &lt;span style="color:#e6db74">&amp;#39;IOMMU Group %s: %s\n&amp;#39;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$g&lt;span style="color:#e6db74">&amp;#34;&lt;/span> &lt;span style="color:#e6db74">&amp;#34;&lt;/span>&lt;span style="color:#66d9ef">$(&lt;/span>lspci -nns &lt;span style="color:#e6db74">&amp;#34;&lt;/span>$n&lt;span style="color:#e6db74">&amp;#34;&lt;/span>&lt;span style="color:#66d9ef">)&lt;/span>&lt;span style="color:#e6db74">&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">done&lt;/span> | sort -V
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>You want multiple numbered groups with your primary PCIe x16 slot isolated in its own group (alongside only its companion HDMI/DP audio function). If &lt;code>iommu_groups&lt;/code> is empty on Intel even after enabling VT-d in BIOS, append &lt;code>intel_iommu=on&lt;/code> to &lt;code>/etc/default/grub&lt;/code> (&lt;code>GRUB_CMDLINE_LINUX_DEFAULT&lt;/code>) or &lt;code>/etc/kernel/cmdline&lt;/code>, run &lt;code>proxmox-boot-tool refresh&lt;/code> (or &lt;code>update-grub&lt;/code>), and reboot.&lt;/p>
&lt;h2 id="step-7--configure-the-network-bridge">Step 7 — Configure the network bridge&lt;/h2>
&lt;p>Proxmox binds &lt;code>vmbr0&lt;/code> to your selected Ethernet NIC automatically during setup. Keep &lt;code>vmbr0&lt;/code> simple on day one; add a second bridge (&lt;code>vmbr1&lt;/code>) or VLAN-aware tagging only when segmenting lab subnets. Verify link speed and bridge state:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>ip -br a
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cat /etc/network/interfaces
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;h2 id="step-8--create-your-first-vm">Step 8 — Create your first VM&lt;/h2>
&lt;p>Upload a Debian 13 or Ubuntu 24.04 Server ISO under &lt;strong>local → ISO Images → Upload&lt;/strong>, or spin up a test VM directly from the host shell:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>qm create &lt;span style="color:#ae81ff">100&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --name debian-docker &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --memory &lt;span style="color:#ae81ff">4096&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --cores &lt;span style="color:#ae81ff">2&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --cpu host &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --net0 virtio,bridge&lt;span style="color:#f92672">=&lt;/span>vmbr0 &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --scsihw virtio-scsi-single &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --agent enabled&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#ae81ff">1&lt;/span> &lt;span style="color:#ae81ff">\
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#ae81ff">&lt;/span> --ostype l26
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>qm set &lt;span style="color:#ae81ff">100&lt;/span> --ide2 local:iso/ubuntu-24.04.1-live-server-amd64.iso,media&lt;span style="color:#f92672">=&lt;/span>cdrom
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>qm set &lt;span style="color:#ae81ff">100&lt;/span> --scsi0 local-lvm:32,discard&lt;span style="color:#f92672">=&lt;/span>on,ssd&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#ae81ff">1&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>qm set &lt;span style="color:#ae81ff">100&lt;/span> --boot order&lt;span style="color:#f92672">=&lt;/span>&lt;span style="color:#e6db74">&amp;#39;ide2;scsi0&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>qm start &lt;span style="color:#ae81ff">100&lt;/span>
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Once the guest OS installs, run &lt;code>apt install -y qemu-guest-agent&lt;/code> inside it so Proxmox sees clean guest IPs and executes filesystem-consistent &lt;code>fsfreeze&lt;/code> snapshots. Lightweight single-service tools (Pi-hole, Tailscale subnet router) can also live in native LXC containers using the same &lt;code>pct&lt;/code> workflow covered in the &lt;a href="https://techfuelhq.com/articles/proxmox-mini-pc-setup/">mini PC Proxmox guide&lt;/a>.&lt;/p>
&lt;h2 id="step-9--pull-the-gpu-and-verify-c-state-residency">Step 9 — Pull the GPU and verify C-state residency&lt;/h2>
&lt;p>Now that SSH and &lt;code>https://&amp;lt;ip&amp;gt;:8006&lt;/code> work over Ethernet, make the hardware call:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>No VM needs the discrete GPU:&lt;/strong> Shut down cleanly (&lt;code>shutdown -h now&lt;/code>), unplug AC power, remove the graphics card, disconnect monitors and keyboards, and power back on headless. Wait two minutes and confirm the web UI comes back. Removing an idle desktop GPU typically saves &lt;strong>15–35W&lt;/strong> at the wall immediately.&lt;/li>
&lt;li>&lt;strong>Keeping the GPU for VFIO or transcoding:&lt;/strong> Leave it installed and bind it to &lt;code>vfio-pci&lt;/code> (or load clean host idle power drivers) so the card enters its &lt;code>D3cold&lt;/code> / &lt;code>P8&lt;/code> low-power idle state instead of sitting stuck in &lt;code>P0&lt;/code> high-clock mode on an unconfigured framebuffer.&lt;/li>
&lt;/ul>
&lt;p>To check why a headless host still draws more watts than expected, inspect CPU package C-state residency with &lt;code>powertop&lt;/code> as documented on the &lt;a href="https://wiki.archlinux.org/title/Power_management" rel="noopener">Arch Linux Power Management wiki&lt;/a>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>apt install -y powertop
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e"># Press Tab once to open the &amp;#34;Idle stats&amp;#34; tab — check Pkg(HW) C6/C8/C10 residency!&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>powertop
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Look at the Pkg(HW) column on the Idle stats tab, not the per-core column. Core states lie on idle desktops. Individual CPU cores can report 98% &lt;code>C6&lt;/code> while the package itself sits at &lt;code>0.0%&lt;/code> deeper than &lt;code>PC2&lt;/code> because one SATA controller, NVMe drive without ASPM &lt;code>L1&lt;/code>, or PCIe card is holding the root complex awake. Review &lt;code>powertop&lt;/code> Tunables carefully before persisting anything (avoid USB autosuspend on Zigbee dongles or UPS cables).&lt;/p>
&lt;h2 id="step-10--take-the-after-measurement-and-make-the-keepsell-call">Step 10 — Take the &amp;ldquo;after&amp;rdquo; measurement and make the keep/sell call&lt;/h2>
&lt;p>Unplug the monitor and keyboard. Reboot Proxmox headless. Wait five full minutes for boot tasks to quiet down, then read your Kill-A-Watt meter and plug the exact watts and your utility&amp;rsquo;s &lt;code>$/kWh&lt;/code> rate into our &lt;a href="https://techfuelhq.com/tools/power-cost-calculator/">Power &amp;amp; Cost Calculator&lt;/a>:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>25–45W headless idle:&lt;/strong> Strong result for ATX desktop hardware. Keep the tower, sell the spare GPU if you pulled it, and build out your VMs.&lt;/li>
&lt;li>&lt;strong>45–70W headless idle:&lt;/strong> Worth keeping when the box earns its keep with 64GB+ RAM, multiple 3.5-inch NAS drives, 10GbE cards, or an active GPU VM. Otherwise check &lt;code>powertop&lt;/code> Idle stats for a stuck &lt;code>PC2&lt;/code> package state.&lt;/li>
&lt;li>&lt;strong>75W+ headless idle with GPU pulled:&lt;/strong> High-idle platform floor (common on older HEDT boards, chiplet X-series desktops with high I/O-die idle draw, or 1000W PSUs at 4% load). Sell the desktop components while they hold value and deploy a &lt;a href="https://techfuelhq.com/homelab/best-mini-pcs-homelab-2026/">low-idle mini PC&lt;/a>.&lt;/li>
&lt;/ul>
&lt;h2 id="troubleshooting">Troubleshooting&lt;/h2>
&lt;p>&lt;strong>Cannot reach &lt;code>https://192.168.1.50:8006&lt;/code> after going headless.&lt;/strong> First confirm &lt;code>192.168.1.50&lt;/code> is replaced with the exact static IP you entered in Step 4, and use &lt;code>https://&lt;/code> rather than &lt;code>http://&lt;/code>. If the box does not ping at all after pulling the GPU on an F-series or non-iGPU Ryzen chip, temporarily plug the GPU back in: either &lt;strong>Wait for F1 If Error&lt;/strong> halted POST on missing VGA, or removing the PCIe card shifted PCI bus numbering and renamed your Ethernet interface (for example &lt;code>enp5s0&lt;/code> became &lt;code>enp4s0&lt;/code> in &lt;code>/etc/network/interfaces&lt;/code> while &lt;code>vmbr0&lt;/code> still pointed at &lt;code>enp5s0&lt;/code>!). Update &lt;code>bridge-ports&lt;/code> in &lt;code>/etc/network/interfaces&lt;/code> to match &lt;code>ip -br link&lt;/code> before pulling the GPU again. That single PCIe renumbering catch has bitten me on consumer B450 and B550 motherboards more than any other headless issue!&lt;/p>
&lt;p>&lt;strong>&lt;code>KVM virtualisation not available&lt;/code> or empty &lt;code>iommu_groups&lt;/code>.&lt;/strong> Re-check Step 2a (&lt;code>VT-x&lt;/code>/&lt;code>SVM&lt;/code> and &lt;code>VT-d&lt;/code>/&lt;code>IOMMU&lt;/code>) and verify CSM is &lt;code>Disabled&lt;/code>. Flashing a BIOS update resets all UEFI toggles back to factory gaming defaults.&lt;/p>
&lt;p>&lt;strong>Realtek 2.5GbE link drops under heavy backup traffic.&lt;/strong> Install an Intel &lt;code>I210&lt;/code> or &lt;code>I226-V&lt;/code> PCIe NIC, or disable Energy Efficient Ethernet (&lt;code>ethtool --set-eee &amp;lt;iface&amp;gt; eee off&lt;/code>).&lt;/p>
&lt;p>Swapping fans, drives, or a smaller Gold-rated PSU in the donor case? Check physical clearances in the &lt;a href="https://techfuelhq.com/tools/pc-builder/">PC Builder&lt;/a>. Next, configure checksummed VM storage in our &lt;a href="https://techfuelhq.com/tutorials/zfs-proxmox-pool-setup-arc-tuning-2026/">ZFS pool and ARC tuning guide&lt;/a> or wire up &lt;a href="https://techfuelhq.com/tutorials/gpu-passthrough-proxmox-vm-2026/">Proxmox GPU passthrough&lt;/a>.&lt;/p>
&lt;h2 id="sources-and-methodology">Sources and methodology&lt;/h2>
&lt;p>Procedure verified against Proxmox VE 9.2 documentation, Debian 13 &lt;code>trixie&lt;/code> repository specifications, and Linux C-state / PCIe ASPM power-management docs:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://pve.proxmox.com/pve-docs/chapter-pve-installation.html" rel="noopener">Proxmox VE installation documentation&lt;/a> — official VE 9.2 installer and disk reference&lt;/li>
&lt;li>&lt;a href="https://pve.proxmox.com/wiki/Package_Repositories" rel="noopener">Proxmox VE package repositories&lt;/a> — deb822 &lt;code>proxmox.sources&lt;/code> configuration for Debian 13 Trixie&lt;/li>
&lt;li>&lt;a href="https://pve.proxmox.com/wiki/PCI_Passthrough" rel="noopener">Proxmox VE PCI(e) passthrough wiki&lt;/a> — IOMMU grouping and &lt;code>vfio-pci&lt;/code> binding&lt;/li>
&lt;li>&lt;a href="https://wiki.archlinux.org/title/Power_management" rel="noopener">Arch Linux Wiki: Power management&lt;/a> — CPU Package C-states, PCIe ASPM, and &lt;code>powertop&lt;/code> residency verification&lt;/li>
&lt;li>&lt;a href="https://www.servethehome.com/hp-elitedesk-800-g4-mini-tinyminimicro-guide-review/3/" rel="noopener">ServeTheHome TinyMiniMicro idle power reviews&lt;/a> — low-power homelab idle wattage reference baselines&lt;/li>
&lt;li>&lt;a href="https://www.techpowerup.com/cpu-specs/" rel="noopener">TechPowerUp CPU specifications database&lt;/a> — processor TDP, integrated graphics, and PCIe lane specs&lt;/li>
&lt;/ul>
&lt;p>Email corrections to &lt;a href="mailto:contact@techfuelhq.com">contact@techfuelhq.com&lt;/a>.&lt;/p></description></item><item><title>WHEA_UNCORRECTABLE_ERROR 0x124: Read the Record</title><link>https://techfuelhq.com/articles/whea-uncorrectable-error-2026/</link><pubDate>Sat, 03 Oct 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/whea-uncorrectable-error-2026/</guid><atom:updated>2026-11-14T10:45:00Z</atom:updated><description>&lt;p>&lt;code>WHEA_UNCORRECTABLE_ERROR&lt;/code> means hardware raised a fatal error that Windows could not contain. Stop code &lt;code>0x00000124&lt;/code> (usually shortened to &lt;code>0x124&lt;/code>) is the operating system halting before corrupted state hits disk.&lt;/p>
&lt;p>Don&amp;rsquo;t buy a replacement CPU yet. Seeing &lt;code>AuthenticAMD.sys&lt;/code> or &lt;code>GenuineIntel.sys&lt;/code> inside a crash viewer does &lt;strong>not&lt;/strong> prove the silicon is dead. Windows Hardware Error Architecture (WHEA) simply forwards the packet raised by a CPU core, memory controller, PCIe root port, or NVMe endpoint. Read that packet first.&lt;/p>
&lt;p>&lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x124---whea-uncorrectable-error" rel="noopener">Microsoft&amp;rsquo;s 0x124 reference&lt;/a> gives you the two fields that route the investigation:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Parameter 1&lt;/strong> identifies the kind of error source that reported the problem.&lt;/li>
&lt;li>&lt;strong>Parameter 2&lt;/strong> points to the &lt;code>WHEA_ERROR_RECORD&lt;/code> that describes it.&lt;/li>
&lt;/ul>
&lt;p>Save both values before touching UEFI voltages or ordering parts.&lt;/p>
&lt;p>I log every crash timestamp, BIOS offset, and test pass inside the &lt;a href="https://techfuelhq.com/tools/diagnostic-workbench/">Hardware Diagnostic Workbench&lt;/a> so one bad memory profile or per-core Curve Optimizer tweak doesn&amp;rsquo;t get confused with a dead motherboard.&lt;/p>
&lt;h2 id="first-make-sure-0x124-was-the-crash--even-on-silent-reboots">First, make sure 0x124 was the crash — even on silent reboots&lt;/h2>
&lt;p>Photograph the blue screen if it stays visible. Did the PC black-screen and reboot instantaneously? Start with the &lt;a href="https://techfuelhq.com/articles/pc-randomly-restarts-2026/">random-restart guide&lt;/a>, where Kernel-Power Event 41 records the decimal &lt;code>BugcheckCode&lt;/code> (&lt;code>292&lt;/code> in decimal equals &lt;code>0x124&lt;/code> in hex).&lt;/p>
&lt;p>Sometimes &lt;code>C:\Windows\Minidump&lt;/code> is completely empty and Event 41 logs &lt;code>BugcheckCode 0&lt;/code>. There is a specific hardware reason for that trap. Windows writes crash dumps to &lt;code>pagefile.sys&lt;/code> on your boot drive—so if your primary NVMe M.2 SSD drops off the PCIe bus mid-game or mid-sleep, &lt;code>0x124&lt;/code> fires with nowhere to write &lt;code>MEMORY.DMP&lt;/code>, and the PC resets straight into UEFI or reboots with zero dump files left behind.&lt;/p>
&lt;p>When a machine reboots silently into the BIOS screen with the boot drive missing until you flip the PSU switch off and on, stop chasing CPU voltage. Power down, unplug AC power, reseat that M.2 NVMe SSD (checking that no thick thermal pad is bowing the PCB), and check the drive&amp;rsquo;s firmware before testing anything else.&lt;/p>
&lt;p>Keep corrected warnings distinct from fatal stops too. Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/whea/error-processing" rel="noopener">WHEA error-processing documentation&lt;/a> notes that Windows logs corrected hardware errors silently while running, whereas uncorrectable fatal errors force a bug check. Both matter, and Event Viewer connects them.&lt;/p>
&lt;h2 id="decode-event-viewer-whea-logger-event-id-18-vs-event-id-17">Decode Event Viewer &lt;code>WHEA-Logger&lt;/code> Event ID 18 vs Event ID 17&lt;/h2>
&lt;p>Even when no &lt;code>.dmp&lt;/code> file survives, Windows frequently writes a hardware entry into &lt;strong>Event Viewer -&amp;gt; Windows Logs -&amp;gt; System&lt;/strong> right as the machine comes back up (or in the seconds leading up to the crash). Filter the System log by Event source &lt;code>WHEA-Logger&lt;/code>.&lt;/p>
&lt;p>Open the &lt;strong>Details&lt;/strong> tab (Friendly View or XML View) on any &lt;code>Microsoft-Windows-WHEA-Logger&lt;/code> entry. Event ID 18 and Event ID 17 point to completely different hardware subsystems:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Event ID &amp;amp; severity&lt;/th>
&lt;th scope="col">Key fields inside Event Details&lt;/th>
&lt;th scope="col">Hardware subsystem implicated&lt;/th>
&lt;th scope="col">Targeted isolation action&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Event ID &amp;amp; severity">&lt;strong>Event ID 18&lt;/strong> (&lt;code>Error&lt;/code> — Fatal hardware error, &lt;code>Processor Core&lt;/code>)&lt;/td>
&lt;td data-label="Key fields inside Event Details">&lt;code>Error Type: Cache Hierarchy Error&lt;/code> + &lt;strong>&lt;code>Processor APIC ID: &amp;lt;N&amp;gt;&lt;/code>&lt;/strong>&lt;/td>
&lt;td data-label="Hardware subsystem implicated">A specific CPU core failed L1/L2/L3 cache execution, most often during a light-load boost transient when a Ryzen Curve Optimizer negative offset or Intel undervolt starves that core of voltage.&lt;/td>
&lt;td data-label="Targeted isolation action">Map &lt;code>Processor APIC ID&lt;/code> to the physical core (with SMT/Hyper-Threading on, &lt;code>floor(APIC ID / 2)&lt;/code> = physical Core &lt;code>0..N&lt;/code>; e.g., APIC ID &lt;code>6&lt;/code> or &lt;code>7&lt;/code> = Core &lt;code>3&lt;/code>). Relax Curve Optimizer on that core by 5–10 steps or test stock BIOS defaults.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Event ID &amp;amp; severity">&lt;strong>Event ID 18&lt;/strong> (&lt;code>Error&lt;/code> — Fatal hardware error, &lt;code>Processor Core&lt;/code>)&lt;/td>
&lt;td data-label="Key fields inside Event Details">&lt;code>Error Type: Bus/Interconnect Error&lt;/code> or &lt;code>Memory Hierarchy Error&lt;/code>&lt;/td>
&lt;td data-label="Hardware subsystem implicated">Infinity Fabric (&lt;code>FCLK&lt;/code>), integrated memory controller (&lt;code>UCLK&lt;/code> / &lt;code>VSOC&lt;/code>), or CPU-to-PCIe interconnect lost sync rather than a single core&amp;rsquo;s clock-voltage curve.&lt;/td>
&lt;td data-label="Targeted isolation action">Disable XMP/EXPO and custom &lt;code>FCLK&lt;/code> overrides in UEFI. Test stock JEDEC memory speed before suspecting the processor.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Event ID &amp;amp; severity">&lt;strong>Event ID 17&lt;/strong> (&lt;code>Warning&lt;/code> — Corrected error, &lt;code>PCI Express Root Port&lt;/code> / &lt;code>Endpoint&lt;/code>)&lt;/td>
&lt;td data-label="Key fields inside Event Details">&lt;code>Primary Device Name: PCI\VEN_...&amp;amp;DEV_...&lt;/code> flooding dozens or hundreds of entries per minute&lt;/td>
&lt;td data-label="Hardware subsystem implicated">PCIe link-training, replay timer, or CRC errors on a GPU riser cable, graphics card slot finger, or M.2 NVMe socket. Left unchecked, link drops escalate into &lt;code>0x124&lt;/code> (&lt;code>Arg1 = 0x4&lt;/code>).&lt;/td>
&lt;td data-label="Targeted isolation action">Copy the &lt;code>VEN_xxxx&amp;amp;DEV_xxxx&lt;/code> string, match it in &lt;strong>Device Manager -&amp;gt; View -&amp;gt; Devices by connection&lt;/strong> (&lt;code>Details -&amp;gt; Device instance path&lt;/code>), bypass any PCIe riser cable, reseat the GPU or M.2 drive, and test stepping that slot from Gen 5/Gen 4 down one generation in UEFI.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>I always check &lt;code>Processor APIC ID&lt;/code> across three or four Event ID 18 crashes before touching BIOS. Seeing APIC ID &lt;code>0&lt;/code> crash one afternoon and APIC ID &lt;code>1&lt;/code> (&lt;code>0&lt;/code> and &lt;code>1&lt;/code> share physical Core 0 on a 2-thread-per-core Ryzen chip) crash the next morning during idle YouTube playback is the textbook signature of an aggressive &lt;code>-25&lt;/code> or &lt;code>-30&lt;/code> Curve Optimizer offset—not a dead CPU, and never a reason to reinstall Windows.&lt;/p>
&lt;h2 id="preserve-the-dump-before-changing-settings">Preserve the dump before changing settings&lt;/h2>
&lt;p>Check &lt;code>C:\Windows\Minidump&lt;/code> for a &lt;code>.dmp&lt;/code> file matching the crash time, or &lt;code>C:\Windows\MEMORY.DMP&lt;/code> for a kernel dump. Copy it to a separate folder immediately so Storage Sense or a repeat crash cannot overwrite it.&lt;/p>
&lt;p>No dump folder at all? Open &lt;strong>System Properties &amp;gt; Advanced &amp;gt; Startup and Recovery &amp;gt; Settings&lt;/strong> and confirm &lt;a href="https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/read-small-memory-dump-file" rel="noopener">Small memory dump (256 KB)&lt;/a> (&lt;code>%SystemRoot%\Minidump&lt;/code>) or Automatic memory dump is enabled alongside an active system-managed pagefile on &lt;code>C:&lt;/code>.&lt;/p>
&lt;p>Jot down everything that changed prior to the first &lt;code>0x124&lt;/code>:&lt;/p>
&lt;ul>
&lt;li>Curve Optimizer, Intel voltage offset, or load-line calibration edits&lt;/li>
&lt;li>XMP or EXPO memory profiles&lt;/li>
&lt;li>a recent UEFI/AGESA/microcode flash&lt;/li>
&lt;li>a PCIe riser cable, new GPU, or secondary M.2 SSD&lt;/li>
&lt;li>cooler mounting or pump header changes&lt;/li>
&lt;li>whether crashes hit at idle/light desktop load (classic undervolt transient) vs sustained 100% load (thermal or power delivery)&lt;/li>
&lt;/ul>
&lt;h2 id="read-parameter-1-and-the-error-record-in-windbg">Read Parameter 1 and the error record in WinDbg&lt;/h2>
&lt;p>Open the copied dump in WinDbg via &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/opening-a-crash-dump-file-using-windbg" rel="noopener">File &amp;gt; Open crash dump&lt;/a> and run:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>!analyze -v
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Locate &lt;code>WHEA_UNCORRECTABLE_ERROR (124)&lt;/code> and copy &lt;code>Arg1&lt;/code> (Parameter 1) plus &lt;code>Arg2&lt;/code> (Parameter 2). Feed the &lt;code>Arg2&lt;/code> hex address directly into WinDbg&amp;rsquo;s WHEA extension:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-text" data-lang="text">&lt;span style="display:flex;">&lt;span>!errrec &amp;lt;Arg2 value&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>If &lt;code>Arg2&lt;/code> reads &lt;code>ffffa10b12345028&lt;/code>, run &lt;code>!errrec ffffa10b12345028&lt;/code> using the exact pointer from your own dump. Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/debuggercmds/-errrec" rel="noopener">&lt;code>!errrec&lt;/code> documentation&lt;/a> shows how the command decodes the Common Platform Error Record (CPER) header, severity, and section descriptors.&lt;/p>
&lt;p>When a 256 KB minidump truncates the CPER payload, switch &lt;strong>Startup and Recovery&lt;/strong> to &lt;strong>Kernel memory dump&lt;/strong> via &lt;a href="https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/configure-system-failure-and-recovery-options" rel="noopener">Microsoft&amp;rsquo;s recovery options guide&lt;/a> so the next crash captures full kernel memory.&lt;/p>
&lt;h2 id="parameter-1-picks-the-branch-not-the-replacement-part">Parameter 1 picks the branch, not the replacement part&lt;/h2>
&lt;p>Microsoft&amp;rsquo;s &lt;code>0x124&lt;/code> table maps &lt;code>Parameter 1&lt;/code> (&lt;code>Arg1&lt;/code>) to the reporting error source:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Parameter 1&lt;/th>
&lt;th scope="col">Error source&lt;/th>
&lt;th scope="col">What the branch establishes&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Parameter 1">&lt;code>0x0&lt;/code>&lt;/td>
&lt;td data-label="Error source">Machine check exception (MCE)&lt;/td>
&lt;td data-label="What the branch establishes">A CPU machine-check bank raised the fault. Inspect Event ID 18 (&lt;code>Cache&lt;/code> vs &lt;code>Bus/Interconnect&lt;/code>) and &lt;code>!errrec&lt;/code> before choosing core, IMC/RAM, or thermal tests.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Parameter 1">&lt;code>0x3&lt;/code>&lt;/td>
&lt;td data-label="Error source">Nonmaskable interrupt (NMI)&lt;/td>
&lt;td data-label="What the branch establishes">Platform NMI asserted. Check board/OEM hardware logs and firmware notes.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Parameter 1">&lt;code>0x4&lt;/code>&lt;/td>
&lt;td data-label="Error source">Uncorrectable PCI Express error&lt;/td>
&lt;td data-label="What the branch establishes">A PCIe root port or endpoint lost its link or hit an uncorrectable TLP fault. Check Event ID 17, GPU risers, and NVMe M.2 slots—not the CPU.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Parameter 1">&lt;code>0x5&lt;/code>&lt;/td>
&lt;td data-label="Error source">Generic hardware error&lt;/td>
&lt;td data-label="What the branch establishes">Platform firmware reported an ACPI/GHES hardware fault; read the &lt;code>!errrec&lt;/code> section descriptor.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Parameter 1">&lt;code>0x7&lt;/code> / &lt;code>0x10&lt;/code>&lt;/td>
&lt;td data-label="Error source">Boot error / Device driver source&lt;/td>
&lt;td data-label="What the branch establishes">Firmware boot record or a WHEA-aware device driver (&lt;code>stornvme&lt;/code> NVMe timeout frequently surfaces under &lt;code>0x10&lt;/code> on modern Windows 11 builds).&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>Stay disciplined on &lt;code>Arg1 = 0x0&lt;/code>. Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/whea/hardware-errors-and-error-sources" rel="noopener">hardware-error source reference&lt;/a> emphasizes that CPU machine-check banks also monitor L3/infinity-fabric links, integrated memory controllers, and system buses. Meanwhile, &lt;code>Arg1 = 0x10&lt;/code> in Windows 11 dumps regularly points right at an NVMe controller timing out rather than processor silicon—always check the &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/whea/error-records" rel="noopener">error-record section&lt;/a> first.&lt;/p>
&lt;h2 id="put-deliberate-tuning-back-to-default">Put deliberate tuning back to default&lt;/h2>
&lt;p>Start with BIOS defaults.&lt;/p>
&lt;p>Microsoft lists overheating, unstable memory, and stressed silicon among &lt;code>0x124&lt;/code> triggers, so its own checklist starts by disabling overclocking and confirming cooler operation before running hardware diagnostics. If you altered a Curve Optimizer offset, CPU core voltage, load-line level, or XMP/EXPO memory profile, write down the current numbers and return only those deliberate tweaks to documented stock defaults, then rerun the exact game or idle workload that crashed before touching a second knob.&lt;/p>
&lt;p>Check your BitLocker key before entering UEFI. Microsoft warns that firmware edits can trigger a BitLocker prompt on reboot and a lost recovery key cannot be recreated, so verify access via &lt;a href="https://support.microsoft.com/en-us/windows/security/encryption/find-your-bitlocker-recovery-key" rel="noopener">Microsoft&amp;rsquo;s recovery-key instructions&lt;/a> first and leave TPM or Secure Boot untouched.&lt;/p>
&lt;p>If &lt;code>0x124&lt;/code> stops at stock settings, your hardware is fine—the tuning was out of bounds. Keep defaults active if crashes continue.&lt;/p>
&lt;h2 id="follow-the-records-branch">Follow the record&amp;rsquo;s branch&lt;/h2>
&lt;h3 id="machine-check-or-processor-section">Machine-check or processor section&lt;/h3>
&lt;p>Check thermals first. Confirm every fan and AIO pump spins normally and compare peak CPU die temperature under the crashing workload against the chip&amp;rsquo;s published limit using the &lt;a href="https://techfuelhq.com/articles/cpu-overheating-2026/">CPU overheating guide&lt;/a>.&lt;/p>
&lt;p>Did the error record implicate the memory hierarchy or follow an XMP/EXPO change? Follow the &lt;a href="https://techfuelhq.com/articles/memory-management-bsod-2026/#step-3-test-the-sticks-so-the-result-means-something">MEMORY_MANAGEMENT test sequence&lt;/a> step by step: stock JEDEC memory clocks first, bootable memory testing second, and single-stick slot isolation only if errors appear. Because CPU machine-check banks watch L3 cache and memory buses alongside execution cores, keep the &lt;code>.dmp&lt;/code> file and &lt;code>!errrec&lt;/code> output ready for the board or CPU vendor before treating a processor swap as anything other than a final isolation step.&lt;/p>
&lt;h3 id="pcie-section-or-parameter-1-0x4">PCIe section or Parameter 1 &lt;code>0x4&lt;/code>&lt;/h3>
&lt;p>Pull the PCIe device ID from &lt;code>!errrec&lt;/code> or Event ID 17 and match it against recent hardware changes—such as a vertical GPU riser cable, a newly added M.2 SSD, or a BIOS update. Shut the PC down completely and unplug AC power before reseating one card or M.2 drive at a time per the motherboard manual.&lt;/p>
&lt;p>Never assume every PCIe fault is the graphics card. M.2 NVMe drives and onboard Wi-Fi/LAN controllers share the PCIe root complex too.&lt;/p>
&lt;h3 id="generic-nmi-or-platform-specific-section">Generic, NMI or platform-specific section&lt;/h3>
&lt;p>Generic (&lt;code>0x5&lt;/code>) and NMI (&lt;code>0x3&lt;/code>) records come from platform firmware rather than a standard CPU core check. Save the complete &lt;code>!errrec&lt;/code> output and run the motherboard or OEM vendor&amp;rsquo;s own hardware diagnostics instead of guessing at parts.&lt;/p>
&lt;h2 id="what-not-to-do-first">What not to do first&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>Do not reinstall Windows before reading the dump.&lt;/strong> Wiping the drive erases &lt;code>C:\Windows\Minidump&lt;/code> and Event Viewer history without fixing a hardware fault.&lt;/li>
&lt;li>&lt;strong>Do not blindly raise core or SoC voltages.&lt;/strong> Adding voltage changes electrical behavior and masks which setting caused the fault.&lt;/li>
&lt;li>&lt;strong>Do not replace the CPU over &lt;code>AuthenticAMD.sys&lt;/code> or &lt;code>GenuineIntel.sys&lt;/code>.&lt;/strong> Machine-check banks report cache, fabric, and IMC bus faults under the same module name.&lt;/li>
&lt;li>&lt;strong>Do not confuse corrected Event ID 17 warnings with fatal crashes.&lt;/strong> Log the warning count and device path, while keeping severity clear.&lt;/li>
&lt;li>&lt;strong>Do not swap three parts in one afternoon.&lt;/strong> Simultaneous swaps hide which change fixed the crash.&lt;/li>
&lt;/ul>
&lt;p>Microsoft Support&amp;rsquo;s consumer &lt;a href="https://support.microsoft.com/en-us/windows/experience/performance-optimization/how-to-fix-whea-uncorrectable-error" rel="noopener">WHEA fix page&lt;/a> adds Windows and driver updates when crash timing points to a recent software change. Let the WHEA record steer that choice.&lt;/p>
&lt;h2 id="the-stopping-rule">The stopping rule&lt;/h2>
&lt;p>RMA or replace a part only when the WHEA record, slot isolation, or a vendor diagnostic pins the fault to that specific component. No dump file yet? Hold stock BIOS defaults, verify pagefile and small-dump settings, and let one clean capture tell you the answer.&lt;/p>
&lt;h2 id="sources">Sources&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x124---whea-uncorrectable-error" rel="noopener">Microsoft Learn: Bug Check 0x124 WHEA_UNCORRECTABLE_ERROR&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/whea/hardware-errors-and-error-sources" rel="noopener">Microsoft Learn: Hardware Errors and Error Sources&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/whea/error-records" rel="noopener">Microsoft Learn: WHEA Error Records&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/whea/error-processing" rel="noopener">Microsoft Learn: WHEA Error Processing&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/debuggercmds/-errrec" rel="noopener">Microsoft Learn: &lt;code>!errrec&lt;/code> in WinDbg&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/read-small-memory-dump-file" rel="noopener">Microsoft Learn: Read Small Memory Dump Files&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/configure-system-failure-and-recovery-options" rel="noopener">Microsoft Learn: Configure System Failure and Recovery Options&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/opening-a-crash-dump-file-using-windbg" rel="noopener">Microsoft Learn: Open a Dump File with WinDbg&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/experience/performance-optimization/how-to-fix-whea-uncorrectable-error" rel="noopener">Microsoft Support: How to Fix WHEA_UNCORRECTABLE_ERROR&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://support.microsoft.com/en-us/windows/security/encryption/find-your-bitlocker-recovery-key" rel="noopener">Microsoft Support: Find Your BitLocker Recovery Key&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>Windows 11 Not Detecting a Second Monitor: Find the Cause</title><link>https://techfuelhq.com/articles/windows-11-not-detecting-second-monitor-2026/</link><pubDate>Fri, 02 Oct 2026 00:00:00 -0500</pubDate><dc:creator>LK Wood IV</dc:creator><guid>https://techfuelhq.com/articles/windows-11-not-detecting-second-monitor-2026/</guid><atom:updated>2026-11-14T10:45:00Z</atom:updated><description>&lt;p>By &lt;a href="https://techfuelhq.com/author/lk-wood-iv/">LK Wood IV&lt;/a> · Published 2026-10-02 · Updated 2026-11-14 · St. Louis County, MO&lt;/p>
&lt;p>A second monitor that Windows 11 will not list has a short list of causes, and most of them sit outside Windows. The cable is plugged into a rear motherboard port that nothing drives, a directional converter cable faces the wrong way, the monitor&amp;rsquo;s DisplayPort scaler is wedged in deep sleep with its EDID offline, or a laptop USB-C port carries no video. Drivers sit near the bottom of that list.&lt;/p>
&lt;p>Your primary screen still works. Use it. Four checks on the working desktop will isolate the physical layer before you touch Display Driver Uninstaller or order parts.&lt;/p>
&lt;p>This page covers a second screen that stays dark while the first display works. If your only screen is black, start with &lt;a href="https://techfuelhq.com/articles/monitor-no-signal-2026/">monitor says No Signal&lt;/a>. If a detected screen works and then drops out mid-session, read &lt;a href="https://techfuelhq.com/articles/monitor-keeps-going-black-2026/">monitor keeps going black&lt;/a>.&lt;/p>
&lt;h2 id="start-on-the-screen-that-works">Start on the screen that works&lt;/h2>
&lt;p>The names below match Windows 11 Home 25H2, build 26200.9457, read on September 29, 2026.&lt;/p>
&lt;ol>
&lt;li>Press &lt;code>Windows + P&lt;/code>. A flyout named Project opens with four modes: PC screen only, Duplicate, Extend, and Second screen only. When PC screen only is highlighted, Windows intentionally turns off every secondary output. Click Extend. Microsoft&amp;rsquo;s &lt;a href="https://support.microsoft.com/en-us/windows/hardware/display-graphics/troubleshoot-external-monitor-connections-in-windows" rel="noopener">external-monitor troubleshooting page&lt;/a> starts with that exact shortcut.&lt;/li>
&lt;li>Open &lt;code>Settings &amp;gt; System &amp;gt; Display&lt;/code>. Microsoft&amp;rsquo;s &lt;a href="https://support.microsoft.com/en-us/windows/hardware/display-graphics/how-to-use-multiple-monitors-in-windows" rel="noopener">multiple-monitor guide&lt;/a> notes that Windows draws numbered rectangles as soon as more than one display answers. Seeing boxes &lt;code>1&lt;/code> and &lt;code>2&lt;/code> confirms physical detection.&lt;/li>
&lt;li>If no numbered boxes appear, expand Multiple displays and click Detect. With a single monitor attached on build 26200.9457, Detect prints &lt;code>&amp;quot;We didn't find another display.&amp;quot;&lt;/code> directly beneath the button, meaning no active graphics adapter received a Hot Plug Detect (&lt;code>HPD&lt;/code>) and Extended Display Identification Data (&lt;code>EDID&lt;/code>) handshake on another port.&lt;/li>
&lt;li>Open Device Manager and expand both Monitors and Display adapters. Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/display/monitor-class-function-driver" rel="noopener">monitor class driver reference&lt;/a> explains that each connected output enumerates under Monitors; on a laptop, one of those entries is the internal panel.&lt;/li>
&lt;/ol>
&lt;p>Check the dark monitor&amp;rsquo;s front LED and OSD buttons next. An amber standby LED with an on-screen &lt;code>No Signal&lt;/code> banner proves the panel has AC power, though you still must press the monitor&amp;rsquo;s physical input button to select &lt;code>DisplayPort&lt;/code>, &lt;code>HDMI 1&lt;/code>, or &lt;code>HDMI 2&lt;/code> manually—auto-scan routinely misses a freshly woken port.&lt;/p>
&lt;h2 id="display-topology-and-adapter-directionality-checklist">Display topology and adapter directionality checklist&lt;/h2>
&lt;p>Before chasing Windows updates, walk the physical path from GPU silicon to panel scaler. Almost every &lt;code>&amp;quot;We didn't find another display&amp;quot;&lt;/code> ticket I troubleshoot fails one of these five physical checks:&lt;/p>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">Topology checkpoint&lt;/th>
&lt;th scope="col">How the trap looks on a desk&lt;/th>
&lt;th scope="col">Why Windows sees zero monitor&lt;/th>
&lt;th scope="col">Exact verification / fix&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="Topology checkpoint">&lt;strong>Motherboard rear-I/O vs discrete GPU bracket&lt;/strong>&lt;/td>
&lt;td data-label="How the trap looks on a desk">Monitor 1 is plugged horizontally into the graphics card lower on the case; Monitor 2 is plugged vertically near the USB/Ethernet ports.&lt;/td>
&lt;td data-label="Why Windows sees zero monitor">Desktop boards often disable CPU integrated graphics when a PCIe GPU is installed, and Intel &lt;code>-F&lt;/code> CPUs lack iGPU silicon altogether.&lt;/td>
&lt;td data-label="Exact verification / fix">Move Monitor 2&amp;rsquo;s cable down to a spare HDMI or DisplayPort socket on the discrete graphics card itself.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Topology checkpoint">&lt;strong>Unidirectional DP-to-HDMI vs HDMI-to-DP cables&lt;/strong>&lt;/td>
&lt;td data-label="How the trap looks on a desk">A passive &lt;code>DisplayPort-to-HDMI&lt;/code> cable or dongle connected backward from a PC/laptop &lt;strong>HDMI output&lt;/strong> into a monitor&amp;rsquo;s &lt;strong>DisplayPort input&lt;/strong>.&lt;/td>
&lt;td data-label="Why Windows sees zero monitor">Passive cables rely on Dual-Mode DisplayPort (&lt;code>DP++&lt;/code>) voltage/protocol shifting on a DP &lt;em>source&lt;/em>; HDMI ports cannot emit DisplayPort link training in reverse.&lt;/td>
&lt;td data-label="Exact verification / fix">Read the moulded housing arrows (&lt;code>Source -&amp;gt; Display&lt;/code>). HDMI-source to DP-monitor requires an &lt;strong>active, USB-powered HDMI-to-DP converter&lt;/strong>—or switch to HDMI-to-HDMI / DP-to-DP.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Topology checkpoint">&lt;strong>DisplayPort deep-sleep EDID lockup&lt;/strong>&lt;/td>
&lt;td data-label="How the trap looks on a desk">Monitor worked yesterday, went into standby overnight, and now stays dark with &lt;code>&amp;quot;We didn't find another display&amp;quot;&lt;/code> even after rebooting the PC.&lt;/td>
&lt;td data-label="Why Windows sees zero monitor">Many DisplayPort scalers drop &lt;code>HPD&lt;/code> or stop serving &lt;code>EDID&lt;/code> if internal standby capacitors brown out or hang during deep sleep; clicking soft power on the bezel leaves the scaler rail powered.&lt;/td>
&lt;td data-label="Exact verification / fix">&lt;strong>60-second AC power reset:&lt;/strong> unplug the monitor&amp;rsquo;s AC wall cord (or pull the external power brick from the wall &lt;em>and&lt;/em> barrel jack) for a full 60 seconds, hold the monitor power button for 5 seconds, reconnect AC power, then wake Windows.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Topology checkpoint">&lt;strong>USB-C data-only port or non-Alt-Mode hub&lt;/strong>&lt;/td>
&lt;td data-label="How the trap looks on a desk">Monitor plugged via USB-C-to-DP/HDMI into a front-panel case USB-C port or a cheap 4-port USB-C data hub.&lt;/td>
&lt;td data-label="Why Windows sees zero monitor">Standard USB 3.x / 5 Gbps / 10 Gbps data ports carry no VESA DisplayPort Alt Mode lanes unless wired to a GPU/iGPU mux or DisplayLink chip.&lt;/td>
&lt;td data-label="Exact verification / fix">Plug directly into a rear laptop port marked with the DP/&lt;code>D&lt;/code> or Thunderbolt lightning icon, or verify DisplayLink driver installation for USB graphics docks.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="Topology checkpoint">&lt;strong>&lt;code>Win + P&lt;/code> mode or ghost EDID state&lt;/strong>&lt;/td>
&lt;td data-label="How the trap looks on a desk">Monitor appears under hidden Device Manager entries (or shows &lt;code>&amp;quot;Display 2 isn't active&amp;quot;&lt;/code>) while staying black.&lt;/td>
&lt;td data-label="Why Windows sees zero monitor">Windows stored &lt;code>PC screen only&lt;/code>, disabled the target topology in cached CCD display state, or hit an adapter pipe limit.&lt;/td>
&lt;td data-label="Exact verification / fix">Press &lt;code>Win + P&lt;/code> -&amp;gt; &lt;code>Extend&lt;/code>, enable the display inside &lt;code>Settings &amp;gt; System &amp;gt; Display&lt;/code>, and inspect &lt;code>Device Manager &amp;gt; View &amp;gt; Show hidden devices&lt;/code> only after physical cable checks pass.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;p>That &lt;strong>60-second AC brick pull&lt;/strong> deserves special emphasis. Rebooting Windows, swapping GPU ports, and tapping the bezel power button all leave standby 5V/3.3V power alive inside the monitor&amp;rsquo;s scaler board; &lt;a href="https://www.dell.com/support/contents/en-us/article/product-support/self-support-knowledgebase/monitor-screen-video/multiple-displays-not-working" rel="noopener">Dell&amp;rsquo;s multi-monitor black-screen guide&lt;/a> and &lt;a href="https://www.displayport.org/faq/" rel="noopener">VESA&amp;rsquo;s DisplayPort FAQ&lt;/a> highlight input/handshake resets so the internal controller cold-boots cleanly and re-asserts Hot Plug Detect. Whenever a DisplayPort screen vanishes after sleep or a power flicker, pull its wall plug for a full minute before touching software.&lt;/p>
&lt;h2 id="windows-10-and-an-extra-display-that-is-not-really-connected">Windows 10 and an extra display that is not really connected&lt;/h2>
&lt;p>On Windows 10, open &lt;code>Settings &amp;gt; System &amp;gt; Display&lt;/code> and click Detect under Multiple displays; on Windows 11, expand Multiple displays first. Both OS versions share &lt;code>Win + P &amp;gt; Extend&lt;/code> per &lt;a href="https://support.microsoft.com/en-us/windows/hardware/display-graphics/how-to-use-multiple-monitors-in-windows" rel="noopener">Microsoft&amp;rsquo;s multiple-monitor instructions&lt;/a>.&lt;/p>
&lt;p>What if Settings shows a phantom box &lt;code>2&lt;/code> or &lt;code>3&lt;/code> that matches no physical screen? Click Identify first, disconnect docks and dongles, and reconnect one direct cable at a time. Note whether the extra entry is an active numbered rectangle in Display Settings or merely a faded grey icon in Device Manager.&lt;/p>
&lt;p>Write that layout down before deleting devices.&lt;/p>
&lt;p>The &lt;a href="#one-fix-to-skip-and-one-to-leave-for-last">hidden-device section below&lt;/a> covers why faded Device Manager entries accumulate harmlessly over time. If your second monitor &lt;em>is&lt;/em> detected yet blanks out for a couple of seconds under load, switch to &lt;a href="https://techfuelhq.com/articles/monitor-keeps-going-black-2026/">intermittent-blackout checks&lt;/a> or our &lt;a href="https://techfuelhq.com/articles/monitor-flickering-fix-2026/">monitor flickering guide&lt;/a> rather than mashing Detect.&lt;/p>
&lt;h2 id="what-each-result-points-to">What each result points to&lt;/h2>
&lt;div class="table-wrap">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th scope="col">What you found&lt;/th>
&lt;th scope="col">The cause and where to go&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td data-label="What you found">Project was set to PC screen only&lt;/td>
&lt;td data-label="The cause and where to go">The display mode. Choosing Extend was the fix.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you found">Two numbered displays in Settings, second screen dark&lt;/td>
&lt;td data-label="The cause and where to go">Windows has the monitor and is not using it. See &lt;a href="#windows-lists-the-monitor-and-the-screen-stays-dark">Windows lists the monitor&lt;/a>.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you found">&amp;ldquo;We didn&amp;rsquo;t find another display&amp;rdquo; on a desktop with a graphics card&lt;/td>
&lt;td data-label="The cause and where to go">Rule out first a cable in a port that nothing drives. See &lt;a href="#the-cable-is-in-the-motherboard-port">the motherboard port&lt;/a>.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you found">The same message with an adapter, a converter cable or a splitter in the path&lt;/td>
&lt;td data-label="The cause and where to go">The adapter&amp;rsquo;s direction or type. See &lt;a href="#an-adapter-or-a-splitter-is-in-the-path">adapters and splitters&lt;/a>.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you found">The same message on a laptop&amp;rsquo;s USB-C port, a hub or a dock&lt;/td>
&lt;td data-label="The cause and where to go">The port carries no video, or the dock needs its driver. See &lt;a href="#a-laptop-usb-c-port-or-a-dock">USB-C and docks&lt;/a>.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you found">Two screens work and a third or fourth will not appear&lt;/td>
&lt;td data-label="The cause and where to go">The graphics adapter&amp;rsquo;s display limit. See &lt;a href="#more-screens-than-the-graphics-adapter-drives">the display limit&lt;/a>.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you found">It worked until a Windows or driver update&lt;/td>
&lt;td data-label="The cause and where to go">The display driver. See &lt;a href="#it-worked-until-an-update">after an update&lt;/a>.&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td data-label="What you found">Detected at startup, lost after the PC sleeps&lt;/td>
&lt;td data-label="The cause and where to go">Often DisplayPort&amp;rsquo;s hot-plug behavior on wake. See &lt;a href="https://techfuelhq.com/articles/monitor-keeps-going-black-2026/#after-sleep">the after-sleep section of monitor keeps going black&lt;/a>.&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h2 id="windows-lists-the-monitor-and-the-screen-stays-dark">Windows lists the monitor and the screen stays dark&lt;/h2>
&lt;p>Two numbered displays in Settings, or a second entry under Monitors, mean the PC has found the monitor, so what is left is how Windows is using it and which input the monitor is showing.&lt;/p>
&lt;p>Select display 2. Dell&amp;rsquo;s &lt;a href="https://www.dell.com/support/contents/en-us/article/product-support/self-support-knowledgebase/monitor-screen-video/multiple-displays-not-working" rel="noopener">multi-monitor guide&lt;/a> lists the choices in the display drop-down as Duplicate these displays, Extend these displays, Show only on 1 and Show only on 2. Pick Extend these displays, select Apply, then Keep changes.&lt;/p>
&lt;p>If the desktop is extended and the panel is still dark, go back to the monitor. Dell&amp;rsquo;s answer for a No Signal message is to select the correct input source on the monitor and check the cable connections, which in practice means using the monitor&amp;rsquo;s own buttons to choose the input the cable is plugged into, then reseating the cable.&lt;/p>
&lt;p>If Advanced display says &amp;ldquo;Display 2 isn&amp;rsquo;t active&amp;rdquo;, Windows has the monitor and is sending it nothing. Microsoft&amp;rsquo;s Q&amp;amp;A site has &lt;a href="https://learn.microsoft.com/en-us/answers/questions/4163127/display-isnt-active-in-windows-11" rel="noopener">a thread on that message&lt;/a> that at least 100 people have marked as their question too. It started from two monitors on a dock, and the fix reported in the thread was in Intel Graphics Command Center, under Display, where the deactivated screen has a three-dot menu with an enable option.&lt;/p>
&lt;h2 id="the-cable-is-in-the-motherboard-port">The cable is in the motherboard port&lt;/h2>
&lt;p>A desktop with a graphics card usually has two sets of video ports. One set sits in the motherboard&amp;rsquo;s block of sockets, with the USB and network ports, and runs from the graphics built into the processor — ASUS&amp;rsquo;s FAQ calls it integrated graphics. The other set is on the card.&lt;/p>
&lt;p>The board&amp;rsquo;s set is sometimes switched off. Intel&amp;rsquo;s &lt;a href="https://www.intel.com/content/www/us/en/support/articles/000058190/graphics.html" rel="noopener">support article on integrated graphics&lt;/a> says some desktop computers disable it automatically when they detect a graphics card, and that you may be able to turn it back on in the system BIOS.&lt;/p>
&lt;p>The workstation on the &lt;a href="https://techfuelhq.com/about/">About page&lt;/a> is built this way. Its board is an &lt;a href="https://techfuelhq.com/reviews/rog-strix-b650a-review-2026/">ASUS ROG STRIX B650-A Gaming WiFi&lt;/a>, which &lt;a href="https://rog.asus.com/motherboards/rog-strix/rog-strix-b650-a-gaming-wifi-model/spec/" rel="noopener">ASUS&amp;rsquo;s specification page&lt;/a> gives one DisplayPort and one HDMI port, and the processor in it is a Ryzen 7 7800X3D. Read with Get-PnpDevice on October 2, 2026, the processor&amp;rsquo;s graphics, AMD Radeon(TM) Graphics, is listed as not present. Device Manager hides a device like that until View, Show hidden devices is on. So nothing drives the board&amp;rsquo;s two ports.&lt;/p>
&lt;p>So read Display adapters on yours and look for the processor&amp;rsquo;s own graphics. If it is missing, or shows only with hidden devices on, the fix is free. Move the second monitor&amp;rsquo;s cable to a port on the card. If it is listed beside the card in the normal view, the board&amp;rsquo;s ports are live and your cause is further down this page. If the card you installed is missing from the list, the card is the fault, and &lt;a href="https://techfuelhq.com/articles/graphics-card-not-detected-2026/">graphics card not detected&lt;/a> covers it.&lt;/p>
&lt;p>Some processors have no graphics at all. Intel&amp;rsquo;s &lt;a href="https://www.intel.com/content/www/us/en/processors/processor-numbers.html" rel="noopener">naming guide&lt;/a> marks the F suffix &amp;ldquo;Requires discrete graphics&amp;rdquo;, so a motherboard port on one of those will never light.&lt;/p>
&lt;p>To run a screen from the board on purpose, ASUS&amp;rsquo;s &lt;a href="https://www.asus.com/us/support/faq/1045574/" rel="noopener">multi-monitor FAQ&lt;/a> gives the BIOS switch. Its Intel example is iGPU Multi-Monitor, under Advanced, System Agent (SA) Configuration, Graphics Configuration, and its AMD example is IGFX Multi-Monitor, under Advanced, NB Configuration. The same FAQ says AM5 boards and Intel 800-series boards support dual display by default, so they don&amp;rsquo;t need the switch. I would still check Device Manager.&lt;/p>
&lt;h2 id="an-adapter-or-a-splitter-is-in-the-path">An adapter or a splitter is in the path&lt;/h2>
&lt;p>A wrong adapter gives Windows nothing to detect, and direction is the first thing to check. Dell&amp;rsquo;s &lt;a href="https://www.dell.com/support/kbdoc/en-us/000125170/hdmi-to-displayport-dp-conversion-information" rel="noopener">adapter guide&lt;/a> says an adapter built to convert DisplayPort to HDMI cannot work in reverse, and that a passive one works only from a DisplayPort output to an HDMI screen, because it relies on the graphics card supporting Dual-Mode DisplayPort, marked DP++.&lt;/p>
&lt;p>Going from an HDMI output to a DisplayPort monitor always takes an active adapter, and Dell&amp;rsquo;s table lists DisplayPort to DVI and DisplayPort to VGA as active too. If the adapter has a USB lead, plug it in. Dell says it powers the conversion.&lt;/p>
&lt;p>USB-C converters have a direction as well. VESA&amp;rsquo;s &lt;a href="https://www.displayport.org/faq/" rel="noopener">DisplayPort FAQ&lt;/a> says USB-C to HDMI, DVI and VGA converters need to be plugged into the device that is sending the video.&lt;/p>
&lt;p>A splitter cannot do this job at all. Microsoft&amp;rsquo;s troubleshooting page says a display splitter duplicates the same signal and does not create two independent ones, so there is no second display for Windows to extend onto.&lt;/p>
&lt;p>The test is the same for all three. Take it out of the path, which is Microsoft&amp;rsquo;s first hardware step as well: disconnect docks, dongles and adapters and connect the monitor directly.&lt;/p>
&lt;h2 id="a-laptop-usb-c-port-or-a-dock">A laptop USB-C port or a dock&lt;/h2>
&lt;p>A USB-C socket does not promise video. To send a picture on its own, the port has to support what VESA calls DisplayPort Alt Mode, and VESA&amp;rsquo;s FAQ says ports that do will normally carry the DP logo beside them. It adds that most video sources with a USB-C port support it even without the logo, and that the device&amp;rsquo;s documentation should say, so the laptop&amp;rsquo;s manual or specification page settles it.&lt;/p>
&lt;p>The same FAQ separates hubs from docks. A hub, as the USB Implementers Forum defines it, supports USB and no Alt Mode, and the product that carries video is a dock. A USB-only hub cannot carry Alt Mode video.&lt;/p>
&lt;p>Count the laptop&amp;rsquo;s video outputs as well. Microsoft says a PC with one video output port supports a single external monitor by default. A second one takes a docking station or, on a PC with a USB-C port, a USB adapter that may add a video output.&lt;/p>
&lt;p>Some docks and USB adapters work another way. They are built on DisplayLink&amp;rsquo;s USB graphics chips. Those need DisplayLink&amp;rsquo;s software. DisplayLink&amp;rsquo;s &lt;a href="https://support.displaylink.com/knowledgebase/articles/544834-how-to-install-displaylink-software-on-windows" rel="noopener">support article&lt;/a> says a working device appears in Device Manager under USB Display Adapters or Display adapters. If it sits under Other devices, Windows has not matched it to the driver, and the remedy is to uninstall the DisplayLink software and install the current release from &lt;a href="https://www.synaptics.com/products/displaylink-graphics/downloads/windows" rel="noopener">Synaptics&lt;/a>, which was 12.3, dated September 4, 2026, when I checked.&lt;/p>
&lt;h2 id="more-screens-than-the-graphics-adapter-drives">More screens than the graphics adapter drives&lt;/h2>
&lt;p>Every graphics adapter has a ceiling. NVIDIA lists the &lt;a href="https://www.nvidia.com/en-us/geforce/graphics-cards/50-series/rtx-5080/" rel="noopener">GeForce RTX 5080&lt;/a> at up to four. For Intel graphics, &lt;a href="https://www.intel.com/content/www/us/en/support/articles/000029126/graphics.html" rel="noopener">Intel&lt;/a> sends you to the processor&amp;rsquo;s specification page and its &amp;ldquo;# of Displays Supported&amp;rdquo; line, and warns that a PC maker can limit a system to one or two monitors.&lt;/p>
&lt;p>Microsoft&amp;rsquo;s page treats a second monitor the same way. If one external monitor works and another does not, the display adapter may not support more than one, and the adapter&amp;rsquo;s maker is who to ask.&lt;/p>
&lt;h2 id="it-worked-until-an-update">It worked until an update&lt;/h2>
&lt;p>This is the branch where the driver is a fair suspect. Work Microsoft&amp;rsquo;s order.&lt;/p>
&lt;ol>
&lt;li>Press Windows key + Ctrl + Shift + B, which resets the graphics driver.&lt;/li>
&lt;li>Restart. If that changes nothing, shut down and turn the PC back on.&lt;/li>
&lt;li>Roll the driver back. In Device Manager, expand Display adapters, right-click the adapter, choose Properties, open the Driver tab and select Roll Back Driver.&lt;/li>
&lt;li>If there is no roll back option, reinstall. Right-click the adapter, choose Uninstall device, tick Attempt to remove the driver for this device and select Uninstall. After the restart, right-click the adapter again and choose Update driver, then Search automatically for updated driver software.&lt;/li>
&lt;/ol>
&lt;p>Driver updates do break detection. Intel&amp;rsquo;s &lt;a href="https://www.intel.com/content/www/us/en/support/articles/000096421/graphics.html" rel="noopener">support article 000096421&lt;/a> records a case in which an HP ZR30w monitor stopped being recognized after an update to driver 31.0.101.4644 or 31.0.101.4669, on both Arc A750 and UHD Graphics 770, and Intel resolved it in 31.0.101.4885. Its remedy was to install that driver or a newer one as a clean install, using Display Driver Uninstaller and Safe Mode, the routine in my &lt;a href="https://techfuelhq.com/articles/gpu-driver-crash-fix-2026/">GPU driver crash guide&lt;/a>.&lt;/p>
&lt;p>Windows updates get blamed too. Windows 11, version 26H2, the Windows 11 2026 Update, began a phased rollout on September 29, 2026. It may be the update you noticed. Its &lt;a href="https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-26h2" rel="noopener">known-issues page&lt;/a> listed three issues on October 2, 2026: USB audio devices that fail to start, domain-joined PCs losing their trust relationship, and a black screen after sign-in that Microsoft has seen mainly in virtual desktop environments. None is about an external display. The pages for &lt;a href="https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-25h2" rel="noopener">25H2&lt;/a> and &lt;a href="https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-24h2" rel="noopener">24H2&lt;/a> listed nothing about it either on the same day.&lt;/p>
&lt;h2 id="one-fix-to-skip-and-one-to-leave-for-last">One fix to skip, and one to leave for last&lt;/h2>
&lt;p>One guide on this problem, updated in July 2025, tells readers to create a &lt;code>TdrDelay&lt;/code> registry value of &lt;code>8&lt;/code>. Skip it. Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys" rel="noopener">TDR registry documentation&lt;/a> defines &lt;code>TdrDelay&lt;/code> as the seconds the GPU scheduler waits on a preemption timeout before resetting a hung graphics driver, and explicitly warns that end users should not manipulate those keys. &lt;code>TdrDelay&lt;/code> never participates in EDID monitor detection.&lt;/p>
&lt;p>Ghost-EDID cleanup inside Device Manager (&lt;code>View &amp;gt; Show hidden devices&lt;/code>) belongs at the very end of the list, right after physical topology, 60-second AC power cycling, and driver rollback. Under &lt;code>Monitors&lt;/code>, faded &lt;code>Generic Monitor&lt;/code> or model-named icons simply represent past connections cached by Windows; Microsoft&amp;rsquo;s &lt;a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/install/viewing-hidden-devices" rel="noopener">hidden-devices documentation&lt;/a> notes that non-present entries ordinarily sit idle, and the About-page workstation carries two non-present &lt;code>Monitors&lt;/code> entries (&lt;code>Get-PnpDevice&lt;/code>, October 2, 2026) with zero effect on its live display.&lt;/p>
&lt;p>When a specific port-and-monitor pair stopped negotiating after a Windows update or dock swap—as reported in a &lt;a href="https://learn.microsoft.com/en-us/answers/questions/5646921/windows-11-cannot-detect-second-monitor-after-upda" rel="noopener">Microsoft Q&amp;amp;A update thread&lt;/a>—you can test a clean EDID re-enumeration safely:&lt;/p>
&lt;ol>
&lt;li>Unplug the affected second monitor&amp;rsquo;s video cable from the PC.&lt;/li>
&lt;li>Open Device Manager, click &lt;code>View &amp;gt; Show hidden devices&lt;/code>, and expand &lt;code>Monitors&lt;/code>.&lt;/li>
&lt;li>Right-click only the faded grey &lt;code>Generic Monitor&lt;/code> (or model-named monitor) entries and select &lt;code>Uninstall device&lt;/code>—never uninstall your live primary display adapter unless you are deliberately running a driver reinstall.&lt;/li>
&lt;li>Restart Windows, press &lt;code>Win + P&lt;/code> to confirm &lt;code>Extend&lt;/code>, and plug the powered-on second monitor directly into the discrete GPU port so Windows reads a fresh EDID block.&lt;/li>
&lt;/ol>
&lt;h2 id="when-the-monitor-or-the-cable-is-the-fault">When the monitor or the cable is the fault&lt;/h2>
&lt;p>If the checks above found nothing, test the parts. Microsoft&amp;rsquo;s list is short: change the cable, move it to another video port if the PC has one, and try the monitor on a different computer. A monitor that stays dark on a second machine, with a second cable, is the fault. One that works there sends you back to the first PC, and to whichever of its port, its adapter or its driver you have not yet ruled out.&lt;/p></description></item></channel></rss>