onedrive-exorcismlisted
Install: claude install-skill scottconverse/onedrive-exorcism
# OneDrive exorcism (and the two traps that make it look already-fixed)
Removing the OneDrive *app* does not un-redirect the folders, and when an agent runs inside
a packaged desktop app, the fix can silently land in a private
virtual registry so it verifies perfectly and changes nothing. Both traps have cost
multi-day debugging sessions. Work through this in order.
## Trap 1: the container lies (check this FIRST)
If the agent is hosted inside a packaged desktop app (confirmed with the **Claude desktop
app**, MSIX package e.g.
`Claude_pzs8sxrjxfjjc`), the session sees a **copy-on-write overlay** of the registry
and other machine state. Writes go to the package's private hive; later reads return
the overlay copy. The fix looks applied, verifies clean, survives reboots, and the
machine is untouched. Confirmed to affect at minimum:
- `HKCU` and `HKLM\Software` registry values
- `Get-ScheduledTask` enumeration (reported zero OneDrive tasks while three were live)
- per-user config keys (`reg query` said "key absent" for a key that existed)
**Rule: never trust an in-session "clean"/"not found" result about machine state, and
never apply a registry fix in-session. Apply AND verify through an out-of-container
channel.** See `references/detect-container.md` for the detection one-liner and
`references/elevated-helper.md` for the runner pattern.
Symptom fingerprint that should make you suspect this immediately:
*"the fix succeeded, verification passed, and nothing changed."*
## T