AOMEI Backupper Pro was/is on GOTD. It's a decent app with the drawbacks that you probably shouldn't plan on getting support from AOMEI -- emails in the past have gone unanswered -- & like any other backup software, it may or may not be capable of booting [or working well with] your device. Some backup apps have more scripting available, & a few versions ago when I tried their file backup option, a restored Windows 10 partition wouldn't start or boot, but that's not what File Backup is designed for anyway I think.
Nothing terribly new to add about Backupper that I haven't said before re: image backups generally, with the possible exception of one complaint that it wouldn't install to win10 1607 because of stricter driver signing requirements in 1607. I ran the trial download using 10's troubleshoot compatibility option, & had no problems at all, but that may or may not be typical.
That said, someone brought up a point about the multiple partitions Windows can add... I can tend to talk too much, & this was an example where I went way overlong for a simple comment on the download page -- so I'm putting it here in case it's ever of any use or interest.
... When no SYSTEM partition is used in Win 7 and above all the boot files are placed in the bootable C: drive
It's a mess IMHO. The important take-away I *think* is back up everything -- I like to do it as separate partitions -- and as possible, backup the MBR portion of the boot drive, whether it's formatted MBR or GPT. Specs call for GPT drives to still have the MBR for compatibility, some ransomware targets the MBR, I couldn't find any data on what that means if you have GPT disks [does the ransomware still mess things up?], so considering you're only talking about a few MB, why not back it up if you can?
FWIW in my experience with Windows 10, the number of partitions added is a bit iffy... Microsoft recommended for 8 & 10 to use 4 partitions -- Boot, Microsoft Reserved, Windows, & Recovery -- using a GPT formatted disk with only the Boot partition formatted FAT32 [as required in the spec for UEFI bios]. Installed fresh using 10's setup files to a device with a *pure* UEFI bios that's what you'll get, though the partition order can vary, & later builds can complain about that order (?).
I've only seen Pure UEFI bios on cheaper devices though, so mileage can vary. On a GPT disk the FAT32 Boot partition must exist per UEFI spec, but you can probably get away without it using some UEFI bios, depending on their hybrid &/or legacy modes.
When Windows 7 came out it supported UEFI, but poorly -- online discussions were full of hacks & work-a-rounds to get it to maybe work. Installed to a MBR disk the boot files were placed on the 1st [as in the 1st partition on the disk], non-system or non-Windows partition, & if that did not exist, a hidden partition was created just for that purpose.
What would later [8 & 10] be placed on the Reserved partition was added to that hidden Boot partition -- I don't know if it was added or skipped when a regular partition was used [usually when the device could boot to more than one OS]. Functionally that hidden partition was optional -- the boot files could be added to the Windows [%system%] partition, & with the exception of Bitlocker, everything worked/works fine. The easiest way to do that is with EasyBCD -- while it will create a file or two on the hard drive, it runs portably as in no install needed [the catch is if the target copy of Windows wont yet run, you need another OS to boot to, e.g. WinPE, to run EasyBCD].
If/when 10 uses a Recovery partition it contains [among other files] a winre.wim image that can be used to restore or repair 10. I've seen it also placed in the restricted access C:\Recovery folder instead of a separate partition -- that may be dependent on MBR vs. GPT & partially dependent on the age of the install, as 10 has changed from the early Insider builds. With 7 that .wim should be in the Recovery folder as well, but may not be, & there's info online re: how to get it there, repair or replace it, though you can certainly get away without that wim in that folder. The winre.wim is responsible for things like booting to the command prompt.
I've also seen 10 skip putting the winre.wim in the Recovery folder when there was no Recovery partition. I've also seen that Recovery folder used to store old driver files from a prior 10 install after a build update.
With Windows 8 Microsoft introduced Wimboot, which was a way to Optionally keep the footprint smaller on disk, by putting some of the Windows system files in that compressed image located on the Recovery partition. It wasn't ideal, so Microsoft dropped it with 10 [in favor of compact.exe], but they also moved some of the files that didn't have to do with the day-to-day running of 10 from the Windows folder to the Recovery partition.
A brief aside while talking about Recovery... Windows 10 does let you create a bootable USB stick, may let you transfer system files to it for later recovery or re-install, which may also save a bit of disk space, and all or none of that may work. Just like using backup software, Test -- Do Not Trust that anything will work unless you test.
Back to the partitions... If you don't plan on using Windows Recovery, e.g. if you regularly perform image backups, you can remove the Recovery partition, expanding the Windows partition to reclaim usually ~500MB *if you want* -- many feel it's not worth the work.
The Microsoft Reserved partition isn't big enough to bother with [if/when it's there], but the Boot partition is worth talking about because it can give you problems. Some people run into errors trying to upgrade 10 builds, with error messages saying that that partition is too small. And when you install or upgrade win10 builds, the contents of that partition change... sometimes those changes cause problems, e.g. won't boot properly, especially if the install or upgrade process fails.
The easiest way to fix it is to restore a partition image backup for that Boot partition. To do anything with the partition itself, you have to assign a drive letter using Windows command line DiskPart. To fully see & work with the files you have to change some other options -- your partitioning software *may* work, or again use DiskPart. You probably don't need more than a drive letter though to resize the partition or replace the contents...
To re-size the partition [using Windows or a partitioning app] you'll need to make all hidden partitions visible [assign a drive letter]. To replace or add the boot files, to the Boot or any other partition, use the command line BCDBoot -- note that you have to run it in 10 for 10's boot files, though you can use another, non-running copy of 10 as the source for those boot files, and the target for the boot files can be pretty much any partition.
Related links, though not the most recent...
technet[.]microsoft[.]com/en-us/library/hh824839.aspx
technet[.]microsoft[.]com/en-us/library/hh825686.aspx
technet[.]microsoft[.]com/en-us/library/Cc766465(v=WS.10).aspx
technet[.]microsoft[.]com/en-us/library/dd744347(v=ws.10).aspx
technet[.]microsoft[.]com/en-us/library/hh824874.aspx
technet[.]microsoft[.]com/en-us/library/cc731662.aspx
winhelp[.]us/restore-windows-re.html