How to Silently Install Microsoft 365 Apps for enterprise

Get a reliable rollout and predictable detection for Microsoft 365 Apps for enterprise with a deployment approach built for repeatable enterprise packaging. This guide is aimed at IT admins who need a practical, machine-wide installation method from Microsoft Corporation, with admin-rights considerations and a clear way to validate installs using the verified silent install command. It also fits cleanly into managed deployment workflows through Intune, SCCM, or PDQ while supporting dependable detection rules and standardized software delivery.

STEP 0

Silently install Microsoft 365 Apps for enterprise on Windows

Run this command as Administrator to install Microsoft 365 Apps for enterprise with no prompts.

Microsoft.Office.16.0.19929.20090.X86.exe /configure https://aka.ms/fhlwingetconfig

Overview

Application	Microsoft 365 Apps for enterprise	Install scope	Machine
Version	16.0.19929.20090	Requires admin	Yes
Publisher	Microsoft Corporation	Restart behavior	No restart
Installer type	Office Click-to-Run	Detection method	Registry
Installer file	`Microsoft.Office.16.0.19929.20090.X86.exe`	Download	download
Silent install	Available	Architecture	x86
Silent uninstall	Available	Homepage	https://www.office.com/

Silent Install Steps

Run any one of the methods below to install Microsoft 365 Apps for enterprise silently with zero user interaction. Both Command Prompt and PowerShell produce the same result — use whichever fits your deployment workflow.

Method 1: Install with Command Prompt

Run the installer from an elevated Command Prompt.

Download or copy the installer file to a local folder, for example C:\Installers.

Open Command Prompt as Administrator.

Switch to the installer folder.

cd /d "C:\Installers"

Run the silent install command.

Microsoft.Office.16.0.19929.20090.X86.exe /configure https://aka.ms/fhlwingetconfig

Method 2: Install with PowerShell

Run the same silent install command through PowerShell.

Download or copy the installer file to a local folder, for example C:\Installers.

Open PowerShell as Administrator.

Switch to the installer folder.

Set-Location "C:\Installers"

Run the silent install command.

$Installer = 'Microsoft.Office.16.0.19929.20090.X86.exe'
Start-Process -FilePath $Installer -ArgumentList '/configure https://aka.ms/fhlwingetconfig' -Wait -NoNewWindow
exit $LASTEXITCODE

Deployment Notes

Key facts to confirm before rolling this out to production machines — permissions required, scope of install, and reboot behavior.

Requirement	Administrator privileges required
Install scope	Machine
Restart behavior	No restart expected

Detection Rules

Configure your deployment tool with the detection rule below to confirm a successful install of Microsoft 365 Apps for enterprise. The same rule works for Microsoft Intune, SCCM, PDQ Deploy, and most RMM platforms — just paste the values into the matching fields.

Registry detection

Registry key	`HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\O365ProPlusRetail - en-us`
Value name	`DisplayVersion`
Expected value	`16.0.20026.20076`

PowerShell detection script

$Path = 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\O365ProPlusRetail - en-us'
if (Test-Path $Path) {
    $Item = Get-ItemProperty -Path $Path -ErrorAction SilentlyContinue
    $Value = $Item.DisplayVersion
    if ($Value -eq '16.0.20026.20076') { exit 0 }
}
exit 1

Silent Uninstall Steps

Remove Microsoft 365 Apps for enterprise silently from one machine or your entire fleet. The commands below uninstall without prompts and suppress automatic reboots so you control the timing.

Method 1: Uninstall with Command Prompt

Run the uninstall command from an elevated Command Prompt.

Open Command Prompt as Administrator.

Run the silent uninstall command.

Microsoft.Office.16.0.19929.20090.X86.exe /configure C:\Source\remove.xml

Method 2: Uninstall with PowerShell

Run the same silent uninstall command through PowerShell.

Open PowerShell as Administrator.

Run the silent uninstall command.

