Mini PC Setup: Step-by-Step Guide for Beginners

Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.

Buying the hardware is the easy half of the job; the mini PC setup that follows is where most first-time owners stall, because the box on the desk is either a finished Windows desktop or a bare chassis with no memory, no storage and no operating system — and those two demand completely different first moves. If the machine is still on your shortlist rather than on your desk, the N100 mini PC buying guide covers how barebone and configured listings actually differ.

That fork sets the order of everything that comes after. A configured system can walk straight into the Windows out-of-box experience. A barebone cannot post usefully until compatible memory and storage are fitted, and it has no reason to look for an operating system that was never installed. Get the sequence wrong and you end up buying DDR5 for a DDR4 socket, flashing firmware meant for a visually identical model, or chasing a boot failure that is really an M.2 SATA drive sitting in a PCIe-only slot.

The eleven steps below run from unpacking to a measured idle-power baseline: identify the exact SKU, install RAM and an SSD when required, confirm a stock boot, pick an operating system, change only the UEFI settings that OS needs, build installer media, install and update, decide whether firmware is worth touching, configure remote access and power recovery, deploy the first real workload, and record what the machine draws at idle.

The same sequence works whether the end state is a desktop, a Plex server, a Proxmox node, a NAS or a dedicated Home Assistant appliance — only the operating-system branch and the last two steps change. No prior experience with firmware menus or Linux permissions is assumed.

Before You Start — What You'll Need

A mini PC is a desktop, not a laptop. Nothing is built in, and a retail box contains no monitor, no keyboard, no mouse and no display cable.

• A monitor or TV plus a cable that matches both ends. Start with one direct connection — no dock, KVM or adapter in the path.
• A USB keyboard and mouse. A 2.4 GHz USB-receiver set beats Bluetooth for a first boot, because Bluetooth needs drivers the machine does not have yet.
• A second computer to download the image and write the installer drive onto a USB stick.
• An 8 GB or larger USB flash drive. Windows' own media tool wants a blank 8 GB drive; Ubuntu's installer recommends 8 GB or more for the stick and at least 25 GB of free space on the target.
• An Ethernet cable, particularly for a server operating system — installers routinely fail to bring up Wi-Fi on their own.
• A Phillips screwdriver if the machine is a barebone.
• Compatible SO-DIMM memory and a storage drive if the machine is a barebone. Step 2 covers how to choose them.

Expect the job to take anywhere from half an hour to most of an evening, depending on which machine you bought.

End to end, that works out at roughly 30–75 minutes for an already-configured Windows machine, 60–120 minutes for a barebone plus a clean operating-system install, and 90–180 minutes for a newcomer to reach a working homelab workload. Your own numbers will move with the machine, the drives and how many updates land on the first boot.

Step 1 — Identify the Exact Model You Bought

Product families are not specifications. A name like IT13, Air12, UN100 or SER5 can cover several processor generations, two different memory standards and three different storage layouts behind one retail page — and every purchase you make afterward depends on which one you actually received.

• GEEKOM's IT13 family currently carries a Core Ultra 7 356H configuration with DDR5 SO-DIMMs alongside a Core i5-13600H configuration with DDR4. Same name, incompatible memory.
• GEEKOM's Air12 covers N95, N100 and N150 processors, all on DDR5-4800 — but the CPU still has to be identified before any performance claim means anything.
• Minisforum's suffix system changes the machine: the original UN100 shipped with 16 GB of soldered LPDDR5-4800 and no SO-DIMM socket at all, while UN100L and UN100D variants differ again.
• GMKtec's G3 takes one DDR4-3200 SO-DIMM and states plainly that DDR5 is not compatible.
• Beelink's SER5 MAX name spans a 5800H chassis and lower-power Ryzen 5 configurations with different cooling and power behaviour.

Before ordering anything, write down five things: the exact CPU model, the memory generation and the number of SO-DIMM slots (or the fact that memory is soldered), the storage positions by length and protocol, the Ethernet controller, and whether the machine arrived as a barebone or with RAM, an SSD and an operating system already fitted. The machine's own system information supplies most of it once it boots; the manufacturer's page for the exact SKU fills in the rest.

