[SOLVED] Windows won't boot without secundary drive, which has been corrupted

Zakya

Prominent
Jan 20, 2023
29
2
535
My pc has 2 drives: C-drive, which is an M.2 and a D-drive, which is a basic ssd. Recently, I managed to lose the data on my D-drive. I have most of it backed up, so thats not a huge problem.
The actual problem is, that i suspect that the D-drive was actually my boot drive for some reason. My C-drive, which is working just fine, won't boot into Windows. It has every folder you'd expect a C-drive to have; Users, Program files and Windows. It just wont boot.
I tried to use a windows installation usb drive, to repair it, but it said it couldn't do that. Is there a way for me to only install the boot drive there? Or if I install Windows to my D-drive, will i somehow be able to import the settings over?
 
Solution
Execute following.
If you get any errors, then stop immediately.

diskpart
list disk
select disk 0
(select 465GB disk)​
list partition
select partition 2
(select 538MB recovery partition)​
delete partition override
create partition primary size=500
format fs=ntfs quick
active
assign letter=H
exit
bcdboot C:\windows /s H:

Last message should be "Boot files created successfully".
Check boot priority in BIOS, set 1st device to 500GB drive.
Should be able to boot into windows afterwards.
Most likely, your boot files were on the D drive....therefore the PC won't boot with only the C drive connected. That can happen if the D drive is attached when Windows is installed on the C drive...therefore, you should install Windows with only 1 drive connected.

It's correctable with a few commands that I don't know. Someone else around here might.

Or you can reinstall Windows again.
 

Zakya

Prominent
Jan 20, 2023
29
2
535
Most likely, your boot files were on the D drive....therefore the PC won't boot with only the C drive connected. That can happen if the D drive is attached when Windows is installed on the C drive...therefore, you should install Windows with only 1 drive connected.

It's correctable with a few commands that I don't know. Someone else around here might.

Or you can reinstall Windows again.
If the boot sector is on D, and D has been corrupted, I don't think its transferable with a few commands
 
If the boot sector is on D, and D has been corrupted, I don't think its transferable with a few commands
It's not a boot sector, but actual boot loader that's located on the wrong drive. A small 100MB - 500MB partition (either "System, Active" or "EFI System").
You have to create bootloader on drive, containing windows.
This can be done.
But first show screenshot from Disk Management.
(upload to imgur.com and post link)
 

Zakya

Prominent
Jan 20, 2023
29
2
535
It's not a boot sector, but actual boot loader that's located on the wrong drive. A small 100MB - 500MB partition (either "System, Active" or "EFI System").
You have to create bootloader on drive, containing windows.
This can be done.
But first show screenshot from Disk Management.
(upload to imgur.com and post link)
I am unable to boot to windows
 
Execute following.
If you get any errors, then stop immediately.

diskpart
list disk
select disk 0
(select 465GB disk)​
list partition
select partition 2
(select 538MB recovery partition)​
delete partition override
create partition primary size=500
format fs=ntfs quick
active
assign letter=H
exit
bcdboot C:\windows /s H:

Last message should be "Boot files created successfully".
Check boot priority in BIOS, set 1st device to 500GB drive.
Should be able to boot into windows afterwards.
 
Solution

Zakya

Prominent
Jan 20, 2023
29
2
535
Execute following.
If you get any errors, then stop immediately.

diskpart
list disk
select disk 0
(select 465GB disk)​
list partition
select partition 2
(select 538MB recovery partition)​
delete partition override
create partition primary size=500
format fs=ntfs quick
active
assign letter=H
exit
bcdboot C:\windows /s H:

Last message should be "Boot files created successfully".
Check boot priority in BIOS, set 1st device to 500GB drive.
Should be able to boot into windows afterwards.
IT LIVES! Thank you so much! Everything seems to be working.