Announcing Windows 10 Insider Preview Build 16215 PC + 15222 Mobile Insider
-
Well 215 is finally installed on the physical machine. It's in a dual boot with Windows Server 2016. Next thing is to re-enable GRUB which is easy using SystemRescueCD and booting in Siduction from the CDROM and then enable 30_os-prober and running update GRUB. Then to boot into Winodws Server 2016 and use EasyBCDedit to install the Windows boot loader to the D: drive where Windows 10 actually lives. Then I will be able to renable the BootIT menu and triple boot with ease. Lot of work though. Could have been avoided if Microsoft internally tested on a mutlboot (Linux/Windows) system. Please do that next time MS.
-
-
... all went well but it stopped around 21% BSOD: "...Failed in First Boot Phase With an Error During Boot Operation". Not giving up, will look into these boot choices (F..) I hope I can find.
I've seen the same scenario posted dozens and dozens of times today. Fails at 30%, inaccesable boot device, rollback to 16199. Words were a little different most of the time, but same scenario.
The same here. Upgrade failed twice on laptop. Next try, started the upgrade from ISO last night before going to bed leaving it to run alone. Woke up, upgrade was stuck in 33%.
Had to hard reset and restore 16199. Back on desktop, this was shown:
-
This happened all the time for me until I did clean install of 193 from the burned MS Insider ISO. I wonder when they will release the next build which has been tested in the "real world". For example maybe the latest canary (from the new buildfeed app) 10.0.16218.1000 (rs_prerelease.170606-1552)
-
So is there a fix for the Stop Boot_device_inaccessible error, or do we pull the pin and wait for the next update?
-
-
Damn MS. This is what I get when running bash in an elevated command prompt. Yes Developer Mode is enable (although there is an error message). Yes The subsystem was installed 
Note Developer Portal is GREYED OUT. Got a workaround for this stupid untested bug??
Or this when I run bash. This should give the devs a hint.
C:\WINDOWS\system32>bash
Windows Subsystem for Linux has no installed distributions.
Distributions can be installed by visiting the Windows Store:
Microsoft Corporation
Press any key to continue...
-
Imported a few Hyper-V machines. After importing 5 the MMC hung on the next. Jeez - where to begin with this build??
-
One tiny bug for me is that the battery indicator sticks to the percentage used on boot. Rebooting shows the correct usage but sticks again.
On connecting power then the battery usage is showing correct usage.
Last edited by Fabler2; 10 Jun 2017 at 02:59.
Reason: update
-
if you cant install I tryed this I have a ssd with rapid mode turn the rapid off and disable windows defender and it might install as it worked for me
And I used the iso build not sure if it would work with the main build update but the iso worked for me
-
got a issue with new build getting error for mp3 files and videos with windows media player i tryed reinstall wmp but no success and tryed sfc can didnt fix the problem so im now ran out of options if this build is no good
-
-
I honestly do sympathize with all those Insiders having problems either updating or installing using an ISO.
I can honestly state that not once since the very first W10 Insider program was released have I failed to update first time.
The only problem encountered was with one iteration, I had to wait for three days after its release.
Now please....lets have none of these........ I must be blessed comments.
Quote
