Navigation

  • Home
  • Documentation

    Known Issues

    Documented issues caused by external changes (e.g. Microsoft updates) that affect Autopilot Monitor. Each entry describes the impact, what still works, and whether a workaround exists.

    2026-04-05Breaking Change

    IME 1.101.x Removes Delivery Optimization Telemetry from Logs

    Starting with IME version 1.101.x, Microsoft no longer writes Delivery Optimization (DO) telemetry data to the IME log. This is a Microsoft-side change, not an Autopilot Monitor bug.

    What changed

    • Old IME (1.99.x): Wrote [DO TEL] = {JSON with all DO stats} after every download — full peer caching metrics were available.
    • New IME (1.101.x): Only writes [Win32App DO] DO download and decryption is successfully done — no DO telemetry JSON at all.

    What the new IME still logs

    • [Win32App] Downloaded file size 37,187,491.00 — file size only
    • [Win32App DO] start creating a new download job, FileId = ... — OriginalSize in ContentInfo JSON
    • [Win32App DO] DO Job set priority is BG_JOB_PRIORITY_FOREGROUND — download mode only

    What is lost

    The detailed DO stats — BytesFromPeers, PeerCaching %, LanPeers, GroupPeers, and all other DO telemetry fields — are no longer present in the IME logs. For IME ≥ 1.101 there is currently no way to extract DO telemetry from the logs because the data is simply not written anymore.

    Impact on Autopilot Monitor

    Sessions from devices running IME ≥ 1.101 will not show Delivery Optimization metrics in the timeline. Older IME versions continue to work as before. We are monitoring whether Microsoft re-introduces this data in a future IME release.