{"version":"2.1.307","anchor":"windows-sandbox-deny-read-paths-and-credential-files-get-a","canonical_anchor":"windows-sandbox-deny-read-paths-and-credential-files-get-a","heading":"Windows sandbox blocks a second path form for each blocked file","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/windows-sandbox-deny-read-paths-and-credential-files-get-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Windows sandbox blocks a second path form for each blocked file\n\nOn Windows, each `denyRead` path and each credentials file path in sandbox settings is now also blocked under a second, alternate path form\n\n**What**\n\nThe sandbox is the restricted space Claude Code runs commands in. Its settings list paths that commands may not read. On Windows only, Claude Code now rewrites those settings so that every `denyRead` entry and every credentials file entry also gets a second, alternate form of the same path. Both forms are blocked.\n\n**Why**\n\nA file on Windows can often be reached by more than one path. Blocking both forms stops a command from getting around a block rule by using a different spelling of a protected path.\n\n- Area: Sandbox\n- Names: `denyRead`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}