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

With hesitation after reading about the problems here, I did an update check and 16215 was already20% downloaded. I never updated to 16199, so this was to be from 16193.1001. Seemed rather slow but eventually ended up at the "restart now" screen with a message something to the effect ..."we could not restart your machine, wait a while and try again...." The "restart now" button was non responsive, so after a while with fingers crossed" did a system reset on my computer. Reboot seemed normal, waited but windows did not continue. Went to settings/update and there was the "restart now" screen, which responded this time and the install was completed. About 2 hrs total. About the time I got the "Hi" screen, my phone went off and 16215 was downloading on it.

Probably non related, but this past week I had a lot of trouble with the Win CU computer, Word/Excel would not save/save as, crashed frequently, could not log into work email and the browser(s) were crawling. I uninstalled MWB Pro, installed MWB Free and everything returned to normal. So with this insider edition, went ahead and deleted MWB Pro while 16125 started to download. MWB Free is installed and at this early minute, everything seems normal. My phone is still working on the update.

UPDATE: Phone updated without issue.

I think we can probably dub 215 as the buggiest upgrade yet. I can't believe they didn't test this on multiboot systems.

Thanks goodness for Virtual Machines. Here I have something going on a remote server (6 ft in back of me :)


This is a VMware WS 12.5.6 VM running on Windows Server 2016 Essentials HP Proliant.

martyfelker said:

I think we can probably dub 215 as the buggiest upgrade yet. I can't believe they didn't test this on multiboot systems.

Thanks goodness for Virtual Machines. Here I have something going on a remote server (6 ft in back of me :)

I had other disk disconnected (it's Linux) and it still wouldn't even start updating after download. Luckily it let me make an ISO which I mounted and updated from it without a hitch. I don't think that build itself is buggy but this darn UUP.

badrobot said:

Too bad for you. Never failed on me,
But that doesn't mean @Wynona shouldn't try.

https://www.amazon.com/TP-Link-Power...p_89%3ATP-Link

Very true, Robot, but what ISP would I use? Kind of expensive just to make a new Build work.

Wynona said:

No way to go wired in this house, Walt. We're completely wireless and here I sit with one router and a cable modem/router combo that I cannot use.

I'm rolled back to 16199, so I'll just have to wait until the issue gets fixed.

Can't you use the router as a wireless repeater, and connect your Insider Preview machine to that router with an ethernet cable?

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.

I fought with this exactly 3 times last night and once this morning. The first time I tried, last night, before restart, I made the 16215 ISO using the tutorial and it's add-on temp fix from Kari.

After the last time this morning, I said enough! Put the ISO on a thumb drive and clean installed. All is fine now.

Doesn't affect everyone, we all know. But does affect many, many, many. It's all over Feedback.

This is an alternative if you still want 16215. The tutorial is here:

UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files Windows 10 Installation Upgrade Tutorials

And the additional fix to go with it is here:

UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files - Page 69 - Windows 10 Installation Upgrade Tutorials

You will need them both. Read carefully, especially the second one. It does work, and well.

TC

Wynona said:

Very true, Robot, but what ISP would I use? Kind of expensive just to make a new Build work.

ISP?
Whatever current you have. Powerline adapter in essence is also like an extender except it is wired.
Or if you meant you are using someone else's wifi, then yeah, that would be an issue.