Unable to launch WSL Ubuntu - The system cannot find the file specified. #16757

@uptownbrown commented on GitHub (Feb 14, 2022):

I've also received this error on v1.12.10393.0; 19044.1348

@uptownbrown commented on GitHub (Feb 14, 2022): I've also received this error on v1.12.10393.0; 19044.1348

claunia commented

@zadjii-msft commented on GitHub (Feb 14, 2022):

Hmm. Settings are basically totally unmodified:


            {
                "colorScheme": "Tango Dark",
                "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",
                "hidden": false,
                "name": "Ubuntu-20.04",
                "source": "Windows.Terminal.Wsl"
            },

Is this because we promoted the startingDirecotry to ~, but then left that as the actual directory to start wsl.exe in? It shouldn't be... wait unless Ubuntu is shipping a fragment that starts ubuntu.exe. That might be a ruh roh.

@zadjii-msft commented on GitHub (Feb 14, 2022): Hmm. Settings are basically totally unmodified: ```jsonc { "colorScheme": "Tango Dark", "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}", "hidden": false, "name": "Ubuntu-20.04", "source": "Windows.Terminal.Wsl" }, ``` Is this because we promoted the startingDirecotry to `~`, but then left that as the actual directory to start `wsl.exe` in? It shouldn't be... wait unless Ubuntu is shipping a fragment that starts `ubuntu.exe`. That might be a ruh roh.

claunia commented

@fourpastmidnight commented on GitHub (Feb 14, 2022):

I reported over on the WSL GitHub project.

I can confirm this is a problem with Windows Terminal because:

I have had no Windows Updates in over a year (a Windows Update in late 2019, and twice more in early 2020 DELETED ALL of my personal user data on my work laptop—so yeah, I no longer allow my laptop to update at this time) and the last time I used my distribution, only a few weeks ago, it was working just fine inside of Windows Terminal.
The very same distribution works just fine if I start it from the Start menu tile inside the standard CMD console host window instead of using WT.

According to the bug report on the WSL project, one user set the starting directory to %USERPROFILE% and then it worked. I did the same and it did work inside of Windows Terminal, On a whim, I then set the starting directory to /home/my-wsl-username as opposed to the default ~. And I still got the error. So it would appear that there's nothing special about %USERPROFILE%, per se, but that setting a starting directory that exists inside the WSL distribution is what is currently not working in recent versions of WT. Again, everything just works if starting from the Start menu tile in the standard conhost.

Component	Version
Windows	Windows 10 20H2, 19042.804, Feature Exp Pack 120.2212.551.0
Windows Terminal (Preview)	1.13.10395.0

