Skip to main content
ConfigMgr / MECMdecimal -2016410847

Fix Intune Error 0x87D00321: The install did not finish inside the "Maximum allowed run time", so Configuration Manager timed it out and failed the deployment.

Open the log below first. It is the quickest way to confirm which of the causes applies before you change anything.

AppEnforce.log

Folder: C:\Windows\CCM\Logs\

Also check: execmgr.log · AppDiscovery.log

Root causes

  • The configured maximum run time is shorter than the installer really needs.
  • The installer is waiting on a hidden prompt, a locked file, or a user who is not there, so it never finishes.
  • The maintenance window on the client is shorter than the app run time, so the install is cut off.
  • A slow or throttled content download runs inside the allowed time.

Step-by-step remediation

  1. In AppEnforce.log find the line showing the command started and the later timeout. Compare the elapsed time with the configured limit.
  2. Run the install command as SYSTEM (psexec -s -i cmd) and time it. If it waits for input, fix the silent switches.
  3. Raise "Maximum allowed run time (minutes)" on the deployment type to a realistic value, and keep it below the maintenance window length.
  4. Check the client maintenance windows are long enough, and that the client received the policy.
  5. Redeploy to a pilot device and confirm the exit code is returned before the limit.

For the full diagnosis around this error, read ConfigMgr app failing: content or detection?.

Keep patching failures out of the queue

Repeat update and client failures are cheaper to prevent than to chase. Compare the options that take app packaging and upkeep off your task list, from Enterprise App Management to PSADT.

Compare Win32 packaging tools

Other ConfigMgr / MECM errors with their own runbooks.

Search all 21 error codes