Context
Seven modules ship today. Collecting further candidates here rather than opening an issue per idea; split them out when one is actually picked up.
The DiagnosticModule trait plus CommandRunner/MockCommandRunner make adding a module a well-trodden path, so the cost is mostly in getting the detection heuristics right.
Candidates
Driver health — devices reporting a problem code via Get-PnpDevice, unsigned drivers, drivers far behind the vendor version. Detection is easy; fixing is risky and should probably stay advisory.
Boot time / startup impact — measure per-entry startup cost and rank autostart entries by it. Complements the existing Registry & Autostart module, which finds broken entries but says nothing about slow ones. Data is available from the Diagnostics-Performance event log channel.
Scheduled tasks — orphaned tasks pointing at deleted binaries, tasks failing repeatedly, tasks added by uninstalled software. Structurally very close to the existing autostart checks.
Firewall — profiles disabled, overly broad inbound allow rules, rules referencing binaries that no longer exist.
Page file / memory — page file disabled on a machine with little RAM, page file on a nearly full drive, misconfigured fixed sizes.
Windows Search index — a corrupt index is a common and very visible performance complaint with a well-defined rebuild path.
Note
Each new module should follow the existing conventions: RiskScore::High for anything destructive, deselected by default, and a dry-run description that lists the exact commands.
Context
Seven modules ship today. Collecting further candidates here rather than opening an issue per idea; split them out when one is actually picked up.
The
DiagnosticModuletrait plusCommandRunner/MockCommandRunnermake adding a module a well-trodden path, so the cost is mostly in getting the detection heuristics right.Candidates
Driver health — devices reporting a problem code via
Get-PnpDevice, unsigned drivers, drivers far behind the vendor version. Detection is easy; fixing is risky and should probably stay advisory.Boot time / startup impact — measure per-entry startup cost and rank autostart entries by it. Complements the existing Registry & Autostart module, which finds broken entries but says nothing about slow ones. Data is available from the Diagnostics-Performance event log channel.
Scheduled tasks — orphaned tasks pointing at deleted binaries, tasks failing repeatedly, tasks added by uninstalled software. Structurally very close to the existing autostart checks.
Firewall — profiles disabled, overly broad inbound allow rules, rules referencing binaries that no longer exist.
Page file / memory — page file disabled on a machine with little RAM, page file on a nearly full drive, misconfigured fixed sizes.
Windows Search index — a corrupt index is a common and very visible performance complaint with a well-defined rebuild path.
Note
Each new module should follow the existing conventions:
RiskScore::Highfor anything destructive, deselected by default, and a dry-run description that lists the exact commands.