Win32 Appshex 0xBC2

Fix Intune Error 3010: The install worked but needs a restart to finish (ERROR_SUCCESS_REBOOT_REQUIRED); it is a soft reboot, not a failure.

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

AppWorkload.log

Folder: C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\

Also check: AppEnforce.log (ConfigMgr) · Application event log (MsiInstaller)

Root causes

The package replaced files that were in use and needs a restart to finish.
The deployment return codes were changed or removed, so 3010 is no longer mapped to a soft reboot.
The app behavior is set to "No specific action" or "Determine behavior based on return codes" with a mapping that does not match the installer.
Detection depends on a file or key that only appears after the restart, so the app reads as not detected until the device restarts.

Open Apps > the app > Properties > Return codes and confirm 3010 maps to "Soft reboot". The defaults are 0 and 1707 success, 3010 soft reboot, 1641 hard reboot, 1618 retry.
Set the Device restart behavior to match your change policy, and tell users when a restart will be requested.
If detection needs the restart, schedule it, or change the rule to something that exists before the restart.
Restart a pilot device and confirm the app moves to Installed and detection passes.

For the full diagnosis around this error, read Win32 app stuck at waiting or pending.

Most Win32 failures are decided by the detection rule and the install command, so fix them at the source before the app is assigned again.

Other Win32 Apps errors with their own runbooks.