ASRM Issue
I like to reinstall (deactivate and reactivate) ASRM after each update in the event that there were any improvements or bug fixes. After doing this with update 6559 and booting with F11 I receive the message "True Image has not found any hard disk drive." The event error code is 0x000101F4+0x000A01FD. The Acronis KB provides no information on this code. The same issue occurs with the recent 6569 update.
Most people might not use ASRM but this is the method I prefer for creating backups since the Windows environment has been historically problematic vs. ASRM.
I was able to restore full ASRM functionality by using the bootable media to reinstall ASRM. It would be nice if this worked properly from Windows without the need to burn a disc.


- Log in to post comments

Thank you for that suggestion. I submitted feedback along with a system report.
Would you mind sharing the reason you decided to stop using ASRM? I only encountered one issue prior to this that made my Logitech wireless keyboard and mouse function erratically. I used the bootable media to reinstall ASRM in that case also to resolve the issue. It seems that using the bootable media to activate ASRM is the best method but I don't understand why the Windows utility does not offer the same functionality.
- Log in to post comments

The main reason I stopped using ASRM was that it exposed some of my hidden drive partitions, in particular my Dell laptop Diagnostics and Recovery partitions and caused these to have drive letters allocated.
I reported this to Acronis at that time and had a case number allocated but eventually was told that they couldn't reproduce the problem on their lab machines even though I have seen other users reporting the same issue since.
In the longer term, I have adopted a different approach by using the free EasyBCD utility and adding extra menu options to the Windows boot menu at start time - this allows me to boot from either the standard, linux based, ATIH rescue media or from the Windows PE rescue media, or from Macrium rescue media etc.
- Log in to post comments

Hello, dcsang!
Let's see if I understood you correctly.
- You had an older build of True Image installed. (Which build, by the way? An older build of True Image 2016? Or was it True Image 2015?)
- ASRM was activated an working fine
- You updated True Image to build 6559
- After that you deactivated, then activated ASRM
- Then you rebooted your machine and pressed F11 to get into ASRM
- The error "True Image has not found any hard disk drives" is shown and the machine boots back into Windows
Please correct me if I'm mistaken.
You also said that you managed to get ASRM working by activating it via Bootable Media. What happens if you deactivate/activate ASRM in Windows? Does the issue reappear?
- Log in to post comments

Hi Dmitry,
The steps you outlined are correct. I upgraded from ATI 2016, the build prior to 6559. I will deactivate and reactivate ASRM from Windows tonight and report back.
Thanks!
- Log in to post comments

Unfortunately, deactivating and reactivating ASRM from Windows using build 6559 causes the error message to reoccur.
- Log in to post comments

dcsang,
I note from your first post that you are having this issue with build 6559 and 6569. When performing the installs, did you use the procedures in the link below:
https://kb.acronis.com/content/48668
The link includes a cleanup utility that should be run after uninstalling. If you did not use the cleanup utility, then I recommend downloading the utility from the link above, and uninstalling, cleanup, and reinstalling build 6569.
If you, in fact, did follow the procedures in the link above then...I'm stumped and at this point don't have a recommendation.
FtrPilot
- Log in to post comments

You are correct, my prievious post should have stated build 6569, not 6559. I am pleased to report that after following the instructions in the referenced KB article and reinstalling build 6569, ASRM now functions correctly when activated from Windows. I suppose it is good practice to utilize the cleanup tool when installing/upgrading to new versions. Thank you!
- Log in to post comments