- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As far as I can see, all of the 2016 beta components (which were working) have been removed successfully.
It seems to be possible to install C++ and Fortran Intel64 compilers, but not the full psxe (Windows 8.1, VS2012/2013/2015), which dies before reaching the first menu about what is to be installed.
Will attempt to attach the log.
- Tags:
- Development Tools
- Intel® License Manager for FLEXlm*
- Intel® Software Development Products Registration Center
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is an Advisor beta folder still there although all the removals have been run as far as I know.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm also having the online and offline installers both die on a Windows 7 test bed system. Another quality release, Intel!
My experience with Parallel Studio installation is now so bad that I have to test install on an old system before risking it on my main development systems. The "updates" are often uninstalling the applications and/or leaving them partially broken. It looks like the QA problems are going to persist with 2016. Ack!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Tim,
Thank you for the report and submitting the install log. I escalated this issue to development.
Regards,
Devorah
Intel Developer Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tim Prince wrote:
There is an Advisor beta folder still there although all the removals have been run as far as I know.
Root cause is previous Amplifier 2015 Update 2 package was incorrectly removed (seems some tool for msi cleanup was used).
Please install again and then remove Amplifier 2015 update 2 package (w_amplxe_pu_2015.2.022\webimage\VTune_Amplifier_XE_2015_update2_setup.exe).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Stuart M wrote:
I'm also having the online and offline installers both die on a Windows 7 test bed system.
In order to get rid of broken installations a repair/remove usually helps: Start the installer of the broken installation, choose 'Repair'. After successful repair run 'Remove'. A removal of a broken installation alone doesn't help. Sometimes it's not easy to identify what product versions have been installed on a system, but a look at c:\Program Files (x86)\Intel\Download\ helps. In case of doubt, you can run one installer after the other and repair/remove unused products. May become a very lengthy task, but in general no other choice to sanitize a system.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That recommendation verifies the finding that somehow it wasn't possible to remove the earlier version cleanly:
Intel® VTune™ Amplifier XE 2015 Update 2 for Windows* Setup Wizard ended prematurely because of an error(s).
Windows Installer failed to configure product:
Error message: The full package of Intel VTune Amplifier XE 2015 Update 2 is already installed.
Error code: 1603
File name: ps_he_cli.msi
Installer logs location: c:\Temp\pset_tmp_amplifier_xe_2015_Tim\2015.08.28_12.10.29_00000198\log\
To install this program at a later time, run Setup Wizard again. Click the Finish button to exit the Setup Wizard.
However, re-installing evidently isn't an option. I still don't see any clear way for the uninitiated to know which version didn't remove cleanly and how to deal with it. I will try to add than remove Amplifier to the current 2015 update 4 installation, then if that doesn't do the job, I will remove all Intel tools and try to install 2016.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I could install all or any components of 2015 update 4 and remove them without helping the issue of 2016 Amplifier.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Devorah H. (Intel) wrote:
In order to get rid of broken installations a repair/remove usually helps: Start the installer of the broken installation, choose 'Repair'. After successful repair run 'Remove'. A removal of a broken installation alone doesn't help. Sometimes it's not easy to identify what product versions have been installed on a system, but a look at c:\Program Files (x86)\Intel\Download\ helps. In case of doubt, you can run one installer after the other and repair/remove unused products. May become a very lengthy task, but in general no other choice to sanitize a system.
Thanks but for PS 2016 I wiped all old Intel 2015 tools off the system first. For the PS 2016 install it doesn't get as far as the screen that would ask to Repair or Remove -- it just exits after some time spent downloading or extracting. I don't have 100 GB free on the C: drive but I extracted to a large HDD with plenty of space so I don't think that is the problem (and the installer should certainly give a message if it doesn't have enough space). I also tried to install with Visual Studio 2015 Express (to see if, unlike PS 2015, it works properly with VS2015) but I read now that Express isn't supported and I need Community, right? That is also no reason for the installer to just exit with no message. I think there is yet another serious problem with the PS installation system.
Stuart
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The supposedly incompletely deleted version has no modify or repair option, so attempt to re-install goes nowhere. Nor does removing old licenses have any effect. Assuming that the way forward is to find the broken entries and kill them under regedit, it seems the only way forward is for someone to reveal where those are hidden, or to build in a means in the installer to avoid these blocks from from formerly installed versions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Tim,
Thank you for reporting additional details regarding your installation issue. I have reported all of these to development and will keep you updated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Stuart M wrote:
Quote:
That is also no reason for the installer to just exit with no message. I think there is yet another serious problem with the PS installation system.Stuart
Hello Stuart,
Please send us your installation log files for further investigation.
Thank you,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'll try the suggested repair script after returning to internet territory in a few days.
I installed psxe 2016 on win10 and rh6.2 without encountering such problems, but didn't have time to test vtune or advisor.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Devorah H. (Intel) wrote:
Hello Stuart,
Please send us your installation log files for further investigation.
Thank you,
No log files found. Sorry.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've spent days battling install issues -- uninstalling, repairing, manually deleting, windows remove..... I, too, use a less-used computer to test installs but, with computers at home and work for development and your new, limited number of installs, this is becoming more difficult.
The issue just seems to get worse with each new version. The obvious fix is to improve your install; however, I suggest you create a tool which would remove ALL Intel compilers & integrations from a computer. Then, at least, one could start with a clean slate and install whatever versions one wishes to. This would still take some time but at least one wouldn't feel that we're playing install roulette with no known path but random thrashing to reach a point where we could get back to our real work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Bruce,
Thank you for your feedback and suggestion. We value your input and I have forwarded your comments to the development team. If you still experience an issue with installation, is it possible to submit install logs? What errors are you seeing during installation?
Regards,

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page