Usage and automation

Daily use

Run one module from the menu or press [A] for all enabled automatic modules. The modules included in automatic execution are defined in config\MaintenanceToolkit.ini.

When the session finishes, start with logs\COMPUTER-NAME\<session>\riepilogo.txt: it is the quickest way to distinguish normal results, warnings, skipped operations and errors. Detailed logs remain in the same session directory; Network Diagnostics reports are stored separately under reports\.

• OK: completed.
• WARN: completed with a condition to review.
• SKIP: module not applicable or not executable under the current conditions.
• ERROR: did not complete correctly.

Command line

Runs all enabled automatic modules without interaction. Other switches are documented in the repository.

Automation with Task Scheduler

Validated on 29 August 2026. Create a full Task:

1. Name: Maintenance Toolkit - System update.
2. Select Run whether user is logged on or not and Run with highest privileges for background execution without a console.
3. Use a daily trigger in a low-impact window.
4. Action: MaintenanceToolkit.exe; arguments -RunAll; Start in = MT root directory.
5. Set power/network conditions, recover missed runs and prevent overlapping instances.
6. Save (Windows may request the password) and test by allowing the real trigger to start.

0x14 is decimal 20: MT completed with warnings, not a scheduler failure.

Winget verification limits

MT reports what Winget returns, but does not certify every application at binary level. If an application remains open or still shows an unexpected version after an update, inspect the Winget log and the version actually installed.

Administrators and enterprise

Across many endpoints, add random trigger delay to avoid simultaneous downloads. GPO distribution is possible but must be validated.

The roadmap includes future centralized logs/reports and an endpoint dashboard, with no promised date.