← Back to Microsoft .NET Runtime 7.0 (x86)

Silent install command for Microsoft .NET Runtime 7.0 (x86) 7.0.20

The exact silent switches the Microsoft .NET Runtime 7.0 (x86) installer accepts, plus a one-line command you can paste into a script, Intune Win32 app, or Configuration Manager package.

One-line silent install (x86)

msiexec.exe /i dotnet-runtime-7.0.20-win-x86.exe /quiet /norestart

Run from the directory containing dotnet-runtime-7.0.20-win-x86.exe. Download the installer from the Direct link below first.

Architecture	Scope	Type	Silent switches	Source
x86	-	EXE Burn bundle	Custom: /norestart	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 Microsoft .NET Runtime 7.0 (x86)?

Microsoft .NET Runtime 7.0 (x86) uses EXE (Burn bundle). After downloading the installer, run: msiexec.exe /i dotnet-runtime-7.0.20-win-x86.exe /quiet /norestart. The silent install switches are /quiet.

How do I deploy Microsoft .NET Runtime 7.0 (x86) via Intune or Configuration Manager?

Use winget for the cleanest path: winget install --id Microsoft.DotNet.Runtime.7.x86 --exact 7.0.20 --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 (Burn bundle)" come from the installer framework's documented defaults.

Prefer the winget route? See the full Microsoft .NET Runtime 7.0 (x86) install page.