Failed to attach disk 'LocalState\ext4.vhdx' to WSL2: The system cannot find the file specified. #10032

liudonghua123 · 2023-04-27T03:13:54Z

Windows Version

Microsoft Windows [Version 10.0.22621.1555]

WSL Version

1.2.5.0

Are you using WSL 1 or WSL 2?

WSL 2
WSL 1

Kernel Version

Linux version 5.15.90.1-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) 2.34.0.20200220) #1 SMP Fri Jan 27 02:56:13 UTC 2023

Distro Version

Kali linux

Other Software

No response

Repro Steps

uninstall the old kali linux
reinstall kali linux from ms store.

Expected Behavior

The Kali linux installed successfully.

Actual Behavior

Could not open/start it when installed finished.

Diagnostic Logs

Failed to attach disk 'C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\LocalState\ext4.vhdx' to WSL2: The system cannot find the file specified.
Error code: Wsl/Service/CreateInstance/MountVhd/ERROR_FILE_NOT_FOUND
Press any key to continue...

C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg>du -v

DU v1.62 - Directory disk usage reporter
Copyright (C) 2005-2018 Mark Russinovich
Sysinternals - www.sysinternals.com

           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\AC\INetCache
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\AC\INetCookies
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\AC\INetHistory
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\AC\Temp
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\AC
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\AppData
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\LocalCache\Local\Microsoft
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\LocalCache\Local
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\LocalCache\Roaming\Microsoft\Windows\Start Menu\Programs
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\LocalCache\Roaming\Microsoft\Windows\Start Menu
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\LocalCache\Roaming\Microsoft\Windows
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\LocalCache\Roaming\Microsoft
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\LocalCache\Roaming
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\LocalCache
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\LocalState
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\RoamingState
           8  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\Settings
          32  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\SystemAppData\Helium
          32  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\SystemAppData
           0  C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg\TempState

Totals:
Files:        8
Directories:  21
Size:         40,960 bytes
Size on disk: 135,168 bytes


C:\Users\Liu.D.H\AppData\Local\Packages\KaliLinux.54290C8133FEE_ey8k8hqnwqnmg>

The text was updated successfully, but these errors were encountered:

cakeGH · 2023-04-30T11:05:33Z

Hello, I'm new to this computer stuff but I had this issue too. Couldn't find anything except a short 2min YT video. Basically you need to re-install and run your Unix installation through Powershell first.

Steps:
run Windows Powershell as Admin
wsl --uninstall kali-linux
wsl --install --distribution kali-linux

This will run kali-linux in the Powershell terminal. You can just close the Powershell terminal then run the app from the store. Not sure how or why it works but it worked for me. Hope this helps you and whoever encounters this!

davhdavh · 2023-05-08T05:31:37Z

>wsl --unregister ubuntu
followed by
>wsl --install
fixes the problem for ubuntu atleast

dreamflasher · 2023-05-22T12:36:26Z

I can confirm, a simple reinstallation via Microsoft Store does not work, but wsl unregister and then install does.

kilogold · 2023-05-31T07:03:18Z

Agreed. Same issue. This is the way.

bi44fv · 2023-06-10T05:26:11Z

it worked for me, thanks alot

danikane · 2023-06-15T19:03:59Z

On point! Thanks!

githubrowdy · 2023-06-24T21:44:58Z

It does also for kali
wsl --unregsiter kali-linux

mcscwizzy · 2023-06-27T18:46:20Z

Can confirm the unregister and install works. Saved my backside today.

azuraerae · 2023-06-28T07:25:30Z

This is it 👍

pauljones0 · 2023-07-12T05:06:56Z

This fixed it. Thank you

V4mp1reeee · 2023-07-13T18:22:08Z

i have it loading, its saying installing ubuntu, im worried.

kumarchandresh · 2023-07-15T15:12:19Z

> wsl --unregister ubuntu
followed by reinstall from ms store also worked.

alizul01 · 2023-07-27T01:56:28Z

worked!

bmaciag · 2023-07-29T17:07:04Z

worked. thx

marviniciuz · 2023-08-03T23:53:40Z

I have the same problem how to solve?

marviniciuz · 2023-08-04T13:44:42Z

I achieved
after running the commands
wsl --unregister ubuntu and wsl --instal

after uninstalling ubuntu from the microsoft store and installing again

sradu86 · 2023-08-07T22:56:49Z

in pws:
wsl --unregister kali-linux

wsl --install kali-linux

