New
#31
So folks,
Created a new USB Win10 install stick following the recommendation:
Option One, here... Create Bootable USB Flash Drive to Install Windows 10
BOOT>CSM>Launch CSM: Enabled
BOOT>CSM>Launch CSM>Boot Device Control: UEFI and Legacy OPROM
BOOT>CSM>Launch CSM>Boot from Network Devices: Ignore
BOOT>CSM>Launch CSM>Boot from Storage Devices: UEFI only
BOOT>CSM>Launch CSM>Boot from PCI-E/PCI ED: UEFI only
BOOT>Secure Boot>OS Type: Windows UEFI mode
BOOT>Secure Boot>Key Management: Install Default SBK
BOOT>Secure Boot>Key Management: Clear SBKs
Boot priority:
Opt-1: UEFI USB drive
Opt-2: M2 drive
Opt-3: USB drive
Same result, Win installer is not able to see my M2 drive.
Via command prompt and diskpart command, I only see my USB drive as Disk 1 (14Gb).
Just so you know - none of the above is going to have any affect at all of Windows detecting the M.2 drive during setup. You can mess with UEFI v. CSM booting all you want to. Once you are booted into Windows setup and at the screen shown in post #15 you are chasing rabbits down the wrong rabbit hole.
I would suggest replacing the SSD.
Thanks for the advice but this is not my problem. My M2 drive is always seen by the bios/motherboard as storage device.
Depending on bios boot settings (CSM enable), I can even try to boot on it but get the message "Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key"
- - - Updated - - -
I've ordered a SATA SSD and will install Win10 on it. Then I will try to fix this NVME issue.
I will let you know the end of the story.
Thanks to all for your help.
When I have problems finding UFEI boot from the USB created by Win Media Creation Tool I always go into bios reset the bios to optimized settings then reboot to bios, then power off, then power up & press F12 to bring up the "boot from only" menu & UEFI or legacy is then displayed there for the USB W10 Installer drive.
Sometimes with M.2 or SSD if you have used it before in another Win 10 install in UEFI mode & then deleted the partition before this install Windows can leave a small partition with the UEFI information on it which blocks another installation from being performed..
& thats how I cure this problem every time for me but may not work for others.
Still going down the same rabbit hole. The problem is not whether or not the SSD is bootable. The problem is that it does not show up in the list of drives to install to in Windows setup.
I had two brand new ADATA SSDs that were bad. They would be only intermittently detected by both BIOS and Windows. Sometimes yes, sometimes not. I finally went with Samsung. While it is much less likely that the Samsung EVO SSD itself is bad, it is still a possibility. Have you tried physically removing it and re-installing it to make sure it is seated correctly?