{"version":"2.1.233","anchor":"windows-nt-object-manager-paths-now-require-manual-approval","canonical_anchor":"windows-nt-object-manager-paths-now-require-manual-approval","heading":"Windows NT object-manager paths now require manual approval","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/windows-nt-object-manager-paths-now-require-manual-approval","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Windows NT object-manager paths now require manual approval\n\nWindows NT object-manager paths now require your manual approval like other suspicious path forms.\n\n**What**\n\nPaths beginning `\\??\\` (the NT object manager namespace, and spellings that normalise to it) are now treated as suspicious. They trigger the same manual-approval ask as other odd Windows path forms, are rejected by the network-path check, and are caught during general path normalization, which previously only recognised the `\\\\?\\` device form.\n\n**Details**\n\n- The ask text is unchanged: \"which contains a suspicious Windows path pattern that requires manual approval\", recorded under the circuit breaker name \"suspiciousWindowsPath\".\n- The file-upload guard used by Claude in Chrome inherits the new check and throws on a \"suspicious path spelling\".\n\n**Evidence**\n\n`\/^[\\\\\/]\\?\\?[\\\\\/]\/`\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}