pbatard
commented
7 years ago Okay. First of all, this looks more like a Windows installer issue than a Rufus issue. If Windows was able to start the installation process, then Rufus' job was properly done (it booted the installer), and unless you got errors during the file copy process (which you didn't), the Windows installer had access to every single file it needs for Windows to be installed properly.
Which means that your best option is to tweak the installation parameters from the Windows installer. The first think you should try is make sure you:
- Have only the disk you want to install Windows on connected, with every other disk disconnected
- The disk you want to install Windows on has been cleaned (i.e. it is NOT partitioned).
If you do that, then Windows should be happy enough to create the partitions it needs, including the EFI System Partition (ESP) which is usually used to boot into the Windows system partition. Please be mindful that the Windows system partition does not need to contain a bootmgfw.efi as this is usually meant to be copied onto the ESP (which is not accessible from Windows).
The other thing I would advise you to try, since your install.wim is less than 4GB, is to use FAT32 instead of NTFS when creating the drive in Rufus, as I have gotten reports that lead me to think that, in some circumstances, Windows does not seem to like to see 2 NTFS partitions on different devices containing Windows (the Windows installer is a mini Windows in itself).
BlackBoxCAD
lock[bot]
Checklist
Logbutton in Rufus and copy/pasted the log into the line that says<FULL LOG>below.Rufus version: x.y.z- I have NOT removed any part of it.Additionally (if applicable):
#button (at the bottom of the Rufus interface), to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.Issue description
First time trying UEFI, as a result of buying a Samsung 960 EVO PCIe x4 drive (and Startech adapter). Samsung's firmware update docs direct one to use Netbootin, which failed.
Searched the topic extensively and found threads that recommended your product. Download your product, tried using Rufus on my VLSC/MSDN Win10x64 Enterprise ISO, which was used to install OS on several x64 workstations under Legacy mode.
Used Rufus in each partition scheme, and File system, before finding your recommendation for GPT for UEFI + NTFS here: https://github.com/pbatard/rufus/issues/506 - didn't work.
More specifically, I reset BIOS to UEFI and disable SATA/RAID (I do not have Secure Boot option), restart, boot to UEFI USB (thanks to Rufus!), Windows setup runs without issue in +/- 4 mins, then at first prompt to restart, I remove the USB before Dell BIOS splash, then either left alone, or manually specifying 'Windows boot manager',the result is always 'No bootable device' message.
I've read the short answer. I would still greatly appreciate your help.
Rufus creates the USB, the USB boots, Windows setup runs, but somehow the Samsung 960 EVO PCIe SSD does not contain the necessary bootmgfw.efi (or whatever the real file is called to allow it to properly boot under UEFI)? THAT is what's irking me, as it makes no sense (to me).
Finally, thought it was time to contact you, and made sure to include the Log. However, I did not attempt those final steps outlined above, as this is the first I am seeing them.
My existing Windows 10 OS (Legacy) recognized the Samsung 960 EVO on first boot. It works. It's fast. Just does not seem to boot.
Dell Precision T3600, Hex-Core Xeon E5, 32 GB RAM, 3 GB Nvidia Quadro K4000, Samsung 960 EVO
I appreciate your time, and consideration.
Cheers
Log