service not started message box

[btreut]

Environment

Microsoft Windows [Version 10.0.17763.1282]
due to restrictions in our environment, after having tried to install WSL and a distribution, I tried now to follow the commandline instructions given here: Manual Installation

Steps to reproduce

1. Enabled the WSL feature in PowerShell and rebooted previously (as a user with administrative rights but not the full Administrator). I have now redone this step and it looks like this:

PS C:\windows\system32> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

Path :
Online : True
RestartNeeded : False

since it says: RestartNeeded : False I did not reboot again.

2. Downloaded DebianGNULinux_1-1-3-0_x64__76v4gfsz19hv4.Appx, unpacked it and run debian.exe from the
   unpacked directory (still with the user with administrative rights), it worked and I was able to create a new user and now I am able to call debian.exe by specifying the full path of the debian.exe file or by calling wsl from anywhere as this user, but I cannot start it as normal user.
   I had previously tried to install it via add-appxpackage and I have a menu entry "Debian", but when I try to start that I get a message box saying that some service is not started:
   

Expected behavior

I would like to be able to start the debian prompt as normal user from anywhere in the filesystem.

Actual behavior

I can start the debian prompt only as administrative user by calling wsl.exe

When I try to start wsl as normal user, I still get

H:>wsl
Für das Windows-Subsystem für Linux wurden keine Distributionen installiert.
Distributionen zur Installation finden Sie im Microsoft Store:
https://aka.ms/wslstore

[therealkenc]

since it says: RestartNeeded : False I did not reboot again.

You needed to restart at that point. Relatively safe to assume you've restarted since though, since you did manage to install the distro.

from the unpacked directory (still with the user with administrative rights)

Install your distro as a normal user. [Similar to but different than #5428, others.]

Microsoft Windows [Version 10.0.17763.1282]

Also advisable to sync up to 19041.

[btreut]

Install your distro as a normal user. [Similar to but different than #5428, others.]

I managed to install & initialize Debian as normal user, but I cannot see/access network drives in linux and I still get that awfull message box (see above) when trying to start Debian from the start menu. When starting Linux from the Shift-Right klick menu in Windows Eplorer on a network drive, I end up in my home directory.

[btreut]

I have no idea what information I should provide for a repro, please advise.

As far as I remember I tried to install the Debian Appx package on the the commandline quite some time ago (before installing manually on the command line as given above), so I tried now to get rid of it also on the command line.

After some experimenting I successfully used this PowerShell command Get-AppxPackage TheDebianProject.DebianGNULinux -AllUsers | Remove-AppxPackage -AllUsers as user with admin rights to remove the package again. Now the start menu entry "Debian" is gone and with it the chance to reproduce the message box. After having reinstalled it with administrative rights and the command line Add-AppPackage -Path .\DebianGNULinux_1-1-3-0_x64__76v4gfsz19hv4.Appx I do not see the Start Menu entry as norrmal user. After reboot, still no menu entry "Debian Gnu/Linux", so I opened a Power Shell as normal user and re-issued the command Add-AppPackage -Path .\DebianGNULinux_1-1-3-0_x64__76v4gfsz19hv4.Appx as normal user. Now the menu entry reappeared and I still or better again get the infamous "Service not started ... " message box.

BTW: I can start the Linux Prompt from anywhere in the filesystem in the explorer with Shift-Right-Klick, but on the network drives the prompt opens in /home/my-user-name and the network drives are not mapped to /mnt/? there is only /mnt/c/ and /mnt/d/ no traces of the other network drives (i.e. H: K: V:, which correspond to several Microsoft Windows Network drives).

[therealkenc]

There isn't an expectation you'll be able to provide additional information. It is more likely it will remain unknown the steps taken to get your system in the current state. Hence the tag. Your constructive path forward would be to sync up to 19041, which will reinstall enough moving parts that there is at least some chance enough of your machine will be reconstituted into operable condition.

[btreut]

sync up to 19041,

hmm, I don't have any chance to influence the sync up, this will be provided by our global administrators. The last update was yesterday, but it was only up to Microsoft Windows [Version 10.0.17763.1339].

Just to summarize my restrictions: I do not have access to MS-App store. I have to download manually and install on the command line. Our environment forces a huge amount of group policies upon us and has an active applocker (which made it quite difficult to install the distro with normal user rights). I cannot start Windows explorer with administrative rights. I did not find a way to start system settings GUI with administrative rights. Updates are regulated and streamlined by our IT-Service Dpt.

[therealkenc]

It is possible WSL is being thwarted by some admin policy. They way to test that hypothesis would be to try WSL on another machine in your organization with the same admin policies. Be careful to do the Enable-WindowsOptionalFeature as Administrator, rebooting, and the rest as a normal user. If it fails similarly on the other locked down machine, there isn't much you can do except ask your IT-Service Dpt. If it does work, it is an exercise in finding out what is special about your machine.

You can try, on a lark, as Administrator:

C:\> sc stop LxssManager
[it might not be started]
C:\> sc start LxssManager

Doing a "restart LxssManager" has cured some ills in the past. After the start, pause for half a minute before starting WSL in another console as a normal user. The chances of this working are "low" but it is worth the shot.

[btreut]

try WSL on another machine in your organization with the same admin policies

there is one other (physical) machine with which I could try it, but that has to wait until I am back from home-office at my "normal" workplace.

When I try to call sc stop LxssManager from a cmd running with local admin rights I see shortly a black window popping up, but I don't have any chance to read any message. Trying the same command from Power Shell (with admin rights) passes silently without any feedback. The same happens for sc start .... But the error message persists.

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!