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.
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.
Hi,
I'm thinking that if there was a problem with your Bios, the HDD would not boot either...
Windows simply does not care whether you are installing to a HDD or SSD...
![](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)
What is "mounting it as UEFI?" The only way to create reliable bootable WIndows 10 media is to use the Media Creation Tool through to when it declares it is complete. Anything else is not going to work. Why would we start with new methods now after almost a billion users use only the Media Creation Tool?
Hi,
There may be a problem with the SSD's internal controller when it comes to being a boot device, but the question still is how did you create the flash drive that you booted with in the image you posted...
And is for UEFI or Legacy ?
Did you select it in boot options, or allow the machine to boot to it on it's own ?
I know this sounds trivial and nit-picky, but it is actually quite important...
