{"version":"2.1.301","anchor":"windows-registry-settings-read-skipped-under-a-new-condition","canonical_anchor":"windows-registry-settings-read-skipped-under-a-new-condition","heading":"Windows per-user registry settings are now skipped in some cases","tier":"notice","area":"Managed Settings","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/windows-registry-settings-read-skipped-under-a-new-condition","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Windows per-user registry settings are now skipped in some cases\n\nOn Windows, Claude Code now reads settings from the per-user registry only when an extra condition also holds\n\n**Unclear.** It is not clear what the new condition checks, so it is not known when registry settings are now skipped.\n\n**What**\n\nOn Windows, organizations can deliver Claude Code settings through the registry, the Windows store of system and app settings. One part of it, HKCU, holds settings for the current user. Claude Code now reads settings from there only when a new extra condition holds. Before, it read them whenever they were present and the existing check passed.\n\nOn Linux, the step that reads the machine's ID from `\/sys\/hypervisor\/uuid` can also now stop early when a new check is true.\n\n**Why**\n\nThis can change when managed settings stored in the Windows registry take effect for you.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}