- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am experiencing the same issue after uninstalling oneAPI Base+HPC 2023 and installing the latest version 2024.0 of both.
No matter if I open a Fortran solution or a C++ one, I am getting the error "Tool path does not exist or not set "\bin32". Make sure install directory environment variable is defined."
After clicking on OK, another warning is displayed:
I did not get this error and warning when updating (=uninstalling older version, rebooting computer, installing new version) oneAPI before; updating to 2024.0 is the first time I get them.
I am using the latest version of Visual Studio Professional 2019, 16.11.32.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@jirina wrote:
I am experiencing the same issue after uninstalling oneAPI Base+HPC 2023 and installing the latest version 2024.0 of both.
No matter if I open a Fortran solution or a C++ one, I am getting the error "Tool path does not exist or not set "\bin32". Make sure install directory environment variable is defined."
After clicking on OK, another warning is displayed:
I did not get this error and warning when updating (=uninstalling older version, rebooting computer, installing new version) oneAPI before; updating to 2024.0 is the first time I get them.
I am using the latest version of Visual Studio Professional 2019, 16.11.32.
See the above posts for suggestions if the issue is with opening an existing project. No issues when creating a new one?
I escalated this for further investigation, however I need a test case solution to be able to test and reproduce.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Even though my Fortran project has many files, I can try creating a new project and adding existing files to it. I can also try creating a new project to see if the problem persists. However, I have many other projects, done in C++ (not Intel), and the problem occurs if I open any of them, so it looks like the installation of oneAPI 2024.0 corrupted something in Visual Studio or in system settings. I am going to add more information later, after I try what I mentioned.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have just tried creating a new empty Fortran project and I am getting the same error.
I used Rapid Environment Editor 9.2 program to check my environment variables and found out that %INTEL_DEV_REDIST%emu value in the PATH variable does not exist on my computer. Deleting it did not change anything.
I checked ActivityLog.xml created by VS to see that VS fails to load the package Intel Inspector XE 2013:
Hovever, I do not know whether and how I can influence/change this.
There is another post on the same topic, it is from 2019, see here: https://community.intel.com/t5/Intel-C-Compiler/bin32-tool-path-is-not-existing/m-p/1180101
It is suggesting it might have something in common with PATH or generally paths to Intel packages; could this be a clue?
I am going to try re-installing oneAPI base+hpc to see what happens...
Edit: re-installation (uninstall, reboot, install, reboot) did not resolve the problem. I am using the default installation options.
Further more, the system variable IFORT_COMPILER24=C:\Program Files (x86)\Intel\oneAPI\compiler\2024.0\windows\ points to a directory that does not exist in the installation. I have noticed this already before when I wanted to add F1 help documentation to this folder (I wonder why it isn't included in the installer anyway). In spite of this fact, I am able to compile my Fortran project with Intel® Fortran Compiler 2024.0.0 [Intel(R) 64].
Could the missing C:\Program Files (x86)\Intel\oneAPI\compiler\2024.0\windows directory be a clue to what is happening?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@jirina wrote:
I have just tried creating a new empty Fortran project and I am getting the same error.
I used Rapid Environment Editor 9.2 program to check my environment variables and found out that %INTEL_DEV_REDIST%emu value in the PATH variable does not exist on my computer. Deleting it did not change anything.
I checked ActivityLog.xml created by VS to see that VS fails to load the package Intel Inspector XE 2013:
Hovever, I do not know whether and how I can influence/change this.
There is another post on the same topic, it is from 2019, see here: https://community.intel.com/t5/Intel-C-Compiler/bin32-tool-path-is-not-existing/m-p/1180101
It is suggesting it might have something in common with PATH or generally paths to Intel packages; could this be a clue?
I am going to try re-installing oneAPI base+hpc to see what happens...
Edit: re-installation (uninstall, reboot, install, reboot) did not resolve the problem. I am using the default installation options.
Further more, the system variable IFORT_COMPILER24=C:\Program Files (x86)\Intel\oneAPI\compiler\2024.0\windows\ points to a directory that does not exist in the installation. I have noticed this already before when I wanted to add F1 help documentation to this folder (I wonder why it isn't included in the installer anyway). In spite of this fact, I am able to compile my Fortran project with Intel® Fortran Compiler 2024.0.0 [Intel(R) 64].
Could the missing C:\Program Files (x86)\Intel\oneAPI\compiler\2024.0\windows directory be a clue to what is happening?
1. Do you have other older packages of Intel Software installed on the system? Those need to be removed before installing VS2022 + HPC Toolkit (if you use only Fortran compiler - HPC Toolkit is all that is needed. Base toolkit is optional). It is important to have a clean environment to ensure a successful VS2022+ HPC Toolkit installation/integration (by nature a very complex process on Windows)
2. "I am able to compile my Fortran project with Intel Fortran Compiler" - is that via cmd or VS IDE or both? Please elaborate if the issue with building projects still exist. Did you try to remove old (unsupported) extensions and Intel software?
3. F1 Help Documentation - please clarify - you have followed all the steps listed in this KB Article and it failed to install? It has been removed years ago due to the fact that most of our customers use online documentation.
4. Please provide the install logs of failed installation/integration. They are in %TEMP%\intel_oneapi_installer.
as well as Visual Studio ones (typically, the file is at %TEMP%\vslogs )
5. It is hard to judge if the issue from 2019 is the same as reported here without looking at install logs from both cases
P.S. @jirina if you or your company have paid Priority Support - your issues will be address quicker than here on the forum when submitting a service ticket
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1. I uninstalled the previous version of oneAPI, 2023.2, before installing the latest version, 2024.0. Anytime I am (un)installing software, no applications are running and I restart my computer after (un)installation finishes. I tried again today, which means it is my third attempt to install oneAPI 2024.0. This is what I have in the list of Apps before after uninstalling 2023.2 and before installing 2024.0:
Also, I searched for any oneAPI-related folders on the system drive to make sure there are not any left.
4. I installed oneAPI 2024.0, Base and HPC, using offline installers, and restarted the computer after installing each of them. I re-downloaded both installers to make sure I used the same ones in previous attempts. Installation logs are attached. Installation itself finishes without any problems.
2., 3. It is not necessary to elaborate project compilation and F1 documentation; it was only a note that despite the reported problem, the Intel Fortran Compiler works well.
The problem is that I keep getting error messages after opening any project (Fortran, C++, ...) in Visual Studio, and the error messages are caused by oneAPI integration to Visual Studio:
I am attaching also the file mentioned in the screenshot above.
By the way, I have only VS 2019 on my computer, so the problem I reported is what I experience on Windows 10 (latest version, all updates defined), VS 2019 Pro (latest version) and oneAPI 2024.0.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I bumped this because I'm having the same problem.
Started with a brand new Windows 11, no other program ever installed. Installed VS 2019, installed OneAPI base + HPC, versions 2024.0.1.45 and 2024.0.1.35, respectively.
No errors reported during the installation. In Visual Studio, Tools/Options/Intel Compilers and Libraries/IFX Intel Fortran/Compilers it says: No compiler installed. In the corresponding IFORT section, the old compiler is listed (which I can't use because some MKL LAPACK functions I need are no longer available.
I get the dialog Tool path doesn't exist or not set /bin32, as in the pic of the original post in this thread.
BTW, I had tried to install oneAPI 2024 with VS 2022, and integration with Visual Studio also failed, with the same error I've seen months ago when I tried OpenAPI 2023 ("SucessWithFail"), which has been reported here in several threads.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have just reported this to Intel as a Support Request. I tested installing oneAPI 2024 with both Visual Studio 2019 and 2022, on several computers with Windows 10 where no other programs are installed, and the problem persists. If I get any solution from Intel, I will post it here.
Strange enough, both IFORT and IFX compile my application, but I could see some strange behavior of the debugger in case IFX was used. I assume it is somehow connected with the reported problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Jiří, we have sent you a private message. Kindly check your community inbox.

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