A newer version of this document is available. Customers should click here to go to the newest version.
Integration into Visual Studio* fails for oneAPI 2022.1 and lower versions of toolkits
During installation of 2022.1 and lower versions of toolkits, integration into Visual Studio* fails on systems with Visual Studio* 2022 installed.
Cause: Incompatibility between oneAPI installers and recent changes in the Microsoft.VisualStudio.Setup.Configuration.Native.dll library provided by Microsoft as part of the Visual Studio 2022 installation.
Solution: Upgrade to the latest version of the oneAPI toolkit. Alternatively, before installing 2022.1 and lower toolkit packages, remove Visual Studio* 2022 from your system. For more information about the available workarounds, refer to Known Microsoft* Visual Studio 2022 and oneAPI Toolkits Installation Issue.
OpenCL CPU Runtime Library fails to load Intel oneTBB
Intel OpenCL CPU Runtime Library fails to load the Intel oneTBB library that was installed via Conda.
Cause: No oneTBB registry key installed when Intel oneTBB is installed via Conda package manager.
Solution: Before completing the workaround steps below, make sure that you already configured the targeted device, otherwise, OpenCL Runtime will load two devices, and use the first one by default.
Locate the corresponding device configuration file in the same folder where the OpenCL Runtime Library file intelocl64.dll resides:
cl.cfg for CPU device
cl.fpga_emu.cfg for FPGA emulator
Open the configuration file for editing and add your oneTBB DLL path to the CL_CONFIG_TBB_DLL_PATH field:
CL_CONFIG_TBB_DLL_PATH = <tbb-install-dir>
- If you configure both cl.cfg and cl.fpga_emu.cfg, the oneTBB DLL path in them should be the same value
Add the value of the CL_CONFIG_TBB_DLL_PATH field without quotation marks
Integrity check fails
During installation, you may get an error message about failed integrity check of downloaded files.
Cause: Downloaded files are corrupted because of the hard drive corruption.
Solution: Check hard drive health and restart the installation.
2021.x installation overwrites existing 2022.x installer
If you launch the installer for the 2021.x version of a toolkit on a system with the 2022.x version installed, your existing 2022.x installer will be downgraded to the 2021.x version. The 2021.x installer does not recognize installed 2022.x packages.
Cause: Compatibility issue between 2022.x and 2021.x versions of the installer.
Solution: Restore the latest installer by launching the installer for the 2022.x version of the toolkit. In future, when you need to install 2021.x on a system with 2022.x installed, before launching the installer, back up the following installer directories by renaming them:
32-bit system: C:\Program Files\Intel\oneAPI\Installer and C:\Program Files\Intel\PackageManager\1.0
64-bit system: C:\Program Files (x86)\Intel\oneAPI\Installer and C:\Program Files (x86)\Intel\PackageManager\1.0
When you are done with 2021.x, you can change back the directory names to restore the 2022.x installer.
Did you find the information on this page useful?