meyerbro · 2023-08-29T11:24:20Z

It's kind of obvious that loosing all your work would fix it guys.
But what's the solution when we can't/don't want to lose all the data???

TheFlash787 · 2023-08-30T17:51:24Z

If your vhdx file is missing, it might be that your data is already gone -- as that file has been deleted which is the storage volume for the Ubuntu operating system. Uninstalling and reinstalling just reinstates that fresh volume.

Senbonzakura1234 · 2023-09-09T11:26:05Z

Facing this problem too, when trying to install wsl

johnnymatt · 2023-09-11T10:25:37Z

Works (as of 11/09/2023):
wsl --unregister ubuntu
wsl -- install

daniel-rodriguez-azumo · 2023-09-12T13:26:59Z

TL;DR: Go to "Turn windows features on and off" -> uncheck windows subsystem for linux -> restart -> do it again and check the windows subsystem for linux box and after restarting again you are good to go.

I had the same issue as OP, I tried moving my ext4.vhdx disk file, in an attempt to free it from whatever process was using it, it denied this action but also told me which process was using this file, it was System in my case, so I tried the steps described on my tldr and it worked, without losing data or any side effects.

I also tried other solutions which didn't work: Signing out of my user, restarting, closing other processes.

Hope this helps.

Silic0nS0ldier · 2023-09-17T04:31:49Z

I've run into the same problem. Tried using Recuva to see if I could restore the file with no luck.

I wonder if this data loss is related to behaviours associated with these directories. From the UWP docs;

Each UWP app gets several folders under c:\users<user name>\AppData\Local\Packages<app package identifier>\, which appears to be the case for WSL distros as well. At least those distributed via the store.
LocalState is for data local to the current device. OneDrive backs up this data, such that it can be restored on new devices.
There is also RoamingState (in Windows 11 it no longer roams) and TempState.
Such backup behaviour should be readonly for the current device, so I do not know how it could cause this. I just know from the docs that it is a mechanism that touches this area and that something abnormal has occurred.

Possibly related issues;

No cause determined - https://stackoverflow.com/questions/52713201/downloaded-files-in-appdata-local-packages-auto-deleting-in-uwp
Certificate issue with side-loaded app - https://stackoverflow.com/questions/74595055/uwp-storage-file-is-deleted-on-close-even-though-i-did-not-how-can-i-prevent-it

I know on Android if the certificate used to sign an app changes, data-loss occurs. I believe the same applies to UWP/sandboxed apps on Windows. So in my case if the certificate for Ubuntu 22.04 changed with an app update, that may have wiped the data (possibly in a manner that leaves just enough behind that errors are raised rather than a new install being started).

Looking at the last modified date in MS Store, I can see "Ubuntu 22.04.2 LTS" was modified on 2023-09-03, which is between my last usage and discovery of this issue. Currently installed version is 2204.2.47.0.

Assuming the issue was caused by LocalState being wiped due to certificate changes, preventing reoccurrence means having the WSL files live somewhere else. The easiest way to achieve this would be;

Install as normal.
Open shell (not in installed distro, Windows Powershell is what I used)
Export distro
wsl --export <distro-name> $env:UserProfile\Downloads\distro.tar
Delete distro
wsl --unregister <distro-name>
Import exported distro
wsl --import <distro-name> <install-location> $env:UserProfile\Downloads\distro.tar

Output is slightly different to what OP posted, so here it what I got (to aid future searches).

Failed to attach disk 'C:\Users\jorda\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu22.04LTS_79rhkp1fndgsc\LocalState\ext4.vhdx' to WSL2: The system cannot find the file specified.
Error code: Wsl/Service/CreateInstance/MountVhd/ERROR_FILE_NOT_FOUND

