Der Befehl WSL ist entweder falsch geschrieben oder konnte nicht gefunden werden

Immer beim Versuch mich anzumelden und mein password eingebe kommt das selbe Fenster immer wieder und ich gebe mehrmals das password ein und es kommt das selbe als boot Schleife weiß keine Lösung falls jmd weiß wie ich dieses Problem lösen kann und wieder ins Desktop komme danke schonmal im voraus.

Hatte davor die Fehlermeldung Start job is running for hold until boot process finishes up No Limit

Und habe dieses Problem schon gelöst in dem ich Ctrl und Alt und F1 oder F2 gedrückt habe öffnet sich das terminal und habe viele Befehle eingetragen

sudo apt-get remove plymouth sudo apt-get remove xserver-xorg-video-intel

Jetzt neu starten,

Drücken Sie Ctrl+Alt+F1und melden Sie sich mit Ihrem Benutzernamen und Passwort an.

Führen Sie dann die folgenden Befehle aus.

Habe lightdm ausgewählt beim Display Manager.

sudo apt-get install lightdm sudo dpkg-reconfigure lightdm

Display-Manager als lightdm ausgewählt

sudo apt-get install ubuntu-desktop

sudo apt-get install -f --reinstall lightdm

sudo apt-get install unity

sudo-apt-get install ubuntu-session

sudo dpkg-reconfigure lightdm Sie werden aufgefordert, eine von zwei Optionen auszuwählen: gdm& lightdm. Wählenlightdm

sudo apt-get install gnome

sudo apt-get autoremove

sudo apt install unity-tweak-tool

sudo apt-get autoremove --purge light-themes

sudo apt-get install light-themes

Aber jetzt kann ich mich nicht einloggen ^weil es eine login boot Schleife es verhindert das ich mich einloggen kann.

Hello,

quite a while ago i used Cygwin to run sh/bash scripts as custom sensors for PRTG. My setup is similar to this kb //kb.paessler.com/en/topic/60017-custom-sensor-bash-script

Now i want to use the "Windows Subsystem for Linux" feature in Windows 10 instead of Cygwin. I made sure the PRTG service runs under the same user as i used to setup WLS (Ubuntu). I changed the batch file accordingly "'c:\cygwin64\bin\bash.exe -l -c" -> "'c:\windows\system32\bash.exe -l -c" and verified it's working by executing it in cmd terminal.

Unfortunately i only get an error message in PRTG (response not well formed) "Antwort nicht wohlgeformt: "(Der Befehl "C:\Windows\System32\bash.exe" ist entweder falsch geschrieben oder konnte nicht gefunden werden. ECHO ist ausgeschaltet (OFF). )" (Code: PE132)"

However. If i copy bash.exe into the EXE folder (Custom Sensors) and write the whole -l -c ... string as parameter into the sensor, it works.

Any idea? I could use it with direct bash.exe command, but it would be nice to be able to just specify the script with its parameters or path.

bash-exe batch custom

Hi

I am trying to install Microsoft Windows Subsystem Linux on Windows 10 Home (ver 10.0.16299.15)

For That I am trying to enable optional feature through "Programs and Features" dialog or running PS command
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
I am getting the following error message

Enable-WindowsOptionalFeature : One or several parent features are disabled so current feature can not be enabled. At line:1 char:1 + Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows- ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException + FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand

Also when I look at the feature list after the restart in the Programs and Features, it is still disabled.

What might be a problem?

Thanks
Darius

Verify if your windows 10 home is 64-bit. Screen tells the problem.It does not give directions though, like how you can enable this feature.Moreover I guess there is dependency issue among features which is missing, like what feature depends on what feaure.

"Enable-WindowsOptionalFeature : One or several parent features are disabled so current feature can not be enabled."

I guess you should find a way to enable this feature "Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand"

if you sort it out share svp.

@dariuspranskus - What do you see if you try to enable the WSL feature through the turn on/off features UI.

I'm no expert on the subject (rather opposite), but I think he might need -All.

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux -All

Without -All you don't get the dependencies. That is absurd default behaviour of course (imagine apt requiring --with-dependencies). And the "One or several parent features" error message is plain lazy. But I digress.

This is also happening to me (I tried with -All and without). Using the Features UI prompts for restart, and upon restarting the box is unchecked.

I'm having the same problem on Windows 10 Pro, version 1709

@samcarlinone I was having the same issue. I think part of the problem was some missing update somewhere. Since I was having a hard time forcing Windows to update, I downloaded the Windows Media Creation Tool and re-installed Windows. I should note that I didn't delete any of my personal files, apps, etc.

Could people encountering this issue ensure that the trustedinstaller service is set to autostart?

SC config trustedinstaller start= auto

For me this was also caused by a different problem where a fresh Windows install wouldn't install the latest cumulative updates, getting in an infinite loop of requiring a restart for updates that wouldn't go through. The fix was reinstalling Windows.

Running PowerShell "as Administrator" solved the problem for me

