← ClaudeAtlas

windows-troubleshootlisted

Diagnose and troubleshoot Windows 10/11 and Windows Server problems with Microsoft's TroubleShootingScript toolset (TSS) - map a symptom to the right TSS scenario and exact .\TSS.ps1 command, run a read-only health triage of the local machine (event logs, crashes, BSODs, disks, services, updates, network, domain), and analyze an already-collected TSS / MS_DATA zip into plain-English findings. Use this whenever the user describes a Windows problem (slow PC, crashes, blue screen, account lockouts, logon or GPO problems, DNS/Wi-Fi/VPN/SMB/proxy connectivity, printing, RDP/AVD/Windows 365, Windows Update or activation failures, Start menu/Store/app issues, WMI/WinRM, Hyper-V, clustering), asks "which TSS scenario", "what does TSS collect", "how do I trace X", mentions TSS, MS_DATA, xray or SDP, asks whether TSS is expired or wants it updated, or hands over a support-data zip or .evtx files to read - even if they don't name TSS.
SharkByte561/windows-troubleshoot · ★ 0 · Data & Documents · score 72
Install: claude install-skill SharkByte561/windows-troubleshoot
# Windows troubleshooting with TSS TSS is Microsoft Support's own signed PowerShell toolkit. It has 157 scenarios, about 400 trace components, 215 CollectLog sets, 9 SDP reports, 24 auto-stop triggers and 34 xray known-issue checks. It **collects** data very well but explains almost none of it. This skill supplies the missing parts: - **choosing** what to collect; - **checking cheaply** before collecting anything; - **reading** what came back. The skill folder holds a pre-built catalog of TSS (`references/tss-index.json`), so lookups work even on machines without TSS. **Running the scripts:** paths are relative to this skill's folder. Use the built-in Windows PowerShell 5.1, which every Windows machine has: `powershell -NoProfile -ExecutionPolicy RemoteSigned -File <script>`. `pwsh` 7 works the same way if it is installed. - `-ExecutionPolicy RemoteSigned` applies to that one process only. It is needed because Windows clients default to `Restricted`, which blocks every `.ps1` file. Never use `Bypass` (see `references/safety.md`). - If a script is still blocked because the skill was downloaded as a zip ("not digitally signed"), run `Unblock-File` on this skill's own `scripts\*.ps1`, never on TSS. - If Group Policy sets the execution policy, the switch has no effect. That is the admins' decision, so tell the user. **Where TSS lives:** the scripts find a local TSS copy with `scripts/Resolve-TssRoot.ps1`. It checks `$env:TSS_ROOT` first, then the folder saved by `Update-Tss.p