This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
So I'm having a bit of a weird issue. I've installed windows 10 on a few computers before and have never run into this until now. I recently bought an ssd to boot my OS from, but running the install media usb doesn't seem to work right. I only used windows 10's install media tool. I should also mention I only have a keyboard, mouse, monitor and the install usb plugged in.
I created the usb (twice now), then shut my pc off, removed the existing hdd, then plugged in the ssd and the usb with the install tool on it. I boot into setup, make sure the drive is all unallocated space, and then hit new. I let it create the necessary partitions and then click next. I've also tried just clicking next with a totally blank ssd.
The setup tool runs normally, prompts a restart which is when I remove the install usb, if I don't remove the usb then it loops back to the installer again. When I remove the usb and then restart though, my pc prompts me to insert boot media into the drive and press any key. It doesnt seem to actually install the necessary files to download and install windows 10. No matter what I do, after the install media tool finishes and causes a restart I cannot continue with the installation.
Any help would be greatly appreciated. I know it isn't a problem with another component because plugging in the original hard drive works fine. I've also plugged both drives in and scanned for errors on the ssd to no avail. I checked and there are files being installed on the ssd. It seems to work normally otherwise so I dont think it's a bad drive either.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 90%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGC%3C/text%3E%3C/svg%3E)
I explained that a UEFI install must be formatted GPT, and that the best way to do this is boot the media as a UEFI device, delete all partitions or wipe the drive, then let it format the partitions for UEFI automatically by clicking Next.
Drivers would only be an issue if the drive didn't show up during install.
Hi,
After wiping the drive and formatting it as MBR... Did you use the specific UEFI or Legacy flash drive ?
Very Important...
There are no drivers needed for what you are attempting to do... Anything needed would be included in the Windows 10 installation media... Whether HDD or SSD...
The only reason my one installation required drivers was that there were no drivers available for that type of device included with windows...
There is no way it could be configured to not be a boot device because of some previous use...
Unless the HDD was plugged in at the same time maybe...
What you see in the way of drive letters within windows has nothing to do with a installation... Especially after the drive was wiped...
In reality, if you were to have a problem installing windows to the SSD, that should happen with UEFI, not the Legacy... You might double check that your Bios does in fact switch to Legacy when attempting a Legacy installation...
I'm thinking that there is a problem with the SSD's internal controller that it is not being recognized properly...
Just a thought... You might try plugging it in to a different SATA port on the motherboard just to see if it makes a difference...
Installing as uefi brings me back to the original error. Wiping the drive and formatting it as mbr gives me an error saying it cannot install because it has a MBR table. Tried both iso with rufus and windows install media tool. It does not appear to make a difference which I use, uefi ends up at the black screen and legacy mode gives the errors I said before. I'm still stuck on how I can run things through the other installation on my hdd, but windows wont boot off the ssd.
Would drivers have something to do with it? I assume before it was originally usable from the hdd it had to download drivers. Should I try uninstalling them or something? I did already wipe the drive so i may need to specifically uninstall the drivers or something. It still is listed as drive D btw. When I remove the hdd this does not change. Is it possible it was automatically configured to not be a boot drive when it was used as a 2nd drive before? This could explain why the ssd has data and is usable but cant boot windows. If it is set to specifically not boot then it might do something like this.
It does really seem like the uefi usb installer is working. It just cannot boot this ssd after it finishes for some reason. If it is made to not be bootable in a way cleaning wouldnt erase then no matter how many times I repeat the steps it would never boot the ssd. At least until it was set to be bootable. Is this an option within windows somewhere?
Hi,
This MIGHT be because the SSD is currently GPT, and the legacy method is not as flexible as the GPT method for a Custom Install...
So I would suggest either try using UEFI Media and install as UEFI, or boot the machine with the HDD and delete everything on the SSD in Disk Management and reinitialize it as MBR..
BTW... I had to post this differently... I was being blocked somehow...
That happens for legacy, on a drive with an iso by rufus. The same thing happens when running legacy using the media creation tool. It could possibly be something wrong with the ssds controller. It is definitely enabled.
I have tried both setting the usb to boot first and setting the drive to fist and overriding to boot the USB with f8. Yesterday I had set the usb to priority 1 but all recent attempts have had the ssd as #1 and am selecting it.
