I used to have VS22 and Intel Fortran installed but had to reimage my PC and lost everything. I’m trying to get the best new stuff installed. I have D/L the VS2026 and was not sure what to pick to edit and compile my old Fortran programs. I have D/L the following files:
For Visual Studio, follow the instructions here. (Intel removed the page, but available through the Internet Archive.)
For Fortran, you need only the first installer you listed. If you need other Intel oneAPI components, the third and then second installer would be the ones to use.
I’ll try to muddle through. I seem to remember something about iFort and IFX in the discussion I had when I was getting VS22 running and trying to compile some old Fortran projects.
I’m going to retire this summer and probably have to play with Fortran on my old home PC.
I think I am on the path. I installed the 2025.3.3.16 and opened VS2026 and opened an old project and it told me I had selected Win32 and I needed to install something. I vaguely remembered that the IFX compiler was 64 bits only, so I did the config manager and created/selected an x64. I built the solution.
BTW, how do you select a light background in VS2026? I was used to how VS22 was with the light background.
Regarding selecting the light background in VS2026…click on Tools --> Theme from the main menu. You should see a few options at that point: “Blue”, “Blue (Extra Contrast)”, “Dark”, “Light”, “Use system setting”, and “Get More Themes”. At least that’s what I see when using VS2022. Hope that helps.
Sorry for the late reply, I must not have subscribed to this post somehow. (I thought it was automatic) I asked Google about the background and was able to get it to a lighter setting. I think I am up and running now and need to open up an old project to try it out. Since I was reloading several software packages, I am behind and compiling old Fortran that still works is down the list a long way.
I’m very old school and my Fortran skills are stuck back in the 1960’s when I learned Fortran IV. I do like to write code to solve engineering problems, but my documentation skills are very bad. I rarely share my code with others and need to learn more about how to debug code when someone reports a problem.
Sorry for the late reply. I was trying to recompile an old Project using the new VS2026 and IFX after leaving it for a long time. I built the debug and tried to run the EXE but get errors about a missing DLL and I may have to reinstall. The libraries are LIBMMD.dll, LIBIFCORE.DLL, and LIBIFCOREMDD.dll.
I stumbled around the Configuration Manager dialog and found a spot where the settings all said NO and I changed to yes but now I cannot find that dialog.
Is there a somewhat easy fix or do I need to uninstall and start over?
I am a rank beginner in VS and barely knew how to compile Compaq Visual Fortran and got a little in the old VS2019.
The dialog is the Configuration Manager, as it says in the title bar, and can be found under the Build menu. But it is unrelated to this issue - I don’t know what you saw with the “No” settings.
The DLL issue is almost certainly due to the compiler install failing to properly update the PATH system environment variable. This has been a longstanding problem - I don’t think it’s actually an installer error but rather flakiness on the part of Windows. Usually this works, but not always.
Do this:
Open the Windows Settings app and select System > About. Just below Device Info is “Related links”. In that line, click Advanced System Settings.
In the new dialog that opens, select the Advanced tab, and then click Environment Variables
Under System Variables, click on PATH and then click Edit.
You want a line reading “C:\Program Files (x86)\Intel\oneAPI\compiler\latest\bin” to be one of the first few, above any lines with “%SystemRoot%”. If it does not exist, click New and create a new entry. Then use the Move Up button to move that line up towards the top.
I had to get our IT people to allow me to get to the dialog with the Admin password but I added that path and I rebooted. I think I did the rebuild solution and it built the manifest. It seems to create the EXE but I get a read end of file error when I try to debug. I must have put a breakpoint in the code the last time I was editing. When I start without debugging I get the read error, and the output window says something about Win32 and an exit code 24.
I guess my code has a problem but the old EXE when I had VS2019 running with Win32 seemed to run OK. I need to figure out the VS and how to look at variable values and set breakpoints to see why it is trying to read my input file and hitting an end of file.
I pasted a couple of screen shots of what it says.
Ignore the (Win32) - you’ll see that all the time. You just have to figure out the end-of-file issue. The most common reason for that I see when Visual Studio users encounter it is that when you run a program inside VS, the “default folder” is the one containing the project file (.vfproj). If your program just opens a file without a path, it may not be looking in the right place and will create an empty file in the project folder.
Try this - rather than starting in the debugger, use “Start without debugging”. Switch to the console window and look to see if there is an error message naming the file it is trying to read.
You can set breakpoints the same way you did with ifort.
It was a PICNIC error. Problem In Chair, Not In Computer. I have the right file listed on my C: drive but I forgot I had added an input variable that should have been added to the TXT file I am reading and I was using an old data file and was reading 6 values on one line and the old file only had 5 values, so the read statement was skipping lines and got to the end of the file. I need to put some error checking in to fix the problem.
OK, I’m back with nearly the same problem. I fixed my read past end of file error and added a couple of write statements and compiled both the Debug and Release versions of the EXE.
I can run the EXE in Debug or without debug inside VS2026 and the EXE runs fine. I typically copy the EXE to another folder for people to use. When I copy the EXE and try to run it, I get the errors that it cannot find the DLL’s and it says to reinstall the program.
Is there a setting in the build menu that adds the missing DLL’s to the EXE so it will run outside the VS2026 program? After I compile and save the EXE and I get out of the VS window, I get the same missing DLL’s errors.
The VS2026 says there is an update available. Should I install the update to maybe fix the problem? I did add the Path to the system variables.
I have registered to this Forum with 2 eMail addresses, and I forget which one I used to post this message. The GWats1 is my home eMail on Gmail. My handle on my work eMail is GTWatson77459 and I replied to Steve with that one.
Sorry for the confusion. I’m George for both accounts.
I should have logged in with my home eMail address and not replied above from my work address. I think my original problem was not fixed by editing the Path. I still get the missing DLL errors when I try to run the EXE outside of VS26.
When I open VS26 with the solution and compile either the Debug or Release options and then tun the EXE from within VS26, it runs fine. When I close VS26 and try to run the EXE, I still get the missing DLL errors that I originally wrote about.
Is there some setting in VS26 that I am missing that will include the missing DLL’s in the EXE? (See the pictures attached above)
I’m still stuck with the above problem with the compiler I posted on 6-14-2026 where it runs the EXE within VS26 but can’t find the DLL’s when I try to run the EXE that was created.
The fact that you cannot run your executable from outside Visual Studio means that the Intel oneAPI environment is not correctly set in your PATH. Steve Lionel explained you how to add the compiler to your PATH (see his post from 06-08-2026).
Even if the compiler is not added to your PATH, you can still run your executable as follows:
(1) Open a Windows Command Prompt (cmd);
(2) Run the “setvars.bat” file located in “C:\Program Files (x86)\Intel\oneAPI”
This will automatically configure the whole Intel oneAPI environment (including the compilers).
(3)From this terminal, go to your executable file and run it. The runtime libraries should be found in this case.
Note: Another way to setup the Intel oneAPI environment is by typing “Intel” in the Windows Search menu and then selecting “Intel oneAPI command prompt for Intel 64 for Visual Studio 202*”:
Thanks for the tips. I did follow what Steve said earlier and thought I had it fixed because I could compile and run the EXE within VS2026.
I found and ran the BAT file you suggested and went to the location of the formerly compiled exe and tried to run it and had the same missing DLL popups. I then went to that command prompt and can go to the folder on my network where the old EXE resides and can run the VS2026 compiled EXE with no problems, so the EXE works as long as I use the Command Window to manually type the EXE name.
I fired up VS2026 and loaded the .SLN project and did the build which seemed to work and I can Start the EXE from within VS2026 and it runs fine. When I minimize the VS2026 window and go to the folder where the EXE was just created, I still get the DLL missing popups. I switched the format from Debug to Release, and it seems to go fine until I get an error about writing to the Manifest, but it seems to create the new EXE.
I did reboot the PC after running the BAT hoping that would work, but trying to run the newly compiled EXE from the folder where it resides outside the VS2026 window gives the same missing DLL popups.
Is there something else to try or should I just reinstall the VS2026 and the Fortran compiler? I’m about to retire and may have more freedom to install software without having to call Guam to get Tech Support to take over my PC in Texas and supply the Admin Password.
Fron what I understand you are exploring 3 ways to run your executable:
(1) From VS 2026: it works => OK this proves that your installation of Intel oneAPI is correct and that the runtime libraries (libmmd.dll, …) are also correctly installed. In this case, they are automatically loaded by VS, you do not have to worry about that.
(2) It also seems to work from an Intel oneAPI command prompt (using “setvars.bat” or directly from the Windows Search menu as I explained you) when you manually type the exe file name and run it. The important thing to understand is that the Intel oneAPI environment is only configured INSIDE this command prompt session.
(3) It seems that you also try to run your exe by double-clicking it from the Windows Explorer (although this point is unclear). This will only work if the compilers are added to your system PATH (see Lionel’s explanations). If double-clicking the exe file from the Explorer still gives missing DLL errors, then the compilers are probably not in the regular Windows PATH, or the wrong folder was added. To check this, please open a normal Windows command prompt (NOT the oneAPI prompt!!) and run:
where libmmd.dll
(libmmd is one of the runtime libs requested by your application)
If the answer is “Info: could not find the file …” (or something equivalent), it means that the PATH was not correctly set up.
You can also type:
echo %PATH%
and check if the folder “C:\Program Files (x86)\Intel\oneAPI\compiler\latest\bin” is specified somewhere. If not, this is the ultimate indication that the PATH is not correctly setup.
So before reinstalling VS or oneAPI, I would first check and fix the Windows PATH.
losing the whole Fortran + VS setup is painful.
)
