3010

What it means

The install completed. Windows needs a restart to finish putting files in place, and it did not restart on its own. This is the single most common exit code that gets misreported as a failure, because tools that only treat 0 as success will mark the device failed.

Real causes

• Files in use during the install were queued for replacement on the next boot.
• A service or driver could not be started until the system restarts.

What to do

1. Add 3010 to the accepted exit codes in your deployment tool. Configuration Manager classifies it as a soft reboot by default, and Intune Win32 apps do the same. Neither treats it as a failure unless you tell them to.
2. Confirm the pending state: check HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending for its presence.
3. Do not re-run the install. It already succeeded.

Where to look

• Application event log, MsiInstaller source

Checked against Microsoft documentation. Last reviewed 2026-08-20.

Decode another code