{"version":"2.1.282","anchor":"windows-legacy-folder-aliases-are-recognized-in-path-matchin","canonical_anchor":"windows-legacy-folder-aliases-are-recognized-in-path-matchin","heading":"Old Windows folder names now match their modern equivalents in path checks","tier":"notice","area":"Windows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/windows-legacy-folder-aliases-are-recognized-in-path-matchin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Old Windows folder names now match their modern equivalents in path checks\n\nPath checks now treat \"My Documents\", \"Application Data\" and \"Local Settings\" as the same as Documents, AppData\\Roaming and AppData\\Local\n\n**Unclear.** Which checks, such as permission or deny rules, use this matching is not known.\n\n**What**\n\nWindows still accepts some old folder names that point to modern ones. When comparing the start of file paths, Claude Code now treats these as the same:\n\n- \"My Documents\" and Documents\n\n- \"Application Data\" and AppData\\Roaming\n\n- \"Local Settings\" and AppData\\Local\n\nShort forms of these names, such as MYDOCU~1, are recognised too.\n\n**Why**\n\nA rule written for one form of a folder name can now also apply when a path uses the other form, rather than being sidestepped by the old name.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}