I have always done my Preview builds installation directly on a production system. I dedicate a computer to test them and intentionally prevent myself from running them in Virtual Machines.
VM's never give a good reading on how good the os runs it's a poor excuse for a testing environment and shows way more bugs because of poorly updated drivers and than new users get confused and thinks there is a issue when none are present real hardware is best
I simply set up a dual boot envionment on my production machine to check out the previews: The main OS is Windows 8.1, installed on disk. For Windows 10, I created a VHD, applied the WIM, and simply boot it from that VHD. This way, I'm able to run it on bare metal next to my stable OS, and if something goes wrong, I can simply delete or replace the VHD.
I am unable to access my Sysnology NAS shared folder. Anyone with the same issue? Web access works normally!
Still cannot change the titlebar color in 10125.. At this point I have no expectation Microsoft will restore this ability. It will require a hack to do and/or use of a third party .msstyles file. Time to break out OllyDbg and IDA Pro and find what to modify.
Some beta versions of Windows 8 also had white titlebar colors. But since it was back in 2012 and everyone was used to the skeuomorphism design of Windows 7 and earlier, it escalated to a big s**tstorm. Now in Windows 10 it's totally normal to have white titlebar colors
EDIT 10125 Language Packs : pastebin.com/WLsSxMMB Arabic, Azerbaijan, Africa ZA, Albania, Bangla india, Bangla Bangladesh, Bulgaria, Baskf, Bosnia and Herzegovina LATIN, Czech, China Simplified, France, German, Great Britain, Espana-ES, ITALY-IT, NETHERLANDS, Japan, Hungary, Portugal-BR, Korean, İceland, Turkish, Greek