SpicyCheck v7.3 — English translation, bilingual detection fixes

Full Changelog: v7.2...v7.3

SpicyCheck v7.3 — English translation, bilingual detection fixes

One-command Windows 11 maintenance: system info, health diagnostic, cleanup, DISM/SFC/BCD repair, disk optimization, HTML report. This release translates the script's code and output to English and bundles several real-world bug fixes found while testing the repair pipeline across multiple runs.

🐛 Critical fixes

• DISM corruption detection is now bilingual (FR/EN). The previous check only matched the English word "repairable" — on a French-language Windows install, DISM could detect corruption without RestoreHealth ever triggering. Now matches repairable|réparable.
• SFC output could be silently corrupted before reaching the detection logic. On some console configurations, sfc.exe's output was captured with a null byte between every character and mis-decoded accented letters (a UTF-16LE-read-as-CP437 artifact). This could make a genuine "corrupted files, unable to repair" result fall through to a generic OK status. Output is now cleaned (ConvertTo-CleanOutput) before any pattern matching.
• SFC now distinguishes 4 real outcomes instead of one generic fallback: no integrity violations / files repaired / files found but not repairable / SFC operation itself failed. The "not repairable" case now correctly surfaces as ERROR instead of being indistinguishable from a clean scan.
• 16 comparison operators were missing whitespace (e.g. $load-gt90 instead of $load -gt 90), a PowerShell syntax pitfall that caused outright parse errors — the script could fail to run at all depending on which code path was hit.
• DISM RestoreHealth failures (missing source files, 0x8... error codes) are now detected and reported as ERROR instead of always showing "Repair completed."

✨ Improvements

• DISM ScanHealth/CheckHealth now show WARN (not OK) when corruption is detected — the status finally reflects what was actually found, not just "the command ran without throwing."
• Unified health scoring. The live console health diagnostic and the final HTML report / end-of-run summary previously drew from two different, partially overlapping data sources — SMART health, battery, network ping, event log, uptime, and pagefile were checked live but never made it into the report. Both views now share a single source of truth.

🌐 Code and console output now in English

The script's code, parameters, console output, HTML report, and log file are now entirely in English (they were French through earlier internal revisions). This is a UI/code-language change only — DISM/SFC corruption detection remains bilingual (French/English), since those tools reply in whichever language the host OS uses, so the script still works identically on English- and French-language Windows machines. Date/time display in the HTML report follows the OS locale, not the script's language.

⚠️ Breaking changes if you're upgrading from an earlier (French) build

• Parameters renamed: -SauterNettoyage → -SkipCleanup, -SauterReparation → -SkipRepair, -SauterOptimisation → -SkipOptimization. Update any scripts or scheduled tasks that pass the old names.
• Report folder renamed: Desktop\Rapports_Maintenance → Desktop\Maintenance_Reports. Existing reports stay in the old folder; only new runs use the new one.
• Report/error file names updated: rapport_<timestamp>.* → report_<timestamp>.*, MAINTENANCE_ERREUR.txt → MAINTENANCE_ERROR.txt.
• Status labels changed: BON/MOYEN/CRITIQUE → GOOD/MEDIUM/CRITICAL (console, HTML report, and JSON export).

📋 Notes

• Run .\SpicyCheck-v7_3.ps1 -SelfTest before your first real run (36 internal assertions, no system changes).
• This script is signed with a personal, self-signed certificate — see the README's "Running a downloaded script" section if Windows blocks execution after download.

FRENCH_SpicyCheck v7.2 — First public release

⚠️ Legacy French-language build. This release's code, parameters, and console output are in French. As of the next release, SpicyCheck's code and output are in English (the script itself works identically on French and English Windows either way — see the current release for details). Kept here for anyone specifically relying on the French parameter names (-SauterNettoyage, etc.) or output paths.

SpicyCheck v7.2 — First public release

One-command Windows 11 maintenance: system info, health diagnostic, cleanup, DISM/SFC/BCD repair, disk optimization, HTML report. This first public release bundles several real-world bug fixes found while testing the repair pipeline across multiple runs.

🐛 Critical fixes

• DISM corruption detection is now bilingual (FR/EN). The previous check only matched the English word "repairable" — on a French-language Windows install, DISM could detect corruption without RestoreHealth ever triggering. Now matches repairable|réparable.
• SFC output could be silently corrupted before reaching the detection logic. On some console configurations, sfc.exe's output was captured with a null byte between every character and mis-decoded accented letters (a UTF-16LE-read-as-CP437 artifact). This could make a genuine "corrupted files, unable to repair" result fall through to a generic OK status. Output is now cleaned (ConvertTo-SortieProprete) before any pattern matching.
• SFC now distinguishes 4 real outcomes instead of one generic fallback: no integrity violations / files repaired / files found but not repairable / SFC operation itself failed. The "not repairable" case now correctly surfaces as ERROR instead of being indistinguishable from a clean scan.
• 16 comparison operators were missing whitespace (e.g. $load-gt90 instead of $load -gt 90), a PowerShell syntax pitfall that caused outright parse errors — the script could fail to run at all depending on which code path was hit.
• DISM RestoreHealth failures (missing source files, 0x8... error codes) are now detected and reported as ERROR instead of always showing "Repair completed."

✨ Improvements

• DISM ScanHealth/CheckHealth now show WARN (not OK) when corruption is detected — the status finally reflects what was actually found, not just "the command ran without throwing."
• Unified health scoring. The live console health diagnostic and the final HTML report / end-of-run summary previously drew from two different, partially overlapping data sources — SMART health, battery, network ping, event log, uptime, and pagefile were checked live but never made it into the report. Both views now share a single source of truth.

📋 Notes

• Run .\SpicyCheck-v7_2.ps1 -SelfTest before your first real run (36 internal assertions, no system changes).
• This script is signed with a personal, self-signed certificate — see the README's "Running a downloaded script" section if Windows blocks execution after download.