New Build 6688 vs. Last Build 6673 - I'm sticking with 6673
Just wanted to mention that I, too, am having many difficulties with Build 6688.
I am running two laptops, Windows 8.1, 64-bit. SSD's and plenty of RAM.
Build 6673 was working just fine since I upgraded to it back in May.
After upgrading to Build 6688, my systems became unstable and would lockup for no seeming reason; maybe once per day.
In addition, I'd still be getting those popups telling me that a newer version was available. I'd start TI2014 and check the Build number and sure enough, it was 6688.
So, now Build 6688 has been uninstalled and I'm using Build 6673 again.
Works for me.
Chuck

- Log in to post comments

Hi Christopher,
Release notes can always be found in your account under downloads and the Download older bulds and read version history. Strangely you will also find the release notes for the latest version there.
The fixes for build 6688 are:
[TIMMXV-108] Online backup stops responding while reconnecting to Acronis Cloud.
[ATIHXOXIV-3527] The SyncAgent service fails to download file from Acronis Cloud. The error is "Invalid usage".
[ATIHXOXIV-3897] Clicking "Download User's Guide" downloads an old User's Guide.
[ATIHXOXIV-3899] Nothing is uploaded to the beta_report server due to certification changes.
[ATIHXOXIV-3576] After a network connection is lost, the Reconnecting... state lasts for an hour, and the backup fails.
[TIMMXV-1441] The links to contact support are outdated.
All minor IMHO.
Best regards,
Pim
- Log in to post comments

Ok, now I remember, it is a strange place for it.
Thanks PIM.
- Log in to post comments

You're welcome Christopher! Via somebody else's contribution in another thread I recently discovered that the changes for build 6688 are exactly the same as for build 6673. Apparently the only difference between build 6673 and 6688 is that since build 6688 Universal restore is no longer included in the program itself nor in a recovery medium created by the program. One has to download a separate ISO for that. I have no clue why that is. It seems better to me to just stick with build 6673.
- Log in to post comments