[SOLVED] TI-Home-2010 Installer Error 1603

This is absolutely crazy! I can't install ANY version of ATI because the same status 1603 MSI error occurs with them all, including the ATI Home 2009 version that I had previously UNinstalled before attempting to install the new ATI Home 2010 version.

And, of course, I'm not able to use any uninstallers (neither MSI nor Revo) because there's nothing listed there for them to uninstall.

Considering the number of similar reported instances here, surely somebody at Acronis must have some better idea about dealing this "Catch-22" situation by now.

Nevermind. It ain't easy finding the authoritative answer amongst all the verbiage about turning off AV and so on, but there actually is one in the knowledge base at http://kb.acronis.com/content/1647 that provides detailed info on analysing the installer log and correcting specific issues.

Acronis people, you really had me going there for a while. I would strongly suggest that it would be in your own best interests to do something drastic about your product uninstall process and its "leftovers" that seem to be causing a lot of upgrading pain and a VERY BAD IMPRESSION for a company having "Compute With Confidence" as its motto.

Try running CCleaner to clean out temporary and temporary internet files. Then see if you can restore a Windows Restore point that is dated before you installed the 2010 version. Next try installing ver 2009 once more.

Richard,

You say you've solved the problem, so exactly what did you do to solve the problem and what exactly do you believe was the cause?

Yep, I and others would like to know too.

Basically, as most posters of similar problems here seem to understand in a general way, it is due to installer problems -- or, more precisely, a problem with the Acronis UNinstaller failing to clean out previous versions completely. Any "leftovers" are then detected for subsequent (upgrade) installation attempts and those attempts are thus blocked.

THE DETAILS OF EACH CASE WILL BE DIFFERENT! So, knowing that much, the trick is then to discover the precise nature and location of the culprit. That, in turn, requires the creation and careful analysis of a verbose installer log and that's also where the info in Acronis KB article 1647 (linked above) is absolutely essential.

In summary, I solved the problem by following instructions. My difficulty was finding the relevant instructions which don't seem to "pop up" readily in response to key word searches. Direct Acronis support responses are spotty at best, and the search is complicated by the fact that it does show up a lot of questionable "help" info here and elsewhere.

Anyhow, here's the relevant extract from the installer log that I attached to the first item in this thread:
==
1: MSIGEN:CheckForUpgradeCode {6152344B-3E2F-4576-8139-5C8DDF65E4E7}
1: MSIGEN:Check For Upgrade Code started {6152344B-3E2F-4576-8139-5C8DDF65E4E7}
1: MSIGEN:Enumerate through related products
1: MSIGEN:Determing context for {7DC265E8-1558-43D4-807B-31205936DCF1}
1: MSIGEN:Error occured during CheckForUpgradeCode for {6152344B-3E2F-4576-8139-5C8DDF65E4E7}: 1605
Action ended 13:21:37: DetectMsiMajorUpgradables. Return value 3.
==

And here's the relevant extract from the Acronis KB article modified to use this example:
==
In the above Example the string is:
1: MSIGEN:Determing context for {7DC265E8-1558-43D4-807B-31205936DCF1}

After that, take the first part of the value in brackets (in Example it is 7DC265E8), rewrite it in the reverse order (Example: 8E562CD7), then open the following branch of the system registry on the problem machine:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UpgradeCodes
HKLM\SOFTWARE\Classes\Installer\Features
HKLM\SOFTWARE\Classes\Installer\UpgradeCodes

Look for the key starting with the reversed part of the code we got (Example: 8E562CD7). After that make sure the rest of the key name digits also match the other parts of the entry found in the MSI log, IN REVERSE ORDER.

Having found the registry key, you should delete and start the installation of the Acronis product over again. This solution applies only to cases in which there was a previously installed Acronis product on the machine.
==

REPEAT WARNING: THE DETAILS OF EACH CASE WILL BE DIFFERENT! So analyze your own installer log carefully and follow the RELEVANT instructions for your own specific results. Random efforts are unlikely to be helpful and may actually do more harm than good, especially deleting wrong items in your system registry.

