Startup Optimization
Task Manager is opened so you can review the Startup apps tab and disable unnecessary startup entries yourself. Maintenance asks whether any apps were disabled and records the result in the report.
Comprehensive Windows Utility
Maintenance
Maintenance is a comprehensive Windows PowerShell utility that combines interactive startup and driver-software checks with file-system repair scheduling, Windows image repair, BSOD crash-dump analysis, browser and temporary-file cleanup, Windows and application updates, drive optimization, restore-point handling, and a detailed HTML report.
Save your work before starting. The launcher requests administrator access, Maintenance closes open File Explorer windows and supported browsers during pre-flight, and Windows is automatically restarted when the maintenance run completes without a fatal error.
Workflow
What Maintenance runs
Maintenance performs a long sequence of repair, cleanup, update, reporting, and restart tasks. Some early steps are interactive so you can review startup apps and vendor driver software while you are still at the computer.
01Startup Optimization
02Intel / NVIDIA / AMD Software
03Schedule CHKDSK
04DISM & SFC
05Crash Dumps
06Browser Cleanup
07Temp Cleanup
08Windows Updates
09App Updates
10Drive Optimization
11Restore Point
12Report + Restart
Pre-flight
Keeping the computer awake during maintenance
The script records the currently active Windows power plan, creates or reuses a custom Always on power scheme, activates it, and sets monitor, disk, standby, and hibernate timeouts to zero for both AC and DC power. In the script's final cleanup block, it attempts to restore the power plan that was active before Maintenance started.
Interactive Checks
Startup apps and hardware-vendor software
Intel
If Intel hardware is detected, Maintenance checks for Intel Driver & Support Assistant. When missing, it can install the tool through WinGet after asking for permission.
NVIDIA
If NVIDIA hardware is detected, Maintenance checks for NVIDIA App. When missing, it can open NVIDIA's official App download page so you can download and install it manually.
AMD
If AMD hardware is detected, Maintenance checks for AMD Software / Adrenalin / Radeon Software. When missing, it can open AMD's official Drivers and Support page for manual installation.
Disk & Windows Repair
CHKDSK, DISM, and SFC
CHKDSK on next boot
Maintenance schedules CHKDSK /f /r on the Windows system drive for the next boot. If Riot Vanguard's tray process is detected, the script asks you to exit Vanguard before continuing.
DISM image servicing
The repair sequence runs DISM AnalyzeComponentStore, StartComponentCleanup, CheckHealth, ScanHealth, and RestoreHealth against the online Windows installation.
System File Checker
After DISM, Maintenance runs sfc /scannow to verify protected Windows system files and attempt repair when Windows reports corruption.
Post-restart CHKDSK report
A one-time RunOnce helper checks recent Windows CHKDSK/Wininit events and Bootex.log after reboot, inserts the result into the HTML report, then removes its RunOnce entry.
Crash Analysis
BSOD crash-dump inspection
Maintenance checks the standard Windows kernel crash-dump locations C:\Windows\MEMORY.DMP and C:\Windows\Minidump. When dumps are present, it attempts automated debugger analysis.
CDB debugger
The script looks for Microsoft's CDB debugger. If it is not available, Maintenance can install Microsoft WinDbg through WinGet so CDB is available for automated analysis.
Temporary debugger installation
When the script installed WinDbg only for this maintenance run, it attempts to remove that installation after dump analysis completes.
BugCheck interpretation
The report can include the dump type, BugCheck name/code, a plain-language description, likely module or driver information, and analysis guidance when CDB returns usable data.
Microsoft symbols
CDB is configured to use a local symbol cache backed by Microsoft's public symbol server while analyzing the dump files.
Cleanup
Browser and temporary-file cleanup
Supported browsers
Browser Cleanup handles detected Chrome, Edge, Brave, Opera, Opera GX, and Firefox profiles. Browser processes are stopped before the cleanup runs.
Browser data cleared
Depending on the browser, the script clears cache, code cache, GPU cache, and history/download-history database files. It measures estimated space before and after cleanup.
Windows temporary locations
Temp Cleanup covers selected Windows/user temp and cache locations including Windows Temp, SoftwareDistribution downloads, Recent items, INetCache, Office web cache, D3D cache, Windows Error Reporting, Delivery Optimization cache, Panther logs, CBS logs, the Recycle Bin, and Windows.old when present.
Before/after totals
The script measures the configured cleanup locations before and after removal and records estimated total space freed.
Browser Cleanup removes browser history/download-history databases for supported profiles. Temp Cleanup can also remove
Windows.old and Windows Update download-cache contents when those locations exist. Run Maintenance only when you are comfortable clearing this data.
Updates
Windows and application updates
Windows Update
Maintenance installs the NuGet provider and PSWindowsUpdate module as needed, then requests Windows/Microsoft updates with Install-WindowsUpdate. Feature-upgrade titles containing “Upgrade” are excluded and update-triggered reboot is suppressed until Maintenance performs its own final restart.
Application updates
WinGet is used to upgrade installed applications with hidden/non-interactive options, source/package agreement acceptance, and support for packages whose installed version is unknown.
Battle.net handling
When a Battle.net update is available, Maintenance searches for the existing Battle.net installation location and tries to update it in place. Battle.net is temporarily pinned while the general WinGet update pass runs so it is not processed a second time.
Failure reporting
Windows Update and App Update failures are captured for the final report rather than silently presenting the section as successful.
Optimization & Recovery
Drive optimization and restore point
Drive Optimization
Optimize-Volume is run for non-removable, non-optical volumes that have drive letters. Each drive receives its own success or error result in the report.
System Protection
Maintenance attempts to ensure System Protection is enabled on the system drive before creating a restore point.
Restore-point verification
The latest restore point is recorded before and after the attempt so the script can verify whether a new Maintenance restore point was actually created.
24-hour Windows limit
If Windows reports that a restore point already exists within 1440 minutes (24 hours), the report treats that as a completed result rather than a failure.
HTML Report
System information and maintenance results
Maintenance builds a local HTML report containing a system-information header and individual status sections for the work performed. The report is finalized on the Desktop after the reboot/CHKDSK handoff completes.
Computer
Operating System
Battery Health
Motherboard
CPU
GPU
RAM
Storage
Laptop battery health is calculated from design capacity and full-charge capacity when that information is available. The script may temporarily generate a Windows battery report to obtain those values and removes that temporary helper report afterward.
Restart & Finalization
What happens after Maintenance finishes
- The working HTML report is written under a hidden Maintenance Temp folder in LocalAppData.
- A one-time RunOnce entry is created for the current user.
- If the main run completed without a fatal error, Windows is restarted immediately.
- CHKDSK can run during boot if Windows determines the scheduled check is needed.
- At the next sign-in, the hidden helper retrieves the newest CHKDSK result or
Bootex.logresult and inserts the normalized result into the report. - The completed report is moved to the Desktop as Maintenance MM-DD-YY.html and opened automatically.
- The helper removes its RunOnce entry and cleans the temporary Maintenance working folder.
The post-restart helper can also remove a recent Maintenance.zip from Downloads and a recent extracted Maintenance folder when that extracted folder carries the marker created by the script.
Launcher
Administrator access and ExecutionPolicy
Run Me.bat launches a new elevated PowerShell process with UAC using -Verb RunAs and uses -ExecutionPolicy Bypass for the launched process. The PowerShell script itself also declares #requires -RunAsAdministrator.
Screenshot
Tool preview
FAQ
Frequently asked questions
Will Maintenance restart my computer?
Yes. When the main script finishes without a fatal error, it issues an immediate Windows restart. Save your work before starting.
Does Maintenance run CHKDSK immediately?
It schedules CHKDSK /f /r on the system drive for the next boot. The final HTML report is updated with the result after reboot and sign-in.
Does it analyze crash dumps?
Yes. It checks MEMORY.DMP and the Windows Minidump folder and can use Microsoft's CDB debugger for automated analysis.
Does it clear browser history?
Yes. The current Browser Cleanup removes history/download-history database files for supported browser profiles along with several cache types.
Does it update third-party apps?
Yes. The App Updates section uses WinGet for installed application upgrades and includes special handling for Battle.net.
Where is the final report saved?
After restart and the one-time CHKDSK result update, the completed HTML report is moved to the current user's Desktop.
Does it preserve my previous power plan?
The script records the active power-plan GUID before Maintenance begins and attempts to restore that plan in its final cleanup block.
Can I stop at interactive prompts?
The script's yes/no prompts accept qq as an exit command, allowing you to leave Maintenance during those interactive stages.