{"version":"2.1.323","anchor":"remote-browse-refuses-folders-until-the-windows-registry-pol","canonical_anchor":"remote-browse-refuses-folders-until-the-windows-registry-pol","heading":"Remote folder browsing on Windows waits for registry policy","tier":"notice","area":"Windows","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/remote-browse-refuses-folders-until-the-windows-registry-pol","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Remote folder browsing on Windows waits for registry policy\n\nOn Windows and WSL, remote folder browsing and folder picks are refused until Claude Code has read the machine's registry policy\n\n**What**\n\nOn Windows and WSL (Windows Subsystem for Linux), browsing and picking folders remotely now waits until Claude Code has read the machine-wide Windows registry policy (under HKLM). Until that reading finishes, folder browsing and picks are refused, because the policy's Read rules are not yet known. If the reading has not finished, Claude Code tries again at most once a minute.\n\n**Why**\n\nOn managed Windows machines, the Read rules set by an administrator in the registry are now respected in remote folder pickers. A refusal right after startup may only mean the policy has not been read yet.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}