Non-System Disk Identified as System Disk

[golem]

I was going to make a disk image of a fresh Win7/64 install but when attempting to do so using the windows utility it insists on labeling and including in the image a completely separate data-only disk claiming it is also a system disk. Unfortunately it will not allow me to un-check for purposes of exclusion.

Probably should be looking at the root of the problem and determine why this Data Disk is labeled a System Disk. It is an older drive and has been used in a couple computer builds so may have at one time had an OS installed but I can find no indication of such, plus, I usually format before re-purposing.

Any insight on either route for resolution would be appreciated.

 

[ignatzatsonic]

I can't recall the details, but in the last few weeks there has been a post or 2 here about similar issues. It seems Windows imaging app has its own idea about what qualifies as a system disc and therefore insists that it be included in a system backup.

There may not be any resolution other than to choose another imaging app. This lack of flexibility is one of the primary complaints about Windows own imaging.

 

[golem]

Much appreciate the quick reply ignatzatsonic!

Not unexpected to hear a bundled software might be just a bit lacking. Will migrate to a dedicated utility, was just hoping to keep streamlined.

Also feel a bit embarrassed. Having attempted Google searches for this query and coming up with no hits I simply assumed it was unique thus I failed to due my due diligence and search this forum prior to posting. Thanks for not flaming!

 

[ignatzatsonic]

Depending on your inclinations, you could dig into that disk to find out what files are on it that make Windows think it is a system disc. It's probably fairly obvious, but it could be hidden files or even a partition of some type.

Or just cut your losses and move on to Macrium, Acronis, or EaseUS TODO. That's what many of us on this forum have done. Maybe Microsoft will engineer Windows Backup a bit differently in future releases, but it is a bit touchy, non-intuitive, and inflexible as it now stands.

 

[golem]

Thanks again!

I feel more a fool each time I post. I just un-hide sys folders/files (which I thought I already did) and now see a "Boot" folder and "bootmgr" file, the likely culprits. As they will not allow direct deletion I'll have to do a bit of research on taking ownership - Not studied much all the security obstacles implimented from Vista on.

Appreciate your having urged me in the correct direction.

 

[whs]

Move the bootmgr from the data disk to C:. Then you may have more luck: http://www.sevenforums.com/tutorials/209885-bootmgr-move-c-easybcd.html

But using Windows imaging is not a good choice. Try this: http://www.sevenforums.com/tutorials/73828-imaging-free-macrium.html?ltr=I But move the bootmgr first else you will have a problem when you need to restore.

 

[golem]

Thanks for the reply whs!

Well, I learned permissions prior to reading your post and hastily began deleting the files even though I fleeting thought it might be good to check boot record directors. As my luck goes, upon rebooting after deletion I was greeted with a stalled boot screen advising no boot record could be found. Why it would have associated or installed any boot files there is a mystery. No biggie though as I had not yet begun to install apps beyond the core OS, Win updates and drivers.

Just completed a clean install with all other drives disabled. Simply for grins I went through the motions with MS imager and it performed as it should. That said, I still think I'll migrate to Macrium Std for purposes of flexibility. Two good things come from this -- I am now quite comfortable with permissioning and, the second install was even cleaner.

Thanks again for the helpful replies from all!