I've had a four-license package for years, nary a problem, and now I'm fully upgraded to Macrium Reflect X.
I've used Reflect full-time since the early free Home days. Quite a few years, actually, using the Home Free version when only working with a single machine. But the past two years I've been doing the four-machine annual option since moving an old brick/mortar family company to a full-time home-based operation. I
love paying for good software!
And I also love Reflect, the software. Never a single issue with
countless life-saving full OS/sys drive restores. It's saved me
SO many times. I do incrementals forever on a daily schedule. Imaging two 4TB NVMEs and an 8TB NVME like clockwork to a RAID6 volume made up of six 8TB QVO SSDs (hosted via an Areca ARC-1883i PCIe RAID card)
I don't have many problems with my primary workstation, very rare. It's the kind of rig/environment where there are very few changes to my staple tool set, the kind of system where loT LTSC makes a lot of sense. But when I do have the rare problem, Reflect is like a literal, bit-perfect time machine.
I have some years in the software dev trenches as well. The random issue I was having, and others have had, will likely get ironed out in future updates.
Reportedly, folks like me never saw the licensing thing until after Reflect 8.1 was EOL'd
For myself, the licensing thing only began when I started using a VPN full-time (Mullvad for the past couple of years). I suspect, and have read, that the same thing can occur when switching frequently between Wi-Fi and Ethernet on the same machine. Makes sense how it could...
The problem was
100% tied to the licensing/activation logic that hinges on the NIC MAC address. Any time I'd change VPN servers, which is all the time, I'd immediately get the license transfer message.
The license routine that runs at Reflect starts each time it's opened after being closed, just "thought" I was using a different machine as it was likely, by default, pulling the MAC address from whatever adapter, virtual or not, was topmost, and generally that's the Mullvad VPN tunnel (a sort of "virtual" adapter). I'm a network/storage geek so the whole thing was more informative than problematic.
I simply followed the Macrium support person's instructions and "hardwired" Reflect to the actual hardware NIC that the VPN tunnel spins off of. Just a simple "reg" command line to add/adjust a single key with specific instructions to use that exact MAC address of my primary, hardware NIC. Obviously, VPN uses a different MAC address one on each VPN server and probably becomes even more problematic if using more hardening like obfuscation and random MAC address...
All good, though. Still haven't dove into ReflectX. I did, briefly but the license thing I now have a solid fix for kept making me think it was due to one of the four machines on my network so I just removed Reflect from all but my main rig and still using vanilla Reflect.
Reflect X seemed much faster, though. Looking forward to migrating to it across all my rigs.
Thanks for the comment.
~s