Updated twice till now: Test Machine (old, AMD 2 Core, 4 GB RAM, MB DFI LanParty): went well within 45min using online update Laptop Acer Aspire 4752G (8GB RAM, 2 Core Intel Core i5-2450M) Problems. On that laptop the Update is now finished after 8h!! It had to restart many times, sometimes ending up in just a black screen with no other activities! It looked like that there were some Hardware problems and I suspect the Intel Hardware! The software was also a problem, with about 10 restart's with installing something for Microsoft C++ 2012, within the updating. After the Update was finish, I went into Settings -->Update and again the C++ update was going on for another 6 times! That was the first time I was getting any problems with an Update on Windows 10 since the first Beta!! That said, for my Main Desktop at Home, I'll wait with the Update a few day and like to see what will happen to the 2 Machine I updated today. I'll also update one of my Office Computers tomorrow and see, there any Problems.
so after a whole night of work and gaming on the new build it's pretty dam fast and stable great work MS
dl and update in 45 minutes, no hiccups but regedit search not repaired, services in admin work again
I find a bug looping Update Microsoft C++ 2012 Update 4 Still works some applications I ran few test.
My windows update does not offer me the updating to 14257 (I am using the 14251). I'm on the fast option, registered in the insider, etc... but does not appear to update. Any idea? Can I upgrade my build to the newest using an iso ?
Yes, you can download the ESD and decrypt then convert to ISO image and either run setup.exe from within Windows or do a clean install.
Yes, if you can find an ISO or do the esd build yourself...you could use the iso image just like a normal upgrade. This is Insider preview software, beta software, remember, so nothing is guaranteed. See my post in the thread for an example of the unexpected...
Build 14257...This is the second consecutive build that will not install on my machine...14251 failed, too, and for the same reasons...I haven't had this much trouble with installing Windows builds since I signed into the program in 10/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...frustrating. My system: 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 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 Microsoft acknowledged it 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 don't absolutely know that this is the problem, of course, but it seems the most obvious candidate. If anyone has any suggestions I'm all ears...
I have the same bug, WU shows as installed but goes in a continuous loop. It can be fixed by going in to apps & features, select modify then repair. I did this for both x86 and x64 installs.