Windows installation error

[aecesr]

Version

codebase-memory-mcp 0.10.4

Platform

Windows (x64)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

standard

What happened, and what did you expect?

error: failed to stage install candidate: activation transaction I/O failed: acl-grants-cross-account-mutation to S-1-5-21-4126844746-1954767206-1186927477-1003

Reproduction

error: failed to stage install candidate: activation transaction I/O failed: acl-grants-cross-account-mutation to S-1-5-21-4126844746-1954767206-1186927477-1003

Logs

Diagnostics trajectory (memory / performance / leak issues)

Project scale (if relevant)

No response

Confirmations

• I searched existing issues and this is not a duplicate.
• My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.

[DeusData]

Fixed on main by 47d2b533 (PR #1625), merged as a036a310. It will ship in v0.10.5.

The cause was ours, and it was the installer rather than the permission check. install.ps1 created its staging directory with New-Item, which inherits whatever %TEMP% carries — and then ran the downloaded binary from that directory, where the binary validates its own directory and refuses inherited cross-account mutation grants. So we handed our own validator a directory we had just made wrong. The S-1-5-21-…-1003 in your error is an ACE the installer inherited, not anything cbm wrote.

Measured on a Windows VM before writing the fix: a fresh New-Item staging directory comes up unprotected with 5 inherited ACEs. After the fix it is protected with a single owner ACE.

Sorry it took a v0.10.4 report to catch this — you filed against the release we had just shipped, and that is exactly the signal that made it obvious the staging half was still broken after the ownership half was fixed.