Yes, using one backup solution over another is personal preference; however, it is also a fact it's pointless to utilize a third party backup solution when Windows natively supports it via DISM.
- There are a few advanced exceptions to this, such as if you require encryption, albeit if one does require encryption, it's more secure to use your own certificates or pgp keys to do so.
- None of the advanced features that would be exceptions are offered in the Free version, and even if one purchased a licensed version, 99.99% of people would never use the advanced features not offered by Windows natively.
Not only is a third party backup solution more time consuming, it requires quite a few extra steps that lengthen the amount of time it takes from start to finish.
- For example, one must first download the Macrium iso, and time will vary greatly depending on the speed of the user's internet connection. Once downloaded one must burn a CD, or DVD if it's over 700MB, which also varies in time depending on the speed of the writer burning the disk. Creating a USB drive also consumes time, and many users don't realize they must manually change the drive to bootable via diskpart or download yet another third party tool, like Rufus, to do so.
- Let's also not overlook the fact if you want to apply the captured image, you're entirely dependent on the third party program, as you must use Macrium's software to do so (they may offer the ability to convert it to a VHD or WIM, which is unlikely to be offered in the free edition, and even if they did, it's yet another time consuming step). You can boot up any WinPE, WinRE, or Windows Setup disk and begin applying the image in under 30 seconds once booted.
Meanwhile... it takes no more than 30 seconds to boot into WinRE and begin the capture process, and if the system partition is under 100GB and the compress flag is set to fast or none, it's likely the capture would be completed prior to having a third party backup solution ready to boot.
It's impossible for a captured WIM or ESD to become corrupted in the capture or apply process if the checkintegrity flag is set for both, as well as the verify flag set for the capture command, so if you've experienced corruption capturing a WIM or ESD this is why.
DISM is the backbone of Windows deployment, imaging, system file parity verification, and recovery, making it one of the most dependable and reliable programs in Windows.
- If, as you say "...is more reliable than Windows...", meaning it's [Macrium] is more reliable than DISM [Windows], Microsoft and all Windows users would have a severe problem since DISM is the only program capable of performing parity checks on WinSxS, thereby making it possible for SFC to fix system file issues.
- Seeming as we don't have users en masse having to reinstall Windows whenever a system file becomes corrupt, I believe that demonstrates the reliability of DISM (not to mention DISM is not a new program and has been around for at least as far back as Windows 7 within the AIK)
I've performed hundreds of WIM captures via DISM, and just as many WIM applies, not once ever having had a corrupted WIM or ESD, nor have I ever come across a single thread on SpiceWorks or TechNet about an individual with a corrupted WIM after a capture. As I stated earlier, your statements lacked factual accuracy.