topic Cannot figure how this could in Software Archive

Duplicated Intel Parallel Studio Entries after Update using Intel software manager

Silvio_M_ — Sat, 26 Mar 2016 00:56:11 GMT

I have updated Intel Parallel Studio from Update1 to Update2 using "Intel Software Manager". The update procedure ended without errors but many entries are duplicated and in Control Panel I see both installations "Intel Parallel Studio Update1" and "Intel Parallel Studio Update2". See the screenshot

If I Unistall Parallel Studio Update 1, the procedure removes not only the older duplicated values but also the components that aren't included with Update2 package like Trace Analyzer and Collector.

Why Intel staff haven't addressed this dirty update procedure?

Hi, Silivia

Yuan_C_Intel — Mon, 28 Mar 2016 06:38:07 GMT

Hi, Silivia

Intel(R) Parallel Studio XE supports multiple installations. This means you can have both Update 1 and Update 2 installed and co-exist. It will not uninstall the old version automatically and replace with the new update. In case if you meet issues with newer version, the old one should still be able to use.

Does this answer your question?

Thanks

Cannot figure how this could

Silvio_M_ — Mon, 28 Mar 2016 10:26:00 GMT

Cannot figure how this could be an intentional choice. Maintain both version should be only optional. If I choose "update" the procedure should replace old components with newer version instead the installer has installed new components removing only some older tools of previous version and leaving other older components installed alongside newer, as result you haven't a fully separate Update2 and Update1 installation that you can use in case Update2 is bugged, but only a dirty setup of Update2 .

Some people to choose to keep

Light_Intel — Fri, 30 Dec 2016 00:32:28 GMT

Some people to choose to keep different versions simultaneously as some of their code may have been compiled with a specific version. We always have to weigh the needs of all customers.

This issue has been resolved.

Light_Intel — Fri, 30 Dec 2016 00:32:47 GMT

This issue has been resolved. If you have a similar question please start a new thread to ensure your issue is being addressed in a timely manner.