The upgrade process (i.e., from one Windows 10 build to another) is absolutely, completely garbage. It causes numerous issues, including not being able to update images. You have to recreate your images every 3 to 6 months because Microsoft treats each build as a completely new operating system. This is a horrible way to do updates.
We need to go back to Service Packs. Service Packs were just very large updates; they didn't do an in-place upgrade of Windows. That's why the whole damn system wasn't replaced with Service Packs and why Service Packs were generally more successful. And it's also why you could upgrade your images from one Service Pack to another; you didn't need to recreate your images from scratch when a Service Pack was released.
I can tell you that we won't be deploying Windows 10 where I work until this is resolved.
Right now and for the next 24 months, we're at a crossroads. We know that Windows 7 support ends at the beginning of 2020. So right now, we are making decisions on what comes next.
What this means is that we have to make some decision soon just because Windows 7 maintenance is ending. In the next 24 months, we are going to be deciding on whether to stick with Windows or go with something else. If we stick with Windows, we have to deal with Windows 10 and its numerous issues, like new builds constantly being released.
What I'm hearing more and more is that many enterprises (mine included) are going to try doing one of two things: (a) moving the Windows-specific software to Windows Server and running it as an App-V instance and buying the appropriate CALs or (b) finding a non-Windows replacement altogether. In either case, this would allow enterprises to move to something more akin to Chromebooks and use an RDP client for the few Windows programs still required.
In any case, because of the debacle that was Windows 8 and Windows 10 having even more issues, enterprises are trying to reduce their Windows footprint. Will this suck for enterprise? At first, it will. But at least once it's done, it's done. We no longer have to deal with these issues. We'll have new issues to deal with, but we know we can't deal with Windows 10 unless something changes.
I missed trying 8.1 out in any form when having been side tracked a bit for some other reasons and then checked out the TP build that was available in January to put that on a VM before going through that other situation all over again! This time however noting nothing had changed as far as hardwares! 10 went on as smooth as silk BUT couldn;t added as a new boot option in the 7 BCD store from being three versions newer! 7 was made a 10 BCD there instead.
The initial upgrade installs on the main build but not the second build accessed remotely as well as the laptop upgraded both saw what best described as a travesty! Both first upgrades were trash! On the main build during the first week the second upgrade to repair the first went unactivated due to bogged down servers. The following weekend then ended like right this time of night on a sunday for the first clean install that activated within a day's time on it's own! Now the activation is seen before you even see the desktop fully loaded automatically if 10 or a previous version being upgraded over saw activation there.
Bot the Home and Pro 10586 editions saw activation on VMs but with the Home VM on the second machine there. 7 product keys were used while the Threshold 2 wouldn't accept any either from already in use or requiring a 10 key instead of any previous version's The VM however is how to check up on things fast without the need to change any physical 10 install since you can run it on any edition or version of Windows from 7 up! I doubt you could even get 10 to run on the Virtual PC 2007 option used on Vista even for 8 or 8.1.
This is why delivering updates simply amounting to Upgrades! by way of Windows updates can be flawed since a clean install is always the better results seen guaranty over bugged up upgrades where you end up needing to wipe everything and start over fresh again. At least with the Insider Preview no key was required as well as the TH2 now seen if 10 had already been activated due to the DE or Digital entitlement change in how Windows is activated.