Why is it not a good idea to just re-use the same hibernation file in a HORM configuration, having EWF protected and unprotected partitions?
After the first boot from the hibernation file the data in the file and on disk gets out of sync with the first write access to disk. If one still reboots from an “old” hibernation file the system will see files that are no longer there (zombies) or will not see files that are there on the unprotected volume. This is a good recipe for desaster. The solution is to umount all unprotected volumes before the creation of the hibernation file (see MSDN technical article). After booting from it, these volumes should be remounted. Be aware, that one has stop any restart any applications using these volumesbefore/after the reboot, additionally. Check out our free tool “HORM Manager Lite” which helps You to handle this situation.