With the roll-out of the Anniversary Update for 10 starting today, it doesn't make sense for me to more fully test the software -- over the next week I'll try multiple installations, backups, check the bootable media etc. as I get non-Insider installs updated, try switching off previews in a few copies that have insider previews turned on & so on. The reason I'm posting this is that the new software is out there now, & might show up on the giveaway sites soon, & there are a few things to report you might want to bear in mind.
The setup files as usual include installations of Microsoft C/C++ runtimes -- those installations run 1st, then the actual setup msi file is unpacked & run. The C/C++ runtime files are out of date -- there's a security patch once you get them installed, if you choose to install them.
support[.]microsoft[.]com/en-us/kb/2467173
Myself, I run setup in a VM, then copy the msi file from the user temp folder before closing the setup dialog window. You should be able to do the same thing running something like Time Freeze & then running setup, copying the msi file to a non-protected partition, then abandoning all changes, i.e. with Time Freeze, re-starting. You should also be able to get the msi file using Universal extractor. Running the msi file installs the software normally -- you just skip the extra runtimes which you probably don't need anyway, & if by chance you do, might as well get the current downloads from Microsoft.
The setup process itself is slightly different -- instead of entering a key to unlock the installation, you enter the key when the app's 1st started. I do not know yet if that limits the number of installations.
The software's interface or GUI is a lot different, much simplified. The Program Files\ Paragon Software\ Backup and Recovery 16\ layout.ini file includes a lot of settings I did not see in the GUI itself, but you'd have to test any changes to make sure it took hold -- they may have re-used that file from earlier versions, so not every option may do anything.
Backup and Recovery 16 is notably faster -- it takes less time to complete a image backup -- but it also seems it may be a bit buggy. I had trouble canceling in progress backups, & had a problem where changing the default settings did not change the way backups happened -- it only took hold after I stopped trying to run a single backup & created a recurring job. Backing up the same partition using the old version 15 & the new 16, version 16 produced slightly smaller files when compression was set to normal [all other setting were also the same].
A couple of times the backup progress showed 100% in 16, it said a few seconds were remaining, and Task Mgr. showed no activity -- once closing the software showed a warning that data might be lost. I found something that I've never checked before, & will have to do more testing... I found that backups of the same 2ndary partition were a slightly different total size using v.16. It could be because I initiated the backup different ways [I wasn't testing for this], & it could be that earlier versions [e.g. 15] did this too [I never looked]. And it could mean an error, or it could mean nothing at all.
Like earlier versions, Paragon Backup & Recovery 16 lets you create the backup image archives in several different virtual hard drive formats. I did not fully test Microsoft's VHD or VHDX yet, but the estimated time to completion before I quit was well over 1.5 hours, for a backup it managed using the Paragon pvhd format in slightly over 12 minutes.
Finally, I came across something new using both versions 15 & 16... As a matter of course I check Task Mgr. once the backup's running to make sure security software isn't slowing the process down. Yesterday Bitdefender was slowing down 15, & McAfee LiveSafe was slowing down v.16. My guess is that someone(s) uploaded a definition or definitions to VirusTotal that both security software companies incorporated, quite possibly without much or any testing [it's normal to want to get the protection out there ASAP]. Everything was fine once I added exceptions for the Paragon software in the security software, but I wanted to mention it in case you wanted to take a look, if/when you ran Paragon apps.