Woke Up and Found Win10 Upgrade already Downloaded

Night Hawk said:

I suspected that something was "MISSING" when continuing to see the fails repeat themselves here. But hearing about that file I will be looking through the 10 media being iso images as well as the dvd and flash drives to see if that file comes up or is delinquent? Then that should be a confirmation of a type to verify your finding there.

After a full search plus looking over the BT and WS resources folders on both OS drives I found bootres.dll, bootmgr, and a couple of other files with the boot word in the file names but no sign of the boot.win file anywhere! Something smell a little MS Fishy at all? Me thinkest some of this is by MS intent to trip you up especially if you opted to reserve a copy and all other download attempts will fail due to that item not being present for the 10 installer to find. I did find a repeat error I tried looking up but only found a slight variation in MS Answers posts.

Error #0xC1900101-0x20017 for me while others saw 0xC1900101-0x40017 with the message saying: "The installation failed in the Safe_OS phase with an error during the boot operation" which is when getting just past the setup's Win logo startup screen you end up witn... nothing but a blank screen where you are then forced to hit the reset for a hard boot into the existing version of Windows you have on. Nothing there was changed since the upgrade simply couldn't proceed with nuking anything.

If you created an ISO or a bootable thumb drive that file should be there. It's only missing if your upgrading via the GWX App. If you look at the error message in windows update for the failed updates, it will state boot.wim missing or could not be found, something like that, anyway. I'm probably soon going to stop posting and just monitor what's going on. I've had a few, . I suffer from chronic pain so sometimes I have a bit of rum and coke instead of Tylenol 3's and mussel relaxers. Works for me, what can I say. :)

Wynona said:

Yeah, I downloaded the 64 bit one. Hate to sound dumb here, but does the created flash drive boot the PC when you want to do the clean install?

It should, if you used the create install media option. I just downloaded the ISO files. It's quicker for me to create bootable thumb drives manually with diskpart from the ISO, than to run the MCT 4 times. I customize each thumb drive for each PC. I add custom OEM info etc, so I have a custom thumb drive for each PC I own. With Windows 8.1 I'd add a PID.txt file with the product code for that PC. Saves me having to look it up and type it in during setup. I guess now I don't have to do that?

alphanumeric said:

If you created an ISO or a bootable thumb drive that file should be there. It's only missing if your upgrading via the GWX App. If you look at the error message in windows update for the failed updates, it will state boot.wim missing or could not be found, something like that, anyway. I'm probably soon going to stop posting and just monitor what's going on. I've had a few, . I suffer from chronic pain so sometimes I have a bit of rum and coke instead of Tylenol 3's and mussel relaxers. Works for me, what can I say. :)

The only search I ran was from the text box in WE as well as a second run off of the 7 Start menu for that file. But as I had to redo the seond drive again following the clone with a clean install all traces would be gone at time from the first few attempts made. With all but one HD plugged in and hardly anything on the fresh 7 install I'm running a few more update checks before the next online upgrade attempt which may still yield some better results not having hardly any processes running.

Also I now know how the BT ended up the storage drive mainly due to how the mbr was placed! Just like the caution for unplugging non OS drives for 10 was noted in the tutorial the same apparently happened with 7 which I found a little rare having previously installed the 64bit beta and RC as well on one drive and an isolated install for the 32bit beta and later RC before without anything ending up on a 3rd drive used for storage on an older build. But that was seen to quickly running the Startup repair tool and seeing the mbr added to the second drive when it was found unbootable once the host was unplugged once again for the next attempt I will be working on shortly! I'm not too worried however since if everything does go onto the fresh 7 install I can clean up the host drive and use that for 10 instead! :)

Wynona said:

Yeah, I downloaded the 64 bit one. Hate to sound dumb here, but does the created flash drive boot the PC when you want to do the clean install?

The Media Creation Tool does make the flash drive bootable since that is strictly intended for booting live from the flash drive when performing a clean install unless you manually start up the setup.exe file located at the root of the drive itself to perform an upgrade install while booted in Windows.

Since MS has geared 10 to be installed like you would any other large updated like a service pack would have been seen with a previous version the best move would seem to be upgrading when using the MC tool whlie still having the flash drive or dvd ready can bail you out if the online upgrade runs into something? and some files get lost or corrupted.

windunce said:

Here are my two folders

Those look identical to what I found here following a few attempts at the upgrade and even to try out a clean install intended to be a quick temp install and not getting anywhere. I thought I had posted a screen earlier where you could see the contents of both folders showing the setup files were found in the WS folder while language packs and other 3rd party stuffed was located in the BT once the upgrade attempts create the WS later.

If you compare the last TP build with the RTM you will see 10240 on both. Instead you need to look at the second group of four digits to see where the change was made indicating which one is what. I thought it was something like 7632 or 3672 for the RTM? Only got a fast glimpse while checking on something else at the Insider Program last week.