Problem installing a test version

[GTHER]

Hello,

I tried to install VTUNE AMPLIFIER XE in order to evaluate, but the installation failed with the following message:

Windows Installer failed to configure product:

Error message: An error occured during the installation of assembly component 98CB24AD-52FB-DB5F-A01F-C8B3B9A1E18E. HRESULT: 0x800703F8.

Error code: 1603

File name: msvcrt_x86.msi

Installer logs location: C:\Users\Greg\AppData\Local\Temp\pset_tmp_amplifier_xe_2016_Greg\2015.09.21_22.07.37_00000b48\log\

I have a version of MS Visual Studio installed, so I do not understand why VTUNE would require to install another version of MSVCRT (unless this is an older version), nor do I understand why it would fail the installation.

Is there anyone around from intel who may help me with this problem?

Thanks in advance

[Peter_W_Intel]

I don't know what MS Visual Studio version you installed. Now 2016 product supports VS2012, VS2013, VS2015.

You need to run VTune_Amplifier_XE_2016_setup.exe as administrator, I think.

I suspect, this is not a defect from our product, it might Windows Installer Service issue, see -

KB2918614 breaks Windows Installer Service:
http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_install/kb2918614-breaks-windows-installer-service/3d75a1c2-114a-4241-a527-35b536edc158

It seems that you need to remove KB2918614 to restore the system. Solving other installation issue can refer to - http://www.winway.com/main3/support/kb/Q000201.aspx

Is there any firewall/anti-virus to prevent of installing this product? Is it possible that you can try in other machine? Or you might attach installer log for diagnose this..

Thanks, Peter 

[Dmitry_P_Intel1]

Hello,

Is it possible to provide the installer log fromC:\Users\Greg\AppData\Local\Temp\pset_tmp_amplifier_xe_2016_Greg\2015.09.21_22.07.37_00000b48\log\

to loo at?

Thank you, Regards, Dmitry

[GTHER]

Hello Peter and Dmitry,

Thank you for your help.

I tried to reinstall while executing as administrator, but it failed again.

But finally, I reinstalled it on a fresh new system and it worked. It seems that my Windows installation system was indeed buggy (corrupted?) on the previous system.

Thanks for the help and for pointing me in the right direction.