Announcing Windows 10 Insider Preview Build 16215 PC + 15222 Mobile Insider

Edwin said:

Yup!

Crash Utility (CU).

Edwin said:

LOL!
Actually, the AU I have on this SSD is flawless,
the CU on tablet works great,
it's the Insider Preview that's a piece of junk!

Yes, I have AU on one desktop and CU on one desktop and two laptops. No problems with either of these -- I agree the big problem is with 215 version of insider. I'm on slow ring til there is something new and better to download.

I am going to try again with 16215 after I backup


I have installed myself temporarily on the Insider Slow Ring. So after the AOEMI image of my Windows 10/Windows Server 2016 dual finishes I'll check and see if any 16xxxx build have been released to the Slow Ring (I don't think so) and then rejoin the Fast Ring. The thing about the 1703 install is that I installed all the features that could be problematic like .Net 3.5 (from WU - when it works. Ubuntu on Windows is installed and so is Xming - I install synaptic to run X programs like Firefox, Thunderbird etc. Also Hyper-V is installed and at least my Windows Server 2016 Essentials Hyper-V got rearmed for another 180 days with 20 hours(!!!) to go.
If I'm not mistaken I guess Dora is relying on folks to have seen the Webcast where we learn it is unlikely we will the great followup flight to 16215. BTW I did see notice anybody at the roundtable remarking on what a disaster 215 turned out to be. My retrying to install 215 will for me be the ultimate test of whether it can be installed on a dual boot (Windows only - As far as Windows knows that is - Siduction is still installed but that's not apparent to Windows). Very interesting day so far - I'm happy with the results.

martyfelker said:

I am going to try again with 16215 after I backup


I have installed myself temporarily on the Insider Slow Ring. So after the AOEMI image of my Windows 10/Windows Server 2016 dual finishes I'll check and see if any 16xxxx build have been released to the Slow Ring (I don't think so) and then rejoin the Fast Ring. The thing about the 1703 install is that I installed all the features that could be problematic like .Net 3.5 (from WU - when it works. Ubuntu on Windows is installed and so is Xming - I install synaptic to run X programs like Firefox, Thunderbird etc. Also Hyper-V is installed and at least my Windows Server 2016 Essentials Hyper-V got rearmed for another 180 days with 20 hours(!!!) to go.
If I'm not mistaken I guess Dora is relying on folks to have seen the Webcast where we learn it is unlikely we will the great followup flight to 16215. BTW I did see notice anybody at the roundtable remarking on what a disaster 215 turned out to be. My retrying to install 215 will for me be the ultimate test of whether it can be installed on a dual boot (Windows only - As far as Windows knows that is - Siduction is still installed but that's not apparent to Windows). Very interesting day so far - I'm happy with the results.

Windows 10 Build 16215 will install on a dual boot machine with Windows 10 CU and Windows 10 Insider Build 16199. I just did it this morning and by this afternoon I had rolled back to 16199 for the third time in the past three or so days. Having to hard wire Ethernet to the machine is just way too slow to deal with.

Preparing to install IP Build 16215 now. 25% .... 32 % .... 41% .... 50% .... 52% .... 56% .... 59%. Now switching from Edge to Chrome Canary

Back using Canary - I much happier although I will confess I've much more time with Chrome and FF than Edge. Still have not see anything compelling about Edge I'm afraid. We are at Preparing to Install (Build 16215) 68% ... Installing FF nightly now we are at 79% ... 94% Switching to Nightly

Back in Nightly as it is syncing and preparing to install still at 94% Making Nightly my default browser (probably temporary).

Preparing to install at 100%.


Now to restart. See you on the other side

FAILURE. INACCESSIBLE BOOT DEVICE. However it was a BLUE screen of death not a GREEN screen of death. Does that give you any information MS?

Had to use Unlocker 1.92 to delete a leftover $Windows~BT directory. Went back to slow ring (when will there be a release to the SLOW ring??)