I received my framework today and I wanted to install Windows 10 ver. 21H2. However, the nvme is not detected by the installer. I can see it in the BIOS and it works fine in Linux.
A couple of times I read online that I should use these drivers during installation:
Intel® Rapid Storage Technology Driver Installation Software with Intel® Optane™ Memory (10th and 11th Gen Platforms)?
but they don’t contain any drivers that are supported by the framework (according to the Windows10 installer)
Samsung does not provide any driver for the 980 pro, so I’m kinda stuck right now.
Any help is appreciated!
Update I can see the NVMe disk in the “diskpart” utility from the Windows installer. All looks good there. I don’t get it…
I have the 980 Pro as well and just installed Windows 11 (so not 10) on it without problems. Not sure if that’s helpful, but maybe one additional datapoint.
@robert_b Did you use the Windows Media Creation tool to create the Windows installer? The reason I ask is that we’ve seen instances of the same thing happening when other methods such as Rufus or Ventoy are used to create Windows installer. You could also try using a different flash drive to see if that makes a difference. I’ve ran into similar situations before on more than one occasion to the point of almost pulling out my hair only to find out that switching to a different flash drive would fix the issue.
@Panda_bak I used the Windows ISO (I can’t use the Media Creation tool as I don´t have access to a Windows machine).
For now gave up on installing Windows. I’m using Linux and it works just fine. The only reason I wanted to install Windows is that I wanted to try if my eGPU case works better if I install Windows on the internal NVMe instead of on the SSD in the eGPU case.
I came to the conclusion, that my eGPU issues have nothing to do with where my Windows is installed. But that’s a different story
I can’t believe how picky windows still is when it comes to HW detection. I can build a ~30M Linux image that can be booted on anything from a small embedded device to a mainframe computer. But the official Windows ISO won’t detect a common NVMe in a laptop…
Linux is designed to be booted in weird configs and on a USB, where windows isn’t.
It might be worth having ethernet plugged in when you try next time.
That said. As long as the NVME drivers are installed in windows. It’s worth trying the Samsung data migration tool, if you’re not fussed about it not being a clean install.
For now, I’ll stick to Linux. But thanks for the hint with ethernet, you think the installer would automatically retrieve the correct drivers?
Windows 10 ISO on a USB stick is officially supported by Microsoft. I wouldn’t call it a “weird config”.
Except that writing it directly is, AFAICT, not supported (at least not explicitly documented, official documentation probably recommends some MS tool that may or may not do extra operations). I also tried a Win11 ISO directly to USB with
dd and it did not want to boot.
I ended up using WoeUSB to create the USB disk (because it has a PPA available so was the least painful way, without having to install too much untrusted/unpackaged stuff) which did work.
Hm, the Windows 10 ISO website is explicitly for non-Windows OSs.
“You’ve been routed to this page because the operating system you’re using won’t support the Windows 10 media creation tool and we want to make sure you can download Windows 10”
“You can use this page to download a disc image (ISO file) that can be used to install or reinstall Windows 10. The image can also be used to create installation media using a USB flash drive or DVD.”
I’d be surprised if MS one the one hand has a dedicated ISO download for ppl not using Windows (yet) but on the other hand requires you to use a MS tool on windows to flash the ISO.
Anyhow, maybe the ISO in general IS different from a stick that MS’s Media Creation tool creates. What is weird, is the fact that the “diskpart” tool from the install media detects the NVMe just fine.
I would expect the Windows creation tool to be a quick and easy way of downloading the ISO and creating a bootable ISO.
Windows wont fetch drivers till late in the install, once it asks for wifi. Before that it’s just using generic or older supplied drivers.
If you can see it in the diskpart utility, then it got detected but filtered out as a valid installation target in the installer for some reason. Maybe because of insufficient free disk space. Delete any partitions with the diskpart utility and try again.