Oliver Kieselbach
8aeadb3728
Three issues surfaced in review of the parent-watch refactor. P1a — Watcher self-disposal deadlock in the appearance callback. Calling RegistryWatcher.Dispose() from the Changed handler re-entered Stop() → Thread.Join() on the same thread that owned the WatchLoop, hanging the watcher and skipping onAppeared(). Fix: RequestStop() (non-blocking) inside the callback, then ThreadPool.QueueUserWorkItem the actual Dispose so the join runs on a different thread after the loop has exited. P1b — All RealmJoin reads + watchers now explicitly bind to RegistryView.Registry64. The agent's intent is 64-bit, but the previous RegistryView.Default would still silently route HKLM\SOFTWARE through WOW6432Node if the host were ever spawned as a 32-bit process. Same defensive note already lives in TenantIdResolver. Affects RealmJoinInfo.cs (3 reads + enumerations), RealmJoinWatcher.KeyExists, and all four RegistryWatcher instantiations (1 parent-watch + 3 subtree-watches). P2 — Stale RealmJoinTimeout DeadlineFired after Resolved. Race: the cancel-effect for the timeout reaches the scheduler at the same time the deadline fires; the queued DeadlineFired signal is processed after RealmJoinResolved has already set Outcome="Resolved". Without a guard, the timeout handler still emitted a spurious realmjoin_timeout timeline event and re-entered TransitionToFinalizing, duplicating phase_transition(FinalizingSetup) on the wire and the FinalizingGrace deadline arm. Fix: short-circuit to a bookkept dead-end transition when either Outcome is already set OR the RealmJoinTimeout deadline is no longer in state.Deadlines (the cancel took effect). DeadEndReason carries the specific cause for the Inspector. Tests: DecisionCore 322 → 323 (new Stale_RealmJoinTimeout_after_Resolved_is_bookkept_dead_end_no_effects). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Autopilot Monitor
Advanced monitoring and troubleshooting solution for Windows Autopilot deployments. Gain full visibility into every enrollment session with a detailed event timeline, fleet health dashboards, and session reporting. Define custom analysis rules to automatically detect issues and gather rules to collect targeted evidence. Retrieve diagnostics packages on demand, configure agent settings like auto-reboot behavior and automatic timezone adjustment — all managed centrally from the web dashboard.
Private Preview
Autopilot Monitor is currently running as a Private Preview. Visit autopilotmonitor.com to request access and learn more.
Overview
Autopilot Monitor provides real-time tracking, intelligent diagnostics, and automated troubleshooting for Windows Autopilot enrollment processes. It consists of:
- Bootstrap Script — PowerShell script deployed via Intune that starts monitoring early in the enrollment process
- Monitoring Agent — Lightweight .NET application that collects telemetry and evidence during enrollment
- Backend API — Azure Functions-based ingestion and processing pipeline
- Web Dashboard — Next.js application for real-time monitoring and fleet analytics
Architecture
For detailed information about the system architecture, components, and data flow, see Architecture Documentation.
Documentation
Full documentation is available at autopilotmonitor.com/docs
License
This project uses a split licensing model:
- MIT License — Agent (
src/Agent/) and Shared library (src/Shared/) — unrestricted use on end-user devices - AGPL-3.0 — Backend (
src/Backend/), Web Dashboard (src/Web/), and MCP Server (src/McpServer/) — server-side components remain open source
See LICENSE for full details.