Mounting an image after latest update fails.
Unfortunately, it looks like the FTP credentials provided by Slava previously have now expired although many users have already downloaded the tibmounter patch version 2637 and used it successfully.
Copy of the zip file attached below for those who need to get this now.
Posted here directly in this thread now - it has been .zipped because the .msi file extension cannot be attached directly in the forum. Zip file contains the original tib_mounter_setup_2637.msi file.
It worked, thank you
Currently I'm not able to view the contents of a TIB file (Full or Incremental) created by TI 6571. Yesterday I installed tib_mounter_setup_2637 and still cannot view the contents. In Explorer2 (Windows Explorer replacement) I double-click on a TIB file, the hour glass spins for a few seconds, in Explorer2 the window refreshes and there is no data content in the window.
I just tried using Windows Explorer and I can open the TIB file, thus Explorer2 seems to have an issue.
jgt1942...is Explorer2 a Microsoft product? Can you provide a link for the version you are using? Thanks.
The issue with Explorer2 is also documented here https://forum.acronis.com/forum/110884#new post#21.
I have the Pro version (3.2.0.2) and per the website this is the latest version. For me it is a must have application.
Thanks Steve and Bobbo for uploading the tib_mounter_setup patch. It still seemed to be necessary even when using Acronis True Image 2016 6581, to mount incremental images.
If you "upgraded" over a version that had the issue, chances are, you'll need to keep applying the patch. The upgrades, do not seem to update every single file for instance, I've noticed that after upgrading, when creating WinPE rescue media, those files are still the previous version).
Another folder that does not seem to get upgraded, or even removed with the clean tool is the .tib mount cache in the user profile - I have reported this to Acronis recently as well.
%userprofile%\appdata\local\VirtualStore\programdata\acronis\trueimagehome\database
I actually installed 6027, then installed 6581, found that mounting incrementals did not work, then uninstalled 6581, then installed 6581, tried mounting again (which still didn't work), then installed the patch. I did not use the clean tool. Seems like Acronis should just put the patch in the regular releases (or if they're already doing that, fix the update problem that you mentioned).
I'd suggest submitting feedback through the app, directly to Acronis as you do have a point. However, I suspect that it would not get included since the patch is designed to help a select few with the issue and may cause trouble for others who aren't having this type of issue. Ultimately, any upgrade/update should update all files and not leave older or leftover files in place. It seems like many users also don't use the right-click and "run as admnistrator" feature of Windows 7 and newer to do installs, repairs or uninstalls. As someone who works in IT, I would recommend that everyone do this for every install, upgrade, or uninstall. Unfortunately, unless you do this, you are not giving full admnistrative access to the applications.
As a simple test, open a regular command prompt with an administrator account and type:
nbtstat -RR
Failed Release and Refresh of Registered names
Access is denied
Failed Release and Refresh of Registered names
Access is denied
Failed Release and Refresh of Registered names
Access is denied
now, right click command prompt and type it again
nbtstat -RR
The NetBIOS names registered by this computer have been refreshed.
You'll see that due to how UAC works, only when the addditional step of using the right-click and "run as administrator" option is put to use, can this basic command be applied. The same can be true for any application that needs to change system files, permissions, or services and I suspect this is why some people have more trouble than others as they are not aware of this security feature of Windows UAC.
I'm stunned this is still an issue. Acronis - your software is crap, filled with bugs that persist literally for years. It's July 4th 2017 and this bug was reported two years ago - AND IT'S STILL NOT FIXED.
Your devs post random fixes for bugs which still exist in your app - then turn off the FTP credentials so that anyone trying to research this gets rejected and has to beg for the file.
I am a systems engineer and have been for over 20 years. Wanna know what I see? I see a disorganized development team with no clear leadership - I see executives and managers that have no idea what goes on behind the scenes, and based on this and all the bugs in your production code - I see a stinking pile of dung which in the end was a mistake, and I would be better off cutting my losses and switching backup software.
David, welcome to these User Forums (note the emphasis on User!)
Which particular problem are you referring to in your post above?
Which version/build of ATIH 2016 do you have and are you experiencing a problem?
The reality, as I understand it, is that the tib_mounter patch was needed for older builds of the product but should not be needed for the latest build 6595 of ATIH 2016. I have not seen any recent reports from users in these forums for this issue.
The actual patch is still available and can be found via the MVP User Tools and Tutorials link on the right where it has been placed on Google Drive within the Log Viewer folder.
If you want to really make your frustration with this Acronis product known, then please use the Feedback tool provided within the GUI or send a private message to Gaidar, General Manager of Acronis True Image, who I am sure would be happy to discuss your grievances with you. As for us users in this forum, sorry but there is little that we can do to address the concerns you have raised.