Acronis True Image 2017 installation file checksum is wrong?
Anyone else download Build 8058? The "Copy checksum" provides ac045ebad746e79417edf8905aec310a. When I run md5 checksum, I get c292f5e399b9582fe505cf73b1632992.
(My installation got corrupted with the latest issues regarding settings getting lost...)
Thanks


- Se connecter pour poster des commentaires

Thanks for the reply.
After I posted I found that I am not the only one that experienced this:
I installed it even though the checksum did not match.
- Se connecter pour poster des commentaires

Hello CD,
please check your private messages
- Se connecter pour poster des commentaires

On 2/12/2020 I posted the following:
Hello Ms. Ekaterina:
I am having the same issue as seen on this post regarding the MD5 mismatch.
MD5: ac045ebad746e79417edf8905aec310a
File: AcronisTrueImage2017_is.exe (multilingual, build: 8058)
File size: 494 MB (518,238,488 bytes)
Not a match
Do you think this can be corrected. Thank you very much. Tom Burns
Immediately after that message I followed up with a second message and no response.
In fact all the different builds are the exact same file when downloaded and have the same MD5.
C292F5E399B9582FE505CF73B1632992
According to the website, each file should have a different MD5 as follows:
8058 ac045ebad746e79417edf8905aec310a
8053 cf30a0e48b1bccd61703e8b89f0a80f9
8041 0e2f77202fb473f4be6013cbecc52c17
8029 5cd8b6576791e3263c585b6e7ef6b3d1
This does not look good at all.
- Se connecter pour poster des commentaires

Hello Thomas,
the issue has been reported to the responsible team, thank you!
- Se connecter pour poster des commentaires

Hi Ekaterina, I am experiencing the same issue as others have posted in both this and the other linked thread above. I see this issue was escalated by you over 1.5 years ago, but it looks like it still has not been resolved.
When trying to download a newly-registered purchase of True Image 2017 from my account (perpetual license), the same file is provided regardless of which build is chosen and it does not match any of the checksums provided in the acount page (all the same as others have reported above - this testing shows the same results are still happening today).
I'd like to know how to be able to download the correct file(s) for this product.
Thank you
Build 8058
Listed:
ac045ebad746e79417edf8905aec310a 489.7 MbActual:
C292F5E399B9582FE505CF73B1632992 494MB (518,238,488 bytes)
Build 8053
Listed:
cf30a0e48b1bccd61703e8b89f0a80f9 489.7 MbActual:
C292F5E399B9582FE505CF73B1632992 494MB (518,238,488 bytes)
Build 8041
Listed:
0e2f77202fb473f4be6013cbecc52c17 493.9 MbActual:
C292F5E399B9582FE505CF73B1632992 494MB (518,238,488 bytes)
Build 8029
Listed:
5cd8b6576791e3263c585b6e7ef6b3d1 493.9 MbActual:
C292F5E399B9582FE505CF73B1632992 494MB (518,238,488 bytes)
- Se connecter pour poster des commentaires

Dear J,
I'm afraid the issue has been archived since the v2017 is no longer supported. I can send you a direct download link with the latest available build of Acronis True Image 2017 or if you need a particular build version, please send me the number.
- Se connecter pour poster des commentaires

Thanks Ekaterina - that would be great if your link is different than download.acronis.com/AcronisTrueImage2017.exe (space added after 'https://' since link posting isn't allowed, apparently).
It's especially concerning that we can't get a matching checksum from the information at account.acronis.com since this build update is closely related to a security vulnerability with Acronis True Image:
CERT KB 489392 / VU#489392
May we please have an official word from Acronis as to what the proper / official checksum of the file is? It takes only seconds to generate an MD5 checksum, and it appears this question was asked but never answered during the time True Image 2017 was still supported.
Thanks!
- Se connecter pour poster des commentaires