$Uninstaller = 'Microsoft.Office.16.0.19929.20090.X86.exe'
Start-Process -FilePath $Uninstaller -ArgumentList '/configure C:\Source\remove.xml' -Wait -NoNewWindow
exit $LASTEXITCODE

Deployment Examples

Drop one of the snippets below into your deployment tool, Group Policy, or scheduled task. Each script wraps the silent install command for Microsoft 365 Apps for enterprise as a batch file or PowerShell script — copy, save, and run.

Batch file example

Save the following content as install-microsoft-365-apps-for-enterprise.bat in the same folder as the installer.

@echo off
cd /d "%~dp0"
Microsoft.Office.16.0.19929.20090.X86.exe /configure https://aka.ms/fhlwingetconfig
exit /b %errorlevel%

PowerShell script example

Save the following content as install-microsoft-365-apps-for-enterprise.ps1 in the same folder as the installer.

Set-Location -Path $PSScriptRoot
$Installer = 'Microsoft.Office.16.0.19929.20090.X86.exe'
Start-Process -FilePath $Installer -ArgumentList '/configure https://aka.ms/fhlwingetconfig' -Wait -NoNewWindow
exit $LASTEXITCODE

Frequently Asked Questions

Can I silently install Microsoft 365 Apps for enterprise on Windows?

Yes. This guide uses Office Click-to-Run switches to carry out a fully unattended installation of Microsoft 365 Apps for enterprise 16.0.19929.20090 without user prompts. It is commonly used with Intune, SCCM, PDQ Deploy, and RMM tools.

Do I need administrator privileges to install Microsoft 365 Apps for enterprise?

Yes, administrator-level permissions are needed to install Microsoft 365 Apps for enterprise. Run it as Administrator or deploy it in the SYSTEM context.

Will installing Microsoft 365 Apps for enterprise restart the computer?

No. For Microsoft 365 Apps for enterprise, Office Click-to-Run streams the installation and handles restart state on its own; the setup.exe /configure command above does not reboot the device. Only plan a reboot if the configuration XML explicitly requests one.

How do I verify Microsoft 365 Apps for enterprise installed successfully?

To confirm Microsoft 365 Apps for enterprise installed successfully, use the detection rule from this guide — file path, registry key, MSI product code, or MSIX package family name — which is commonly supported by Intune, SCCM, and PDQ.

How do I silently uninstall Microsoft 365 Apps for enterprise?

To silently remove Microsoft 365 Apps for enterprise, run setup.exe /configure with an Office Click-to-Run removal XML. There is no msiexec or MSI product code involved.

Which deployment tools support these commands?

These Microsoft 365 Apps for enterprise commands are commonly used with Intune, SCCM/MECM, PDQ Deploy, ManageEngine, NinjaOne, Datto RMM, Atera, and Action1. Other deployment tools usually work as well if they can run the command in the required SYSTEM or User context.

Troubleshooting

If the install fails, exits with a non-zero code, or leaves no trace on the target machine, work through the checks below. Most issues come down to permissions, paths, or exit code handling.

Run as administrator	Make sure Command Prompt or PowerShell is opened as Administrator. This installer writes to a machine-wide location and will fail silently without elevated permissions.
Verify the installer file name	Confirm that the installer file name matches the command shown in this guide: Microsoft.Office.16.0.19929.20090.X86.exe.
Run from the correct folder	Run the command from the folder that contains the installer file. For batch or PowerShell deployments, place the script and installer in the same folder.
Check exit codes	If the installer returns a non-zero exit code, review the installer log or deployment tool logs. Some packages may use additional success exit codes.
Restart if required	If the application does not appear immediately after installation, sign out and sign back in, or restart the device — this refreshes Start menu shortcuts, file associations, and Path entries written by the installer.
Validate detection rules	If your deployment tool reports the app as not installed, verify that the detection rule matches the installed file path, registry key, or package identifier. Use the detection rule above to confirm whether the application was installed successfully.