a media driver your computer needs is missing.

Hopefully others who are installing Windows Server will find this thread and avoid wasting many hours too. If there's some common characteristic of the USB flash drives the H2 will never recognize as bootable, it would be nice if that were documented somehow (maybe it was just my one faulty drive, I don't know) or if it's a firmware issue, fix the firmware. I think Hardkernel/Odroid should create a short article on 'Installing Windows 10 and Windows Server on the H2' that is easy to find. Lesson: only use Rufus, don't use Etcher or dd. Only when I used Rufus to create the USB did it finally work, likely because of the partitioning, file system and driver added by Rufus to the USB.

I had used dd to write the ISO directly to the USB (works for Linux) and then tried used Etcher, figuring that it wouldn't make a difference. I don't know if the fault was with the USB drive or with the H2 firmware.īut then there was the problem of the 'media driver your computer needs is missing' dialog box during Windows Server installation. Lesson: it might not be any bits you can control on the USB, it could be the physical USB drive itself, so try another vendor's USB if the H2 doesn't recognize the first USB as a boot option (even when the USB was created with Rufus).

Then I tried another USB 3.0 flash drive from a different vendor (Kanguru) and the H2 recognized it immediately. Short story, 1) must use Rufus to create the bootable installation USB, and 2) if one USB drive doesn't work, try a different one from a different vendor.īefore coming here, I spent many hours using Rufus, Etcher, dd, cfdisk and gdisk to create a Windows Server installation USB from Microsoft's ISO, trying a variety of firmware configuration settings, trying a variety of partition types, file system types, sector sizes, zeroing out every sector first, etc., but the H2 wouldn't even see the USB drive as bootable (it was an ADATA S102 16GB USB 3.0). I had the same issue with installing Windows Server 2019 onto the NVME M.2 drive, namely, the dialog box that says 'A media driver your computer needs is missing', even though the necessary driver was on the USB driver.

A media driver your computer needs is missing.