ACPHO Runtime Issues
Two ACPHO Run Time Issues.
I have been using True Image for many years. Until recently on a 5-year-old Dell laptop with 1TB HDD running Windows 10 and an external WD My Book 2T HDD. Several months ago I replaced them with a new, faster Dell laptop with a 1TB SSD running Windows 11 and a faster WD My Passport 2TB HDD. At that time TI was not certified for Windows 11 so I upgraded to ACPHO. Throughout this entire time I have done a full back once a week when my computer is otherwise idle and disconnected from the internet and the backed up data has remained around 360GB. So now I have faster equipment, but ACPH run times are more than double those I had with TI. Perhaps this is because, by default, Win 11 encrypts data storage, ACPHO does not, so there is a de-encryption runtime burden. Is this so, or is ACPHO just slower?
Also, while the operating/processing environment is the same the ACPH run times vary significantly. Here are the log entries in minutes beginning April: 271, 209, 239, 198, 337, 165, 254, 139. What can account for this?


- Log in to post comments

Thanks, Steve. I agree that ACPHO is operating under the Windows OS making the process transparent but the stored encrypted data must be unencrypted in the process. I have no idea what those added steps due to the end-to-end runtime. I was looking at my current runtime vs my experience with ATI under Windows 10. However, it certainly isn't worth opening a support ticket, Thanks again.
- Log in to post comments