If you want to know which company actually designs the board behind the badge — Beelink is Shenzhen AZW Technology, MINISFORUM sits inside the Meigao group, and ASUS took over the Intel NUC line — who makes mini PCs breaks down the brand-to-factory relationships.

Step 2 — Install Memory and Storage (Barebone Systems Only)

If the machine arrived with RAM, an SSD and Windows, skip to Step 3. If it arrived as a barebone, it may contain none of those, and it will not boot into anything useful until they are fitted. Unplug the power supply before opening the chassis.

DDR4 and DDR5 SO-DIMMs are not interchangeable. They differ in pin count, voltage and signalling, and no amount of "the slot looks the same" makes a DDR5 module work in a DDR4 machine. Match the generation first, then the speed.

Soldered memory cannot be upgraded. Compact systems such as the original Minisforum UN100 use onboard LPDDR5 with no socket, which makes memory capacity the single most important line on the listing — what you buy is what you keep.

A faster module label does not mean a faster machine. Mini-PC firmware frequently exposes no XMP or EXPO controls, so a DDR5-6000 enthusiast kit can quietly fall back to a JEDEC speed; Minisforum UM780 XTX owners reported exactly that, with XMP kits settling at 4800 MT/s. A JEDEC-rated kit is the safer purchase — the Crucial 32 GB DDR5-5600 SO-DIMM kit is the pattern to look for at 2×16 GB, CL46 and 1.1 V, and it will also run at 5200 or 4800 on a platform that sets a lower supported speed. For DDR4 machines such as the NUC 13 Pro or a SER5-class chassis, the equivalent is a 32 GB DDR4-3200 SO-DIMM kit at 2×16 GB, CL22 and 1.2 V, which downclocks to 2933 or 2666 where the platform requires it.

Fit two modules, not one, if you have integrated graphics. Radeon 780M and 890M systems and Intel Arc configurations all use system memory as graphics memory, and a single 32 GB stick halves the bandwidth. ASUS specifies two SO-DIMMs for the intended Arc graphics configuration on the NUC 14 Pro.

M.2 describes a shape, not a protocol. A slot can be PCIe/NVMe, SATA-only, or both, and drives come in 2242 (42 mm) and 2280 (80 mm) lengths with a matching screw or standoff. GMKtec's K8 Plus has two M.2 2280 PCIe 4.0 x4 positions and no SATA support at all. The GMKtec G3 pairs an M.2 2280 PCIe 3.0 NVMe slot with an M.2 2242 SATA slot. GEEKOM's IT13 chassis adds a third option — M.2 2280 PCIe 4.0 x4, M.2 2242 SATA and a 2.5-inch 7 mm SATA bay — and ASUS's NUC 13 Pro takes an M.2 2280 PCIe 4.0 x4 main drive while slim chassis may add an M.2 2242 SATA position and tall chassis add 2.5-inch SATA.

An M.2 2280 PCIe 4.0 NVMe drive such as the Crucial P3 Plus 1 TB works in a PCIe 4.0 slot and is electrically backward-compatible with slower PCIe NVMe slots, where it simply runs at the host's link speed. It is not a substitute for an M.2 SATA drive in a SATA-only slot. Where the chassis has a genuine 2.5-inch bay, a 1 TB 2.5-inch SATA SSD is the inexpensive way to add secondary storage.

Two mechanical cautions. Preserve the factory thermal pads and remove any protective film before closing the chassis, and do not stack a tall aftermarket SSD heatsink on a drive that already sits under a top plate designed to cool it.

Step 3 — Connect the Basics and Confirm a Stock Boot

Connect in this order: one display cable, keyboard and mouse, Ethernet if you have it, and the power supply last.

