Skip to content
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

Installation fails when creating a user #319

Closed
LKS90 opened this issue May 3, 2016 · 3 comments
Closed

Installation fails when creating a user #319

LKS90 opened this issue May 3, 2016 · 3 comments

Comments

@LKS90
Copy link

LKS90 commented May 3, 2016

Hey there!

I just installed the Windows 10 Insider Preview Build 14332.rs1_release.160422-1940 and tried using the Windows Bash shell. Problem is, the user creation fails and the Bash on Ubuntu for Windows application simple doesn't open anything. I have also tried to use the /setdefaultuser option of LxRun.exe but this fails as well, this time it at least provides an error code:

Error: 0x80040306

image

Any help would be appreciated :).

Greetings
Lukas

@benhillis
Copy link
Member

@LKS90 by chance are you running a non-English version of windows? There normally would be an error print for that error code.

Unsupported console settings. In order to use this feature the legacy console must be disabled.

  1. Open cmd.exe
  2. Right click title bar -> Properties -> Uncheck Use legacy console
  3. Click OK

@LKS90
Copy link
Author

LKS90 commented May 4, 2016

@benhillis my system is in english, I might have switched it from german at some point though.

Unticking the "legacy" option solved the problem, thanks!
Quick question: Where did you find the information for the Error Code? I googled 0x80040406 but came up with (I think) unrelated results

@LKS90 LKS90 closed this as completed May 4, 2016
@benhillis
Copy link
Member

@LKS90 Great I'm glad it solved your problem!

The error code is actually just defined locally in our project so we can print actionable error codes to the user. Once our error message are localized you should see the correct string error message. We basically have a big switch statement that maps error codes to strings. The actual error code of the API that fails due to legacy console is very generic (E_INVALIDARG I think) so we had to define our own error code. Hope that makes sense :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants