My secondary drive is included (mandatory) in system image backup.Why?

Brink said:

There's nothing in Disk Management showing for why the other disk is being included in the system image.

If you like, you could disconnect the other disk to not have it included in the system image. Make sure that you do not have any issues with it disconnected before creating the system image though. If you do, you'll just have them with the created image as well.

done. everything is ok. THANK YOU Brink.

Kari said:

This may not have anything to do with your issue but according your Disk Management screenshot you have assigned your data partition letter A:. The A: and B: are due historical reasons treated as removable media and should not be used for hard disks. Reasons are many, starting from the fact that Windows does not index the content on A: and B: drives.

Kari

maybe. I' ll change that to make things right. Thank you for the tip.

agasabellaba said:

Hi,
I want to create a system image of my primary drive (an SSD) on an external 230gb hard drive as backup for any incovenience..
The problem is my other drive (games,movies, photos, etc) is automatically checked as default because "required for Windows to run" among my primary drive and System Reserved 350MB partition.
I cant uncheck its box.
Can you guys help me?

My pc runs windows 10
It' s a custom built pc with:
i7 4770k
GeForce GTX 770 2GB
8gb RAM
230 gb of SSD (primary drive) with still 70gb of free space
1 Terabyte of Hard disk (secondary drive)
230 gb of external TrekStore drive (NFTS formatted)

Thank you,
agasabellaba

Don't know how old this thread is but still might help others as issue is still on going.
If your back up image includes another hard drive it's because you have installed games main file on the slave drive. in other words it's ok to install a game on a slave drive but the main part of the game like for instance Rockstar game launcher application must be installed on C drive and then the game or games under that app can then be installed on your slave drive. if you install Rockstar launcher app on the slave drive the back up image will see it as part of your OS system because c: drive still deals with it's execution it then sees the slave drive as an extension of windows.
anyway could't find any solutions and took me a while to figure that out but I finally got there hope it helps others.
now I can choose what drive to include and also solved the other issue of image back up stuck at 97% which is a very common issue!

Citizen Smith said:

like for instance Rockstar game launcher application must be installed on C drive and then the game or games under that app can then be installed on your slave drive. if you install Rockstar launcher app on the slave drive the back up image will see it as part of your OS system because c: drive still deals with it's execution it then sees the slave drive as an extension of windows.

I'm having this exact issue with Rockstar game laucher being on my H: drive and it being included in the system image.
I've uninstalled it but H: still has a system tag. Do I just disconnect the drive and boot win10 to remove it and then reconnect the drive? Is that the fix? The post above this were'nt clear.
Thanks,

T.

thomashouseman said:

I'm having this exact issue with Rockstar game laucher being on my H: drive and it being included in the system image.
I've uninstalled it but H: still has a system tag. Do I just disconnect the drive and boot win10 to remove it and then reconnect the drive? Is that the fix? The post above this were'nt clear.
Thanks,

T.

You might have something else installed from C drive your unaware of you could try using an app like Lock Hunter and get it from somewhere you trust like GitHub.com. It tells you what' processes are holding on to your file or drive. there is another but I haven't used it called Unlocker. I only had Rockstar Launcher process hanging on that drive. just make sure after removing launcher install directory that you don't forget to uncheck system protection for the slave drive as that will still be enabled then reboot and check again. but I would download Lock hunter or something similar to see first it can come in handy now and again for other issues you could also try and uncheck system protection on C drive and reboot then re-enable it.
If it were me if all else fails remove the slave drive and reboot then plug it in using a dock of some kind to remove any remnants of the process that was holding it and sometimes when you reboot windows it will report a problem if the file was important or needed but I think Lock Hunter will enlighten you as to whats got a hold of your drive so I would try that first and don't forget you will have to make another system image and reset and system file backups once fixed other wise the issue will return.