During more than one build I had insoluble problems with *what I think* involved my AHCI driver and my Samsung EVO 850 256GB Win10 boot drive (which requires AHCI and won't function under an IDE driver) . I suspect that at least two builds simply wouldn't install at all because of AHCI problems--but I don't know that because while Microsoft fixed the bugs (I had reported them, too) they didn't write up the bug or identify it as fixed even after it obviously was (since I could install later builds.)2. Had to reinstall Intel RST on the VP 11 as well, because AHCI driver got rolled back a couple of generations.
I am still, however, having problems with with the latest Win10 builds (14316 & 14328) with my UEFI bios "Windows 8" settings particular to secure-boot and fast-boot. Often lately, the only way I can install a build is to completely disable these UEFI functions. After installation I can reenable the secure/fast-boot functions--but then the Samsung Magician EVO software can no longer see the AHCI or Sata3 bus...;)...so the Magician software thinks my S3/AHCI bus is simply disabled--even though it is working else the drive could not function and Win10 would not boot...;)
Looked in there myself more than once and been amazed at what's there...;) Gives the "last known good configuration" setting a new meaning...;)5. Running RAPR (DriverStore Explorer) on both machines, found numerous duplicate/outdated drivers in that store after the upgrade install finished. All are now cleaned out (can provide details if anybody's interested).
See my earlier post in the thread...I reverted to 14316...;) Sometimes I forget the sublime joys of beta testing.So far, though, everything seems to be running OK and I'm having fun exploring all the new interface stuff. Especially like Windows Update and the Action Center changes.
A separate speed control option! Still waiting for the new VM to play catch up while the new recording is in progress. Hopefully it will be a "take you through each step" clip.
I have an object not found error when I enter my PIN to logon, password still works. The Settings/Accounts/Connexion Options page won't load to try to fix it. I had this on the last build and now on a clean install of this one.
And as expected, still no
f*ckingoption, to change/increase the (modern GUI/Apps) system fonts.
Whats wrong with these guys?
And yes, I'm aware of the scaling options...
Maybe a 4-5hr wait again for the new VM as seen previously when first setting each of the others. The recording will remain on pause until it shows up.
So far still haven't gotten to using any pin or picture to log in with. The VMs are set to login automatically as well as the main since I might have to bounce back and forthe between the 10 and 7 dual boot at times. That hasn't been seen much lately however for some reason. Seem to be spending too much time in 10!
Update on the recording process. Despite the new VM already having been activated and still not receiving the latest build while all other updates have arrived the "Clean install from "$Windows~BT" folder backed up to a second volume created following an expansion of the vhd is now at 90%! The upgrade over failed finding it wasn't a suitable upgrade path for the newer Pro Insider build to upgrade over the Threshold 2 Pro? Just installed updates and now almost finishing up before restart and finishing up recording.
Restarted and now will be waiting for fresh clean install to finish before next update on clean install from BT! Ended up using a 7 key after the first install took the 10 key. Will wait to see if watermark for 14328 build appears since TH2 lacks any!
And the news is? The initial TH2 clean install on new VM accepted the 10 OEM for System Builders key while the Insider build wouldn't for the likely reasons where a 7 key was used after all initial attempts to first upgrade and after several attempts also finding that both despite being the 64bit 10 TH2 update to latest 14328 build wasn't a correct upgrade path? Yet the TH2 anything will readily take on any newer insider build coming by way of the WU. When the build wasn't prompted it then came down to seeing a totally clean install of 14328 take place from a seond partition created when expanding the VHD and then seeing the entire $Windows~BT folder backed up there not only for the clean install that came out successful but as a recovery method.
This will next be tried on one of the desktops for the physical clean install to test this method of no media no mounted iso type but direct manual run of setup.exe file.
Last edited by Night Hawk; 24 Apr 2016 at 05:38. Reason: additional information added