Skip to content

Windows PC — FAQ

Windows workstation at 192.168.2.200 — client only; servers run on TrueNAS. See PC index.

WIN-001 — What is the Windows PC for?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Daily driver — browsing, gaming, media clients. Not the homelab server. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-002 — PC IP address?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. 192.168.2.200 on home network. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-003 — NAS IP address?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. TrueNAS at 192.168.2.203 — where Docker apps run. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-004 — Where is Jellyfin server?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. On NAS — PC uses Jellyfin client pointing at stream.saxobroko.com. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-005 — What is A: drive?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Mapped network drive to TrueNAS media share — Windows shares. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-006 — PC won't boot?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. F12 at restart → Boot menu → pick boot drive — PC index. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-007 — Reseat SSD steps?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Open case, reseat NVMe — see boot troubleshooting in PC index. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-008 — Bitwarden on PC?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Desktop + browser extension, URL vault.saxobroko.com. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-009 — Desk YubiKey port?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. USB-C on PC — leave plugged for convenience. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-010 — Remote desktop to PC?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Not typical — physical access at Saxon's desk. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-011 — PC off — does docs still work?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Yes — docs on Cloudflare Pages. Vault/auth need NAS on. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-012 — PC off — does media work?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. If NAS on, stream.saxobroko.com still works from other devices. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-013 — Install new software?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Normal Windows — Ryan maintains if inheriting per will. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-014 — Windows update stuck?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Reboot once, retry updates — don't force during homelab emergency. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-015 — No internet on PC only?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Check cable/Wi‑Fi, compare to phone on same network. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-016 — Can't reach 192.168.2.203?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. NAS off or network issue — turn everything on. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-017 — Map A: drive missing?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Remap share — Windows shares. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-018 — qBittorrent on PC?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Web UI in browser — app runs on NAS, not PC. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-019 — Sonarr/Radarr on PC?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Browser to LAN/tunnel URLs — servers on NAS. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-020 — Gaming on this PC?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Yes — separate from server duties. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-021 — Specs location?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. PC specs — fill from System Information. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-022 — Storj on PC?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. See Storj if active. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-023 — Aither tracker in browser?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. PC browser only — automation on NAS. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-024 — Antivirus conflicts?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Rare — note exact error for Ryan. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-025 — PC fans loud?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Check Task Manager — may be normal under load. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-026 — Blue screen?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Note error code, reboot once — persistent BSOD → Ryan. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-027 — Forgot Windows password?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Microsoft account reset or Ryan with recovery media. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-028 — Sell the PC?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Will says Ryan gets tech — cannot sell — must learn/use per will. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-029 — Wipe PC after death?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. No day one — passwords and files may be needed. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-030 — Photos on PC vs NAS?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Canonical copy on NAS pool — PC may have caches only. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-031 — RDP to NAS?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. TrueNAS web UI in browser — not RDP. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-032 — NPM admin from PC?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Browser to NAS LAN port — NPM FAQs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-033 — Clone PC drive?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Ryan task for backup — not urgent for survivors. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-034 — Dual monitor issue?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Cable/driver — not homelab critical. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-035 — Printer on PC?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Local Windows printer setup — unrelated to NAS. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-036 — Time zone wrong?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Set to Australia/Melbourne — affects certs and logs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-037 — Hostname on network?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Check Settings → System → About — may be SAXON-PC or similar. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-038 — Wi‑Fi vs ethernet?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Either works on 192.168.2.x LAN. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-039 — PC guide for beginners?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Windows PC basics. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-040 — Who inherits PC?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Ryan — Who gets what. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-041 — Leave PC on?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Fine — low power idle; needed for desk YubiKey access. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics
WIN-042 — More PC help?

Stack context: Windows 11 @ 192.168.2.200 · A: share client Integrated runbooks: Service matrix · PC

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. PC folder, equipment map. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Windows PC basics