Start with a single direct display connection. Docks, KVMs, USB-C hubs and adapters add variables that have nothing to do with the mini PC, and a first boot that fails through a hub tells you nothing. A 48 Gbps HDMI 2.1 cable carries more bandwidth than a 1080p or 4K60 setup needs, but it removes cable ambiguity from the diagnosis. Only buy a DisplayPort 1.4 cable if both the mini PC and the monitor expose full-size DisplayPort — plenty of these machines offer HDMI and USB-C instead, and buying both "just in case" is wasted money.

For input, a USB-receiver set behaves like a plain wired keyboard and mouse the moment the USB stack loads. Bluetooth is the wrong choice for a first boot, because the drivers that would make it work are on the disk you have not installed yet — the Logitech MK270 is the classic example of a 2.4 GHz receiver set with no pairing step.

Power on and confirm two things before anything else: the firmware reports the full memory capacity you fitted, and it lists the SSD. That is the entire point of this step. A configured Windows machine can complete its out-of-box experience here — there is no reason to start changing firmware settings before the hardware underneath is proven.

If no display output appears, reseat the memory until both clips engage, confirm the drive length and standoff match the slot, and try the other display output, since these machines commonly split their video across two HDMI ports plus USB-C or DisplayPort.

Step 4 — Choose the Operating System

Two rules matter more than the table. First, Proxmox earns its place when there are several workloads to isolate — Home Assistant plus Jellyfin plus Docker plus a test VM. If Home Assistant is the only thing the box will ever run, Home Assistant OS on bare metal is less machinery to maintain for the same result.

Second, pick the operating system you can maintain rather than the one that sounds more professional. Plex on Windows is a perfectly good first server; Linux becomes worth the learning curve once the machine is primarily a service host and you want SSH, containers and unattended updates. If the box is going to run Linux, the best mini PCs for Ubuntu covers which hardware exposes its networking, Wi-Fi and graphics cleanly; if it is going to be a hypervisor, the Proxmox hardware guide covers NIC controllers, IOMMU groups and idle power.

Download the installer from the project's own download page rather than from a walkthrough that pins an older release. It matters: the current x86 Proxmox VE installer is 9.2-1, while several widely circulated mini-PC Proxmox tutorials still describe an earlier generation. Debian's current stable release is 13, codenamed trixie.

Step 5 — Configure UEFI for Your Chosen OS

Firmware menus differ by vendor and the setting names differ with them. "Restore on AC Power Loss", "State After G3", "SVM Mode", "Intel Virtualization Technology" and "IOMMU" mean roughly what they sound like, but there is no universal menu path to follow. Change only what your chosen operating system requires:

• Boot order. Use the one-time boot menu to launch the installer rather than permanently moving USB to the front of the queue.
• Virtualization (VT-x / AMD-V / SVM). Required for Proxmox or any virtual machine workload; usually enabled from the factory.
• VT-d / AMD-Vi / IOMMU. Relevant only for device passthrough — a GPU, NIC or storage controller handed to a VM. It is not needed simply to run containers.
• Secure Boot. Conditional, and the two extremes prove it: Windows 11 expects a system capable of Secure Boot, while Home Assistant OS's generic x86-64 installation specifies Secure Boot disabled. Neither "always on" nor "always off" is correct.
• Restore after power loss. Useful on an unattended server so the machine returns after an outage, irrelevant on a desktop.
• Power mode and fan curve. Leave these at stock until you have a real heat or noise problem; the profile changes acoustics as much as performance.
• XMP / EXPO. Do not assume the controls exist. Where they do not, a JEDEC-rated module is the answer, not a firmware hunt.
• Wake-on-LAN. Configured partly in firmware and partly in the operating system; on Windows, Fast Startup can change whether WOL works from the S5 state.

Then hold one discipline for the whole step: change a single setting, save, reboot and confirm the machine still posts. Six options changed at once followed by a black screen leave no route back to a known-good state.

Step 6 — Build Installer Media and Install the OS

