This board generation has no support for M.2 or NVMe drives. The built-in emulator allows for access to the drive, but this does not mean that booting from it is possible.
Since these boards are long past their EOL date, no firmware (including BIOS) updates are forthcoming.
What built-in emulator?
Yes, booting from it is key. The BIOS would need to be aware of NVMe for booting from M.2 NVMe, but in this case, since it's obvious that there will be no further BIOS updates, I just want to settle for M.2 AHCI, which needs no NVMe support.
The DZ68BC can boot an AHCI device, of course, so it really comes down to whether or not it can boot one via an interface other than SATA or USB.
This message was posted on behalf of Intel Corporation
Thnak you very much to N.Scott.Pearson for the information provided above, it is really helpful for all the peers viewing this thread.
I just wanted to confirm that the option to boot from an M.2 SSD or an NVMe is not available for this board, the board does not support that configuration, it can only boot from SATA or USB.
In regard to your question about the built-in emulator, the best thing to do is to wait for N.Scott.Pearson to provide those details.
Any questions, please let me know.
And floppy and network.
But I'm just wondering if anyone's ever tried an M.2 adapter on this generation of board and attempted to boot an AHCI drive that way. What happens? Does it not show up as a selectable boot device at all despite it being AHCI? Or does it show up and just not boot? It would be usable as a non-boot drive, but very few would care for that.
This is what I have been told: The drive's built-in AHCI emulator does not, with any Intel Desktop Board product, provide you with a boot capability. You can access it from Windows but you cannot use it as your system drive.
Ah, AHCI emulator (I never thought of that as being an emulation, so I didn't know what you were referring to).
It's surprising that even the next generation (or two) of Intel desktop boards are in the same predicament.
So I suppose short of finding a drive that's made to workaround this problem (I think a couple do exist), or finding an adapter that is more than just an adapter and provides some logic to also workaround the problem (no idea if this exists), then we're stuck with SATA.