[SOLVED] System Image Question

[mmullen2]

I am running win 7 HE 64-bit.
When creating a system image not only is C: automatically checked but also another data drive is checked and unchecking is not allowed. How can I tell, if at all, what program(s) is causing windows to flag the data drive as a system drive. Possibly a log file That I am not aware of?? Thanks in advance.

 

[Digerati]

Windows 7 "HE"? What is "HE"?

You really didn't give us anything to go on. What is the other drive? Is it the System Reserve drive? If so, as seen here, other drives may be selected.

 

[mmullen2]

My apologies. It's HP for Home Premium. I was thinking HE for Home Edition.
I do not have a system reserve partition.
The Win 7 OS is one the first partition of C: and the flagged data drive is on the third partition (of 3). The second partition (not flagged for imaging) is used for other purposes.
When creating a system image, the OS checks the 1st partition of course, but also the third one.
My question is how can I tell which program (or whatever) causes the 3rd partition to be flagged for imaging which cannot be unchecked.
Thank you

 

[Digerati]

My apologies. It's HP for Home Premium. I was thinking HE for Home Edition.

No problem. Thanks for clarifying.

The Win 7 OS is one the first partition of C: and the flagged data drive is on the third partition (of 3). The second partition (not flagged for imaging) is used for other purposes.
When creating a system image, the OS checks the 1st partition of course, but also the third one.
My question is how can I tell which program (or whatever) causes the 3rd partition to be flagged for imaging which cannot be unchecked.

What is the name of the 3rd partition? Frankly, I think all is how it should be.

 

[mmullen2]

Problem solved.

First what did not work. I looked at what was running in Task Manager and also loaded from the data drive. All such processes were ended and the associated programs uninstalled. System rebooted, but the data drive was still flagged.

So, I went to plan B. There were about 50 folders on the drive. I tried deleting the ones which did not have drivers or services associated with them. Rebooted but still no luck.

The folder causing the issue was (per chance) about #45 of 50 to be deleted, but once done I can now image C: and nothing else.
Thanks for your efforts in trying to help me. This thread can be closed.

 

[Digerati]

You don't happen to know what was in that #45 folder, do you? Because just the existence of a folder, even if full, should not have been causing this problem. Something during the boot process must have been trying to load, or open an object that was (at least at one time) in that folder.

 

[mmullen2]

It was a program called Protected Folder from IOBIT. It contained a sys file and several dlls, and one executable.

 

[Digerati]

I am leery of programs like IOBIT that promise to make your computer faster than it ever was - much in part, besides making things worse - because of problems like you encountered. Windows today just don't need such programs. I am glad you were able to resolve it and thanks for the followup.