New
#250
Even better.. I captured the ESD during the upgrade process and now I have the ISO.
Great build!!
I was messing around with one of my PCs last night and tried to activate the 10576 build using the old *3V66T product key. This PC was newly built after Windows 10 went RTM so it's not registered for Tech Preview. But to my surprise, it got activated and when I upgraded it to 10586, it became fully licensed with no time bomb.
I had one laptop with build 10547 with 10565 upgrade sitting there almost a month, I had my reasons to stay in 10547. As long as you don't restart from Update page in Settings app when it tells a restart has been scheduled, you are OK. Restarting from the Start Menu does not launch the upgrade.
When I no longer needed 10547 I clean installed 10586 this week, never using the 10565 upgrade which waited there all this time.
I don't think you understood what I was pointing out when mentioning that you need to first see the 10 build activated in order to see the entire Personalization section unlocked. From that point you can then go in and tweak the appearances of things
As for those other two screens one was right click on the taskbar while the other was on the Start button bringing two different types of screens one before the Start and taskbar properties while the other is the jump list for thing like the command prompt, Control Panel, run command line, etc.
Didn't take more then so many hours when first setting the 10240 on a VM to see the 10565 arrive and then in a few days see the 10576 go on. Finally a pair of VMs where this was all happening now see collectively both Home Pro editions of the 10586 Threshold 2 the one without the watermark activated. The VMs are on two separate machines however.
What was interesting was seeing the first VM upgrade from 10240 to the 10565 not by the updates but when brought to an Insider page right as the 10565 was also in the updates to find a download link and quickly saved that iso to a folder on the VHD! Later that was downloaded and saved to the host main build and following the need to restore a system when the av program suddenly pooched for no reason I replaced the first VM with a new 10565 by mounting the iso after the new VHD was created.
Following the upgrade with that one to the next 10576 build and then onto the 10586 I tried a key and the VM was activated on the spot! On the second 7 Pro machine there besides finally getting it connect by Cat 6 not the usb WiFi to router adapter the Pro VM had an uuuber day and didn't play as friendly with a C10004C1003 error and ended up seeing a 10 Home x64 10586 activation instead having an old 7 HP key not in use. In each case however there were no bugs with any upgrade and all files and settings were as if no upgrade even took place since the differences are not so much registry related but modular core related as how each newer build goes on like a service pack rather seeing a full upgrade where everything gets bounced around a bit.