Boot files, wherever they may reside, are considered part of the system image.
When you install a second copy of Windows on a system, the installer modifies the existing boot loader to include a new entry for the freshly installed Windows version. You have added a new drive to the system and installed a fresh copy of Windows on that drive, but the boot files are still on the original drive. While the exact reasons for this problem are unclear, I found a few scenarios likely to occur.ġ. Every time I went to create a new system image, it insisted on adding an F: image. I tried several workarounds, like removing the swap file from that drive, but nothing worked. For example, when I set backup to add a system image, it did so for my C: drive, and then it also insisted on adding F: - a drive mainly for storing virtual machine images and software installation packages. The biggest problem I've had is with Windows 7 adding multiple hard drives (that are not system drives) to the image for no apparent reason.
But for all its benefits, the backup system has several frustrating quirks.
