microsoft / microsoft/WSL

Corrupted disk/Data loss after --move to a VHDX drive

Open
#13,951 9 comments 0 reactions 0 assignees View on GitHub
file system
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.7462]

### WSL Version

2.6.1.0

### Are you using WSL 1 or WSL 2?

- [x] WSL 2
- [ ] WSL 1

### Kernel Version

6.6.87.2-1

### Distro Version

Ubuntu 22.04

### Other Software

_No response_

### Repro Steps

1. Move the disk to G: drive with `wsl --manage Ubuntu --move G:`
2. Re-move it to the intended drive `D:`
3. `Wsl/Service/CreateInstance/WSL_E_DISK_CORRUPTED`

### Expected Behavior

I can actually use WSL when I move it to a D: Drive.

### Actual Behavior

WSL corrupts my drive and most likely destroyed all of my work.

### Diagnostic Logs

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the two-step move from G: to D: with `wsl --manage Ubuntu --move`, then inspect the resulting `Wsl/Service/CreateInstance/WSL_E_DISK_CORRUPTED` failure. Compare the virtual disk and move behavior across both drives; done means WSL starts after the repeated move without corruption or data loss. Diagnostic logs are not provided, so collect them if reproduction succeeds.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.