[DOCS] Inconsistent Windows Managed Settings path (Deprecated `C:\ProgramData` vs `C:\Program Files`)

Resolved 💬 2 comments Opened Jan 17, 2026 by coygeek Closed Jan 21, 2026

Documentation Type

Unclear/confusing documentation

Documentation Location

Section/Topic

  • "Settings files" section in Settings - "Configuration file locations" table in Troubleshooting

Current Documentation

In Settings:

"Windows: C:\Program Files\ClaudeCode\"

In Troubleshooting (Configuration file locations table):

"Windows: C:\ProgramData\ClaudeCode\"

In Changelog (v2.1.2):

"Deprecated Windows managed settings path C:\ProgramData\ClaudeCode - administrators should migrate to C:\Program Files\ClaudeCode"

What's Wrong or Missing?

There is version drift between different sections of the documentation. While the "Settings" page was partially updated to reflect the change made in v2.1.2, the "Troubleshooting" section still provides the deprecated C:\ProgramData path as a reference. This inconsistency could lead system administrators to deploy organization-wide policies to the incorrect directory.

Suggested Improvement

Update the "Configuration file locations" table in docs/en/troubleshooting.md to match the current standard.

Suggested Text for the table in Troubleshooting:
| File | Purpose |
| :--- | :--- |
| managed-settings.json | [Managed settings](/en/settings#settings-files) |
| managed-mcp.json | [Managed MCP servers](/en/mcp#managed-mcp-configuration) |

Managed file locations:

  • macOS: /Library/Application Support/ClaudeCode/
  • Linux/WSL: /etc/claude-code/
  • Windows: C:\Program Files\ClaudeCode\

Impact

High - Prevents users from using a feature

Additional Context

  • Related Documentation: Changelog v2.1.2 explicitly states: "Deprecated Windows managed settings path C:\ProgramData\ClaudeCode - administrators should migrate to C:\Program Files\ClaudeCode"
  • Impact: Administrators following the Troubleshooting guide for file locations will be misinformed.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