Setup Prod Offscrub May 2026

| Service Name | Required? | OffScrub Action | |--------------|-----------|------------------| | Spooler | Yes (printing) | Keep | | WSearch | No (search indexing) | Disable | | SysMain | No (Superfetch) | Disable | | Themes | Yes (UI stability) | Keep | The most common production-ready implementation is a PowerShell script that wraps Set-Service , Stop-Process , and Disable-ScheduledTask .

foreach ($taskPath in $tasksToDisable) Disable-ScheduledTask -Verbose setup prod offscrub

Why would you do this in production? To , improve session density, or eliminate application conflicts on shared servers. However, running OffScrub incorrectly in production can break critical services, crash applications, or orphan user sessions. | Service Name | Required

$tasksToDisable = @( "Microsoft\Windows\DiskDiagnostic*", "Microsoft\Windows\Power Efficiency Diagnostics*" ) To , improve session density, or eliminate application

Use Infrastructure as Code (Terraform + Ansible) to version-control your OffScrub configuration. Treat your optimizations like application code—with tests and rollbacks. Have you deployed OffScrub in production? Share your exclusion list or horror story in the comments below.