Monday, March 6, 2017

Install Windows 10 from USB to new drive fails boot

I have a laptop that came with a non-SSD drive that I have Windows 10 on. I am trying to create an installation on an SSD drive for this same machine (to eventually use as the primary boot drive--I wanted to clone the existing installation, but every tool I tried either a) didn't work with Windows 10 or b) didn't want to clone a drive with a 512B sector size to one with a 4KB sector size. I want this all to work with secure boot and UEFI, to take advantage of those features.


I have followed the directions here: http://www.tenforums.com/tutorials/1950-windows-10-clean-install.html. I have a flash drive with installation media that I am able to boot to (I have tried with both Rufus and the official Windows installation media creator, with identical results), and I can perform up through step 13 on that tutorial. I have retried this several times and been very painstaking about following instructions, so that is not the problem. On the restart after step 13, I am unable to boot into the new installation. Depending on the exact configuration of drives in my computer at the time (I've done it with many different combinations to rule things out), the UEFI boot menu is either able to see the installation and fails with the error below, or simply does not see it as bootable media and shoves me into BIOS (or boots from the flash drive, if that is still inserted).


This is the error shown when attempting to boot from this volume from within UEFI when that option is available gives this (paraphrased, but the paraphrasing is accurate):


Operating system couldn't be loaded because a required file is missing or contains errors.
The file Windows\System32\winload.efi is missing.
(error code 0xc0000225)

I can't understand why my UEFI-bootable installation media cannot create a Windows installation that is also bootable, and want to know what I'm missing.

No comments:

Post a Comment

hard drive - Leaving bad sectors in unformatted partition?

Laptop was acting really weird, and copy and seek times were really slow, so I decided to scan the hard drive surface. I have a couple hundr...