password entry bug when using TI 2021 backup file encryption
Well, this SUCKS (especially as I have to redo and twice re-upload 300 GB of backups)!
When using the password
wSs)yngH,K~I;AbdQZaJQC?i'KET|))*eLi6qF*Ipn/;K t@SiKQ/nRi}|^klP,U:PH*%$<VGwjxj|bJq!x}u;?Tp~y"^5m'Cc|7-yq0[:fi`nD\qd'b3~bJ8JM)7z/sc:+]M];S5iZxj.zO`te=+o 2tMgCpA]Bx]_u2njGn6k>A,pE/!?QbJ`<EZ^q-:%Jbx>Y6bze{Z6Epz(sh>q=Ifn%zYt<_[3Oe#?Co%}} O1qg<B=(Q+#PG=aP2E;Yt~3
to AES-256-encrypt my backups I can, as expected, reconfigure the job and restore files (i.e. the UI accepts the password) but I'm unable to open/mount the resulting *.tib file (password not accepted).
Please find as *.zip attached
- the password in a *.txt (to avoid web form issues of this forum)
- the job definition XML
- the resulting *.tib
I appreciated if you focused on guaranteeing Trueimages core functionality instead of adding loads of crap.
Thanks, Jörg
Attachment | Size |
---|---|
Acronis.zip | 4.91 KB |

- Log in to post comments

You could've recreated the issue at your place in less time than your misleading answer took.
Or you could have had a look in the XML that the backup is validated after creation. Or just read what I wrote: I can restore the backup just fine using the GUI.
edit:
I just change the password until a complex one works for both and redo the backup, way less effort.
Debugging is your job, not mine!
- Log in to post comments

See?! I already found it (w/o all that KB-crap, bc it's one of the most common beginners mistakes of programmers):
Different parts of the software accept different password lengths.
Password can be max 127 characters for mounting a tib file, quite obviously it can be at least 257 characters in the GUI.
So after I did all the work how about you fixed it?
Thanks!
- Log in to post comments

Jörg Silker wrote:You could've recreated the issue at your place in less time than your misleading answer took.
Or you could have had a look in the XML that the backup is validated after creation. Or just read what I wrote: I can restore the backup just fine using the GUI.
edit:
I just change the password until a complex one works for both and redo the backup, way less effort.
Debugging is your job, not mine!
Hello,
I understand that you are frustrated with the situation you encountered.
In order to investigate the issue you're experiencing, it would be helpful if you could provide more specific details about the problem, any error messages received, and the exact behavior you observed, machine logs or to schedule a remote session. This will allow us to better understand the issue and provide you with appropriate assistance.
As mentioned earlier, contacting our support team at the provided link (https://kb.acronis.com/content/8153) would be the best course of action to address the problem, as there aren't any known issues at the moment with the password . Additionally, referring to the knowledge base article (KB) we previously shared (https://kb.acronis.com/content/45806) can serve as a useful resource for troubleshooting steps for this case. All the scenarios should be investigated.
We appreciate your understanding and cooperation. Please feel free to reach out to our support team.
Thank you
- Log in to post comments

Jörg Silker wrote:See?! I already found it (w/o all that KB-crap, bc it's one of the most common beginners mistakes of programmers):
Different parts of the software accept different password lengths.
Password can be max 127 characters for mounting a tib file, quite obviously it can be at least 257 characters in the GUI.
So after I did all the work how about you fixed it?
Thanks!
I can confirm that this issue exists with ACPHO latest build #40338 which I tested by creating a small Files & Folders backup task which I encrypted using a 150 character password, then tried to open that backup archive in Explorer and to paste the same password into the challenge box!
All that happened was that the password entry / challenge box just redisplayed again asking for the password to be entered! There was no error given! I cannot find any logs associated with the action of Explorer in not accepting the 150 character password!
- Log in to post comments

Did a further test with ACPHO 40338 Files & Folders backup using a 127 character password and this time I could open the backup archive in Explorer successfully, confirming the report from Jorg above.
To summarise:
ACPHO (& ATI) allows users to use encryption passwords to create backup tasks / archives of lengths greater than 127 characters but the Windows Shell integration by Acronis with Explorer for opening / mounting archives (.tib / .tibx) does not allow the input of more than 127 characters for the password field. This is a coding issue that Acronis should address!
- Log in to post comments

Hello everyone.
The message was passed to the team so they can test it.
As soon as they provide me a feedback I will update the thread.
Thanks.
- Log in to post comments