Most Valuable Professional
Group: Forum Members
Windows Defender is first-party anti-virus, so no issues there. Thinking about it more, I suppose I may never have noticed this since I may have been looking only at total CPU utilization rather than per-core, but as Task Manager is showing, your real bottleneck is still your disk, and if your destination is a spinning hard drive rather than an SSD, that 559 MB/s would be read speed off the source SSD. I suspect Reflect may be reading somewhat ahead and compressing, then waiting for the destination disk to catch up, since spinning disk write speeds normally top out around 120 MB/s. You would be able to see that if you go to Task Manager > Performance and check the listings for your disks.
Again, it’s possible that Reflect simply isn’t multi-thread enabled for this operation, in which case it wouldn’t be possible to spread the load from Reflect out across your other cores; that’s something that an application has to support. Windows can’t just do that on its own. And if that’s the case, the reason could be that there simply wouldn’t be any benefit to multi-threading this operation. Macrium would have to confirm, but in the meantime, there’s no setting you’re missing, and your limiting factor is that your source disk read speed is much greater than your destination disk’s write speed.