-
Notifications
You must be signed in to change notification settings - Fork 859
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Store installed Ubuntu fails to launch - Invalid parameter (french canadian) #2577
Comments
Your user profile could be damaged. I'd try to create a new user account with admin rights and after enabling WSL install Ubuntu from the store. |
Are you trying |
I received the same thing - I tried executing the ubuntu.exe directly ( I've also tried:
|
Same problem here. |
@zadjii-msft I was trying |
@mdentremont Can you try the other way to install a distro? Follow these steps:
If that works then there is a problem with the Windows Store. |
hello @onomatopellan, sorry, but that didn't work for me. nb: this is not only an issue with ubuntu. the same happens with openSUSE, too. what i tried so far: first attempt
restored windows to 1703 from bare metal backup
bye, oskar |
Same problem, found "a" workaround:
|
@rohatsu - this worked for me too. I had an unrelated error when trying to run L.E. The problem with this (and I think it's not even a problem) is the fact that the root filesystem gets created under the new directory instead of |
@rohatsu - I confirm that your work around also works for me; many many thanks! |
@zadjii-msft this is still an issue for many users (without the workaround of course) - just want to make sure it doesn't fall through the cracks |
@mdentremont Don't worry, it's still on the radar, even though I apparently forgot to mark it as a bug. My bad. It is on the radar though :) |
Any progress on this? |
today a colleague of mine did an update from wsl on 1703 to 1709. same
result.
we are still able to use legacy bash, but a solution would be desirable..
…On Fri, Jan 19, 2018 at 11:24 AM, Oliver Hanappi ***@***.***> wrote:
Any progress on this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2577 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AO8mppChipyoPqZq8qaHGtXRNKwjAY0Oks5tMG1WgaJpZM4P_V_m>
.
|
I also encountered the same error |
installed 1803 last night. same "the parameter is incorrect" as before (with debian, too) |
What's the status on this? The old product on 1703 worked. On 1709 , I got "the parameter is incorrect". Now on 1803, I get the same message "the parameter is incorrect". Please someone! |
@zadjii-msft Still broken on latest April 2018 update. Should it have been fixed here? Is there anything I should be doing to clear caches, etc? |
@benhillis owns the launcher code now, maybe he has a better idea |
Does that problem happen for all WSL Windows Store app? |
@Biswa96 I just tried openSuse and got the same dialog |
Since you are seeing this as a error dialog I feel this is likely a store issue and unrelated to WSL, however we could quickly confirm that by a trace. Could somebody who is experiencing this issue please collect a trace while attempting to launch? https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs |
@mdentremont - Thanks for sharing the traces. As I feared there are no events coming from our components so I suspect something else in Windows is causing this failure. Are there any interesting events in your event log around when this error occurs? |
@benhillis I've browsed around and couldn't see anything - do you know of a custom event filter which might catch anything relevant? |
@mdentremont - Sorry none that I know of. You might be able to track down where the error is coming from by using ProcMon. |
Is it because of domain control users? |
It's not just a domain issue, also happens with local users. I had a local profile with this issue, and a while back tracked it down with ProcMon to some Windows History folder (IIRC the folder name also referred IE) somewhere in AppData. Unfortunately I was in a hurry and didn't take notes. I couldn't tell exactly what was going wrong with the folder, but deleting the folder manually fixed the issue. It seems to be a more general Store/Windows issue as suggested above and not specific to WSL, even though WSL installs happen to trigger it. |
@benhillis This has happened to everybody in my office - we all were part of the "bash for windows" beta, which was before the Windows 10 Fall Creators update. Once we installed the fall creators update which I believe added support for installing linux ditros through the store, none of the available distros worked. I'd venture a guess that pretty much everyone in this thread is experiencing the same issue. Do you think it would be possible for you to test this out on your end? As I mentioned, this is an issue on the 2 other developer laptops in my office, so it will hopefully be easy to reproduce. |
@mdentremon - I use WSL every day and have never hit this issue. This is likely something configuration-related. Do other store apps work on these machines? |
The workaround @rohatsu described works for me as well (thanks mate!). I have multiple store apps installed and none of them give any issues, it's only the Ubuntu Windows Store App. Other distro's like Kali Linux or openSUSE give the same error. I found the following error in the event viewer: |
@benhillis Other store apps work for us. Were you using WSL back when it was in beta and not available through the Windows store? And then after updating to the Fall Creators update, the store Ubuntu app worked fine despite still having the old WSL installed? |
@benhillis Update: I tried installing Slack through the Windows store today and the issue is present for it as well, so this likely isn't a WSL issue. |
I found that it may not be a WSL issue also. It is a Windows Store issue. The only solutions that seems to work for people are drastic. Create new windows store user or reinstalling Windows are some of the things that do work. I guess i won't be using any windows store programs from now on. |
Same problem as described by others above. In addition to the workaround by @rohatsu running |
Works as of the latest Windows October update (1809)! |
i can confirm that it works with the latest windows 10 update (1809) |
@benhillis Do you have a communication channel to the Windows Store team? I can confirm the issue is still present with Windows 10 1903. Two years seems like an awfully long time for this bug to persist. |
Ridiculous that this is still a problem and a horrendous first-time user experience. Easier to just download VirtualBox than to DO ANY of this CRAP |
thanks @rohatsu, it works for me too. i just execute wrong command(like mv /* /xx) on ubuntu, then everything is gone. so i restarted reinstall everything, the result is the error code: WslRegisterDistribution error 0x80370102 when openning wsl ubuntu |
Still getting this: @rohatsu's solution works for me and the advantage is that Ubuntu is running on the HD instead of the SSD so less wear on it. |
unfortunately this didnt resolve the issue. I am still getting Installing, this may take a few minutes... |
This is an actual problem with the Microsoft Store. I was getting the same error while trying to launch Ubuntu and this is what worked for me:
As I said, this worked fine for me and it got rid of the error. Let me know if it's any help. Edit: It's been one day and the error is back. The steps I followed yesterday don't seem to work anymore. |
I found a solution how to fix this, following the tips by @rohatsu . so what I did is, first I make my PC current user as administrator to get the ownership of files which is private, I followed step no.2 on this website to get it website. |
I gave up on this a long time ago...this is an absolutely HORRIBAD first
time user experience
|
you might want to try it again following the instructions slowly, and you
will get it. the idea is simple, what you just need to do is accessing the
installation folder of wsl and move it else where. and open it from the new
directory of wsl.
at least it works for me, would be glad if I could help
|
Yes this definitely works. I was never able to repair the permissions issue with the original 'WindowsApps' hidden folder though; even when setting permissions for EVERYONE to have access to the folder. |
Can reproduce for Debian as well. ^^ |
I did a shortcut on my desktop of ubuntu.exe file from problematic path and no problem. Runing it from Start menu is still the problem. |
I feel like it's pretty clear that the issue here is spaces within the ubuntuXXXX.exe path. On my machine, the program installs to When running the ubuntuXXXX.exe from that location, I received the same error as everyone else in this thread: The parameter is incorrect. When moving the folder to C:\ubuntu instead, the program successfully installs and runs:
There is clearly an issue with how the package deals with spaces within it's path. I would recommend either properly quoting the string as it is passed around the application, or ensuring that all spaces are preceded with the escape character to resolve this issue. |
I followed the steps (manual installation steps) on this site and solved the problem: |
Is there any fix for this now? Can anyone give some solid advice and guidelines how to overcome it? |
For me, install WSL directly from the store, solved the problem, especially after the, following issue.
https://askubuntu.com/questions/1447753/error-when-installing-wsl-and-ubuntu-on-windows-11 |
ver
at a Windows Command Prompt)Microsoft Windows [version 10.0.16299.19]
I just installed the Windows 10 Fall Creator Update and I was thrilled at the fact that I could install Ubuntu.
However, all my attempts resulted in the following error:
From the UI (attempt to launch from Windows Store, I simply Ctrl-C, Ctrl-V the Dialog box here)
Power Shell (both as regular user and as administrator)
(Sorry for the french...)
What I did was this:
I am now out ouf ideas...
The text was updated successfully, but these errors were encountered: