GPT disk windows 10 tries to load windows from wrong 500mb partion it seems / unfixable via bios / maybe diskpart solution?

T

ThorstenSixt

Hello there,


i need some guidance on how to fix an issue with diskpart (i hope).


My UEFI controlled GPT Windows crashed due to tweaking my ram. Windows updates may have occured before that. I don't know.


The real OS Partition on my ssd is not c: drive anymore. Instead it tries to start win from a 500mb c: partition.


With a windows usb stick i could not fix the issue.


But i could take this screenshot after trying to find a driver:

66c15399-a3a7-4baf-8b24-c02a020a5e7d?upload=true.jpg


with diskpart my only m.2 ssd looks like this:

71b3dda9-2f05-4fb9-b85c-7e34d0c8c7b7?upload=true.jpg



choosing disk 0 reveals:

018f1770-60d1-4093-9064-8aad105fe192?upload=true.jpg



My issue is that in my Asus/Apex xi/ Bios the ssd will show up only as one entry:

Windos Boot Manager - samsung evo // and that entry is mapped to the wrong partition i believe


Somehow C: drive is mapped to partition 1 or 3, instead of my OS on partition 2



Is this fixable via diskpart ?



My Bios settings:


CSM: disabled

OS Type: windows uefi os

Fast boot: disabled (usually enabled)

Sata Controller(s): enabled

Sata Modus: Intel RST Premium with intel optane / i don' have optane btw

M.2_2 PCIE Storage RAID Support: RTS controled

Native Ami nvme driver enabled


Thanks in advance


Best Regards

Carlyle


ps twice before i had an issue that the OS would not start after an bios update. I had to enable and disable some sata controller settings and play around with CSM (on/off) and the type of OS (other/windows uefi) before it startet at some point with the final config always beeing the one listed above.

Continue reading...
 
Back
Top Bottom