{"version":"2.1.281","anchor":"windows-credential-stores-added-to-the-protected-path-read-d","canonical_anchor":"windows-credential-stores-added-to-the-protected-path-read-d","heading":"Windows credential stores added to the protected-path read-deny list","tier":"notice","area":"Windows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/windows-credential-stores-added-to-the-protected-path-read-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Windows credential stores added to the protected-path read-deny list\n\nOn Windows, the Credentials, Vault and Protect folders are now protected paths that cannot be read\n\n**What**\n\nClaude Code keeps a list of protected paths that commands are not allowed to read. On Windows it now includes:\n\n- `Microsoft\\Credentials` under both `LOCALAPPDATA` and `APPDATA`\n\n- `Microsoft\\Vault` under both `LOCALAPPDATA` and `APPDATA`\n\n- `Microsoft\\Protect` under `APPDATA`\n\nThis matches the existing macOS entry for `Library\/Keychains`. Entries in the list also gain a place flag.\n\n**Why**\n\nWindows credential stores now get the same read protection the macOS keychain folder already had.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}