It's the simple reason I asked that question when such issue arose from the initial installation process. I think it makes sense because I have seen such case with somebody trying to run it on 32-bit Window 10 with an old build version.
Ive managed to run cmd via task manager. can't run powershell though "cant start because mscoree.dll is missing ..." something is verybroken heh. I can run explorer, and after that i tried opening pc settings which gave "microsoft security client error...." anyway, im gonna format this box, should i avoid developer mode the next time i try lxss?
I am on 'Developer Mode' without having any issue. Sorry for the inconveniences the changes must have caused you.
Just for the record, are you somewhat affiliated with microsoft or the creation of lxss? Anyway, what's the proper way to install LXSS? I might have missed something.
Yes, It's been discussed privately and they're aware. It's not a major issue since it's secure, any possible changes will likely only start to appear sometime after the RS2 release later this year. That would be sihost.exe and that process is unrelated to WSL. I've seen that happen when people use very badly written tools to uninstall Cortana, Windows Defender or other Windows packages (and also when COM has fatal registry/configuration corruption). The only way you're going to fix that corruption is by reinstalling Windows or resetting to an earlier restore point (if you've used a modded or customized Windows installation disk, bin it and download a normal ISO). WSL has never been available on 32bit Windows because the x86 Linux user-space uses incompatible calling conventions. Trying to force install those packages on 32-bit will destroy your system.
A run of chackdsk then sfc /scannow, is enough to fix any image corruption, no matter if you removed the crap from the iso with the proper tools or if you brutally removed something from the online system. If the system worked on the first run it must work later.
sfc is overrate, yes, but by a different mean. People thinks it can fix "everything", while 90% of Win errors are related to user's settings, not to files corruptions BUT It fixes missing, corrupted, replaced system files and this is enough in cases like the mentioned one where a needed dll is gone.
is a very badly written tool something like MSMG toolkit? i did use MSMG to remove cortana, edge, and default metro apps to an offline image before installing. wrong to do this?
i've been stripping the crap out of my systems using MSMG for the longest time, no problems, no errors, works wonders
closed my firewall app and now its working properly -_- i didnt think of closing the firewall hahahah thanks for the tip
When are we going to get stable Windows Subsystem for Linux? It has been in beta since it came out and that is very discouraging at this point.
Hi there I would like to use WSL under WindowsPE I´ve found the Microsoft-Windows-Lxss-Optional-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cab and the Microsoft-Windows-Lxss-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cab and integrated it, but I cant start it under PE.... Does anyone sees an possibility? Thanks
WindowsPE is not live linux CD and Lxss require DeveloperMode FOD package to function, which is not installable on WinPE