[BozemanDoug]

I carefully disconnected all my drives except my NVME C drive when I did a clean install of windows.  My purpose was to have a single dedicated System drive.  After installing and testing Win10, I hooked up my remaining SSD's and hard drives and proceeded to re-install all my other software.

 

Some of the software insisted on being installed on the C drive. (like Anaconda3, PyCharm, etc) .

 

After making sure my system was stable, I did a Windows Image Backup.  I was hoping to just image the C drive (both partitions).  Instead, the Backup routine insisted on imaging one of my other SSD's as well as the C drive.

 

In the past this has caused headaches when attempting to recover from a crash.

 

What's going on? and what should I do different?

 

TIA   Doug

[Advertisements]

Just wondering do you have a raid configuration?

[KiwiProbie]

Just wondering do you have a raid configuration?

[BozemanDoug]

No

 

PS>   Thanks for your quick view!

[KiwiProbie]

Welcome I will have a look around for answers but if someone get in here before I get back then that would be good too.

[KiwiProbie]

Have you tried forcing it to install on C:\?

Everything that I have read so far points to bugs with the applications that you mentioned above.

[BozemanDoug]

Win10 went onto the C drive easily and completely; I booted up with no problem.  This was without any of my other drives attached.  It created 2 partitions on the C drive (normal behavior).

 

Something I did (or the other software did) loading my other software onto my other drives triggered at least one of these drives to be flagged as a system drive (in addition to the C drive).

 

The appearance of this "false?" system flag can cause restoring an image file to fail (I think)