> For the complete documentation index, see [llms.txt](https://docs.autopilotmonitor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autopilotmonitor.com/changelog/agent-changelog.md). # Agent Changelog **Current versions:** ![Latest agent version](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fautopilotmonitor.blob.core.windows.net%2Fagent%2Fversion.json\&query=%24.version\&label=Agent\&prefix=v\&color=2563eb) ![Latest bootstrapper version](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fautopilotmonitor.blob.core.windows.net%2Fagent%2Fversion.json\&query=%24.bootstrapVersion\&label=Bootstrapper\&prefix=v\&color=2563eb) User-facing changes to the Autopilot Monitor agent, newest first. Only includes changes that affect agent behavior on the device. ## July 2026 * Fixed false enrollment failures during Account Setup on sessions that were still installing apps * Passive internet-bandwidth estimate during app installs, with a LAN/WAN split — survives reboots * MSIX/Store app install failures during ESP now identify the specific failing package * Fewer false ESP failures when Windows retracts a failure after a retry; a real failure now names the app still holding up Account Setup * More accurate script run-time shown for Remediation and Platform Scripts * Fixed a rare crash-loop that could follow a self-update restart * Windows Update-during-OOBE detection — reports quality/cumulative updates that start, succeed, or fail during enrollment * Best-effort emergency-break report when the agent hits its 48-hour absolute self-destruct * Registry gather collector reads the 64-bit view by default and supports emitting only when the key exists ## June 2026 * Optional keep-awake during Account Setup (off by default) prevents standby from stalling app installs * Fewer stuck enrollments — skipped ESP apps and advisory "continue anyway" failures now resolve quickly instead of hitting the 6-hour timeout * Desktop-arrival detection no longer stalls when the device-owner lookup fails * Agent now names the specific app holding up Account Setup completion instead of just reporting a stall * More accurate Office (M365 Apps) install tracking — no false failures for pre-installed Office, progress survives reboots * Low-disk-space warning when free space drops below 2 GB during enrollment * Repetitive ModernDeployment event bursts are rolled up into a single entry — less timeline noise * Hello for Business policy is no longer reported as "not configured" when it simply couldn't be detected * New liveness signals show what enrollment completion is waiting on — stuck sessions easier to spot * Startup events are de-duplicated across agent restarts, so a mid-enrollment reboot no longer repeats them * RealmJoin client detection is now opt-in per-tenant (off by default) and reports its release channel * Agent records the device's outbound IP for network correlation * Each agent request now carries a correlation ID for easier troubleshooting * Microsoft 365 Apps (Office) install tracking surfaces the real Click-to-Run install progress that Intune hides * Provisioning-package (`.ppkg`) detection, with security rules flagging packages outside a built-in allow-list * AutoLogon detection — flags only when a plaintext password is actually stored, avoiding false positives * ESP sub-category state changes are now surfaced even when they aren't failures * Stall-probe file and registry scans now enforce a hard timeout ## May 2026 * RealmJoin client detection — version, deployment-phase changes, and per-package install progress * Device hardware now reports CPU architecture (`x86` / `x64` / `ARM` / `ARM64`) * Startup power-state check warns when the device is running on battery below 80% * ESP app-install failures are now classified by HRESULT, with a 30-second settle window for late results * Crash mini-dumps are captured for deeper post-mortem analysis * More accurate Health Script results — no more false "failed" labels, and failures show an actionable message * Fewer false failures — ESP "continue anyway" and self-deploying scenarios now get a settle window before failing * Shutdown, diagnostics, and summary events are no longer dropped after a terminal enrollment decision * Bootstrap reports its version so it's visible in the session * Agent retries the remote-config fetch with a fallback when the first attempt fails * Security hardening for agent self-update, diagnostics URLs, and PowerShell argument handling * Agent V2 is now the primary production line — new installs ship V2 by default, existing V1 devices keep working * Health Scripts lifecycle monitoring — detection, remediation, and post-remediation shown as separate timeline events * Apps still installing when ESP-Apps times out are flagged "likely stuck" instead of disappearing * ASR / EDR-blocked install handoff no longer strands devices — agent resumes on next reboot * Hello-disabled enrollments now complete reliably instead of running into the 6-hour timeout * Fixed premature completion signals when AccountSetup actually failed * Hybrid User-Driven (HAADJ) enrollment-completion gaps closed — fewer sessions stuck in the timeout fallback * TPM PSS-unsupported devices now get a clear failure category instead of a generic Schannel error * Fixed certificate selection on devices with both MDM and MMP-C client certs * Client certificate rejections now show detailed context — easier to diagnose mTLS auth failures * Tenant ID resolution now falls back to the CloudDomainJoin registry when the primary key is empty * Event-driven Tenant ID wait — agent reacts to registry changes during pre-enrollment instead of polling * New liveness signals help distinguish a dead agent from a user who never logged in * Detailed shutdown reasons recorded when the agent exits unexpectedly * A prior-run crash is now surfaced in the next session instead of silently lost * V2 diagnostics ZIP is size- and count-capped — no more multi-gigabyte uploads on long sessions * Diagnostics ZIP now includes the State and Spool folders for richer post-mortem analysis * Agent log files rotate at a size cap — no unbounded growth on long-running devices * New "Submit Logs" page — admins can upload diagnostics even without an active session * Delivery Optimization breakdown adds MCC and LinkLocal sources * Software inventory now correctly enumerates Azure AD and personal MSA user profiles * Hardware spec event reports VM detection — security rules skip VMs to avoid false positives * Bootstrap `--install` mode preserves existing settings instead of clobbering them on re-install * Optional "enrollment started" webhook fires at session registration ## April 2026 * Delivery Optimization monitoring — download performance metrics per app during install * ConfigMgr co-management detection with confidence scoring * Non-whitelisted hardware detection with optional admin alerts * IME version change tracking * Hello for Business skip detection — distinguishes completed, timed out, or explicitly skipped * User-profile-aware diagnostics — gather rules can reference the logged-on user's profile directory * Improved vulnerability matching accuracy * Faster agent startup * ESP provisioning status verification before completion, with a 30s settle window for pending results * Structured error codes (exit codes, HRESULT) extracted from IME logs and included in timeline events * Dual-hash integrity verification detects tampering between download and install * Vulnerability matching improvements — confidence levels, platform-aware filtering, exclude patterns * Vulnerability reports now available during pre-provisioning (White Glove) sessions * More reliable enrollment summary dialog launch * PowerShell script output is now fully captured in the timeline * More reliable bootstrap and download handling * Agent reports self-update events so updates are visible in the session timeline * Emergency channel — agent can send distress signals when it detects critical failures * ESP "resumed" event is now only emitted for Hybrid Join scenarios * Improved crash recovery — completion state is persisted so the agent can resume after an unexpected restart ## Late March 2026 * Agent crash detection — crashes are automatically detected and reported to the backend * SHA-256 integrity verification for agent downloads (bootstrapper + self-updater verify hash before install) * Reboot tracking — reboots during enrollment are now tracked and visible in the timeline * NTP time sync check with clock skew warning when device time is significantly off * Automatic timezone detection and configuration * SecureBoot certificate collection for security posture reporting * IME process watcher — detects when the Intune Management Extension starts or stops * Network change detection — captures network adapter changes during enrollment * Agent self-update mechanism — outdated agents in the field update themselves automatically * Unrestricted mode option (per-tenant) to disable most guard rails * Notification system reworked — supports Teams (legacy + Workflow), Slack, and custom webhooks ## Mid March 2026 * Software inventory collection with automatic vulnerability correlation (CVE matching) * Hardware specification event — detailed hardware info collected and reported * Agent shutdown event — clean shutdown is now explicitly tracked * Postponed app detection and handling during enrollment * Self-deploying mode detection and event tracking * Enrollment summary dialog shown on the device after enrollment completes * ESP provisioning status tracking — catches non-IME errors like certificate failures * PowerShell script execution tracking during enrollment * Clock skew detection with geo-location failure reporting * Community analyze rules support ## Early March 2026 * Bootstrap session support — monitoring starts before MDM enrollment (during OOBE) * ESP configuration detection — identifies ESP settings on the device * TPM info collection for device details * Activity-aware idle timeout replaces fixed 4-hour collector limit (default: 15 min idle) * Reliable session end-detection for all deployment scenarios (user-driven, pre-provisioning, hybrid) * Network performance data collection (latency, throughput) * Geographic location support via IP-based lookup * Emergency break — remote kill switch to stop agents * Automatic retry on transient backend errors * Custom User-Agent header for easier firewall allowlisting * ESP state tracking via registry watcher * XML and JSON file gathering in diagnostics * Configurable `--await-enrollment` parameter for pre-enrollment wait ## Late February 2026 * Pre-Provisioning (White Glove) support — full end-to-end monitoring of pre-provisioning sessions * mTLS for all agent-to-backend communication (consolidated endpoints) * Diagnostics SAS URL fetched on-demand — no longer stored on disk * Max collector duration policy (configurable per tenant) * Diagnostics package upload from device * Configurable reboot-on-complete and keep-logfile options via remote config * Configurable diagnostics log paths (global + per-tenant) * Lenovo model detection fix (WMI query) ## Mid February 2026 * Windows Autopilot v2 (Device Preparation) support * GatherRules guard rails — prevents collection of overly broad paths * IME log replay for testing and demos (`--replay-log-dir`) * Agent state persistence — survives reboots and resumes monitoring * Embedded Intune root + intermediate certificates for chain validation * OS info and boot time collection * Hello screen detection improvements * Download progress tracking ## Early February 2026 * Initial agent release * Real-time enrollment telemetry (IME log parsing, ESP phases, app installs) * Geolocation support for enrollment sessions * Hello screen detector for enrollment completion * Reboot-on-complete support * Session ID persistence across agent restarts * Bootstrap token authentication for pre-MDM scenarios --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.autopilotmonitor.com/changelog/agent-changelog.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.