Announcing Windows 10 Insider Preview Build 16215 PC + 15222 Mobile Insider
-
Chnages for WSL
Install 215 from an ISO (clean install). When I run bash I get the following.
So I guess I'll wait until Ubuntu, Fedora etc appear in the store. Guess that will be a couple of months at least but worth waiting for since I have VMs with Ubuntu installed in WSL.
Next up. Hyper-V.
BTW there were C++ runtime errors during and after installing this and I did run into a GSOD. If we had polls on this forum I have no doubt that 215 would win worst Preview Build ever.
-
-
Hi,
BTW there were C++ runtime errors during and after installing this and I did run into a GSOD. If we had polls on this forum I have no doubt that 215 would win worst Preview Build ever.
Seen those too. And yes, I agree worst IP build ever.
Cheers,
-
Finally managed to enable Edge in this build.
Reset app didn't work, reset Windows didn't work, in-place upgrade didn't work... Was just going to do clean install, but tried reset Windows in safe boot (troubleshooter) and looks like Windows are behaving somewhat better... This is practically clean install thou. Lost all of third party apps, just documents and some settings remained.
-
Install 215 from an ISO (clean install). When I run bash I get the following.
So I guess I'll wait until Ubuntu, Fedora etc appear in the store. Guess that will be a couple of months at least but worth waiting for since I have VMs with Ubuntu installed in WSL.
Next up. Hyper-V.
BTW there were C++ runtime errors during and after installing this and I did run into a GSOD. If we had polls on this forum I have no doubt that 215 would win worst Preview Build ever.
@martyfelker
Marty, not sure if this pertains to you, but this is from Post #1.
Windows Subsystem for Linux (WSL) no longer requires Developer Mode! Previously, you had to enable Developer Mode (Settings -> Update & Security -> For Developers) in order to run Bash & Linux tools on Windows. This restriction has been lifted; you can now run Bash on Windows without developer mode being enabled! More information here
How to Enable or Disable Bash on Ubuntu in Windows 10
Known issues for PC
- Features that are delivered on-demand from Windows Update such as Developer Mode, .NET 3.5, and Speech Packs will not be available for this build. If you are a developer and require Developer Mode – please ensure it is enabled BEFORE taking this build.
Obviously, if you have a clean install, you can't do it before, as they say to.
Just thought I'd point that out. May apply to you, not sure.
And the .net 3.5 can't be installed via Programs and Features in this build. You have to use that DISM enable command on your 16215 ISO.
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\sources\sxs
(sub the mounted letter for "d")
Deploy .NET Framework 3.5 by using Deployment Image Servicing and Management (DISM)
-
-
Tried Kari's first solution and it mirrored what happened before. Got to 28% or so then restored to Build 16193. Error message was the same.
-
Tried Kari's first solution and it mirrored what happened before. Got to 28% or so then restored to Build 16193. Error message was the same.
I'm sorry it didn't work for you. Working on it...
-
I'm sorry it didn't work for you. Working on it...
No worries; it's about the adventure. Lol.
-
Got your post about Bash no longer requiring developer mode a bit late for my physical machine. I am using an image created by Terabyteunlimited Image for Windows created 6/7 to restore (hopefully) the entire disk - ie the BOOTIT partition, Windows Server 2013, Siduction17.1 and Windows 10 Build 16xxx (not sure whether it is 193 or 199). In any event, I will wait until the next build when things may be sorted out. In VMs where Bash Ubuntu had already been installed, it still worked after the 215 upgrade. Otherwise not. As you can see there are no distros in the store now. But thanks for the link!
-
Got your post about Bash no longer requiring developer mode a bit late for my physical machine. I am using an image created by Terabyteunlimited Image for Windows created 6/7 to restore (hopefully) the entire disk - ie the BOOTIT partition, Windows Server 2013, Siduction17.1 and Windows 10 Build 16xxx (not sure whether it is 193 or 199). In any event, I will wait until the next build when things may be sorted out. In VMs where Bash Ubuntu had already been installed, it still worked after the 215 upgrade. Otherwise not. As you can see there are no distros in the store now. But thanks for the link!
Sorry it was late for you. Notes are published by MS and Shawn as soon as they are available, usually right after release is announced. I try to read them first so not to get caught before DL.
-
-
Not a problem. If the full disk restore works as I expect I will be back in business and immediately go to the slow ring to prevent the reboot loop. And if one really can install say Fedora in WSL it will be very cool. Also looking towards the Windows Server 2016 insiders.