New
#90
I tried three times to install 14251 from 11099, but failed three times. Three times the install aborted after the "copy files" portion was completed, upon the automatic reboot, with an INACCESSIBLE_BOOT_DEVICE error, after which the system restored my previous build 11099. I can only think that 14251 is trying to boot itself to finish the install process with the IDE driver in place instead of the AHCI driver I must use with my EVO 850 SSD. I tried several things before giving up, including turning off secure boot, legacy booting, and using the UEFI bios's Bootmenu to tell the install program which drive to boot from in case it was getting confused there. This is the second consecutive build I've not been able to use--11102 installed without a problem, but the graphics stack was buggy--so I reverted from there as well. 11099 is the last stable build I'm able to use.
Lucky for all of you who reverted back successfully. Mine forced the revert and it screwed it up. No start menu, no Settings flyout, no Edge (other apps as well), my profile screwed for insider loads (error D0000001) etc, etc.
First time in 15 months I've had it screwed. Thought it was because of having Malwarebytes Ransomeware installed but Wynona had a successful update with Ransomeware installed so that is a mystery.
But the Network Discovery seems to have reverted to the stuffed 1511 setup. Looks like they just had an experiment with the 11099 and 11102 versions. This will be very disappointing to very many people as the small glimmer of light has seemingly been snuffed out. Back to the waiting game.
Damn thing is stuck at 42%, I only remembered it when I looked at this forum, I will try to see if getting rid of temporary files will work.
Pale Moon crashes when trying to do a copy and paste using the mouse in this build.
I ended up having to go back to 10099, as I was still getting lockups and crashes in games and when doing stuff like launching Chrome on the new build.