Skip to content

FRENCH_SpicyCheck v7.2 — First public release

Choose a tag to compare

View all tags
@NephVx2 NephVx2 released this 22 Aug 10:43
· 13 commits to main since this release
v7.2
c46dad1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

⚠️ 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.
Assets 3
Loading