When using git in wsl, an error occurred, causing vscode to freeze. As a result, my local custom diebian was deleted, and there was no recycle bin for my system has been reset

[i88o]

Windows Version

10.0.19044.5371

WSL Version

2.7.0.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

No response

Distro Version

debian

Other Software

WSL 版本: 2.7.0.0
内核版本: 6.6.114.1-1
WSLg 版本: 1.0.71
MSRDC 版本: 1.2.6676
Direct3D 版本: 1.611.1-81528511
DXCore 版本: 10.0.26100.1-240331-1435.ge-release
Windows: 10.0.19044.5371

这个问题非常严重，我不明白，为什么我在 WSL 环境的 Git 提交卡住了，会让我的 WSL 系统被重置，而且我自定义路径导入的 WSL 系统文件夹下面的文件也被删除。我很清楚这不是我的操作，而且回收站没有文字证明了这一点。现在我自定义的 WSL 系统丢失，所有的文件包括系统都没有了。我希望官方可以解决这个问题，并帮我找回文件。

This issue is very serious, I don't understand why when my Git commit in the WSL environment got stuck, it caused my WSL system to be reset, and the files in the WSL system folder that I imported with a custom path were also deleted. I am sure this was not my action, and the Recycle Bin has no evidence to prove otherwise. Now my custom WSL system is lost, and all the files, including the system, are gone. I hope the official can solve this problem and help me recover the files.

Repro Steps

git got stuck when submitting files to kafka,zk and redis

Expected Behavior

git successfully submitted kafka,zk and redis files

Actual Behavior

My custom system was deleted and a new debian system was automatically reinstalled

Diagnostic Logs

[2026-01-04 08:33:02.640] Extension version: 0.104.3
[2026-01-04 08:33:02.640] L10N bundle: file:///c%3A/Users/text/.vscode/extensions/ms-vscode-remote.remote-wsl-0.104.3/l10n/bundle.l10n.zh-cn.json
[2026-01-04 08:33:02.656] authorityHierarchy: wsl+debiannew
[2026-01-04 08:33:02.656] WSL extension activating for a local WSL instance
[2026-01-04 08:33:02.713] Download in background is enabled
[2026-01-04 08:33:02.714] Resolving wsl+debiannew, resolveAttempt: 1
[2026-01-04 08:33:02.714] WSL feature installed: true (dll path)
[2026-01-04 08:33:02.715] NodeExecServer run: C:\Windows\System32\wsl.exe --list --verbose
[2026-01-04 08:33:02.777] 1 distros found
[2026-01-04 08:33:02.778] Starting VS Code Server inside WSL (wsl2)
[2026-01-04 08:33:02.778] Windows build: 19044. Multi distro support: available. WSL path support: enabled
[2026-01-04 08:33:02.778] Scriptless setup: false
[2026-01-04 08:33:02.778] No shell environment set or found for current distro.
[2026-01-04 08:33:02.888] WSL daemon log file:
[2026-01-04 08:33:02.890] Probing if server is already installed: if [ -d ~/.vscode-server/bin/618725e67565b290ba4da6fe2d29f8fa1d4e3622 ]; then printf 'install-found '; fi; if [ -f /etc/alpine-release ]; then printf 'alpine-'; fi; uname -m;
[2026-01-04 08:33:02.890] NodeExecServer run: C:\Windows\System32\wsl.exe -d DebianNew -e sh -c if [ -d ~/.vscode-server/bin/618725e67565b290ba4da6fe2d29f8fa1d4e3622 ]; then printf 'install-found '; fi; if [ -f /etc/alpine-release ]; then printf 'alpine-'; fi; uname -m;
[2026-01-04 08:33:02.958] Unable to detect if server is already installed: Error: Failed to probe if server is already installed: code: Failed to probe if server is already installed: code: 4294967295, , ~p��'Ee�� [2026-01-04 08:33:02.958] ���Nx: Wsl/Service/E_UNEXPECTED [2026-01-04 08:33:02.958] [2026-01-04 08:33:02.959] NodeExecServer run: C:\Windows\System32\wsl.exe -d DebianNew sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" 618725e67565b290ba4da6fe2d29f8fa1d4e3622 stable code-server .vscode-server --host=127.0.0.1 --port=0 --connection-token=3411232329-2683684040-3594644385-2539292149 --use-host-proxy --without-browser-env-var --disable-websocket-compression --accept-server-license-terms --telemetry-level=all' [2026-01-04 08:33:03.029] ~p��'Ee��
[2026-01-04 08:33:03.029] ���Nx: Wsl/Service/E_UNEXPECTED
[2026-01-04 08:33:03.029]
[2026-01-04 08:33:03.029] 有关启动问题的帮助，请转到 https://code.visualstudio.com/docs/remote/troubleshooting#_wsl-tips
[2026-01-04 08:33:32.730] New commit detected: 994fd12f8d3a5aa16f17d42c041e5809167e845a
[2026-01-04 08:33:32.730] Recently used WSL platforms: linux-x64
[2026-01-04 08:33:32.731] Found C:\Users\text\vscode-remote-wsl\stable\994fd12f8d3a5aa16f17d42c041e5809167e845a\vscode-server-stable-linux-x64.tar.gz. Skipping download.

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[i88o]

/question

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'

[i88o]

adding tag 'question'

[OneBlue]

/logs

[microsoft-github-policy-service]

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body.

Thank you!