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

Buildfeed canary is at 16221 compiled Friday. I've created 3 215 VMs on Linux which I'm copying for use with Windows Server 2016.

HippsieGypsie said:

I hear what you’re saying about testing. John. That’s why we choose to volunteer, but if Insiders can’t get their systems updated at all there won’t be any testing of the system itself, let alone 3rd party apps. It looks as if many can’t even use the ISO install.

First off, it could be that the main problem is the UUP delivery MS chose. It may not be downloading all the necessary system files needed for some. It’s going back and forth keeping track and delivering only the necessary files needed. Heck it could be a flaw that it’s not fulfilling the correct database to do so, again, for some. And yes, it is a “fat” upgrade install. Took me roughly 15 minutes more to install. A lot of changes for sure.

I saw Kari’s frustrated tweet of asking MS for the ESD. I can understand why MS wants us to use and test UUP, but simply ask us to. If it doesn’t work, then an ISO should be made available. Even make it a week after update date. I understand MS's approach with UUP to save data for those on a metered connection or even otherwise. Heaven knows we use too much utility resources as it is.

BTW, TBO I do run some 3rd party SSD disk and Asus MoBo utilities on my CU partition. I only install these when I think the system is stable enough, especially Ai Suite II for it’s managing a lot of the system. Usually 3 or 4 days after upgrading. I’m about to install them on my 16215 too. I’ll give it til after an update. Hopefully tomorrow, Tuesday. We’ll see.

Gotcha. I think running through the reboot process is what messed mine up, it would get to the second or third reboot and just hang. Forcing the reboot and attempting to manually install must have triggered something, because it was right after that that the machine start and completed the upgrade process.

I might try to revert and then see if I can replicate the issue (and my fix) late tonight.

Although possible, anything is, I sincerely doubt that the calamitous install debacle with this build is due in most part by 3rd party software. I set up a clean install of 16199, completely virgin and untouched by anything non-MS, and it failed thru WU as did all the rest.

dencal said:

In Settings, Network and Internet......check what status is showing.....is it Ethernet or Wi-Fi?

What I did was to roll back to Build 16199, hook up to Ethernet and then let it offer me Build 16215 again. That's when I got the There were problems . . . Retry, so at that point I was on Ethernet. I have since gone back to WiFi on Build 16199; unplugged the Ethernet cable.

WiFi is showing right now.

f14tomcat said:

Although possible, anything is, I sincerely doubt that the calamitous install debacle with this build is due in most part by 3rd party software. I set up a clean install of 16199, completely virgin and untouched by anything non-MS, and it failed thru WU as did all the rest.

I agree. In my opinion the fact that the same install can even fail with different errors supports the fact that 16215 simply was and is busted.

Like this laptop of mine. I made a Macrium image after upgrade was downloaded and initialized because at that point first posts and tweets about it failing started to appear. I wanted to be sure, so after creating ISO but before upgrade I made an image.

- Round 1, upgrade from WU > Restart now, error code 0x30018
- Round 2, upgrade from ISO, error code 0x30018



- At this point I restored the image and tried again

- Round 3, upgrade from WU > Restart now, error code 0x2004
- Round 4, upgrade from ISO, error code 0x2004

Same machine, exactly the same start situation.

Kari said:

I agree. In my opinion the fact that the same install can even fail with different errors supports the fact that 16215 simply was and is busted.

Like this laptop of mine. I made a Macrium image after upgrade was downloaded and initialized because at that point first posts and tweets about it failing started to appear. I wanted to be sure, so after creating ISO but before upgrade I made an image.

- Round 1, upgrade from WU > Restart now, error code 0x30018
- Round 2, upgrade from ISO, error code 0x30018



- At this point I restored the image and tried again

- Round 3, upgrade from WU > Restart now, error code 0x2004
- Round 4, upgrade from ISO, error code 0x2004

Same machine, exactly the same start situation.

And a VM of mine (VMWare) went right thru without choking once. But that is with the VMWare Host in charge of the Boot process........

Wynona said:

What I did was to roll back to Build 16199, hook up to Ethernet and then let it offer me Build 16215 again. That's when I got the There were problems . . . Retry, so at that point I was on Ethernet. I have since gone back to WiFi on Build 16199; unplugged the Ethernet cable.

WiFi is showing right now.

Sometimes even though you have an ethernet cable hooked up, wifi is still kicking in. Try disabling the wifi adapter. (Open network and sharing center>>> Change adapter settings>>>right-click & disable wireless network)