Hello there
I just wondered, if it would be possible to modify the BIOS of ASUS H110M-R Mainboard to support PCIe m.2 NVME drives.
(There are Versions of H110M with M.2 slot and support, but i dont know if that is helpfully to solve the problem)
BIOS shows me them as a bootable device, but only if I boot manually from it, it wont show up regulary in BIOS boot settings as a drive.
Neither it would show up on Win 10 on the Device Manager, or on the Desktop Explorer
So i suggest in last instance the OS maybe must be installed on the PCIe m.2 NVME drive to support it as a regular drive,
something i haven’t tried yet and also is not quite an option for me, because i need that drive for some kind of hot swap
(it is supposed to work also in several other more modern PC Mainboards that are for shure compatible, so an OS would be quite a mess on that device, but to have that option would be good anyway)
Due to there is only one 3.0 PCIe x16, and two PCIe 2.0 x1 slots I have to deal with the PCIe 2.0 x1 configuration with a Riser device x1 to x16 to support my Samsung 980 pro.
I am aware it is not quite efficent to put a NVME 4.0 x4 device into a PCIe 2.0 x1 Slot, but for my particular case it must be.
Also i am thinking about to have this NVME drive swappable, so i can transport it to another place and just plug it into another PC that is newer and compatible to PCIe 3.0 / 4.0
As I can remember, the PC was configurated in 2019, so I suggest the “newest” Updates should be installed, anyway i downloaded the avaible Drivers from offical ASUS website and would install them to be shure.
PC Specs:
Built 2019, me receive and use it in 2022
Following Software i know of:
OS: Freshly installed:
Windows 10 Pro / Home
installed to two SSD 240GB GIGASTONE Sata3 Devices
(One has Win 10 Pro, other one has Win 10 Home)
> also preparing for optional using Línux (Operating System) Boot USB-stick after the NVME problem is solved, but as said this is more optional.
BIOS: (what i yet could find)
ASUS H110M-R (ACPI BIOS Revision 3601)
AMI BIOS (C) 2016 American Megatrends. Inc.
Following Hardware is used:
Motherboard:
ASUS H110M-R
(ACPI BIOS Revision 3601)
CPU:
i5-7600k
GPU:
GTX 1660 6GB (I suggest OC version)
(working on the PCIe 3.0 x16 slot)
PSU:
Xilent (Sticker was ripped off, so i dont know what version it is)
RAM:
BrainZap DDR4 - 2x 16GB 2400 Mhz (2x RX8 | CL17 | 1,2V | DIMM 288-Pol)
→ System normally set RAM to 2133 Mhz, but throughout BIOS it is automatically set to 2666 Mhz if i can trust the Informations showed in BIOS settings
Tower:
Midi Tower (NoName)
supports 2x USB2.0 | 1x USB3.0 | 2x HD Audio Jack | Power Button at Top Panel
Additional Devices on PCIe 2.0 x1 Slots:
1)
(StarTech.com PEX1TO162) PCIe x1 to x16 Low Profile Riser Adapter
(PCIE 4.0/3.0/2.0 compatible as far as I know)
+Mounted:
> Sabrent (RoHS) PCIe x16 M.2 NVME to PCIe x16 Device/Adapter
+Mounted to Sabrent Device:
→ Samsung Pro 980 1 TB
2)
Intel Wifi (RoSH) PCIe x1 802.11 AC 867M - Bluetooth 4.2
I would truly be happy if someone may could handle this Problem, also I really hope it is not too much work to do!
Thank you for reading my request, so hopefully you maybe have enough free time and knowledge to bring up a solution for me 
Edit by Fernando: Thread title shortened
Edit: Problem Solved, thanks very much and I apologize for posting, as it seems i just did not read enough. H
opefully i will get used in time to many other topics here, thanks to this great Forum!
A lot of confusion on your head… this motherboard already has support for NVMe drives (as storage device or as boot device).
No mod needed as its comes already with AMI NVMe DXE module as Standard on Intel 100 Series.
For booting, you have to perform a fresh new OS install in PURE UEFI environment. Do not recommend any system cloning.
This applies to a motherboard with M.2 slot on it or add-in card PCIe to M.2, for storage or boot.
Point #4 here: [HowTo] Get full NVMe support for all Systems with an AMI UEFI BIOS
EDIT: So nothing is needed as you intend to use the NVMe drive as storage, its fully recognised in modern OS, as legacy or UEFI environment,
optional is only Samsung driver instead of the MS and Samsung Magician also as optional.
Recommended AHCI/RAID and NVMe Drivers
It should be partitioned as GPT type, NTFS file system and this can be done from windows in Disk Management, that’s it.
For later UEFI OS install, the partition must be resized to free space prior in order to the installer create the EFI system partition and will a automatically use the rest as primary OS partition.
This without touching the already data… i do always recommend a clean install on a empty full disk, your choice.
UEFI environment setup doesn’t disable SATA ports unless specific notes by the OEM specified in the motherboard manual.
All ports should be set as AHCI/RAID, AHCI in your case.
Sorry for my Confusion, i am not used to M.2 Drives and other later Devices
@MeatWar : thank you for your fast reply!
Both SSD Sata3 Drives and the M.2 NVME drive are fresh purchased and unused (except both SATA3 SSDs i freshly installed new OS Win10 Home/Pro two days ago)
So do i get it right, i have to install new clean OS now to the NVME drive at the PCIe Slot to get it working?
my goal was to let the OS files be on the both SSDs with SATA3 and use the M.2 NVME as storage device only (installing programs, games etc. but no OS) but leaving the option to install an private OS later on. My thaugt was, i can take the data with me via NVME drive but leave the PC with an operating system (at the SATA SSDs) without the stored Data and a clean installed OS without additionally files where the children can play off.
So i suggest PURE UEFI environment would lead to disable my additional SATA devices? (two SSD Sata3 drive for OS only + one HDD Sata3 drive for backup/Install Files)
in case there is no other way ofcourse i would install a third OS to the M.2 NVME to have it functioning, but if i can avoid that, it would be perfect
or to be more precise, i want both , the SATA SSDs and the M.2 SSD NVME to work with the PC, but the OS on the SATA SSDs
*sorry if this Request is finally some kind of stupid due to missing knowledge, or maybe even just wrong in place here!