The Storage Team Blog about file services and storage features in Windows and Windows Server.
We’ve heard a lot of feedback recently from beta testers regarding the loss of restore points caused by dual-booting Windows XP. We’d like to explain the reasons behind this behavior, the impact on various recovery features, and why a backported fix is not currently planned for Windows XP.
The problem: Windows XP automounts every disk it detects, including external or removable hard disks. As part of the automounting process, NTFS writes to the disk, and these writes are detected by the volsnap.sys driver in Windows XP. Because this version of volsnap.sys does not recognize the persistent shadow copies (also known as restore points) made by the volsnap.sys driver in Windows Vista, Windows XP cannot maintain the integrity of the shadow copy storage area and deletes the shadow copies to avoid corrupting them. Note that dual-booting Windows Vista with Windows Server 2003 or Windows XP Professional x64 Edition will also result in the shadow copies being deleted.
The impact: When you boot into Windows XP and automount a disk, you will notice the following effects on the disk after booting back to Windows Vista:
File backups are not affected because these backups do not rely on restore points.
Why this fix is not trivial for Windows XP: Backporting volsnap.sys to Windows XP would require significant development and testing time. The entire Volume Shadowcopy Service (VSS) subsystem in Windows Server 2003, Windows Vista, and Windows Server “Longhorn” would need to be backported to Windows XP and would likely break a number of third-party backup applications that rely on the current version of volsnap.sys in Windows XP.
The workaround: To avoid losing Windows Vista shadow copies on a disk that you don’t need to access from Windows XP, disconnect or power off the disk prior to booting to Windows XP.
Would it be a good idea to **STOP** automounting drives (at least with read/write access) in Windows in future versions?
How about "Windows has detected a new drive - do you want to use this drive?" to which we could answer "No".
This would also solve the problem of Windows wanting to assign drive letters and format partitions of types it doesn't recognise - a real pain in the backside if you dual-boot Linux and Windows on one PC.
PingBack from http://tanveerbadar.wordpress.com/2007/02/06/whats-wrong-with-my-system-protection/
Apparently there is a registry hack which prevents XP from automounting the Vista volume. The Vista drive's letter appears in (XP's) explorer, but no label or anything else. TweakUI won't fix this problem by hiding the Vista volume either.
Ach Yes, here it is Herr Doktor Baron; HKLM\System\MountedDevices. If there is an 'Offline' key modify it if not create it. In this key create a new DWORD value with the name \DosDevices\X: (the slashes are necessary and, obviously, substitute the XP-relative drive letter of the Vista volume for X). Give this the value 1 and bingo! Your maniacal laughter should resound through this and all other worlds to which you have access.
PingBack from http://oscar.supermedianews.info/windows2003serverrestorepoints.html
PingBack from http://www.hilpers.pl/410428-vista-warto/2
PingBack from http://www.hilpers.nl/396191-system-restore
Pingback from Recover Files with the Shadow Copy Feature | Anotherwindowsblog
Pingback from Recover Files with the Shadow Copy Feature