← Back to Microsoft MSXML (XML Core Services) 4.0 Parser

Silent install command for Microsoft MSXML (XML Core Services) 4.0 Parser 4.0-SP3

The exact silent switches the Microsoft MSXML (XML Core Services) 4.0 Parser 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)

msxml4-KB2758694-enu.exe /quiet /qn /norestart

Run from the directory containing msxml4-KB2758694-enu.exe. Download the installer from the Direct link below first.

Architecture	Scope	Type	Silent switches	Source
x86	-	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 Microsoft MSXML (XML Core Services) 4.0 Parser?

Microsoft MSXML (XML Core Services) 4.0 Parser uses EXE. After downloading the installer, run: msxml4-KB2758694-enu.exe /quiet /qn /norestart. The silent install switches are /quiet /qn /norestart.

How do I deploy Microsoft MSXML (XML Core Services) 4.0 Parser via Intune or Configuration Manager?

Use winget for the cleanest path: winget install --id Microsoft.MSXML.4 --exact 4.0-SP3 --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 Microsoft MSXML (XML Core Services) 4.0 Parser install page.