{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiacrdfaps5ntpxogqqx2nly4zucbqti3h47pgnthbkvlna4u2pmja",
    "uri": "at://did:plc:25rdn5elo5izoxrmtis34zuk/app.bsky.feed.post/3mppai6iwy4b2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreictq3u46kgfmk5nozrg2773maf7zqmir4ozxrc2tsj7xthahbxppy"
    },
    "mimeType": "image/webp",
    "size": 74504
  },
  "path": "/systems_byreg/i-got-tired-of-rebuilding-my-diagnostic-usb-on-every-machine-so-i-fixed-it-once-2d62",
  "publishedAt": "2026-07-02T22:59:20.000Z",
  "site": "https://dev.to",
  "tags": [
    "windows",
    "sysadmin",
    "productivity",
    "tutorial"
  ],
  "textContent": "very IT tech I know has the same ritual. New machine lands on the bench, or you're at a client site, and before you can actually fix anything you spend twenty minutes assembling the same handful of tools. Download this. Extract that. Oh, this one wants .NET. Oh, this box has no internet. Oh, the client's policy blocks installs.\n\nI did that dance for years. Then I got tired of it and built a portable kit that lives on one USB stick and installs nothing. This post is mostly about what belongs on that stick — because whether you build your own or grab a packaged one, the thinking is the same, and I wish someone had just laid it out for me years ago.\n\nWhy \"no install\" is the whole game\n\nThe constraint that shapes everything is this: the machine you're diagnosing is often the machine you can't install software on.\n\nLocked-down corporate profiles block installers.\nA dying machine can't afford the disk writes or the reboot an installer wants.\nYou don't want to leave residue on a client's PC that isn't yours.\nHalf the time there's no internet to download anything anyway.\n\nSo the rule I settled on: everything runs from the USB, writes nothing to the host, and leaves no trace when I pull the drive. Portable executables and scripts only. If a tool needs to be installed, it doesn't make the cut.\n\nThat one rule kills a lot of otherwise-good tools and forces you toward the portable ecosystem. It's worth it.\n\nWhat actually goes on the stick\n\nI think about a diagnostic USB in three buckets. Same three problems, every single call:\n\n  1. System health — \"is this machine actually okay?\"\n\n\n\nBefore anything else, you want a fast read on the hardware and OS state:\n\nDisk health — SMART status, because a failing drive explains a lot of \"random\" symptoms. Catch it before you spend an hour chasing software ghosts.\nMemory + CPU + temps — a quick snapshot so you know if you're looking at a resource problem vs. a config problem.\nBoot and startup bloat — what's loading at login and dragging the thing down.\nWindows integrity — a quick way to check for corruption (sfc /scannow and DISM are built in and free, but knowing when to reach for them is the skill).\n\nThe goal of this bucket is a 60-second answer to \"hardware problem or software problem?\" — because that split decides everything you do next.\n\n  1. Network diagnostics — \"why won't this thing connect?\"\n\n\n\nHalf of all tickets are really network tickets wearing a costume. Portable tools I want on hand:\n\nAdapter + IP config at a glance — faster than typing ipconfig /all and squinting.\nDNS resolution testing — because \"the internet is down\" is usually \"DNS is down.\"\nConnectivity + latency — ping, traceroute, port checks, packaged so you're not building command lines by hand under pressure.\nWi-Fi signal / channel info — for the \"it's slow in this room\" calls that are really RF problems.\n\nBuilt-in Windows commands cover a surprising amount of this (ipconfig, nslookup, ping, tracert, netsh wlan show). The value of a kit is having them wrapped so you're reading answers, not typing syntax while the client watches.\n\n  1. Profile & user management — \"the account is the problem\"\n\n\n\nThis is the bucket people forget until they're stuck. So much Windows weirdness is really a broken or bloated user profile:\n\nCorrupt profile causing login loops or vanished settings.\nProfile bloat quietly eating the disk.\nNeeding to move or reset a user's environment without nuking their data.\n\nHaving a portable way to inspect and manage profiles turns a \"reimage the whole machine\" afternoon into a ten-minute fix more often than you'd think.\n\nPut it on the right USB\n\nSmall thing that matters: use a decent USB 3.0+ drive. A slow stick makes portable tools feel broken when they're just I/O-starved. Label it. Keep a second copy — the day your only diagnostic USB dies is always the day you need it most.\n\nThe honest part\n\nYou can absolutely build this yourself. Everything I described is assemblable from free portable tools plus commands already baked into Windows. If you enjoy curating your own kit, do that — you'll learn more.\n\nI got tired of maintaining mine and packaged it up so I stop rebuilding it every time I switch machines: three tools (system health, network diagnostics, profile manager) on one USB, Windows 11, no install, nothing left behind. If you'd rather not assemble your own, it's here: Portable Windows IT Toolkit ($34, one-time, instant download).\n\nEither way — build it or buy it — the lesson is the same one that took me too long to learn: decide your kit once, standardize on \"no install,\" and stop rebuilding it on every machine. Your future self, standing at a locked-down PC with no internet, will thank you.",
  "title": "I got tired of rebuilding my diagnostic USB on every machine, so I fixed it once"
}