[process exited with code 4294967295 (0xffffffff)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

dobigbadwolf · 2023-09-21T00:30:19Z

i had to adapt the unix command so it was 'wsl unregister kali-linux' the ran the 2nd linux command and it worked perfectly thanx!

realyukii · 2023-09-22T23:40:39Z

I've also had a similar problem, and trying @daniel-rodriguez-azumo's solution didn't work for me. In my case, wsl error after updating the user directory

what should I do? how to update the OldPath to CurrentPath on users directory?

Failed to attach disk 'C:\Users\OldPath\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu_79rhkp1fndgsc\LocalState\ext4.vhdx' to WSL2: The system cannot find the path specified.
Error code: Wsl/Service/CreateInstance/MountVhd/ERROR_PATH_NOT_FOUND

// The old path
C:\Users\OldPath\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu_79rhkp1fndgsc\LocalState\ext4.vhdx
// The right path:
C:\Users\CurrentPath\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu_79rhkp1fndgsc\LocalState\ext4.vhdx

realyukii · 2023-09-22T23:46:00Z

Ah NVM, #9349 (comment) solved my problem

I hope in the future this process will be done automatically when updating the user directory.

gexadax · 2023-09-27T22:04:38Z

Thanks this is working 👍
wsl --unregister ubuntu
wsl -- install

TuanDung0902 · 2023-10-04T13:55:02Z

Yeah, it worked!

TiloGit · 2023-11-02T18:05:18Z

had this today. Got lucky just reboot of Windows fixed it. (Microsoft Windows NT 10.0.22621.0)

xanthisafk · 2023-11-18T08:18:08Z

This is the one. Thank you!

CihatDinc · 2023-11-29T14:03:35Z

it worked, thanks 👍

gayashvihangana · 2023-12-04T14:21:38Z

This worked for me. Thank you!

mcpower · 2023-12-06T10:19:36Z

WARNING: wsl --unregister ubuntu MAY REMOVE USER DATA

If you unintentionally run it:

Try finding your old files in AppData\Local\Packages. My files were in CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc, which is thankfully different from the newly installed CanonicalGroupLimited.Ubuntu_79rhkp1fndgsc.
Recover your files by either mounting them in a new WSL distro with wsl --mount --vhd <pathToVHD>, or following WSL2 Register Command #4762 (comment).

Leonezz · 2023-12-29T06:42:25Z

One should NOTE this operation removes the distro entirely

dmtzs · 2023-12-30T16:21:02Z

Executing the command: wsl --unregister adn then wsl --install doenst fix the problem.
What really does is to install another ubuntu which is the latest version too with LTS, and is not the same as the one in the microsoft store.

But if for a reason you prefer to install it like this way then you should be sure to delete the broken version if you dont want to have trash in your pc

adnanh5 · 2024-01-08T06:35:19Z

Thank you so much for this solution I was struggling for hours

ueeou · 2024-01-13T00:49:45Z

Thank you so much

Smiley2507 · 2024-01-16T12:38:58Z

Thank you. This solved my problem.

spidy2356 · 2024-01-22T13:48:40Z

just use unregister instead of uninstall in the given cmd wsl --uninstall kali-linux

and my issue solved

safwanshamsir99 · 2024-03-26T05:37:08Z

I found another solution on David Bombal YouTube

ASV1995 · 2024-04-01T21:13:06Z

Still works thank you :)

dobigbadwolf · 2024-04-02T00:49:55Z

Hey there, I'm glad to hear that the fix worked for Ubuntu! Thanks for the help. Cheers!

…

On Mon, Apr 1, 2024 at 5:13 PM Amir Vasseghi ***@***.***> wrote: >wsl --unregister ubuntu followed by >wsl --install fixes the problem for ubuntu atleast Still works thank you :) — Reply to this email directly, view it on GitHub <#10032 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7QYAJHCX2CSZMZNKRITOZDY3HEXVAVCNFSM6AAAAAAXNH5LWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZQGU3DMMBYGM> . You are receiving this because you commented.Message ID: ***@***.***>

fikfr · 2024-04-15T19:49:23Z

help, i cant unregister it, cos powershell says there is no wsl installed, even tho it says there is...

when starting kali, it still says the same error...

Emereh-boop · 2024-05-12T12:56:06Z

thank a lot this fixed the issue 👍

Fabienjulio · 2024-06-14T07:59:49Z

Thanks a lot!
I had the same problem but with Docker Desktop
provisioning docker WSL distros: ensuring main distro is deployed: checking if main distro is up to date: checking main distro bootstrap version: getting main distro bootstrap version: exit code: 4294967295: running WSL command wsl.exe C:\Windows\System32\wsl.exe -d docker-desktop -u root -e wsl-bootstrap version: Échec de l’attachement du disque « <HOME>\AppData\Local\Docker\wsl\distro\ext4.vhdx » à WSL2. Error code: Wsl/Service/CreateInstance/MountVhd/HCS/ERROR_FILE_NOT_FOUND : exit status 0xffffffff

Solved it with just wsl --unregister docker-desktop and then restarting Docker

jjavierdguezas · 2024-06-14T10:00:58Z

same problem here, wsl --unregister docker-desktop and restart Docker Desktop just work! thanks @Fabienjulio ... no data was lost btw

