{"version":"2.1.227","anchor":"files-with-windows-and-wsl-hostile-names-are-skipped-during-","canonical_anchor":"files-with-windows-and-wsl-hostile-names-are-skipped-during-","heading":"Files with Windows- and WSL-hostile names are skipped during sync","tier":"notice","area":"Remote Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/files-with-windows-and-wsl-hostile-names-are-skipped-during-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Files with Windows- and WSL-hostile names are skipped during sync\n\nIncoming files with names Windows or WSL cannot handle are skipped instead of breaking the sync.\n\n**What**\n\nIncoming file lists are now validated and filtered before anything is written, so names that cannot exist safely on Windows or WSL are dropped rather than causing failures mid-apply.\n\n**Details**\n\n- A malformed, oversized, wrong-side or wrong-version list is rejected outright (`oversize`, `unsupported_version`, `malformed`, `wrong_side`).\n- Paths that look like internal sync paths are dropped.\n- On Windows and WSL each path segment is cut at the first colon and stripped of trailing dots and spaces, then rejected if it matches an old-style 8.3 short name pattern.\n- Dropped paths are counted separately and reported as filtered files in the sync telemetry.\n- Conflicted-copy naming separately rejects reserved Windows device names (con, prn, aux, nul, com, lpt).\n\n**Evidence**\n\n`unsupported_version`\n\n- Area: Remote Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}