Use case: We hit this with Google Earth Pro - the install reached 100% execute but failed verification (“No version of Google Earth Pro (64-bit) was found”). The real blocker was a pending reboot: the MSI couldn’t finalize/register until the machine rebooted. Nothing surfaced that visually - we only found it by reading the session log line “A pending reboot was found.”
Requests:
(1) A small badge/icon on any software with “Reboot Required” checked, shown in the Software list and on deployment rows, so it’s obvious at a glance which apps need a reboot to complete.
(2) A clear “Reboot Pending” badge on the computer overview (and in session results), driven by the existing RebootPending inventory state.
(3) When a maintenance action fails verification while a reboot is pending, add a hint on the failed action like “a pending reboot may be blocking this install” instead of just “no version found.”
This would turn a log-diving diagnosis into a one-glance signal.