What it is
A small toolkit of PowerShell scripts and checklists for checking the health of Windows office computers — and deciding what to do about a slow machine using facts rather than guesswork.
Why I built it
“Can you look at this computer? It has become very slow.” That request arrives in almost every office, and the usual answer is a mix of habits: clear the temp files, disable something in startup, or replace the machine. Without a report, none of those decisions can be justified, and the same machine is back in a month.
The toolkit produces the report first and changes nothing.
Who it is for
- Office administrators looking after a handful of Windows computers.
- IT support staff who want a repeatable first-line check.
- Small businesses deciding between an upgrade and a replacement.
How it works
- Download and extract the ZIP.
- Read the README, then run the health report.
- Review the output: disk space, memory, Windows version, uptime, heaviest processes.
- Work through the checklist for the problem you actually have.
- Keep the report with your maintenance notes so the next check has a baseline.
A separate one-click runner groups the checks into a menu, and the packaged checklists cover monthly PC care, new-PC setup, and daily or weekly quick checks.
What problem it solves
It replaces opinion with evidence. It also prevents two expensive mistakes: reinstalling Windows to fix a full disk, and buying a new computer when the existing one only needed a damaged startup item removed or more memory.
The scripts give an office administrator a clear, printable answer to the question “what is happening on this machine?”
Technology used
- PowerShell scripts (report-only behaviour, no registry or file deletion)
- PDF and Markdown checklists generated from the same source
- ZIP packaging for distribution
- Distributed as static files through this site
Safety design
- Report first, act later. Nothing is changed until a person reviews the output.
- Runs as a normal user, requesting elevation only where Windows requires it.
- No internet connections, no telemetry, and no data collection — every script can be read in a text editor before running.
- Read the Terms of use before using the toolkit on a work computer, and test on one machine first.
Current status and next steps
Version 1.0 is published. Planned additions include a printer and network diagnostics walkthrough, an asset-register template for office machines, and a documented Windows reinstall checklist.
Community discussion
Comments 0
Comments are reviewed before they appear publicly. Be respectful and avoid sharing private information.
No approved comments yet. You can be the first to share a useful thought.
Add a comment
No account or login is needed. Your comment is emailed for moderation and is published only after approval in the CMS.