Cyber Risks · Trail of Bits Blog

Why Windows can’t follow WSL symlinks

Summary: Symlinks created inside Windows Subsystem for Linux cannot be followed by Windows, which opens them as 0 KB files and fails with an STATUS_IO_REPARSE_TAG_NOT_HANDLED error because it does not recognize the "LX symlink" tag. Windows symlinks and junctions work normally when accessed from WSL, and WSL-created hard links work on Windows, so the failure is limited to WSL-created symlinks.

Key Takeaway: Anyone using Windows and WSL against the same files can hit a link that resolves inside WSL and fails on the Windows side, and the author notes one tester saw relative-path links work while absolute-path links did not, leaving the exact conditions unresolved.

Read the original at Trail of Bits Blog ↗