Write the installer image from your main computer, not the mini PC, and remember that writing an image erases the USB drive. Windows' media tool requires a blank drive of at least 8 GB, while Ubuntu's installer recommends an 8 GB or larger flash drive and at least 25 GB of space on the target. A 128 GB USB 3.0 flash drive is far larger than any of these need, which is exactly what makes it a reusable installer and recovery stick rather than a write-once purchase.

Plug the drive directly into the mini PC during installation. Hubs and front-panel adapters create failures that look like a corrupt image.

The most expensive mistake at this step is choosing the wrong disk. If the machine already carries a Windows installation on its original SSD and you have added a second drive, the installer will list both without prejudice. Check capacity and position before committing.

Windows installs must match the licence held in firmware: a Pro key will not activate a Home installation, and the edition the machine shipped with is the edition to reinstall.

On a machine destined to be headless, install with a wired connection, create the user account and enable OpenSSH during installation so the box is reachable the moment it reboots. You still need a display and keyboard for the firmware work in Steps 5 and 8 — the headless part begins once the operating system is in.

Step 7 — Update the OS First, Then Vendor Drivers

Install operating system updates first, then vendor drivers. Windows Update is not a guarantee of chipset, network or graphics completeness, and the manufacturer's support page for the exact model should still be checked for chipset, Ethernet and graphics packages.

On an Intel machine that will transcode, the graphics and media driver is the piece that matters, because Quick Sync is what Plex and Jellyfin will use. On AMD, the graphics stack ships in the kernel, so a current distribution kernel is worth more than any download.

On Linux media servers, hardware acceleration means exposing the DRM render node (/dev/dri) to the application or container and granting the service account access to the render and video groups. A low-power N-series box running an older 6.8-generation kernel can fail to expose that node at all; a current kernel and Intel media driver resolve it.

Then let the machine finish. Updates, driver installs and background indexing run for a while after first boot, and both noise and power draw sit higher until they settle. Do not judge acoustics or idle wattage until the disk activity stops.

Step 8 — Decide Whether the Firmware Actually Needs Updating

Updating firmware is not step one, and on a machine that boots and behaves correctly it is often not a step at all.

The reason is branch fragmentation. Beelink's support process for models such as the SER7 asks for the serial number and installed BIOS before supplying a file, and users have reported multiple branch builds under one model name that are not interchangeable. Searching for "latest BIOS" and flashing the first result is how a working machine becomes a paperweight.

If you do update:

• Confirm the exact model and hardware revision against the manufacturer's support page.
• Compare the installed version with the file on offer before downloading anything.
• Read what the update actually changes. Firmware revisions can alter microcode, C-states, PCIe behaviour, power management, memory compatibility and IOMMU grouping.
• On a machine already running virtual machines with passthrough, record the working BIOS version first so you keep a known-good reference.
• Flash only a file published for that exact model and revision, from a stable power source.

Once the machine is stable, a fixed support issue or a measured idle-power improvement is a legitimate reason to update. "It might help" is not.

Step 9 — Set Up Remote Access and Power Recovery

Set up remote access, and test it in the right order: local login first, remote second. A firewall or addressing mistake made on a machine you can no longer reach locally costs an evening and a spare monitor.

• Remote shell or desktop. SSH for Linux, RDP for Windows, and Tailscale or WireGuard if the machine will be reached from outside the house.
• Wake-on-LAN. Firmware and operating system both have a part to play; on Windows, check Fast Startup's effect on behaviour from the S5 state before concluding WOL is broken.
• Restore after AC loss. On a server, enable it so an unattended machine comes back after an outage.
• A second network interface if the chassis has only one port and you need separate WAN/LAN or a second path. A USB 2.5GbE adapter works, but its official compatibility list covers Windows, macOS, ChromeOS and iOS — check the chipset and driver situation for Linux before depending on it, and prefer a built-in Intel 2.5GbE controller where the chassis offers one.
• A powered USB hub such as the Anker 7-port 36 W model once several bus-powered drives or dongles are in play. Keep it out of the picture during boot troubleshooting.
• A UPS for anything holding filesystems or databases. A 600 VA / 330 W unit with five battery-backed outlets gives a NAS or hypervisor time to shut down cleanly; it is not hours of runtime, and it has no place on a desk machine's shopping list.

