Searching the older Macrium forums turns up this thread
and this other thread
discussing that error. Do either of those possibly apply to you?
A few general notes as well in case you find any of them useful:
- The "site" constraint in Google is extremely useful for cases like this when you know/suspect that the information you want exists within a particular domain's webpages. I Googled "0x40010004 site:macrium.com" to limit results to webpages that exist within Macrium.com, for example.
- The Snipping Tool built into Windows since Win7 is a much more effective and flexible means of capturing screenshots than pasting into Word, the latter of which reduces image quality quite a bit. It's not an issue for this particular case, but it can make text illegible in some cases. Additionally, if you save the screenshot as an image file, you can use the Insert Image feature here so that you get a clickable thumbnail right in your post, and clicking it displays the screenshot at full resolution. See below for an example.
- If you're backing up your entire D drive, as one of my clients does, you may want to consider excluding the System Volume Information folder and also probably the Recycle Bin folder, since that way you would still be able to restore the entire backup without overwriting those existing folders on the drive or having to exclude those folders from the restore selection. You wouldn't want to try to restore System Volume Information from a backup and may not need or want to restore the Recycle Bin either. Adding these exclusions may also reduce your backup size. See screenshot below for how to configure that.
- Alternatively, if you're backing up the entire D drive, you might prefer to perform image backups. They will run more quickly, and Incrementals/Differentials will typically be much smaller. The latter is true because if you change a tiny bit of a very large file, for example, an image job Inc/Diff only has to back up the actual portions, whereas an F&F job Inc/Diff has to back up the entire file again. The sole reason my clients backs up the entire D drive as an F&F job rather than an image job is because this system is a file server that has custom NTFS permissions defined, and it's much easier to restore custom NTFS permissions using the F&F restore mechanism than out of a mounted image backup. And speaking of mounting, files larger than 4GB do not display properly when mounted in an F&F backup, even though they restore properly. Mounted image backups do not have this issue.
Screenshot of recommended exclusion configuration for a full drive F&F backup in case you still don't want to switch to images: