infra-windows-servicinglisted

# Windows servicing and repair: the traps Repairing a Windows component store is not hard to execute - the commands are well known. It is hard because several distinct failures all surface as **"Access is denied"**, a **quiet log**, or a **clean health report**, so a competent operator confidently fixes the wrong thing. This skill is the set of those false signals, each with the measurement behind it. Assume you already know `DISM`, `takeown`, `icacls` and `setup.exe`. Read this for what they do not tell you. ## The false signals | Symptom | The obvious reading | What it usually is | |-------------------------------------------------|-----------------------------------|-------------------------------------------------------------------------------------------------------------| | Update fails, `ScanHealth` clean | not corruption, so look elsewhere | **disk headroom** - a cumulative update needs far more free space than its own size | | "Access is denied" on a delete | ACL or ownership | the **read-only attribute** - not a permission, so `takeown`/`icacls` cannot fix it | | Permission command says success, op still fails | need a bigger permission pass | the **diagnosis is wrong** - inspect the object