getting in an infinite loop of requiring a restart for updates that wouldn't go through

I hit that too in early January and a total wipe ended up being the only path to salvation, despite my considerable best efforts to solve it otherwise.

Running PowerShell "as Administrator" solved the problem for me

@dariuspranskus can you confirm you were running an elevated Powershell? That was kind of taken as a given in this thread. I think you probably were, because I'd expect a different mode of failure if you weren't. But "solved the problem for me" (emphasis on definite article mine) loose end above needs tidying up. Running elevated will definitely solve a problem, but not necessarily your problem.

Hi

I had the same issue (the One or several parent features are disabled so current feature can not be enabled. one).

In my case it was that the Trusted Installer service wasn't up. I started it and set it to run automatically and than wait a cople of minutes and try again to activate the feature and then it works.

Hope it helps other people.

Same problem

PS C:\Windows\system32> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Enable-WindowsOptionalFeature : One or several parent features are disabled so current feature can not be enabled.
At line:1 char:1

  • Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows- ...
  • + CategoryInfo : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException + FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand

I turned the TrustedInstaller to Auto and restarted and everything. Just don't understand what does it want me to do!
If I try to turn on WSL via GUI it say finished doing requested changes and restarts. But when I check it again after restart, the box is unchecked!
Please help

Same problem, same error COMException.

OS: Windows 10 x64
Build: 16299

Same issue here, brand new machine.

OS Name: Microsoft Windows 10 Pro OS Version: 10.0.16299 N/A Build 16299 System Type: x64-based PC

Same issue again, I'm led to believe it's a problem with version 1709. Restarts do nothing, no system changes are saved, no updates going through. Any solutions? I've tried everything but the media creation tool, trying to avoid a fresh install.


The same issue with Windows 10 Home (1709) - 64

The same issue. I tried installing the update recommended by stensson, but ended up in the "infinite loop of requiring a restart for updates" as described by Morthy.

@tanjakantola Have you also tried starting Windows in recovery mode and choosing to repair the installation? I believe that fixed my infitite loop issue, together with 4093112. Can't remember all details on which sequence i did this though.

CapsuleID, hoe dus you do that??!!

Select "Turn Windows Features on/off"

@Groumy , the trusted installer service set to up fixed the thing.
When typing "Enable-WindowsOptionalFeature -Online -FeatureName TelnetClient" (or whatever feature) I was having "Enable-WindowsOptionalFeature: Impossible de lire la clé du Registre de configuration" (Enable-WindowsOptionalFeature : Impossible to read Configuration regitry key).
Turning on and automatic start the "Programme d'instalaltion pour les module Windows" service which I think correspond in english to the Trusted installer has solved the problem.

@Groumy : you saved me...

I had the same problem as everyone else. My solution was disabling firewall / antivirus software before installing WSL from the PowerShell. The logs of the security software showed it was preventing a registry update from being completed at around the same time as running the install.

Giving @arnaudoisel kudos for February answer. My problem, too, was solved simply by running PowerShell as Administrator.

I am still running into this problem. I'm running PS as Administrator, and according to the graphical Windows feature installer, WSL is active. However, upon trying to start Ubuntu, I'm running into the familiar error message. I'm also positive I'm running a 64-bit Windows.

I'm assuming this is a different problem, but with similar symptoms. Can anyone help?

Edit: Perhaps I should clarify that the checkbox in the Windows Features window remains checked after a reboot. The attached screenshot is made just after rebooting.

I also have the exact problem as @wvdschel commented. In addition, if I try to enable the windows feature 'Windows Subsystem for Linux' it shows the error code 0x70083701. I tried to resolve it using the Microsoft support threads. But they are of no help.

Running power shell as admin solved the problem for me as well. Thank you!

Wie starte ich WSL?

Schalten Sie das WSL frei: Sie drücken Win-R, geben optionalfeatures ein und drücken die Eingabetaste. Es öffnet sich neues Fenster, in dem Sie Windows-Funktionen aktivieren oder deaktivieren. Setzen Sie ein Häkchen vor "Windows-Subsystem für Linux" und bestätigen Sie mit "OK".

Was macht WSL?

WSL umfasst einen Session-Managerdienst im Benutzermodus zur Verwaltung der Linux-Instanz, minimierte Pico-Prozesse zum Durchführen von Linux-Systemaufrufen und Pico-Treiber für das Emulieren des Linux-Kernels.

Wo ist WSL gespeichert?

WSL bindet die Festplattenlaufwerke Ihres Computers unter dem Ordner /mnt/<drive> in Ihre Linux-Distributionen ein. Das Laufwerk C: wird beispielsweise unter /mnt/c/ eingebunden.

Was ist WSL Exe?

Windows Subsystem für Linux über die Kommandozeile (wsl.exe) installieren. Das Subsystem für Linux besteht aus einem optionalen Windows-Feature sowie den jeweiligen Distributionen, die pro Benutzer als APPX-Paket hinzugefügt werden.

Toplist

Neuester Beitrag

Stichworte