Windows 10: No System Reserved Partition On My SSD

I have an SSD with WIN7 installed. It has no System Reserved Partition (SRP) and thus no boot files on that nonexistent partition.
I've read here that individuals with a SRP of only 100mb have had issues installing WIN 10 and that those issues were resolved by expanding the SRP from 100mb to 450mb.
Will WIN 10 install if I have no SRP? Will it merely alter the boot files on my C drive?

:)

 

Two System Reserve Partitions

I have two hard drives on my computer, an SSD with my operating system (Windows 8.1 which I just successfully upgraded to Windows 10) and an hdd for additional storage. After upgrading to Windows 10 I noticed that I now have two System Reserve Partitions.
One partition is on the SSD and the other is on the hdd. Both contain bootmgr and similar files. The files on the hdd have newer file modified/created dates than those on the ssd System Reserve partition. If I set my BIOS to boot from the SSD I get the
blue screen message "no bcd found". If I set the BIOS to boot from the hdd it takes over a minute, but Windows 10 boots fine.

I'm guessing that the System Reserve partition on the hdd (storage hard drive) contains the boot files for Windows 10, but Windows 10 is not installed on that drive, it is installed on the SSD (which I think has the old Windows 8.1 boot files on its own
System Reserve partition).

I've given the two System Reserve partitions drive letters so that I can see the contents of the drives. Can I simply copy the contents of the newer System Reserve partition onto the older System Reserve partition so that Windows 10 will boot from the same
SSD that it is installed on?

Thanks for any suggestions,

Craig

 

How can I move the "system reserved" partition?

When installing windows, the system reserved partition was installed on my hard drive, and windows was installed on my SSD. Is there a way to move the partition to my SSD without removing any of my personal data? If so than how can I do this safely? Thanks
in advance.

 

I'm not certain.

I think your machine will be fine. It's not important where the boot code lives (SysReserve or WinDrive).

For the record though, it appears that a Clean install of Win10 on MBR initialized drives defaults to 500 MB. I have not seen any documentation yet.

If you only have the SSD connected, there should not be an issue when you upgrade. If have other drives connected, the install might use one of those for the boot code - this is not an optimal disk configuration. You want the System and Boot partitions on the same drive. Since your boot code is on the Windows Drive, no problem there.
I'd like to see your Disk Management. If you already downloaded the custom Management snap-in, you don't need to download it again. Just launch dmDskmgr-vd in the location you previously saved it (yes, you can still open the zip folder and launch it from inside)

Download this zip file (contains dmDskmgr-vd.mmc)

dmDskmgr-vd.zip
Double click dmDskmgr-vd.zip to open the compressed folder
Double click dmDskmgr-vd.mmc to launch the custom Disk Management console
You'll get an output similar to this:




Press Alt+PrtScn to grab a snapshot of just the Disk Management window
Open Paint and Ctrl+V to paste it, then save the image
Attach the image to a new post.

 

Here is a screenshot of Disk Manager. My C Drive is my SSD boot-main operating drive.
Two of the other HDDs contain windows (one XP and the other win 7) and are technically bootable (if I removed my SSD the system would automatically boot to one of them).

The unallocated space on the C drive is the space set aside for Over Provisioning by the SSD

 

Thanks,

Yeah, I think you'll be fine if you disconnect the other drives. Only C is flagged as System.

Test that before upgrading - make sure the machine boots without the other drives - it should looking at your Disk management.

To be on the safe side, create a system image of disk 0 and store it on one one of your HDDs.
See: Backup Complete Computer - Create an Image Backup - Windows 7 Help Forums