- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Intel Visual Fortran 2019 prerequisite fails no matter what
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
No matter the conditions or command line options, the Intel Visual Fortran 2019 for Update 4 Redistributable 64-bit prerequisite always fails. https://software.intel.com/en-us/articles/redistributable-libraries-for-intel-c-and-fortran-2019-compilers-for-windows
This .msi installs fine when double-clicking, or when run from the command line with /quiet /qn /norestart. Both the install as a prerequisite and the command line are done as administrator, so that's not the problem.
I am also installing a Visual C++ redistributable prerequisite, and that works fine.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @SpiderLily1 ,
Can you assist with me below details:
- What is the OS-detail of the machine you are verifying?
- Is it 32-bit or 64-bit?
- I had attached working .prq file in the below attachment
- Please change the .msi location of your machine specific and give it a try for UI installation.If that seems to be working then go for silent installation
- I had validated this in both 32-bit & 64-bit which works with no issues
Thanks,
Jenifer
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
I can tell that the registry comparison condition is not working, but the file version comparison (IntelCondition2.png) does work, because when I've already installed the redistributables outside of my InstallShield installer and then run my installer, I am not prompted that it is pending.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @SpiderLily1,
You can refer the MSXML 6.0 prerequisite, which uses file version comparison detection condition.
Apart from that it will be good if you specify the path using predefined variable instead of absolute path.
And can you check manually what is the version before installation and what version got installed during the failure. Is the version installed satisfy the condition mentioned in the prerequisite.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @SpiderLily1 ,
Your registry condition needs to be given like this:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{23872E2A-4505-4C17-B971-4202705EE84F} rather than adding WOW6432Node in the registry key name itself.
The option :Check the following location on 64-bit system will take care whether to append WOW6432Node node or not.Here you can select 32-bit/64-bit based on your requirement.
Please refer the attached snapshot.
Thanks,
Jenifer
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
I've also considered whether the .msi has a problem being packaged in a single .exe, as I'm doing, but the separated files in Disk Images output also has the same problem.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Did you try with registry condition as referred in snapshot?
I had given a try and it worked. Can you confirm please?
Thanks,
Jenifer
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @SpiderLily1 ,
Can you assist with me below details:
- What is the OS-detail of the machine you are verifying?
- Is it 32-bit or 64-bit?
- I had attached working .prq file in the below attachment
- Please change the .msi location of your machine specific and give it a try for UI installation.If that seems to be working then go for silent installation
- I had validated this in both 32-bit & 64-bit which works with no issues
Thanks,
Jenifer
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hello Jenifer,
THANK YOU SO MUCH! I finally see what was wrong the whole time! There was nothing selected in the grayed-out dropdown box on the "Application to Launch" tab! I noticed yours had something there, and then I saw mine didn't. I check my Visual C++ redistributable .prq, and it had the file selected.
I have it working now!
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)