Skip to main content

Install Problems after Update to build 7046

Thread needs solution

ATI 2010 Home with PlusPack.

I updated from build 6053 (the initial install) to build 7046 yesterday (April 8). Although it seems to be functioning OK it does show one weird attribute whenever I start it up. That is, the ATI window appears but it is completely blank for several seconds and then it finally fills in. Today I noticed that ever since the update, whenever I start ATI it get 8 MsiInstaller errors. They come in pairs and there are 2 pairs for ATI and 2 pairs for the PlusPack.
I have attached screen shots of one pair (they happen to be for the PlusPack but they are like the ones for ATI itself).

The first error of each pair is MsiInstaller claiming that it has successfully reconfigured the product.
The second error of each pair is MsiInstaller claiming that it has failed to connect to server.

I did the install of the updates with antivirus/spyware stuff turned off.

Should I just try running the 7046 installers again?

--Larry

Attachment Size
AcronisInstallError-edit.jpg 120.23 KB
AcronisInstallError2-edit.jpg 102.92 KB
0 Users found this helpful

One of the normal troubleshooting procedures would be to run a repair on the install. You can start the install program and one of the options is a repair.

As for the connecting to server, you might disable the new Acronis check for updates which now look for updates each time you start TI. I have that feature turned off since I frequent the forum often.

I did the "repair" operations on ATI and PlusPack. Did not help at all.

However, as soon as I turned off the "look for updates", the problems went away. I don't know why they are failing after the upgrade but I'm happy to have that issue gone. Thanks for the hint GroverH !

--Larry

Grover,

I've posted this problem previously here . As you can see no response from Acronis as yet.

garyrh wrote:

I have the same problem as you and turning off "look for updates" fixed it.

So it does!

Looks like the code is either in a blocking loop or needs to be in it's own thread. I'd call it a minor buglet. :)