Guides & resources
Guides &
resources
Short, practical walkthroughs for the parts of installing software that nobody explains — plus a directory of longer write-ups we have published elsewhere.
Start here
Four habits that prevent almost every bad install
None of this is advanced. It is the checklist an experienced technician runs without thinking about it, written down so it can be followed once and then remembered.
1. Reach the source, not the search result
Type the developer's domain directly, or open their repository, rather than clicking the first result. Paid placements and lookalike domains cluster around popular free software, and the download they serve is rarely the one the author published.
2. Verify the file when a checksum is offered
If the release page lists a SHA-256 value, compare it against your download. On Windows that is one certutil command; on macOS and Linux, shasum -a 256. A match confirms the file arrived intact and unmodified. A mismatch means stop and download again from the source.
3. Read the installer instead of clicking through
Optional bundled offers appear two or three screens in, pre-selected, often phrased as a recommendation. Choose the custom or advanced path when it exists, and clear anything you did not come for. This one habit removes most unwanted toolbars and background updaters.
4. Keep a way back
Before driver or system-level changes, create a restore point. Before replacing a working tool, note its version. Being able to undo a change in two minutes is what makes experimenting on your own machine reasonable.
Portable or installed?
A portable build runs from a folder and leaves the rest of the system untouched, which makes it perfect for evaluating a tool, working on a machine you do not administer, or carrying a small kit on a USB stick. Installed builds earn their place when you want file associations, context-menu entries and automatic updates. For anything you rely on daily, install it; for anything you are still deciding about, run it portable first.
Moving a working setup to a new machine
Write down the tools you actually opened in the last month — it will be a shorter list than you expect. Export settings where the application supports it, copy the notes and documents folders as data rather than as applications, then reinstall each tool from its official source on the new machine. Restoring program folders wholesale is how old, broken configuration follows you around for years.
External write-ups
Longer notes published elsewhere.
Some pieces are too long for a catalogue page, so they live on other platforms. This directory keeps them in one place. Entries marked placeholder are slots reserved for articles that are not published yet.
- How to verify a software download in two minutes Checksums explained without the cryptography lecture, with the exact commands for Windows, macOS and Linux.
- Building a portable utilities kit on a USB stick Which tools work well without installation, how to organise them, and what to do about settings that expect a home folder.
- Rolling back a graphics driver without breaking anything else The order of operations for a clean removal and reinstall, and the three situations where a rollback is the wrong answer.
- Why a .docx breaks when three people edit it in three suites What actually changes during a round trip between office suites, and the exchange conventions that keep formatting intact.
- A twenty-minute disk space audit for a full system drive Finding the real offenders with a treemap, and which caches are safe to clear versus which ones simply rebuild overnight.
- Reading installer offer screens: a field guide Annotated screenshots of the patterns used to slip extra software past a fast clicker, and the wording to watch for.
- Setting up a new Windows machine in one evening An order of installation that avoids conflicts, with the short list of tools worth having before anything else.
Contribute
Know a guide that deserves a place here?
This directory grows from reader suggestions and our own notes. If a write-up genuinely solves a desktop software problem — yours or someone else's — send it over and we will read it properly.