microsoft / microsoft/WSL

recovering from Windows reinstall; howto

Open
#5,416 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
C++
Stars
33.7k
Forks
1.8k
Avg merge
3d 17h
Merged PRs (30d)
116

Description

Is your feature request related to a problem? Please describe.
This request is not related to a problem; per se.

Describe the solution you'd like
I recently had a fault in the underlying parts of windows, and needed to go through a recovery seqeunce. In that sequence, I chose "restore my data files". My data files - including all the directories in the windows file system which I use with WSL1 - are perfectly intact. I suspect that, somwhere in my machine, my WSL root points are

However, my WSL mappings are lost.

Could you please publish instructions for this exact case? How to find your WSL workspaces, where they tend to reside (appdata?) and how to map them into distributions again?

I did take a backup, and have a zip file that is 6 months old. Since I don't keep my data in WSL (thankfully I don't use WSL2), the older version is a good starting point, but it's especially frustrating as I know the entire up-to-date distribution is very likely somewhere on my drive, taking up space, and I am, at least theoretically, one choice command away from reviving.

Describe alternatives you've considered
I have searched the drive for file names and patterns. No dice.
I have considered scanning the source for the wsl command tools, which specifically included the --export command to see from what directories it pushes files.

Additional context
I do take backups --- of my host OS. I have most of my up-to-date data files. The issue is that any program that forces me to take extra "export" steps to separately backup, creates a fragility.

And, this is "just" a documentation task. I argue it's better than a wsl --scan to find old installations, and a wsl --revive to bring back an old one, although maybe that is needed. Some way to re-assert old "distributions" is the key requirement.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names the WSL command tools and the --export, --scan, and proposed --revive entry points, but no documentation file or test. Start by reviewing the existing WSL recovery and distribution-registration guidance. Done means documenting how to locate intact WSL1 data after a Windows reinstall and map or re-register it safely.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, operating-systems
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.