Closed a-t-0 closed 2 years ago
<p>Thank you, I think it is pretty awesome you're giving the installer a try! You are actually the first person to test it besides myself, so I hope you can spare me slight patience if my responses are somewhat slow. I will look into it later today.</p>
<p>Indeed line 1080 seems to be commented yet also seems to be responsible for the error. It does make me curious that the first error message refers to line 805 in the log you so kindly provided. I would have to look into it in more detail to understand how that is possible.</p>
Yet the underlying problem seems to be that lxrun
is not available on your device. This lxrun
is an old command used to control the WSL
from commandline.
I think you already did this manually, and I think my code also does it automatically (in line 7), but just to verify, could you ensure
Windows Subsystems for Linux
is enabled in the Windows Features
? As illustrated in the next figure (doesn't have to show Beta):
In the meantime, I will look to determine why lxrun
would not be available, I think it might be dependent on some windows update or version.
<p><a href="https://github.com/MicrosoftDocs/WSL/issues/353" data-hovercard-type="issue" data-hovercard-url="/MicrosoftDocs/WSL/issues/353/hovercard">This issue with the same error message</a> suggests:</p>
wslconfig /unregister Legacy
Could you perhaps give that a try and retry execution of the ./TaskwarriorInstaller.ps1
?
In the PS1 file, line 1080 is commented, but it seems like that is the line responsible for the first error.
If I continue with the installation, I also receive the same error again, and other errors. Full printout is shown below: