Asrock B450M Pro4 M.2 Not Detected | Proven Fix Steps

Guide / By

For Asrock B450M Pro4 M.2 not detected, reseat the drive, set M2_1 to PCIe in BIOS, update BIOS, and match NVMe/SATA slots for your SSD.

M.2 drives fail to appear on this board for clear, repeatable reasons. The good news is that every cause maps to a short, testable step. This guide walks you through quick checks first, then the deeper fixes that bring an M.2 back in BIOS and in Windows.

What Causes M.2 On This Board To Vanish

Several things can hide an installed M.2 from BIOS or Disk Management. The board has two M.2 sockets with different wiring, some SATA ports share lanes with one socket, and a few BIOS toggles can block detection. Add common build issues like standoffs, stiffer thermal pads, or a half-seated edge, and the problem looks random when it is not.

  • Different Slot Types — M2_1 is PCIe (NVMe). M2_2 is SATA. An NVMe stick in M2_2 will not show. A SATA M.2 in M2_1 will show only if the module supports SATA there.
  • Shared Lanes — Using M2_2 disables one SATA port on the board. A cable on that port makes the M.2 look missing.
  • Boot Mode Mismatch — Legacy boot with CSM can hide NVMe. UEFI mode exposes NVMe to setup and the OS installer.
  • Outdated BIOS — Early revisions have weaker NVMe handling. A modern build with a new SSD benefits from the latest BIOS.
  • Install Errors — Wrong standoff height, a bowed heatsink, or a loose screw can lift the contacts and break the link.

Asrock B450M Pro4 M.2 Not Detected — Fast Checklist

Quick check: Run each item once, in order. Most systems spring to life by step three or four.

  1. Confirm The Slot — Put NVMe in M2_1 and SATA M.2 in M2_2. If you have only one slot free, match the drive to it.
  2. Pull The SATA Cable From The Shared Port — If M2_2 is in use, unplug the SATA device on the linked port, then reboot and retest.
  3. Reseat The Drive — Remove the screw, lift the stick to 30°, slide fully, press flat, then tighten until snug. Do not over-torque.
  4. Clear CMOS Safely — Shut down, switch the PSU off, hold the power button 15 seconds, move the jumper or pop the battery for a minute, then restore.
  5. Load UEFI Defaults — Enter setup, load defaults, set UEFI boot, enable AHCI, save, and test detection again.
  6. Update BIOS — Flash the latest stable release with Instant Flash from a FAT32 USB stick. Do this on AC power with defaults loaded.
  7. Check In Windows Setup — Boot a Windows installer USB and open the drive screen. If the SSD appears there, delete old partitions and create new.

After the checklist, the drive should appear in BIOS under Storage and in Windows under Disk Management. If it shows in BIOS but not in Windows, initialize as GPT and create a fresh volume.

BIOS Settings That Make M.2 Appear

The goal is simple: expose NVMe under UEFI and avoid legacy paths that hide the controller. Small changes flip that switch.

  • Switch To Full UEFI Boot — Disable CSM. Set Boot Mode to UEFI. This exposes NVMe to the firmware, the installer, and your tools.
  • Pick The Right Boot Target — When you install Windows, choose the USB entry with the “UEFI” tag. After setup, pick the NVMe entry named by the drive.
  • Enable AHCI For SATA — Set SATA Mode to AHCI, not RAID, unless you run arrays. AHCI keeps SATA M.2 simple to detect.
  • Load Defaults Before Flashing — Saving defaults cuts odd side effects after a BIOS update and helps storage re-enumerate cleanly.
  • Turn Off Fast Boot During Testing — Fast Boot skips checks that can mask a half-seen device. Re-enable it after the drive is stable.

Path in setup: In BIOS, open Boot and set CSM to Disabled. In Boot, set Boot Mode to UEFI. In Storage, set SATA mode to AHCI. Save and reboot. These three changes solve most “drive missing” reports on this board.

Slot Compatibility: NVMe Vs SATA On This Board

This model gives you one PCIe M.2 slot and one SATA M.2 slot. Mix them up and the SSD seems dead, even though the hardware is fine. Use the map below when you plan boot or storage roles.

Slot Accepts Notes
M2_1 (Ultra M.2) NVMe PCIe x4/x2 Boot-ready under UEFI. Use for your main OS drive.
M2_2 M.2 SATA Using this slot disables one SATA port on the board.
SATA3 Ports 2.5″/3.5″ SATA One port shares with M2_2; move the cable if M2_2 is active.

Heads-up: Many M.2 sticks look alike. NVMe uses PCIe lanes; SATA M.2 carries the same protocol as a 2.5″ drive. Check the box, the label, and the model page before you assume the type.

