Many times when you install a new application on your system you find a lot many changes in it. These changes can just render your system unstable. One can avoid this by using system restore that is formed by using the Restore Points that the operation system records periodically. This is mostly possible if the user uses a single boot configuration system that contains only one operating system, but in systems that are dual-boot i.e. they have two different operating systems working on them. The problem becomes shoddier when one of the operating systems installed is of the older versions in case of windows when the system was Windows Vista or Windows 7 or Windows Server 2008 are configured along with Windows XP or Windows Server 2003 because the earlier backup files are not available when you create new restore points using Windows 7 or Vista.

What happens is that when the system boots using Windows XP or Server 2003 it deletes all the restore points that Windows Vista or 7 have created. This leaves with only the most recent copies of the backup files that these operating systems have created. This was becoming a hectic problem for most of the user. People did find out a way to work around this problem as well. One needs to make a registry entry HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices\Offline this will prevent Windows XP from deleting any restore points that are created by Windows Vista or 7. The registry sub key details are a follow:

Value name: \DosDevices\D:
Value data: 1

There are various effects of the work around that is mentioned above. One of them is that if you have configured a volume that is created in Windows XP can be easily accessed from Windows Vista but the vice versa of it is not possible. Along with such effects the work around also has some limitations, this only helps protect the volumes of windows Vista from Windows XP. Moreover, if the user wants to add or increase the volume in Windows XP inside the windows restore setting for Windows Vista the already created volumes by Vista will any ways be over-written, this is mostly called volume-shadow-data. This problem can be avoided but for this the user will have to write all the XP volumes in the above mentioned registry sub key. This again has further problems that if in future the created volume is deleted than it will stop Windows XP from booting.

The other problem that one faces is that this can only be done when both the operating system are manually exclusive in simple words should be a volume in different drives on the Hard Drive.

The other way of work around is a built in facility that is provided in Windows Vista this is called the Bitlocker. This facility must be enabled on those volumes on which the restore points are enabled this should be done Windows Vista starts. Now when Windows XP or Server 2003 is booted the Vista Restore points remain intact because the Volumes on which Bitlocker is enabled are inaccessible in XP or Server 2003.

Thus, this problem can be partially solved using the above mentioned methods but cannot be completely eliminated. Even Microsoft agrees to it that this is a problem with there products.