You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Bug FixesKind: in v2.1.282,
Bug FixesSection of the release
What
WSL (Windows Subsystem for Linux) lets you run Linux on a Windows machine. Managed settings are policy settings an organisation's administrator sets, which users cannot override. On WSL, Claude Code can take these from the Windows side as well as from the Linux file managed-settings.json.
Claude Code now tracks whether each policy source loaded, was absent, or failed to load.
With Windows policy inheritance on: a Windows-side policy source you cannot edit now takes charge if it holds policy or failed to load. Before, when it gave no usable settings, Claude Code quietly used the Linux managed-settings.json instead.
With inheritance off: when a higher-priority policy source is present, the Linux managed-settings.json is now treated as absent.
Why
Before, someone could escape an organisation's policy on WSL by breaking or blocking the Windows-side file. A policy that fails to load now stays in charge.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear exactly which policy source outranks the Linux file when inheritance is off.
Anthropic's release notes agreeChanged Windows/WSL managed settings so an admin policy that is present but invalid or unreadable (HKLM, managed-settings.json) keeps…
