Salta al contenuto principale

Hibernation Mode damaging other partitions when Trueimage is installed

Thread needs solution

Hi,

I have a laptop computer provided by my company that has two Windows XP installations on it. When starting up and booting, I chose the installation via the GRUB bootloader.

When chosing one XP installation in GRUB, GRUB is hiding the partition of the other XP installation and vice versa, so there is no drive letter assigned to those hidden partitions. All partitions are NTFS.

Now I noticed the following:

Trueimage 2010 is installed on the second Windows XP installation. When I use the hibernation mode of Windows XP on that second installation, it is damaging the file system of the first installation. This leads to the automatic start of CHKDSK when booting the first installation of Windows XP.

It took me a long time to find out what is happening. I used Sysinternals-Tools such as Process Monitor and Disk Monitor to check which process is writing to the (hidden!) partitions of the first Windows XP partition. It is the system process. It is writing 4 kB to the path \Device\HarddiskVolume1\$Logfile (while HarddiskVolume1 is the hidden first Windows XP installation) - but it shouldn't do that because it is damaging the file system of the hidden partition.

Since I could not determine which drivers are causing the system process to write to the hidden partitions (or better: to the hidden volumes), I checked all other software on the second Windows XP partition, uninstalled the Antivirus-Software and everything which could possibly interfere with the file system of the hidden partition and tried hibernation mode after each uninstall.

Only after uninstalling Trueimage 2010, it didn't show that effect any longer. After re-installing Trueimage 2010, I had the same problems again. So the effect is related to Trueimage 2010.

Is there any way to prevent Trueimage 2010 from writing to hidden partitions when entering hibernation mode in Windows XP?

0 Users found this helpful

Hello Philipp,

I understand the issue and can say that this is not a common one so we should investigate it in order to find the possible solution or workaround for you.

I would recommend you create support case using the following link and attach the following diagnostic information:

1) AcronisInfo. See this KB article how to collect it.

2) Sysinfo

- Open Start\Programs\Accessories\System Tools\System Information;

- Choose the "Save" option in the "File" menu (or "Action" menu under Windows 2000), enter the "File name" and set the field "Save as type" to "System Information File (*.NFO)";

- Send us the saved file.

After you create a case write me PM and I will escalate the case to our expert team.

Before gathering the requested info I would suggest you to download the latest build of the program 6053 and install it. I am not certain if the issue is addressed in the new build at this point, however it is generally a good idea to be up to date. You can download the latest builds from your account under Registered Products.

Let me know if you have any questions.

Thank You.