Error on starting WSL after importing from VHDX

[dfantonio]

Windows Version

Microsoft Windows [versão 10.0.26100.3476]

WSL Version

2.4.12.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-1

Distro Version

I'm not sure, but I believe it was Ubuntu 20 or 22

Other Software

wsl -v
Versão do WSL: 2.4.12.0
Versão do kernel: 5.15.167.4-1
Versão do WSLg: 1.0.65
Versão do MSRDC: 1.2.5716
Versão do Direct3D: 1.611.1-81528511
Versão do DXCore: 10.0.26100.1-240331-1435.ge-release
Versão do Windows: 10.0.26100.3476

Repro Steps

My pc started acting weirdly a few weeks ago, and yesterday it started BSOD in loop so I had to format. Before formatting I backed up my WSL 2 VHDX file to restore it.

I import the WSL succesfully with wsl --import-in-place but I can't start it because of the this error:

<3>WSL (12 - Relay) ERROR: CreateProcessParseCommon:863: Failed to translate C:\WINDOWS\system32
<3>WSL (12 - Relay) ERROR: CreateProcessParseCommon:909: getpwuid(0) failed 74
<3>WSL (12 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\WINDOWS\system32
<3>WSL (12 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\WINDOWS
<3>WSL (12 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\WINDOWS\System32\Wbem
<3>WSL (12 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\WINDOWS\System32\WindowsPowerShell\v1.0\
<3>WSL (12 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\WINDOWS\System32\OpenSSH\
<3>WSL (12 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\Program Files\NVIDIA Corporation\NVIDIA app\NvDLISR
<3>WSL (12 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\Program Files\Git\cmd
<3>WSL (12 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\Users\anton\AppData\Local\Microsoft\WindowsApps
<3>WSL (12 - Relay) ERROR: UtilTranslatePathList:2878: Failed to translate C:\Users\anton\AppData\Local\Programs\Microsoft VS Code\bin
Processing fstab with mount -a failed.
Failed to mount C:\, see dmesg for more details.
Failed to mount D:\, see dmesg for more details.
Failed to mount E:\, see dmesg for more details.
Failed to mount F:\, see dmesg for more details.

An error occurred mounting the distribution disk, it was mounted read-only as a fallback.
See recovery instructions on: https://aka.ms/wsldiskmountrecovery
<3>WSL (12 - Relay) ERROR: ConfigUpdateLanguage:3001: fopen(/etc/default/locale) failed 74
<3>WSL (12 - Relay) ERROR: operator():420: getpwuid(0) failed 74
<3>WSL (12) ERROR: Bad message @init.cpp:603 (CreateProcessCommon)
<3>WSL (12 - Relay) ERROR: CreateProcessCommon:647: Create process failed

I've tried this fix but it didn't work.

Is there a way to fix my WSL? Or at least access it's content so I can copy it over to a new VM

Expected Behavior

Should be able to start WSL normally.

Actual Behavior

I get the above error

Diagnostic Logs

No response

[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 here

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

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[dfantonio]

/question

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'