Cloning from a SATA disk to a fresh NVMe is fine, but set the clone to GPT and let the tool make a new EFI System Partition. If the old disk was MBR with legacy boot, you will avoid boot loops by doing a clean install on the NVMe and keeping the clone as a data move only.

Physical Checks And Install Technique

Small hardware details have a big effect on link quality. Five minutes with a screwdriver often beats an hour in firmware menus.

  • Match The Standoff — Use the 2280 position for most drives. A wrong standoff bends the PCB and lifts the contacts.
  • Mind The Thermal Pad — If the pad is too thick, remove it for testing or swap to a thinner pad so the stick sits flat.
  • Clean The Edge — A quick wipe with isopropyl on the gold pads removes oils that raise contact resistance.
  • Seat With Even Pressure — Press the opposite end while you set the screw. The spring in the slot should be flat, not bowed.
  • Try Without The Heatsink — Test bare, then add the heatsink back. If detection fails with the sink on, reduce pad thickness.
  • Test The Drive In Another PC — If possible, plug the SSD into a known-good system. A dead stick wastes time on the wrong path.

Once the controller appears, keep temps in check. M.2 sticks can throttle under sustained writes. A low-profile heatsink and decent case airflow hold speeds steady without blocking the slot.

When The Drive Still Won’t Show Up

If the board still reports no M.2, switch to targeted tests to isolate the fault. Each step removes one unknown so you can decide what to replace or rewire.

  1. Boot A Live Linux USB — Use a live distro and run lsblk or nvme list. If Linux sees the SSD, Windows tooling is the gap.
  2. Format From The Installer — In the Windows installer, delete all partitions on the SSD and create a fresh GPT volume. That wakes up drives that ship uninitialized.
  3. Move Any GPU From The Secondary Slot — Keep add-in cards out of slots that share lanes with storage during testing.
  4. Swap Cables And Ports — If you use M2_2, move any 2.5″ drive off the shared SATA port and retest. Label the working pair.
  5. Test With Known-Good Power — Use a wall outlet with a surge strip off. A wobbly PSU rail can trip device init timing.
  6. Reflash The Same BIOS — Flash the current version again. A clean flash after defaults can restore NVMe detection logic.
  7. Open A Support Ticket — If nothing lands, contact the board vendor with your serial, CPU, SSD model, and steps tried. You may have a faulty socket.

The exact phrase “asrock b450m pro4 m.2 not detected” can also point to a simple mix-up: an NVMe stick in M2_2 or a SATA cable left in the shared port. Fix those, and most builds post on the next power-on.

Windows: Initialize And Letter The Drive

  1. Open Disk Management — Press Win+X, pick Disk Management. If a prompt appears, choose GPT.
  2. Create A New Volume — Right-click the unallocated space, pick New Simple Volume, choose a size, assign a letter, and format NTFS.
  3. Assign A Label — Name the volume so you can spot it in tools and in your backups.
  4. Run A Quick Copy — Copy a large folder to prove sustained writes work without drops.

Common Messages And Real Causes

  • “No Bootable Device” After Install — You installed in legacy mode on NVMe. Reinstall in UEFI mode so the EFI partition lands on the NVMe.
  • Drive Seen In Installer Only — Windows on the old disk uses legacy boot. After you switch to UEFI, it boots the old disk, not the NVMe. Set the NVMe as first boot or reinstall clean.
  • SSD Seen, Vanishes Under Load — The stick runs hot or sits uneven. Add a thin pad and a low-profile sink, then retest.
  • Only One Of Two Drives Shows — You used M2_2 and the shared SATA port together. Move the SATA cable to a free port.

When to replace: If the SSD fails in two known-good PCs, logs CRC errors, or throws SMART media errors, start an RMA. If two working SSDs fail in the same board slot, the slot is suspect. Swap the board or run the M.2 in the other slot with the right type.

Plan Your Setup For A Clean Boot

A tidy plan locks in stable storage and cuts repeat visits to BIOS. When you start fresh, lay out roles, ports, and boot mode before you install the OS.

  • Pick The OS Drive Slot — Use M2_1 for your NVMe system drive. Keep M2_2 for a SATA cache or a game library.
  • Label The Shared SATA Port — Mark the port that turns off with M2_2 so future cable changes don’t break the M.2.
  • Stick To UEFI Everywhere — Create the installer in GPT mode, pick UEFI targets, and leave CSM disabled.
  • Back Up Before Changes — Clone or export files before you flash BIOS or re-partition. Storage tests can wipe data fast.
  • Keep Firmware Current — Update the board and the SSD to the latest stable versions after the system is steady.

With the map, the checks, and a clean boot path, this board handles both NVMe and SATA M.2 without drama. If you ever hit the same wall again, run the checklist in order and you’ll land on the step that brings the drive back.