@fourpastmidnight commented on GitHub (Feb 14, 2022): I reported over on the WSL GitHub project. I can confirm this is a problem with Windows Terminal because: 1. I have had no Windows Updates in over a year (a Windows Update in late 2019, and twice more in early 2020 _DELETED_ **ALL** of my personal user data on my work laptop—so yeah, I no longer allow my laptop to update at this time) and the last time I used my distribution, only a few weeks ago, it was working just fine inside of Windows Terminal. 2. The very same distribution works just fine if I start it from the Start menu tile inside the standard CMD console host window instead of using WT. According to the [bug report on the WSL project](https://github.com/microsoft/WSL/issues/5906), one user set the starting directory to `%USERPROFILE%` and then it worked. I did the same and it did work inside of Windows Terminal, On a whim, I then set the starting directory to `/home/my-wsl-username` as opposed to the default `~`. And I still got the error. So it would appear that there's nothing special about `%USERPROFILE%`, per se, but that setting a starting directory that exists _inside the WSL distribution_ is what is currently not working in recent versions of WT. Again, everything _just works_ if starting from the Start menu tile in the standard conhost. | Component | Version | |:-|:-| | Windows | Windows 10 20H2, 19042.804, Feature Exp Pack 120.2212.551.0 | | Windows Terminal (Preview) | 1.13.10395.0 |

claunia commented

2026-01-31 05:21:54 +00:00

@fourpastmidnight commented on GitHub (Feb 14, 2022):

Just by way of update, using the Start tile entry for Ubuntu, I just updated the distribution, just in case there was something within the distro that might be causing this issue, especially since I haven't updated it in a bit. Still no dice.

Also, the distro is:

@fourpastmidnight commented on GitHub (Feb 14, 2022): Just by way of update, using the Start tile entry for Ubuntu, I just updated the distribution, just in case there was something within the distro that _might_ be causing this issue, especially since I haven't updated it in a bit. Still no dice. Also, the distro is: ![image](https://user-images.githubusercontent.com/6895593/153962956-58e438cc-3df5-4820-a54b-5d5990556460.png)

claunia commented

@DHowett commented on GitHub (Feb 15, 2022):

Would you mind grabbing a screenshot of that profile in the Settings UI? We'd like to see what the "final" command line is set to (which might not be reflected in your personal settings file, given that Ubuntu is known to ship a Terminal plugin :))

@DHowett commented on GitHub (Feb 15, 2022): Would you mind grabbing a screenshot of that profile in the Settings UI? We'd like to see what the "final" command line is set to (which might not be reflected in your personal settings file, given that Ubuntu is known to ship a Terminal plugin :))

claunia commented

2026-01-31 05:21:54 +00:00

@fourpastmidnight commented on GitHub (Feb 16, 2022):

@DHowett Apologies for the delay...

Let me know if you need to see the JSON or anything. Thanks.

@fourpastmidnight commented on GitHub (Feb 16, 2022): @DHowett Apologies for the delay... ![image](https://user-images.githubusercontent.com/6895593/154338090-4ca23c8c-fd6a-48eb-a2d8-3712ed2b5fa5.png) Let me know if you need to see the JSON or anything. Thanks.

claunia commented

2026-01-31 05:21:54 +00:00

@ghost commented on GitHub (Feb 20, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Feb 20, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.

claunia commented

@fourpastmidnight commented on GitHub (Feb 20, 2022):

@DHowett Just checking in to see if you require any additional information to help with resolving this issue.

@fourpastmidnight commented on GitHub (Feb 20, 2022): @DHowett Just checking in to see if you require any additional information to help with resolving this issue.

claunia commented

@fl commented on GitHub (Feb 20, 2022):

seeing comparable behavior here after upgrading from 21H1 to 21H2. Now on 21H2, after the upgrade, my "Debian" Terminal profile refuses to start with the error message

"Das System kann die angegebene Datei nicht finden.
[process exited with code 4294967295 (0xffffffff)]"

(never mind the german Windows, that's a corporate artefact).

the setting "Starting Directory" is set to "~". When I change it to either

/home/fl or
%USERPROFILE%

then Debian starts up with no errors displayed.

@fl commented on GitHub (Feb 20, 2022): seeing comparable behavior here after upgrading from 21H1 to 21H2. Now on 21H2, after the upgrade, my "Debian" Terminal profile refuses to start with the error message ``` "Das System kann die angegebene Datei nicht finden. [process exited with code 4294967295 (0xffffffff)]" ``` _(never mind the german Windows, that's a corporate artefact)._ the setting "Starting Directory" is set to "~". When I change it to either - `/home/fl` or - `%USERPROFILE%` then Debian starts up with no errors displayed.

claunia commented

@SeeJayEmm commented on GitHub (Feb 22, 2022):

Would you mind grabbing a screenshot of that profile in the Settings UI? We'd like to see what the "final" command line is set to (which might not be reflected in your personal settings file, given that Ubuntu is known to ship a Terminal plugin :))

I changed the starting directory to the work around of %USERPROFILE% since that works and I couldn't just sit around and wait for a fix.

@SeeJayEmm commented on GitHub (Feb 22, 2022): > Would you mind grabbing a screenshot of that profile in the Settings UI? We'd like to see what the "final" command line is set to (which might not be reflected in your personal settings file, given that Ubuntu is known to ship a Terminal plugin :)) I changed the starting directory to the work around of %USERPROFILE% since that works and I couldn't just sit around and wait for a fix. ![image](https://user-images.githubusercontent.com/788552/155173410-ef4ae557-bbac-443b-ad6a-4bea0c7d4279.png)

claunia commented

@phil-blain commented on GitHub (Feb 22, 2022):

@SeeJayEmm my workaround is to change the commandline to wsl.exe ~ -d Ubuntu. This is with Windows Terminal 1.11.3471, Windows 1909. I have not yet upgraded to WT 1.12.

@phil-blain commented on GitHub (Feb 22, 2022): @SeeJayEmm my workaround is to change the commandline to `wsl.exe ~ -d Ubuntu`. This is with Windows Terminal 1.11.3471, Windows 1909. I have not yet upgraded to WT 1.12.

claunia commented

@supersu097 commented on GitHub (Feb 24, 2022):

@SeeJayEmm my workaround is to change the commandline to wsl.exe ~ -d Ubuntu. This is with Windows Terminal 1.11.3471, Windows 1909. I have not yet upgraded to WT 1.12.

It works for me on Windows Terminal 1.12.10393.0 and Win10 20H2, thanks a lot~

@supersu097 commented on GitHub (Feb 24, 2022): > @SeeJayEmm my workaround is to change the commandline to `wsl.exe ~ -d Ubuntu`. This is with Windows Terminal 1.11.3471, Windows 1909. I have not yet upgraded to WT 1.12. It works for me on Windows Terminal 1.12.10393.0 and Win10 20H2, thanks a lot~

claunia commented

@AlistairHardy commented on GitHub (Feb 25, 2022):

I've tried the above 1.12.10334 on Win10 Enterprise version 2004 and it has not worked

@AlistairHardy commented on GitHub (Feb 25, 2022): I've tried the above 1.12.10334 on Win10 Enterprise version 2004 and it has not worked

claunia commented

@fourpastmidnight commented on GitHub (Mar 5, 2022):

I have new information. On a whim, I opened a new WSL Ubuntu tab in Windows Terminal on my home computer, and it worked!!

My home computer is also running Windows Terminal v1.13.10395.0. So what's different?

The starting directory setting is different.

On my work laptop, the starting directory was set to ~. This value exhibits the problem described in this issue.
On my home laptop, the starting directory is set to //wsl$/Ubuntu/<my-username>/home. This setting is working under the very same version of Windows Terminal.

Not sure why my work laptop is using a different Starting directory setting, as I never changed it.

@fourpastmidnight commented on GitHub (Mar 5, 2022): I have new information. On a whim, I opened a new WSL Ubuntu tab in Windows Terminal on my _home_ computer, and it worked!! My home computer is also running Windows Terminal v1.13.10395.0. So what's different? The starting directory setting is different. On my work laptop, the starting directory was set to `~`. This value exhibits the problem described in this issue. On my home laptop, the starting directory is set to `//wsl$/Ubuntu/<my-username>/home`. This setting is working under the very same version of Windows Terminal. Not sure why my work laptop is using a different Starting directory setting, as I never changed it.

claunia commented

@fourpastmidnight commented on GitHub (Mar 29, 2022):

So, I tried updating my work computer's Windows Terminal profile for Ubuntu to the starting path being used by my home computer. No dice. Every time I change the Home directory path, Windows Terminal continues to change it back to ~. Since I originally posted, Windows Terminal has updated to v1.13.10733.0. So this is still an issue. BUT, it seems like it could be computer related, i.e. not necessarily Windows Terminal?

@fourpastmidnight commented on GitHub (Mar 29, 2022): So, I tried updating my work computer's Windows Terminal profile for Ubuntu to the starting path being used by my home computer. No dice. Every time I change the Home directory path, Windows Terminal continues to change it back to `~`. Since I originally posted, Windows Terminal has updated to v1.13.10733.0. So this is still an issue. BUT, it _seems_ like it could be _computer_ related, i.e. not necessarily Windows Terminal?

claunia commented

@Trinovantes commented on GitHub (Apr 5, 2022):

Been also having this issue for the past few days. Changing the starting directory to \\wsl$\Ubuntu-20.04\home\{name}\ fixed it for me

This might be caused by 1.13.10336 update where it sets the default starting directory to ~ if the Windows build is 19041 or higher but I'm currently on 19043

@Trinovantes commented on GitHub (Apr 5, 2022): Been also having this issue for the past few days. Changing the starting directory to `\\wsl$\Ubuntu-20.04\home\{name}\` fixed it for me This might be caused by `1.13.10336` update where it sets the default starting directory to `~` if the [Windows build is 19041 or higher](https://github.com/microsoft/terminal/pull/12315/files#diff-5e9c1a502c638d38b8faa6fc82b884b3208d39a93d2ebc3c8d5a8fc504c82a3aR31) but I'm currently on 19043

claunia commented

@fourpastmidnight commented on GitHub (Apr 6, 2022):

UPDATE

OK, I tried again to update the Starting Directory of my WSL Ubuntu Windows Terminal profile. This time, the change I made "stuck" and I was able to use Windows Terminal again to start Ubuntu.

The starting directory I used was \\wsl$\<wsl-distro-name>\home\<distro-username>. So, I'm using the "evergreen" Ubuntu distro, so that would be \\wsl$\Ubuntu\home\<my-distro-username>.

This is now working for me. My version of Windows Terminal since my last update has not changed. So I no longer believe this to be a Windows Terminal issue. It may have been a WSL Ubuntu issue, or an issue local to my machine (though, it seems many others also experience a similar issue).

Bottom line: WOMM.

@fourpastmidnight commented on GitHub (Apr 6, 2022): **UPDATE** OK, I tried _again_ to update the Starting Directory of my WSL Ubuntu Windows Terminal profile. This time, the change I made "stuck" and I was able to use Windows Terminal again to start Ubuntu. The starting directory I used was `\\wsl$\<wsl-distro-name>\home\<distro-username>`. So, I'm using the "evergreen" Ubuntu distro, so that would be `\\wsl$\Ubuntu\home\<my-distro-username>`. This is now working for me. My version of Windows Terminal since my last update has **not** changed. So I no longer believe this to be a Windows Terminal issue. It may have been a WSL Ubuntu issue, or an issue local to my machine (though, it seems many others also experience a similar issue). Bottom line: WOMM.

claunia commented

@WowSuchRicky commented on GitHub (Apr 10, 2022):

Hello,

I had this same issue and changing the starting directory in my Windows Terminal profile for WSL from ~ to %USERPROFILE% worked perfectly.

@WowSuchRicky commented on GitHub (Apr 10, 2022): Hello, I had this same issue and changing the starting directory in my Windows Terminal profile for WSL from `~` to `%USERPROFILE%` worked perfectly.

claunia commented

@isaacgr commented on GitHub (Apr 11, 2022):

The command line on the profile is: C:\WINDOWS\system32\wsl.exe -d Ubuntu-20.04

I am able to run this command line successfully without error. I have also tried creating a new profile from scratch with the same command line and it fails.
PS> wsl -l -v
  NAME            STATE           VERSION
* Ubuntu-20.04    Stopped         1
If I create a profile that just launches wsl with no parameters it works fine. C:\WINDOWS\system32\wsl.exe

Adding this line to the settings.json for the ubuntu profile file worked for me
"commandline": "wsl.exe ~ -d Ubuntu",

@isaacgr commented on GitHub (Apr 11, 2022): > The command line on the profile is: `C:\WINDOWS\system32\wsl.exe -d Ubuntu-20.04` > > I am able to run this command line successfully without error. I have also tried creating a new profile from scratch with the same command line and it fails. > > ``` > PS> wsl -l -v > NAME STATE VERSION > * Ubuntu-20.04 Stopped 1 > ``` > > If I create a profile that just launches wsl with no parameters it works fine. `C:\WINDOWS\system32\wsl.exe` Adding this line to the settings.json for the ubuntu profile file worked for me ` "commandline": "wsl.exe ~ -d Ubuntu",`

claunia commented

@EvanMcEwen commented on GitHub (Apr 14, 2022):

seeing comparable behavior here after upgrading from 21H1 to 21H2. Now on 21H2, after the upgrade, my "Debian" Terminal profile refuses to start with the error message
"Das System kann die angegebene Datei nicht finden.
[process exited with code 4294967295 (0xffffffff)]"
(never mind the german Windows, that's a corporate artefact).

the setting "Starting Directory" is set to "~". When I change it to either
* `/home/fl` or

* `%USERPROFILE%`
then Debian starts up with no errors displayed.

This fixed my issues thank you.

@EvanMcEwen commented on GitHub (Apr 14, 2022): > seeing comparable behavior here after upgrading from 21H1 to 21H2. Now on 21H2, after the upgrade, my "Debian" Terminal profile refuses to start with the error message > > ``` > "Das System kann die angegebene Datei nicht finden. > [process exited with code 4294967295 (0xffffffff)]" > ``` > > _(never mind the german Windows, that's a corporate artefact)._ > > the setting "Starting Directory" is set to "~". When I change it to either > > * `/home/fl` or > > * `%USERPROFILE%` > > > then Debian starts up with no errors displayed. This fixed my issues thank you.

claunia commented

@tydemeadows commented on GitHub (Apr 25, 2022):

Fixed My Issue with This by going to

Terminal Settings
Defaults (Just Under Profile Header)
Starting Directory
!!!! Uncheck "Use Parent Process Directory"

@tydemeadows commented on GitHub (Apr 25, 2022): Fixed My Issue with This by going to - Terminal Settings - Defaults (Just Under Profile Header) - Starting Directory - !!!! Uncheck "Use Parent Process Directory" ![Capture](https://user-images.githubusercontent.com/59396897/165114429-8fa303e0-8928-4515-8293-e4ba21b663fc.JPG)

claunia commented

@zadjii-msft commented on GitHub (May 2, 2022):

Okay there's a lot of reports here, I'm gonna try and distill this down

Seems like the whole "default to ~ for WSL's on <= 19041" doesn't work for folks. Reports that this doesn't work on:

21H2 (19044)
19043 (19043)
1909 (18363)
20H2 (19042)
Win10 Enterprise version 2004 (19041)

For people affected by this, changing to %USERPROFILE% works as a workaround.

I coulda swore that #12437 should have fixed this, which is in Windows Terminal v1.12.10393.0 / Windows Terminal Preview v1.13.10395.0. I need to dig out a win10 machine to be able to validate though.

Edit: Dug out my 19044 machine.

1.13.10983 works perfectly fine with ~ as the starting directory.
1.12.10982 does NOT, and gives the same 0xffffffff error.

Considering that 1.14 is about to come out and 1.13 is gonna get promoted to the Stable version, I'm inclined to close this out as "fixed in preview"

Ah. This is cause the check that should enable this came in #12315, but that only ever went to Preview, not stable. #9223, which goes all the way back to Preview v1.11.2421.0.

I'm definitely gonna close this as "fixed in preview". Sorry for the weird torn state here for a couple releases folks.

@zadjii-msft commented on GitHub (May 2, 2022): Okay there's a lot of reports here, I'm gonna try and distill this down Seems like the whole "default to `~` for WSL's [on <= 19041](https://github.com/microsoft/terminal/pull/12315/files#diff-5e9c1a502c638d38b8faa6fc82b884b3208d39a93d2ebc3c8d5a8fc504c82a3aR31)" doesn't work for folks. Reports that this doesn't work on: * [21H2](https://github.com/microsoft/terminal/issues/12474#issuecomment-1046337276) (`19044`) * [19043](https://github.com/microsoft/terminal/issues/12474#issuecomment-1088800417) (`19043`) * [1909](https://github.com/microsoft/terminal/issues/12474#issuecomment-1047977717) (`18363`) * [20H2](https://github.com/microsoft/terminal/issues/12474#issuecomment-1049522652) (`19042`) * [Win10 Enterprise version 2004](https://github.com/microsoft/terminal/issues/12474#issuecomment-1050899689) (`19041`) For people affected by this, changing to `%USERPROFILE%` works as a workaround. I coulda swore that #12437 should have fixed this, which is in `Windows Terminal v1.12.10393.0` / `Windows Terminal Preview v1.13.10395.0`. I need to dig out a win10 machine to be able to validate though. <hr> Edit: Dug out my 19044 machine. * 1.13.10983 works perfectly fine with `~` as the starting directory. * 1.12.10982 does NOT, and gives the same `0xffffffff` error. Considering that 1.14 is about to come out and 1.13 is gonna get promoted to the Stable version, I'm inclined to close this out as "fixed in preview" Ah. This is cause the check that should enable this came in #12315, but that only ever went to Preview, not stable. #9223, which goes all the way back to `Preview v1.11.2421.0`. I'm definitely gonna close this as "fixed in preview". Sorry for the weird torn state here for a couple releases folks.

claunia commented

@Gerschel commented on GitHub (Jun 2, 2022):

I landed on this thread after I had this issue. So I'm going to leave a comment for those that come across this because of a different reason.
In my scenario, once upon a time I setup a connection to debian using "net use" and setting it up as the z drive.

At another point when I decided to give windows terminal a whirl, it decided to use that setup for the startup directory.

For some reason, it happened a few times, where my z drive didn't connect properly on a fresh boot, and I would get this error.
The solution then was reestablishing that z drive using net use.
After coming across this thread, I tried changing it to use ~, and it worked fine.

@Gerschel commented on GitHub (Jun 2, 2022): I landed on this thread after I had this issue. So I'm going to leave a comment for those that come across this because of a different reason. In my scenario, once upon a time I setup a connection to debian using "net use" and setting it up as the z drive. At another point when I decided to give windows terminal a whirl, it decided to use that setup for the startup directory. For some reason, it happened a few times, where my z drive didn't connect properly on a fresh boot, and I would get this error. The solution then was reestablishing that z drive using net use. After coming across this thread, I tried changing it to use ~, and it worked fine.

claunia commented

@sandeepDevJs commented on GitHub (Jun 2, 2022):

seeing comparable behavior here after upgrading from 21H1 to 21H2. Now on 21H2, after the upgrade, my "Debian" Terminal profile refuses to start with the error message
"Das System kann die angegebene Datei nicht finden.
[process exited with code 4294967295 (0xffffffff)]"
(never mind the german Windows, that's a corporate artefact).

the setting "Starting Directory" is set to "~". When I change it to either

/home/fl or

%USERPROFILE%

then Debian starts up with no errors displayed.

Worked Out!! Thanks mate!

@sandeepDevJs commented on GitHub (Jun 2, 2022): > seeing comparable behavior here after upgrading from 21H1 to 21H2. Now on 21H2, after the upgrade, my "Debian" Terminal profile refuses to start with the error message > > ``` > "Das System kann die angegebene Datei nicht finden. > [process exited with code 4294967295 (0xffffffff)]" > ``` > > _(never mind the german Windows, that's a corporate artefact)._ > > the setting "Starting Directory" is set to "~". When I change it to either > > * `/home/fl` or > * `%USERPROFILE%` > > then Debian starts up with no errors displayed. Worked Out!! Thanks mate!

claunia commented

@hubertsvk commented on GitHub (Jul 2, 2022):

Hello,
no solutions doesn`t work for me, even if I changed ~ to %USERPROFILE% or /home/fl

w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained here
wsl --version
WSL version: 0.61.8.0
Kernel version: 5.10.102.1
WSLg version: 1.0.39
MSRDC version: 1.2.3213
Direct3D version: 1.601.0
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22000.778

@hubertsvk commented on GitHub (Jul 2, 2022): Hello, no solutions doesn`t work for me, even if I changed ~ to %USERPROFILE% or /home/fl w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained [here](https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/) `wsl --version` `WSL version: 0.61.8.0` `Kernel version: 5.10.102.1` `WSLg version: 1.0.39` `MSRDC version: 1.2.3213` `Direct3D version: 1.601.0` `DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp` `Windows version: 10.0.22000.778`

claunia commented

@sandeepDevJs commented on GitHub (Jul 2, 2022):

Hello, no solutions doesn`t work for me, even if I changed ~ to %USERPROFILE% or /home/fl

w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained here wsl --version WSL version: 0.61.8.0 Kernel version: 5.10.102.1 WSLg version: 1.0.39 MSRDC version: 1.2.3213 Direct3D version: 1.601.0 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22000.778

Manually change the home directory in general setting

@sandeepDevJs commented on GitHub (Jul 2, 2022): > Hello, no solutions doesn`t work for me, even if I changed ~ to %USERPROFILE% or /home/fl > > w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained [here](https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/) `wsl --version` `WSL version: 0.61.8.0` `Kernel version: 5.10.102.1` `WSLg version: 1.0.39` `MSRDC version: 1.2.3213` `Direct3D version: 1.601.0` `DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp` `Windows version: 10.0.22000.778` Manually change the home directory in general setting

claunia commented

@hubertsvk commented on GitHub (Jul 2, 2022):

Hello, no solutions doesnt work for me, even if I changed ~ to %USERPROFILE% or /home/fl w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained [here](https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/) wsl --version WSL version: 0.61.8.0 Kernel version: 5.10.102.1 WSLg version: 1.0.39 MSRDC version: 1.2.3213 Direct3D version: 1.601.0 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22000.778`

Manually change the home directory in general setting

didnt helped even if i changed from ~ to %USERPROFILE% or /home/username

@hubertsvk commented on GitHub (Jul 2, 2022): > > Hello, no solutions doesn`t work for me, even if I changed ~ to %USERPROFILE% or /home/fl > > w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained [here](https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/) `wsl --version` `WSL version: 0.61.8.0` `Kernel version: 5.10.102.1` `WSLg version: 1.0.39` `MSRDC version: 1.2.3213` `Direct3D version: 1.601.0` `DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp` `Windows version: 10.0.22000.778` > > Manually change the home directory in general setting didnt helped even if i changed from ~ to %USERPROFILE% or /home/username

claunia commented

@sandeepDevJs commented on GitHub (Jul 2, 2022):

Hello, no solutions doesnt work for me, even if I changed ~ to %USERPROFILE% or /home/fl w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained [here](https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/) wsl --version WSL version: 0.61.8.0 Kernel version: 5.10.102.1 WSLg version: 1.0.39 MSRDC version: 1.2.3213 Direct3D version: 1.601.0 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22000.778`

Manually change the home directory in general setting

didnt helped even if i changed from ~ to %USERPROFILE% or /home/username

Change it to other directories like c:/users/

@sandeepDevJs commented on GitHub (Jul 2, 2022): > > > Hello, no solutions doesn`t work for me, even if I changed ~ to %USERPROFILE% or /home/fl w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained [here](https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/) `wsl --version` `WSL version: 0.61.8.0` `Kernel version: 5.10.102.1` `WSLg version: 1.0.39` `MSRDC version: 1.2.3213` `Direct3D version: 1.601.0` `DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp` `Windows version: 10.0.22000.778` > > > > > > Manually change the home directory in general setting > > didnt helped even if i changed from ~ to %USERPROFILE% or /home/username Change it to other directories like c:/users/<your-username-here>

claunia commented

@hubertsvk commented on GitHub (Jul 2, 2022):

Hello, no solutions doesnt work for me, even if I changed ~ to %USERPROFILE% or /home/fl w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained [here](https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/) wsl --version WSL version: 0.61.8.0 Kernel version: 5.10.102.1 WSLg version: 1.0.39 MSRDC version: 1.2.3213 Direct3D version: 1.601.0 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22000.778`

Manually change the home directory in general setting

didnt helped even if i changed from ~ to %USERPROFILE% or /home/username

Change it to other directories like c:/users/

no, didnt helped, still the same. I changed it to C:\Users\hubertsvk\Documents

@hubertsvk commented on GitHub (Jul 2, 2022): > > > > Hello, no solutions doesn`t work for me, even if I changed ~ to %USERPROFILE% or /home/fl w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained [here](https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/) `wsl --version` `WSL version: 0.61.8.0` `Kernel version: 5.10.102.1` `WSLg version: 1.0.39` `MSRDC version: 1.2.3213` `Direct3D version: 1.601.0` `DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp` `Windows version: 10.0.22000.778` > > > > > > > > > Manually change the home directory in general setting > > > > > > didnt helped even if i changed from ~ to %USERPROFILE% or /home/username > > Change it to other directories like c:/users/ no, didnt helped, still the same. I changed it to C:\Users\hubertsvk\Documents

claunia commented

@sandeepDevJs commented on GitHub (Jul 2, 2022):

Did u resatrt

Hello, no solutions doesnt work for me, even if I changed ~ to %USERPROFILE% or /home/fl w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained [here](https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/) wsl --version WSL version: 0.61.8.0 Kernel version: 5.10.102.1 WSLg version: 1.0.39 MSRDC version: 1.2.3213 Direct3D version: 1.601.0 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22000.778`

Manually change the home directory in general setting

didnt helped even if i changed from ~ to %USERPROFILE% or /home/username

Change it to other directories like c:/users/

no, didnt helped, still the same. I changed it to C:\Users\hubertsvk\Documents

Did you restart the terminal? See if it helps .. I don't seem to figure it out

@sandeepDevJs commented on GitHub (Jul 2, 2022): Did u resatrt > > > > > Hello, no solutions doesn`t work for me, even if I changed ~ to %USERPROFILE% or /home/fl w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained [here](https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/) `wsl --version` `WSL version: 0.61.8.0` `Kernel version: 5.10.102.1` `WSLg version: 1.0.39` `MSRDC version: 1.2.3213` `Direct3D version: 1.601.0` `DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp` `Windows version: 10.0.22000.778` > > > > > > > > > > > > Manually change the home directory in general setting > > > > > > > > > didnt helped even if i changed from ~ to %USERPROFILE% or /home/username > > > > > > Change it to other directories like c:/users/ > > no, didnt helped, still the same. I changed it to C:\Users\hubertsvk\Documents Did you restart the terminal? See if it helps .. I don't seem to figure it out

claunia commented

@hubertsvk commented on GitHub (Jul 2, 2022):

Did u resatrt

Hello, no solutions doesnt work for me, even if I changed ~ to %USERPROFILE% or /home/fl w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained [here](https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/) wsl --version WSL version: 0.61.8.0 Kernel version: 5.10.102.1 WSLg version: 1.0.39 MSRDC version: 1.2.3213 Direct3D version: 1.601.0 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22000.778`

Manually change the home directory in general setting

didnt helped even if i changed from ~ to %USERPROFILE% or /home/username

Change it to other directories like c:/users/

no, didnt helped, still the same. I changed it to C:\Users\hubertsvk\Documents

Did you restart the terminal? See if it helps .. I don't seem to figure it out

no, still the same

@hubertsvk commented on GitHub (Jul 2, 2022): > Did u resatrt > > > > > > > Hello, no solutions doesn`t work for me, even if I changed ~ to %USERPROFILE% or /home/fl w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained [here](https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/) `wsl --version` `WSL version: 0.61.8.0` `Kernel version: 5.10.102.1` `WSLg version: 1.0.39` `MSRDC version: 1.2.3213` `Direct3D version: 1.601.0` `DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp` `Windows version: 10.0.22000.778` > > > > > > > > > > > > > > > Manually change the home directory in general setting > > > > > > > > > > > > didnt helped even if i changed from ~ to %USERPROFILE% or /home/username > > > > > > > > > Change it to other directories like c:/users/ > > > > > > no, didnt helped, still the same. I changed it to C:\Users\hubertsvk\Documents > > Did you restart the terminal? See if it helps .. I don't seem to figure it out no, still the same

claunia commented

@sandeepDevJs commented on GitHub (Jul 3, 2022):

Did u resatrt

Hello, no solutions doesnt work for me, even if I changed ~ to %USERPROFILE% or /home/fl w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained [here](https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/) wsl --version WSL version: 0.61.8.0 Kernel version: 5.10.102.1 WSLg version: 1.0.39 MSRDC version: 1.2.3213 Direct3D version: 1.601.0 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22000.778`

Manually change the home directory in general setting

didnt helped even if i changed from ~ to %USERPROFILE% or /home/username

Change it to other directories like c:/users/

no, didnt helped, still the same. I changed it to C:\Users\hubertsvk\Documents

Did you restart the terminal? See if it helps .. I don't seem to figure it out

no, still the same

That's it, dude, that's all I knew.

@sandeepDevJs commented on GitHub (Jul 3, 2022): > > Did u resatrt > > > > > > > Hello, no solutions doesn`t work for me, even if I changed ~ to %USERPROFILE% or /home/fl w11 21H2 with Windows Subsystem for Linux Preview from this https://aka.ms/wslstorepage explained [here](https://devblogs.microsoft.com/commandline/a-preview-of-wsl-in-the-microsoft-store-is-now-available/) `wsl --version` `WSL version: 0.61.8.0` `Kernel version: 5.10.102.1` `WSLg version: 1.0.39` `MSRDC version: 1.2.3213` `Direct3D version: 1.601.0` `DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp` `Windows version: 10.0.22000.778` > > > > > > > > > > > > > > > > > > Manually change the home directory in general setting > > > > > > > > > > > > > > > didnt helped even if i changed from ~ to %USERPROFILE% or /home/username > > > > > > > > > > > > Change it to other directories like c:/users/ > > > > > > > > > no, didnt helped, still the same. I changed it to C:\Users\hubertsvk\Documents > > > > > > Did you restart the terminal? See if it helps .. I don't seem to figure it out > > no, still the same That's it, dude, that's all I knew.

claunia commented