WSL2 virtual disk recovery

A WSL2 distribution can become inaccessible or read-only when its ext4.vhdx or underlying Windows storage is damaged.

WSL2 stores a Linux distribution inside an ext4-formatted virtual hard disk. Sudden shutdown, a full host disk, VHDX damage, or ext4 metadata errors can prevent the distribution from mounting even when much of the Linux file system remains readable.

Understand the symptom

The VHDX container and the ext4 file system are separate recovery layers.

WHY

What is happening

A valid VHDX must first expose its virtual blocks before ext4 superblocks, journals, inodes, directories, and file extents can be evaluated. Microsoft documents mounting the VHD bare and using e2fsck for ordinary mount errors, but repair writes should not begin on the sole copy.

What you may see

Symptoms that change the recovery path.

01

Distribution disk mount error

WSL cannot attach or mount the VHDX during startup.

02

Mounted read-only as fallback

File-system errors may have triggered protective read-only behavior.

03

Unexpected end or VHD error

The container may be truncated, sparse blocks unavailable, or host storage unstable.

04

Projects or home folders missing

The distribution may be mounting a different disk or damaged directory metadata.

Protect the source

Actions that can make the situation worse.

01

Running repair changes metadata

e2fsck and VHD repair can alter the only recoverable state.

02

Starting Docker can lock the disk

Docker Desktop may use WSL storage and cause sharing or write conflicts.

03

Resetting the distro can delete evidence

Unregistering or reinstalling may remove the original virtual disk.

Do this now

Safe steps before evaluation.

01

Run wsl --shutdown

Stop every distribution and related container workload before acquisition.

02

Copy the whole package

Keep ext4.vhdx, distro configuration, logs, file sizes, timestamps, and original paths.

03

Check host storage health

A VHDX problem may originate from NTFS, SSD, power, or free-space failure.

04

List priority Linux data

Identify home directories, repositories, databases, SSH keys, and container bind data needed first.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Container assessment

NEPFOSYS maps VHDX headers, regions, block allocation, file size, and readable ranges.

02

File-system extraction

The ext4 layer is examined from a protected copy or image without registering the original distro.

03

Workload validation

Priority paths, repositories, databases, permissions, timestamps, and file hashes are checked.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Should I run e2fsck immediately?

Only after preserving the original VHDX. Repair can help ordinary errors but it also writes metadata.

Can ext4.vhdx be opened outside WSL?

It can be attached through supported VHD workflows, but the VHDX must be offline and the ext4 layer handled correctly.

Will reinstalling WSL recover the old distro?

No. Reinstallation can create a new environment and may make the original state harder to locate or preserve.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case