DLL fails to register ATIH 2011

I have fixed a problem on Acronis True Image Home 2011 that has been bugging me for about six months so I thought I would let you know how I did so.
I am using Windows 7 64 bit Home Premium.
When I first installed the new version of TIH 2011, I got an error message stating that C:\Program Files (x86)\Acronis\TrueImageHome\x64\backup_cpl_control.dll could not be registered.
I tried to manually register the file using the Run command regsvr32 "C:\Program Files (x86)\Acronis\TrueImageHome\x64\backup_cpl_control.dll"
but was unable to register.
I also tried adding the full path to regsvr32: C:\Windows\System32\regsvr32 and this was still unsuccessful.
I tried the 64 bit regsvr32: C:\Windows\SysWOW64\regsvr32 and this was also unsuccessful.
This failed registration of the dll causes the issue in Windows where if you right click on a file, select the file properties menu and then click on the previous versions tab, this would crash explorer.

Today I searched the registry for references to backup_cpl_control.dll and found it several times, so I realised that my attempts to register had been at least partially successful.
So, I did a Windows Run of regsvr32 / u to unregister the dll using both the
64 bit and the 32 bit regsvr32. I used the full path:
C:\Windows\System32\regsvr32 /u "C:\Program Files (x86)\Acronis\TrueImageHome\x64\backup_cpl_control.dll"
C:\Windows\SysWOW64\regsvr32 /u "C:\Program Files (x86)\Acronis\TrueImageHome\x64\backup_cpl_control.dll"
It seemed promising because as Windows processed each command Windows showed me a message stating that the dll had been successfully unregistered.
I had not seen the message before during previous attempts.
After I did this I then restarted the PC, activated the Run command and typed in C:\Windows\SysWOW64\regsvr32 "C:\Program Files (x86)\Acronis\TrueImageHome\x64\backup_cpl_control.dll"
Windows showed a message stating that the dll had been successfully registered.
So, now the versions tab in the properties menu is operational and fully functioning.
I think that maybe I had caused the issue by inadvertently using a 32 bit command on a 64 bit dll. It might be that by default if you do not include the full path to C:\Windows\SysWOW64\regsvr32 Windows uses C:\Windows\System32\regsvr32.