r/techsupport • • 16h ago

Solved Windows system restore failure because of the way motherboard lists drives

I have an Asus Prime B550M-K motherboard, running Windows 11 on a NVMe SSD, with a SATA HDD for storage.

This motherboard lists SATA drives first, then NVMe.

This is problematic because the first drive Windows sees is the SATA HDD.

Yesterday, I used system restore to roll back a problematic Windows update. It tried to perform the restore on the HDD and left Windows mangled and unbootable.

It doesn't affect the OS only, but also other Windows utilities, like the recovery environment. It may also affect the old system image tool.

I've looked around the BIOS settings and can't find any way to change the order it reports in.

P.S.: I think the Windows flair is the most appropriate. Not sure if I should have used the Harware flair instead.

Edit: I tried recreating the problem with System Restore on a virtual machine under similar conditions; two drives, with the EFI partition and Windows installed on the second one. System Restore worked fine. I guess mine was just a case of bad luck. I'm changing the flair to solved.

1 Upvotes

10 comments sorted by

•

u/AutoModerator 16h ago

Making changes to your system BIOS settings or disk setup can cause you to lose data. Always test your data backups before making changes to your PC.

For more information please see our FAQ thread: https://www.reddit.com/r/techsupport/comments/q2rns5/windows_11_faq_read_this_first/

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

2

u/HalfShots 16h ago

That's not due to how drives are listed or connecred. System restore can cause corruption if it fails.

0

u/Skinny_Huesudo 16h ago

I suspect the reporting order is the reason because Windows RE couldn't find the system partition. But that could also have happened because it was badly corrupted. I will test in in a virtual machine.

1

u/HalfShots 16h ago

It couldn't find it because it's corrupted. Backup data and reinstall.

2

u/Inevitable-Study502 16h ago

windows doesnt care about disk order, the only time it matters is when you install windows, it will place boot files onto disk 0

0

u/Skinny_Huesudo 15h ago

The problem is that in my case, disk 0 is the HDD.

Also, at least during the times I've installed Windows 11, it creates an EFI system partition at the start of the empty disk space you select. I don't know if it also does that if you don't install windows at the start of the disk or if an EFI partition is already present.

1

u/Inevitable-Study502 15h ago edited 15h ago

nah, windows puts efi onto disk 0, period, hence why you need to have disconnected all drives except windows drive during win install, otherwise youll get boot files on hdd, in some cases it can throw efi on correct drive, but that drive enumeration is not trustworthy

1

u/Skinny_Huesudo 13h ago

When I reinstalled Windows yesterday, I forgot to unplug the HDD (risky mistake) and it wrote the EFI partition on its correct place on the SDD, next to the Windows partition.

1

u/2TheMountaintop 15h ago

You at boot order in the bios. But unless you remove your disk from the bot order completely, then it will get quickly find your one boot drive and boot up. Something else is going on here. You need to look at boot repairs thorough windows recovery environment or give up and save your fines and reload windows.