The real solution, of course, is for Acronis to fix their blankety-blank (un)installer so that these kinds of problems don't happen in the first place!!! Their installer being blocked by things that their uninstaller doesn't get rid of is utterly absurd. In the circumstances, their abandonment (more or less) of any real direct support is understandable, but definitely NOT a good sign.

Hi Richard.

Your solution is exactely what I have been looking for a long time.
Thanks to your comment I solved my problem with the ATI 2010 installation - it works now!
You are great!

Thanks again and regards!

Zencooler

Hi Richard..... I had the same error, and you line by line solution solved the problem.... In my case, "mea culpa". I deleted the whole subdir [ c:\windows\installer ] by mistake.... and some, but NOT ALL programs that depend on their duplicating themselves in that section will no longer uninstall or new version 'install'. TI Home was such an issue. I've resolved most updates, but this key, reading backwards stumped me.

Hate to say so, but all this convoluted code is turning people into hackers.... if you are going to use your machine with many installed programs. Again 'THANK YOU' -= CB =-

I had a problem like this when I went to install the software updates. It would not install them. After seeing some similar problems posted for a McAfee product, their solution said to go check a key in the registry to make sure it had been upgraded to the new value properly.

I looked in my registry under the SOFTWARE and acronis/trueimage folder. As I was clicking through the registry in this area, there was one item I clicked on that popped up a message saying I didn't have permission to view the key. For me it was the "scheduler" key. This happened even though I was running regedit as an administrator.

What I then did was go into the permissions (right-click) for the key, click advanced and had the administrator take ownership of the key (since there was no way to change the permissions unless I took ownership first).

I have no idea why the permissions were so crazy on this key and even the administrator didn't have permissions to view it. I suspect some leftover crap from a previous install or uninstall. However having the administrator take ownership allowed the update to install correctly finally. I figure the software must have been trying to read/write to this area and didn't have permissions so it crapped out with that 1603 error, even though I was running as the administrator.

Weird problem.

ATI 2011 install error 1603.  

fwiw, I also encountered the same error when trying to install ATI 2011 Home (build 6868) under XP. I previously had ATI v11 on my computer.

I couldn't find an ATI v11 cleanup tool, but eventually stumbled across this thread while googling for a solution.

From my ATI 2011 Home install error log:

1: MSIGEN:CheckForUpgradeCode {6152344B-3E2F-4576-8139-5C8DDF65E4E7}
1: MSIGEN:Check For Upgrade Code started {6152344B-3E2F-4576-8139-5C8DDF65E4E7}
1: MSIGEN:Enumerate through related products
1: MSIGEN:Determing context for {7DC265E8-1558-43D4-807B-31205936DCF1}
1: MSIGEN:Error occured during CheckForUpgradeCode for {6152344B-3E2F-4576-8139-5C8DDF65E4E7}: 1605

I deleted the keys beginning 8E562CD7 but ATI 2011 Home still produced the same error. After deleting the keys beginning B4432516, ATI 2011 Home successfully installed.

I think the problematic keys in question appear to be associated with the 'BartPE Plugin' for ATI v11. Unless I'm mistaken, there doesn't appear to be an uninstall option for the v11 Plugin which perhaps may have prevented this issue from occuring in the first place.

Hi, I solved with this topic the upgrade from TI11 to TI12
My error was 1: MSIGEN:Error occured during CheckForUpgradeCode for {52593AD8-556C-4CB5-AE17-F3 CC FC D6 B3 33}: 1605
and I've find the registry key 8DA39525-C655-5BC4-EA71-3FCCCF6D3B33 deleted and install i successfull.

Thank you a lot

This is stupid but works.

Turn off machine right before the "rollback" message in the install status. Shut it of at first sight of the message. Independent of machine speed this occurs at 7.6 % of the time of the entire install time from the point you click "Proceed". For example the install time was 1:45 and the shut of time was near 1:38.

I don't know if you can install an upgrade on top. The above will probably allow this. My machine never had a working version installed.

Don't bitch at me about how stupid this is. I know . . . I tried everything written to solve this including the above. It was my last choice.