In my opinion, the difficulty that some of us are experiencing can be attributed to the "state" of the Windows OS before the upgrade. Some of us are very aggressive in terms of using 3rd party software which is one possible cause of the upgrade problems. In my case, my 14986 was almost clean when I did the upgrade and I did not encounter any issues. In fact, I finished the upgrade in 20mins or so including the cumulative updates before upgrading to 15002.
Reading through the release notes again, ( something I missed in my haste to glean what changes M$ had made in this flight )
Brink in his wisdom has inserted extremely helpful tutorial links for each article.
My thanks to Brink.
To me, this shows that 1) they are trying to get as many people onto this build for testing as possible, and 2) that they are well aware of the issues that most of us are experiencing and wanted approval teasing performed by is Insiders.
I haven't had the time to check, but I did fire off the upgrade on my laptop as well, and I will know more about it this evening as well.
Here's how you can exit from account creation loop, setup always going back to network selection and starting account creation process over and over again:
After clean install or complete reset when you arrive to network selection, open Command Prompt with SHIFT + F10, then type lusmgr.msc and hit Enter to start Local Users and Groups Manager:
Delete the defaultuser() account:
Confirm (you will get three prompts, click Yes on two first and OK on last one):
Close lusrmgr.msc. Type shutdown -r -t 0 to restart Windows:
After restart, Windows recreates the defaultuser(), seems that it was somehow corrupted and forcing Windows to recreate it , also the normal user creation will now work and you are finally able to sign in to desktop
Defeating the objective, once again,
Last edited by Kari; 5 Days Ago at 20:34. Reason: Typos
What you may not be taking into consideration is that there are a whole lot of us out here that have been through the gamut of "an update/upgrade brings along with it all the problems of the prior install" and found that to be a true statement. And believe me, that same thing has happened to me several times throughout the Insider Preview Program; thus, forcing a clean install if I want things to work right. So, yeah, update information is important, but so is clean install information if Microsoft wants to get it right.
Secondly, there are a few gazillion (yeah, I like that word) of those who aren't on the Insider Preview Program that have upgraded to Windows 10. A large percentage of those will have problems, so they'll grab the ISO provided by Microsoft and do a clean install. Are they supposed to be left out in the cold because we "aren't supposed to test clean installs"?
Thirdly, if we're not supposed to test clean installs, how is Microsoft going to be made aware of bugs within that area? Oh, yeah, if Microsoft doesn't want us to do a clean install, why, then, are we provided new ISOs of the latest Builds every so often? I believe there's an ISO of Build 14986 available to us.
Yep, we can use an ISO to do a reset, repair, or clean install. And I'm getting into territory I'm not familiar with, since the only thing I am totally familiar with is a clean install from that ISO. Although I have done a repair/reset before, using my ISO when things went South. ISOs are made available to Insiders and to the great unwashed out there.
Yeah, they have internal testing going on and there are a group of testers that rank above us, but their numbers are limited, especially when you consider the number of Insiders out here.
Then you have those on the Insider Preview Program that don't come here or even to any forums (I have several friends who are in that grouping) so aren't aware they're not supposed to be testing clean installs.
Finally, ISOs of Insider Preview Builds would not be provided if we're not supposed to use them for clean installs. That means that Microsoft has to be very sure that a clean install will work as well as an update/upgrade. And if we're not supposed to test clean installations, then who is?
very unimpressed with this release so far...
So far, the only really bad thing I've found is that my first boot fails and I have to hard shutdown and then boot again. So far, this works. Anyone else having this happen?