Windows 10: A 2nd System Reserved on Another Hard Drive Under Its Own Drive Letter

So I have this other System Reserved Partition that isn't for my main drive (C). It is under a drive I use for backing up (F). Now it wouldn't really be a big issue as it isn't much space but it also has it's own drive letter (D) which I find unorganized. I guess I could just remove it which should remove the drive? But I'm not sure if it's safe to do so since I'm not really sure the importance of this even if it's not under my main drive.

Could someone let me know if I can just remove this without issues arriving later?

Screenshot: https://i.imgur.com/sdJMl6T.png

:)

 

After Upgrading to Windows 10 My 2nd Hard drive doesn't have a drive letter nor can I assign one that option is grayed out

Hi - I upgraded from Windows 7 to Windows 10. In my system I have a primary drive and a 2nd hard drive that has valuable data on it. Under Windows 7 the drive had a drive letter and was a single partition that I could read and write to perfectly. After the
update, the 2nd drive shows up in Disk Management as 2 partitions, one allocated (this is where all the data is) and unallocated space. There is no drive letter assigned to this drive.

When a go to assign a drive letter to the drive, that option is grayed out and not available. Also the drive does not show up in My PC and I cannot access the drive at all. I want this drive to show up and I do not want to lose any of my data. Any ideas
? Thanks.

 

Clone System Disk Issues

Hi slance310

> The boot sequence doesn't go by drive letter anyway, I don't think... it goes by location on the drive... Drive 0 Partition 2 for instance...

That is what I now believe. The drive letters are particular to the OS. Which is why the drive letters in the command prompt within the recovery console are different. And the boot sequence goes by drive and partition reference.

> Your boot partition is probably the 100mb System Reserved on the original drive with C:\ being the 2nd partition...

Yes, the active(boot) partition is the 100mb Reserved. However the C: drive was not the 2nd partition on the original drive. Which was the the cause of the issues.

>BTW... Are those 200GB and 500GB actually GB or are they really MB ?

On my old physical drive the partitions were:

System Reserved (100MB)

E: partition (500GB)

D: partition (200GB)

C: Drive (The rest of the 1.5 TB drive).

I have my new SSD drive booting up now with the dummy small partitions. So my SSD looks like:

System Reserved (100MB)

Dummy E: partition (100MB)

Dummy D: partition (100MB)

C: Drive (Rest of the 525GB drive)

So Windows needs to be in the same partition as is it used to be to boot all the way up. Within Windows I have not assigned drive letters to the two dummy partitions.

I think what used to happen with older versions of Windows when this issue occurred. Is it would say it could not find an operating system. Now the boot loader on the system reserved is being smarter and finding Windows on a different partition, so Windows
starts to boot. But than Windows is not happy probably because it uses drive and partition internally to find some of its files.

This is also why 'Reset this PC’ with ‘Keep you files’ was probably not working. A bit more feedback here would have been nice.

 

Temporarily disconnect disk 0 (contains F and D) by disconnecting the SATA cable from it then reboot your PC. If it boot then you can safely delete the System Reserved D.

To delete the system reserved partition from disk 0 (Drive D), Open Admin command prompt:

• diskpart
• select disk 0
• select partition 1
• delete partition override
• exit

After done with the above, You might also want to swap the SATA cables between disk0 and disk1 to make C drive on disk 0 and F drive on disk 1.

 

You are good to go to delete the system reserved partition on the current disk 0. Your computer is booting from disk 1 (according to the screenshot you posted).

If you swap the sata cables to make your boot drive and C: drive disc 0, you might also have to change the hard drive boot order in bios.

 

Thanks to both of you. I deleted the partition, the drive went away, and I have not encountered any issues.