For small-business IT and solo sysadmins
Windows Fix & Deploy Toolkit
The fixes you do every week, as safe PowerShell scripts and printable runbooks. Stop retyping the same commands from forum posts at 4:55 pm.
What's inside
- 9 PowerShell scripts with full comment-based help (
Get-Help -Full), logging, confirmation prompts and-WhatIfwhere they change anything. - 15-page runbook PDF: 11 step-by-step procedures, each step labeled safe / changes / careful, with Windows Update error-code and blue-screen stop-code tables and a quick-reference page.
- Editable checklists (Markdown): imaging and sysprep, new-PC setup and handover, user offboarding.
| Script | What it does | Safety |
|---|---|---|
Repair-DomainTrust.ps1 | Fixes “The trust relationship between this workstation and the primary domain failed” in place. Tests first; repairs only with -Repair. | Changes only with -Repair |
Get-BitLockerRecoveryInfo.ps1 | Local key IDs and status, AD lookup by the Key ID on the recovery screen, and backup to AD or Entra ID. Keys hidden unless -ShowKey. | Read-only except -Mode Backup |
Reset-WindowsUpdate.ps1 | Stops the update services, renames SoftwareDistribution and catroot2 (kept as .bak), restarts them. Optional DISM + SFC. | Confirms first, -WhatIf |
Reset-PrintSpooler.ps1 | Lists queues, then clears stuck jobs by moving them to a backup folder. Works on a remote print server. | Confirms first, -ListOnly |
Invoke-SystemRepair.ps1 | DISM /RestoreHealth then SFC in the right order, offline-media support, plain-English summary. | -ScanOnly is read-only |
Test-SysprepReadiness.ps1 | Pre-flight before sysprep /generalize: pending reboot, BitLocker, upgraded OS, per-user Store apps, domain join. | Read-only |
Test-NewPCBaseline.ps1 | New-PC handover check: activation, Secure Boot, TPM, BitLocker, Defender, firewall, updates, local admins. CSV + HTML report. | Read-only |
Start-UserOffboarding.ps1 | AD offboarding: disable, random password, ticket stamp, group removal, OU move. Saves a JSON record so it's reversible. | Preview unless -Apply |
Get-StaleADComputers.ps1 | Enabled computer accounts idle for N days, with CSV export, before an audit or cleanup. | Read-only |
Built to be safe on production PCs
- Read-only by default wherever possible; changes need an explicit switch and a confirmation.
- Nothing deleted: update caches and print jobs are renamed or moved to a backup; offboarding saves a JSON record so group removals can be undone.
- Secrets stay hidden: BitLocker recovery passwords print only with
-ShowKey; offboarding passwords are generated straight into a SecureString and never shown. - Transcripts saved to
%ProgramData%\PlainErrorToolkit\logs.
Sample: Reset-WindowsUpdate.ps1 (excerpt)
[CmdletBinding(SupportsShouldProcess = $true, ConfirmImpact = 'High')]
param([switch]$RunDism)
$services = 'wuauserv', 'cryptSvc', 'bits', 'msiserver'
$stamp = Get-Date -Format 'yyyyMMdd_HHmmss'
if (-not $PSCmdlet.ShouldProcess("$env:COMPUTERNAME Windows Update components",
'Stop update services and rename SoftwareDistribution and catroot2')) { return }
try {
foreach ($s in $services) { Stop-Service -Name $s -Force }
foreach ($f in "$env:SystemRoot\SoftwareDistribution", "$env:SystemRoot\System32\catroot2") {
# Renamed, never deleted: you can roll back by renaming it again.
if (Test-Path $f) { Rename-Item $f -NewName "$(Split-Path $f -Leaf).bak-$stamp" }
}
}
finally {
# Always bring the services back, even if a rename failed.
foreach ($s in $services) { Start-Service -Name $s -ErrorAction Continue }
}
Runbook topics
- Domain trust relationship failed
- BitLocker recovery screen (where the key is, and how to stop repeat prompts)
- Windows Update failures, with a 12-code table
- Print spooler: stuck jobs
- System file repair: DISM and SFC
- Blue screen triage, with a 13-code stop-code table
- Imaging and sysprep checklist
- New PC setup and handover checklist
- User offboarding checklist (AD, Microsoft 365, devices)
- Stale computer accounts
- Quick reference commands
Questions
- Who is this for?
- IT generalists at small businesses, solo sysadmins, MSP techs and help-desk staff who support Windows 10/11 PCs, usually in Active Directory or hybrid Entra ID.
- What do I need to run it?
- Windows 10/11 or Server 2016+, admin rights, and Windows PowerShell 5.1 (built in). The AD scripts need the free RSAT ActiveDirectory module.
- Is it safe to run?
- Every script is read-only by default or asks before changing anything, supports -WhatIf where it changes things, renames or moves files instead of deleting them, and logs what it did. Still, test on one machine first: you know your environment, we don't.
- How do I get it?
- Pay through Stripe and you go straight to a download page. Bookmark it: the same link gets every v1.x update.
- Refunds?
- 14 days, no questions asked. Email hello@plainerror.com with your receipt number.
- Can I use it for clients?
- Yes. One purchase covers one organization with unlimited technicians and devices; MSPs can use it for their own clients. Please don't resell or repost the files.
Get all 9 scripts, the runbook and the checklists.