Copying symlink from File Explorer causes infinite copy loop
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
Windows Version
Microsoft Windows [Version 10.0.26200.8457]
WSL Version
2.7.3.0
Are you using WSL 1 or WSL 2?
- WSL 2
- WSL 1
Kernel Version
6.6.114.1-microsoft-standard-WSL2
Distro Version
Fedora 44
Other Software
Windows File Explorer
Repro Steps
This report is to reopen #9031 which is still an active bug - confirmed today, 8 June 2026. I encountered this bug while copying a folder with a Python venv inside it.
- Open a WSL terminal.
- Enter these commands:
mkdir ~/test # Create test folder
cd ~/test # Open test folder
echo "abcd" > test.txt # Create dummy test file
ln -sf test.txt test-symlink.txt # Create symbolic link
- Open File Explorer on the host Windows system.
- Navigate to
\\wsl$\[machine name]\home\[user]\test - Copy the test-symlink.txt file.
- Paste the test-symlink.txt file.
- Refresh File Explorer and observe the file being copied repeatedly in an infinite loop.
Expected Behavior
The symlink copied a single time, as with other types of files or folders.
Actual Behavior
The symlink copied infinitely, with the folder filling up with numbered copies of the symlink. The copy action cannot be stopped via the copy progress dialogue, and the only way to stop the infinite loop is to restart explorer.exe from the Windows Task Manger or log off/restart the machine.
Diagnostic Logs
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the linked WSL issue using the shell commands and Windows File Explorer steps, then read issue #9031 for prior investigation and context. Done means copying the symlink through \wsl$ completes once, without numbered duplicates or an unresponsive copy operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100