sayol · 2024-08-21T09:17:16Z

Confirm that this works perfectly!

EricHerlitz · 2024-09-03T13:58:17Z

This is usually an issue with your rights, ensure you have sufficient rights to the vhdx file. Which you probably don't have since this file most likely was moved from another computer.
E.g

chozillla · 2024-09-18T18:21:50Z

it is 2024 and this works for me!

wsl --unregister ubuntu wsl -- install

omereliusuk · 2024-12-21T21:02:04Z

thank you

RobertoAlessandri · 2025-02-05T10:10:17Z

What if I don't want to --unregister? I am afraid I'd loose al my (non backed-up) files

luwukien · 2025-02-13T04:22:36Z

thank you. It's working.

This was referenced Mar 12, 2024

Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2: The system cannot find the file specified. #11288

Open

Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2: The system cannot find the file specified #11290

Closed

Failed to attach disk 'LocalState\ext4.vhdx' to WSL2: The system cannot find the file specified. #10032

Failed to attach disk 'LocalState\ext4.vhdx' to WSL2: The system cannot find the file specified. #10032

Comments

liudonghua123 commented Apr 27, 2023 • edited Loading

Windows Version

WSL Version

Are you using WSL 1 or WSL 2?

Kernel Version

Distro Version

Other Software

Repro Steps

Expected Behavior

Actual Behavior

Diagnostic Logs

cakeGH commented Apr 30, 2023 • edited Loading

davhdavh commented May 8, 2023

dreamflasher commented May 22, 2023

kilogold commented May 31, 2023

bi44fv commented Jun 10, 2023

danikane commented Jun 15, 2023

githubrowdy commented Jun 24, 2023

mcscwizzy commented Jun 27, 2023

azuraerae commented Jun 28, 2023

pauljones0 commented Jul 12, 2023

V4mp1reeee commented Jul 13, 2023

kumarchandresh commented Jul 15, 2023

alizul01 commented Jul 27, 2023

bmaciag commented Jul 29, 2023

marviniciuz commented Aug 3, 2023

marviniciuz commented Aug 4, 2023

sradu86 commented Aug 7, 2023

meyerbro commented Aug 29, 2023

TheFlash787 commented Aug 30, 2023

Senbonzakura1234 commented Sep 9, 2023 • edited Loading

johnnymatt commented Sep 11, 2023

daniel-rodriguez-azumo commented Sep 12, 2023

TL;DR: Go to "Turn windows features on and off" -> uncheck windows subsystem for linux -> restart -> do it again and check the windows subsystem for linux box and after restarting again you are good to go.

Silic0nS0ldier commented Sep 17, 2023 • edited Loading

dobigbadwolf commented Sep 21, 2023

realyukii commented Sep 22, 2023 • edited Loading

realyukii commented Sep 22, 2023

gexadax commented Sep 27, 2023

TuanDung0902 commented Oct 4, 2023

TiloGit commented Nov 2, 2023

xanthisafk commented Nov 18, 2023

CihatDinc commented Nov 29, 2023

gayashvihangana commented Dec 4, 2023

mcpower commented Dec 6, 2023

Leonezz commented Dec 29, 2023

dmtzs commented Dec 30, 2023

adnanh5 commented Jan 8, 2024

ueeou commented Jan 13, 2024

Smiley2507 commented Jan 16, 2024

spidy2356 commented Jan 22, 2024

safwanshamsir99 commented Mar 26, 2024

ASV1995 commented Apr 1, 2024

dobigbadwolf commented Apr 2, 2024 via email

fikfr commented Apr 15, 2024

Emereh-boop commented May 12, 2024

Fabienjulio commented Jun 14, 2024

jjavierdguezas commented Jun 14, 2024

sayol commented Aug 21, 2024

EricHerlitz commented Sep 3, 2024

chozillla commented Sep 18, 2024 • edited Loading

omereliusuk commented Dec 21, 2024

RobertoAlessandri commented Feb 5, 2025

luwukien commented Feb 13, 2025

liudonghua123 commented Apr 27, 2023 •

edited

Loading

cakeGH commented Apr 30, 2023 •

edited

Loading

Senbonzakura1234 commented Sep 9, 2023 •

edited

Loading

Silic0nS0ldier commented Sep 17, 2023 •

edited

Loading

realyukii commented Sep 22, 2023 •

edited

Loading

chozillla commented Sep 18, 2024 •

edited

Loading