@sebus Thanks for your effort to guide me through the tons of contradictory comments. May I ask, do you use insider program system files? do you have case sensitive filesystem turned on? I assume even if I manage to install Ubuntu 16.04, I'd still have the main problem to solve. An installer package containing the current insider program system files would indeed be great.
I thought you were stating an issue based on on how you wrote your comment and I didn't bother looking at the link because I already knew the answer WSL is implemented almost entirely in kernel mode and you would have to replace ntdll.dll, ntoskernl.exe and lxrun.sys (to name a few) but replacing those files will also render your current installation unbootable. You either have to suck it up and switch to the Slow insider ring or wait until the next GDR of Windows 10 in February.
Well just a thought for what it's worth, I think it would be remarkable if the Linux subsystem devs would use brand new APIs which is under development in parallell with them. There could of course be additions to the common NT APIs done by the Linux subsystem devs themselves and thereby require an update of nt.dll et al. However I suspect the large part of the work done by WSL team is about properly implement unix syscalls, as it was in the old POSIX subsystem. I haven't looked in the WSL files at all though. But perhaps you know for a fact the insider program WSL system files need an updated NT API? As for me I will not switch to the insider program and turning off case sensitivity isn't an option, so it'll probably be February for me (thanks for the info BTW).
Perhaps you are running Anniversary update. I don't know how much the differences are with WSL on the AU from the IP but I think nothing so much separated both, from the dependences to the whole Windows subsystem there seem to be nothing new. You don't really need to switch to Insider Preview to carry out proper test on WSL. February would be a long time and the Creator Update is coming by next month. I would expect you to do that in that timeframe.
i use windows 10 enterprise ltsb 2016 if i start bash.exe (installed with ad function and dev mode is enabled) he says "Die gewünschte App wird unter dieser Windows-Version nicht unterstützt." this windows version is not supported is there any workaround ?
Works perfectly fine here, so must be something else, you use different language? EDIT It does NOT work any more! The app that you are trying to run is not supported on this version of Windows. That is with KB3206632 installed. So obviously this update does BREAKS WLS