Windows 10: After 2 days, finally upgraded to windows 10 pro!

I was finally able to upgrade from Windows 8.1 Pro to Windows 10 Pro after loading the default bios settings. The fail codes I had included, 80240020, 0x80246017, C1900101, and 80246010. I have a homebuilt Intel 980x with an EVGA X58 LE motherboard with 16GB of RAM. Once I loaded the default BIOS settings, the Windows upgrade proceeded to full installation. After ensuring everything was setup correctly, I rebooted and reloaded my saved bios profile. Windows 10 would not boot after restoring my saved bios. However, once I turned off the Virtualization Technology setting in the bios, Windows 10 is now up and running again. I hope this helps some of you. *Smile

:)

 

After 2+ days of troubleshooting, was finally able to successfully upgrade to Windows 10 Creator Version 1709

You got it, Frank. Plus I may have found a good complement to your fine detective work. Please bear with me here.

To begin, a nice part of using the MCT/ISO Windows Setup versus the internal
Windows Updater is you see Installing Windows full status with specific progress details rather than mere overall completion. Following are the
Setup steps and status process.

• Copying Windows files
• Getting files ready for installation
• Installing features
• Installing updates (1%)
• Finishing up

When my clean install reached "Installing updates" it rushed by so quickly you could have, almost literally, "missed it if you blinked." From the beginning of your post I worried what the various installation iterations would do when no Internet connection
was found. I should have realized neither the Updater or the executables have the capacity for a, "Hey, turn on the
#$@&%*! Wi-Fi!" pop-up. Confirmation came when I was surprised by a short update not long after
1709 completed.

So, looking back at the status steps "Installing updates" likely ends at the Updater's 80% mark. And that's our invariable doomsday freeze. Conversely, "Installing updates" likely begins at the
Updater's 75%, another universal freeze point. I believe as the Updater and the executables when not in clean install seek Internet access for "Installing updates" the
Ralink goes from unstable to fatal. Perhaps updates installation is where your disabled LAN card reactivated.
Microsoft's suggestion to turn off Wi-Fi becomes pointless when a script activates a problem LAN or WAN.

Or perhaps your LAN was reactivated during "Getting files ready for installation." That just so happens to
line up with our universal freeze at 30%. However, I've no conjecture for why my own disabled card smoothly passed 30% with first the Updater and subsequently an MCT/ISO clean install. As I've noted there were no freezes --
none -- for the ISO.

So with our dilemma likely resolved, I notice many reported failures -- perhaps a majority -- occur at
identical or similar progress points. That hints at additional LAN or WAN culprits. Plus
I now firmly believe those unable to install Windows 10 despite trying every
Microsoft suggestion are overwhelmingly card/driver cases. And while the company does emphasize updating drivers, in my case the
Ralink has the latest. Which leaves the potential benefits from aligning failure points to
Windows Setup's five steps. Though I concede the steps are quite cryptic. "Installing updates" may be the lone exception.

 

After 2+ days of troubleshooting, was finally able to successfully upgrade to Windows 10 Creator Version 1709



Thanks for the detailed description, Bill.

Glad you got things running.

Best!

Frank