Storm season is back, bringing with it the potential for significant weather events. If you have clients in areas prone to infrastructure disruption, visit the Disaster Recovery Resources guide for preparedness information. Datto recommends performing proactive disaster recovery testing to mitigate potential downtime. See our articles about the importance of disaster recovery testing and Preparing For A Cloud Virtualization Test: Policies, Procedures, And Partner Responsibilities to learn more. For live updates, follow @datto on Twitter.

Failed screenshot with "BOOTMGR is compressed"



This article describes the cause and possible solution for the screenshot verification error "BOOTMGR is compressed."


This is caused because NTFS compression has been enabled on the volume containing the Windows boot files.

When this option is selected, Windows will try to compress all files, including critical boot files.


1. On the production machine, open Windows Explorer (explorer.exe)

2. Right click the drive where BOOTMGR is located (typically C:), and select Properties.

3. Uncheck the Compress this drive to save disk space option.

4. Take a new backup, and then schedule a screenshot for the new backup.

5. If the "BOOTMGR is missing" message appears after a new backup, manually force a differential merge for the agent.

Note: This will force the agent to traverse the entirety of each volume being backed up, and it will appear to be a full backup. However, a diff-merge backup will only incur a cost of space on the storage array equal to a normal incremental and a minor amount of overhead.

Was this article helpful?

0 out of 0 found this helpful

You must sign in before voting on this article.

Calling all Partners! We want to hear your feedback! Please participate in this quick survey and help us build a better, more-relevant Knowledge Base!

Want to talk about it? Head on over to our Community Forum!