After every remote-access change, verify that you can still log in at the console.

Step 10 — Deploy the First Workload

Pick one job and finish it before tuning anything. Optimising a machine that has not yet done its actual work is the most reliable way to lose a weekend.

• Desktop. Browsers, office applications and the emulation layer if that is the point of the machine.
• Media server. Install Plex or Jellyfin, point it at a library and confirm a Direct Play session before testing transcodes. Hardware transcoding needs the media path working end to end — Quick Sync on Intel, VA-API on AMD — plus permission for the service to reach the render device.
• Hypervisor. Create one VM or one container and boot it. Get that working before adding storage pools, passthrough devices or a second NIC.
• Home Assistant. Restore or create a backup early, and confirm the machine recovers after a restart before automating anything you care about.
• NAS. Create the pool and one share, then confirm the data survives a reboot.

If the box exists only to hold a media library and Home Assistant, a dedicated HTPC mini PC is a simpler target than a hypervisor you have to maintain.

Step 11 — Measure a Real Idle-Power Baseline

The last step is the one almost nobody performs, and it is the one that pays off every month: measure what the machine actually draws.

Processor power specifications are not system power. An N100's 6 W processor base power is not the wall figure for a complete N100 mini PC — memory, storage, network controllers, fans and power-supply losses all add to the total.

Take a clean measurement:

• Finish updates, driver installs and any indexing first.
• Let the machine reach a stable idle.
• Switch the display off.
• Keep the normal network link active and the intended storage installed.
• Measure at the AC outlet with a plug-in meter.

Write the number down. It is the only honest baseline for judging a later change — a different kernel, a disabled ASPM setting or an extra NIC — and it is easy to reason about: one continuous watt is 8.76 kWh over a year, so a 5 W difference is worth more than 40 kWh annually per machine.

Common Mistakes to Avoid

• Ordering memory from the family name instead of the exact SKU. One product page can list a DDR5 configuration and a DDR4 configuration side by side.
• Assuming DDR5 works in a DDR4 socket, or the reverse. The two generations are not interchangeable in either direction.
• Assuming M.2 means NVMe. A slot can be SATA-only, and a 2280 drive will not fit a 2242 position.
• Opening the chassis of a machine that shipped configured before confirming whether it did.
• Making the firmware update the first task. Establish a stock boot, identify the revision, then decide.
• Applying a single BIOS recipe to every machine. Secure Boot, IOMMU, AC-loss restore and power profiles are all workload-dependent.
• Troubleshooting a first boot through a dock, hub or KVM. Those devices belong in the setup only once the machine is proven.
• Configuring remote access before local login works, which is how a small mistake becomes an evening on the floor with a keyboard.
• Reading processor base power as wall consumption. Measure the complete system at the outlet.
• Judging noise or idle power before updates and indexing settle. The first hour is not representative.

Frequently Asked Questions

Conclusion

Mini PC setup is a short, ordered job once the first question is answered correctly: what is actually in the box? A configured machine and a barebone take different routes to the same place, and almost every beginner failure — the wrong memory generation, a SATA drive in a PCIe slot, a firmware file built for a different revision — comes from skipping the identification step.

From there the sequence is deliberately conservative. Prove a stock boot before touching firmware, change one setting at a time, install the operating system you can actually maintain, update the OS before the vendor drivers, and treat a BIOS flash as the fix for a specific problem rather than a rite of passage. The final step is the one worth keeping: a wall-meter reading at idle gives you a baseline to measure every future change against.

If the hardware is still undecided, the mini PC testing hub collects the full pick lists, and what you should actually pay walks through how barebone pricing, memory and licensing really add up. Buyers working to a budget should start with the cheapest mini PCs, while anyone short on desk space can compare the smallest ultra-compact options — both decisions belong before these setup steps, not after them.