AMD Catalist Can't Install - Application Install : Install Install Package Failure

[Liyanagedlas]

When i install the AMD Catalist driveres, it says " Application Install : Install Install Package Failure". I tried cleaning all old drivers by using Driver Fusion and install it again and again. But it didnt work for me.
I have HP G42 Notebook.

Please somebody help me on this....

 

[Hysteric33]

As soon as I try to navigate to %SYSTEMDRIVE%\AMD\AMD-Catalyst-Omega-14.12-With-DOTNet45-Win7-64bit\Packages\Apps\CIM\Win64 it says "The system cannot find the path specified" and I double-checked my copying. Is there something special I need to do to get the file?

This directory is created after amd-catalyst-omega-14.12-with-dotnet45-win7-64bit.exe is downloaded from AMD's site and executed. If it has not executed successfully, the directory will not exist.

Let us know if this helps.

myitguy, I know this is a few days past but hopefully you check back.

First of all I want to shoot you a thanks for the write up and documentation you did. It was very easy to follow along with.

I was able to go ahead and change all instances of NewBinary22.dll to NewBinary21.dll as you said and tried installing from the edited MSI file. Sadly I received a fresh error 1723. I went and checked it out in Event Viewer and here was the specifics:

"Product: AMD Catalyst Install Manager -- Error 1723.There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action SetInstallDir, entry: SetInstallDir, library: C:\Windows\Installer\MSICEFD.tmp"

Maybe I messed up along the way but any further help is greatly appreciated!

 

[myitguy]

Hey Hysteric33

The SetInstallDir Custom Action is controlled by the DLL we are correcting. Can you confirm that all Custom Actions in the CustomAction table, including the SetInstallDir Custom Action, within the MSI have been changed to NewBinary21.dll?

Thx

 

[Hysteric33]

Hey Hysteric33

The SetInstallDir Custom Action is controlled by the DLL we are correcting. Can you confirm that all Custom Actions in the CustomAction table, including the SetInstallDir Custom Action, within the MSI have been changed to NewBinary21.dll?

Thx

Thanks for the quick response. I went ahead and double checked just to make sure. Here's a screenshot: MSI Edit

Just checking to make sure this is what you were referring to.

 

[myitguy]

Thanks for the quick response. I went ahead and double checked just to make sure. Here's a screenshot: MSI Edit

Just checking to make sure this is what you were referring to.

That was exactly what I was looking for.

Forgive me if you've already done this, but let's take a step back and make sure we are tackling the same problem. To do this we should verify NewBinary21.dll within the MSI is the 64-bit version and that the installer is failing where we believe it is.

In the issue document I posted earlier..

..please use Understanding the Issue, Step 3 to get the log file for the installer. Attach the log to this forum post.
..please use Understanding the Issue, Steps 8-13 (changing NewBinary22 to NewBinary21) to verify the DLL we are going to use is the 64-bit version. There should be no error stating "Error: Modules with different CPU types were found."

 

[Hysteric33]

Thanks for the quick response. I went ahead and double checked just to make sure. Here's a screenshot: MSI Edit

Just checking to make sure this is what you were referring to.

That was exactly what I was looking for.

Forgive me if you've already done this, but let's take a step back and make sure we are tackling the same problem. To do this we should verify NewBinary21.dll within the MSI is the 64-bit version and that the installer is failing where we believe it is.

In the issue document I posted earlier..

..please use Understanding the Issue, Step 3 to get the log file for the installer. Attach the log to this forum post.
..please use Understanding the Issue, Steps 8-13 (changing NewBinary22 to NewBinary21) to verify the DLL we are going to use is the 64-bit version. There should be no error stating "Error: Modules with different CPU types were found."

myitguy, thanks for sticking with me

I sneaked away from the kiddo and tried everything from step one. I have no issues up until step 12-13 of Understanding the issue.

When I open up Binary.NewBinary22 in dependency walker I receive this log instead of what you showed.

In addition I went ahead and tired Binary.NewBinary21 and received this log.
It seems somehow that my results are reversed and a tad different if not very similar.

**Edit - - Sorry I forgot the install log but here it is: Install Log

 

[myitguy]

myitguy, thanks for sticking with me

I sneaked away from the kiddo and tried everything from step one. I have no issues up until step 12-13 of Understanding the issue.

When I open up Binary.NewBinary22 in dependency walker I receive this log instead of what you showed.

In addition I went ahead and tired Binary.NewBinary21 and received this log.
It seems somehow that my results are reversed and a tad different if not very similar.

**Edit - - Sorry I forgot the install log but here it is: Install Log

It looks to me that they may have fixed their installer. Can you try running the install without doing the binary rename and provide the log file?

Thx

 

[Hysteric33]

myitguy, thanks for sticking with me

I sneaked away from the kiddo and tried everything from step one. I have no issues up until step 12-13 of Understanding the issue.

When I open up Binary.NewBinary22 in dependency walker I receive this log instead of what you showed.

In addition I went ahead and tired Binary.NewBinary21 and received this log.
It seems somehow that my results are reversed and a tad different if not very similar.

**Edit - - Sorry I forgot the install log but here it is: Install Log

It looks to me that they may have fixed their installer. Can you try running the install without doing the binary rename and provide the log file?

Thx

The log I posted was of a fresh install attempt before messing around with any of the dlls. The software wouldn't error out if it couldn't detect my card would it? I know that sounds odd but its a new system I just built with an XFX R9 280X. No matter what I do I cant get it to display nor can I install the drivers. After uninstalling the onboard, resetting CMOS, and also cleaning all drivers using DDU I still can't get any display off the card. It boots just fine off of the mobo.

For troubleshooting I went ahead and borrowed a 750TI and following the same steps had no issues getting it to work and display in under 5 mins. I also had zero issues installing NVIDIA drivers. Really makes me sad because Ive been a long time AMD user haha.

Oh well sorry to go off on that tangent. I just think I have a bad card along with the driver issues.

 

[Simon Ayres]

This maybe a silly question and i am to lazy to read all the posts to see if it has been asked but, are you sure you are trying to install the laptop drivers and not the desktop drivers?

http://support.amd.com/en-us/kb-articles/Pages/737-28041SupportforATIMobility.aspx

 

[Aki Lan]

This prolem is due to the following reasons:
1. Username
If u have a special charector in the user name, (like #god) then it causes the problem because your user directry in C drive will be named as same as your USER NAME/ ACCOUNT NAME. Install manager will not find its path for app data, if you used special charector. Therefore change your name without special charector. you cant rename it. You should clean install your OS once again..

2. When downloading verify for laptop/desktop model

HOPE IT HELPED!

 

[cheshster]

Hi myitguy, I hope you see this. I've been getting this error as well, and found your guide. I started following it, but I'm getting a different error in step 4 of the Understanding the Issue section:
Error 1310. Error writing to file C:\Program Files\AMD\CIM\Config\DLMServer.cfg. Verify that you have access to that directory.

I've checked and that directory does exist, but it's empty. Do you have any idea what I can do to get around this and get the drivers installed?

Thanks so much!