See more. Fix faster. Stay secure.

We are introducing new visibility and diagnostics that help teams quickly understand whether endpoints are fully remediated after patching and why devices restart or power off.

Reboot Required Visibility in Assets View

A new Reboot Required column is now available in Assets View, providing an at-a-glance, filterable view of Windows and Linux devices that require a reboot to complete updates.

This makes it easy to distinguish between endpoints that are fully patched and those that remain in a pending state due to a required restart.

The Reboot Required status is also available in saved views and dynamic tag rules, making it actionable across automation and policy workflows.

Key benefits

• Confirms whether patching is truly complete, not just installed
• Reduces time spent troubleshooting issues that persist because a reboot has not yet occurred
• Improves confidence in endpoint security and compliance posture following a patching cycle

Technicians can now quickly determine whether initiating a reboot is likely to resolve an open issue, rather than spending time investigating symptoms.

• You will see the new column in the Assets View with the reboot icon, here’s how it looks:

Easily see assigned tags directly within the Asset Details view

We have also added in the ability to view assigned tags directly within the asset details view allowing quick and easy access to this additional detail.

Expanded system shutdown and reboot activity tracking

We have enhanced the device Activities view to include system shutdown and restart events, giving teams clearer insight into when and why a device rebooted or powered off.

Event ID 1074  – Planned shutdown/restart initiated by a process or person.

This provides visibility into expected restarts, including those triggered by users, applications, update processes, or management tools. It records who initiated the action, what triggered it, and the stated reason.

For example:

• A user manually clicked Restart or Shutdown
  • An application invoked a restart (e.g., Windows Update, software installer, RMM agent)
  • A system operator used shutdown.exe / RMM / PSRemoting
  • Windows Updates forced a restart after deadline

Event ID 1076 – Unexpected Shutdown – Reason Provided After Boot.

This captures unplanned outages such as power loss, system crashes, forced power cycles, or virtual machine interruptions, with the reason recorded after the system comes back online.

For example:

• Power loss / battery drain
  • Kernel crash (BSOD)
  • Unresponsive system requiring hard power cycle
  • Virtual machine forcibly powered off
  • Hypervisor host crash taking VMs down
  • Forced reset via cloud or management tool

The results are faster root cause analysis for reboots and outages, clear differentiation between planned maintenance and unexpected disruption, and improved visibility and auditability when investigating downtime or user-reported issues To improve usability, shutdown and reboot events now include a slide-out details panel, making it easier to review full event context without leaving your workflow.