YOU want this build copy over a single file simple and if they want to fix it you can wait all they will do is either use the old installer or build a new one from the old one either way same fix just depends on lazyness
not home brew just using a older installer nothing changes on the install at least i can install the build now
Heh that error is the same error that happened with the original 11103 ISO, so guess MS haven't fixed the bug
I think they did it on purpose to prevent average users from clean installing. Try doing diskpart and apply image.
I edited my post. It came off a little too cocky. I wasn't really being serious. It very well could just be a bug with their setup program.
Actually, It's been a long while since I've had an upgrade go awry (knock on wood)... Speak of the Devil: My upgrade install from 11099 just failed! System restored the old build...inaccessible boot device...if it does it again I'll turn off UEFI and see if that makes a difference....I've turned off Defender...am ~50% done with the second download...will see how this goes...(Knock on wood did not help me!) Edit#2: No go. Install fails upon the reboot immediately after files have been copied 100%...reboots to INACCESSIBLE_BOOT_DEVICE...I suspect that the 14251 build is trying to install IDE drivers which will not work with my SSD system which requires AHCI drivers at boot. Tried it twice and turning off secure boot and even UEFI did not help--there's nothing wrong with my SSD drive and both failures restored me to 11099 without a problem, so that has to be the answer...Have given Microsoft the appropriate feedback... Edit#3: OK I am preparing for upgrade install attempt #3 of 11099 to 14251. So far I haven't been able to find any other reports of my specific error, and that leads me to believe something is awry on my end (as opposed to a Windows bug.) Something I just remembered was that a few days ago I had upgraded the bios of my mobo and had not cleared CMOS as is my usual procedure--I also noticed that my UEFI bios drive listings seemed jumbled & confused--so I reset CMOS, and reset my options and the drive list is much more accurate now. AM hoping this was at the root of my earlier problems. Edit#4 No go. Will be awaiting the next build. Even using the UEFI bios boot manager and selecting the drive it still errors out @ Inaccessible boot device--has to be trying to boot 14251 with the IDE drivers instead of the AHCI.
Using the legitimate install method worked perfectly. Did not give me the HI! sequence after first login.
What is all this talk of this being a bad Build ? I am typing this from 14251, had NO problems installing from Windows Update.
I'm waiting for the returns to come in on this before upgrading. This could be crippling. "Due to a recent memory management change, you may see periodic app crashes or other memory related app errors. The workaround is to reboot your PC."