Got it installed finally. Surprised how quickly this build arrived to me. Usually takes 2-3 days to arrive on my pc. Yeah!
Mine is almost there, waiting to find out if it tore up my VM Mint 17.3?
Just got it successfully, easier than the last build.
Build 14257...This is the second consecutive build that will not install on my machine...14251 wouldn't either...I haven't had this much trouble with installing Windows builds since I signed into the program in 10/1/2014--the pre-Win10 launch builds never gave me as much trouble. I reported this problem a week back and yet it isn't mentioned anywhere in the list of known or fixed bugs in 14257.
My system @ home:
MSI 970 Gaming motherboard, latest bios, M.4
AMD FX-8320e @ stock speeds
8GBs (2x4) running @ stock 2133MHz
Samsung SSD 850 EVO 250GB (boot)
2 x ST3500418AS HDs
2 x WDC WD10EZEX HDs
AMD R9 380 4GB GPU running the Crimson 16.1.1's
Last successful build 11099
When doing the internal "flight" install through WU, everything is fine through the "copy files" portion of the install--it hits 100% and the system auto reboots to continue the install...and then *WHAM* suddenly I have a blue screen failure INACCESSIBLE_BOOT_DEVICE...upon reboot, even if I hit F11 and manually select the boot drive--it does not matter, the system fails to boot and I am restored to my last fully working build 11099...! Thank goodness the "restoring previous build" function has worked perfectly each time.
My SSD drive is fine of course and the "previous build" I have is located there as well--so the error is clearly a build problem & bug and it would be NICE if it was acknowledged somewhere. The only time I have ever seen this error under normal operating conditions is when the system tries to boot with the IDE driver installed instead of the AHCI driver--the SSD *requires* the AHCI driver and will not function with the IDE driver. All the Win10 builds I've tested since 10/2014--all of them--successfully carried the AHCI settings over to the next build. (Except 14251 and 14257.)
I ran across one person in Feedback who had the same error I did, INACCESSIBLE_BOOT_DEVICE, and he reported that disconnecting all the drives in his system except for his c:\ boot drive got him past the error and allowed him to install. Didn't work for me.
Ideas, suggestions, anyone?
Updated to new latest build and all is well
anyone in California got this update? Please advise!
check for last 16 hours and it's not appears yet!