Silent install command for Intel® oneAPI Base Toolkit 2025.1.3.8

The exact silent switches the Intel® oneAPI Base Toolkit installer accepts, plus a one-line command you can paste into a script, Intune Win32 app, or Configuration Manager package.

One-line silent install (x64, machine scope)

intel-oneapi-base-toolkit-2025.1.3.8_offline.exe -a --silent --eula accept -p=NEED_VS2019_INTEGRATION=0 -p=NEED_VS2022_INTEGRATION=0

Run from the directory containing intel-oneapi-base-toolkit-2025.1.3.8_offline.exe. Download the installer from the Direct link below first. Run an elevated terminal (Run as Administrator) for machine-scope installs.

Architecture	Scope	Type	Silent switches	Source
x64	machine	EXE		Declared by publisher

Declared by publisher means the switches come straight from the winget manifest the publisher (or community maintainer) submitted to microsoft/winget-pkgs.
Default for {type} means the manifest doesn't specify silent switches, so the framework's standard switches are shown (e.g. /S for NSIS, /quiet /norestart for MSI).

Frequently asked questions

What is the silent install command for Intel® oneAPI Base Toolkit?

Intel® oneAPI Base Toolkit uses EXE. After downloading the installer, run: intel-oneapi-base-toolkit-2025.1.3.8_offline.exe -a --silent --eula accept -p=NEED_VS2019_INTEGRATION=0 -p=NEED_VS2022_INTEGRATION=0. The silent install switches are -a --silent --eula accept -p=NEED_VS2019_INTEGRATION=0 -p=NEED_VS2022_INTEGRATION=0.

How do I deploy Intel® oneAPI Base Toolkit via Intune or Configuration Manager?

Use winget for the cleanest path: winget install --id Intel.OneAPI.BaseToolkit --exact 2025.1.3.8 --silent --accept-package-agreements --accept-source-agreements. If winget isn't viable in your environment, package the publisher's installer directly using the silent switches above.

Where do these silent switches come from?

The switches marked "Declared by publisher" come from the winget manifest the publisher (or community maintainer) submitted to microsoft/winget-pkgs. Switches marked "Default for EXE" come from the installer framework's documented defaults.

Prefer the winget route? See the full Intel® oneAPI Base Toolkit install page.