Acronis Telemetry Finds Microsoft Patches Take 7.7 Days at Median, With a 38.6-Day Tail

· Original article ↗

Summary

Acronis H2 2025 telemetry found median Microsoft patch installation took 7.7 days, with P90 at 38.6 days. Third-party patches were faster at median but also had a long tail. Recommendations include weekly tail reviews, staged rollouts, reboot discipline and endpoint (

Key points

  • Acronis telemetry for H2 2025 measured Microsoft patch installation at a median of 185 hours (7.7 days) and a P90 of 926 hours (38.6 days).
  • Third-party patches had a median installation time of 136 hours (5.7 days) and a P90 of 597 hours (24.9 days).
  • In the global status mix, about half of patch candidates were New/Pending and more than 40% were Obsolete; the report cautions that obsolescence can reflect catch-up patching rather than patches being ignored.
  • The report identifies delayed reboots, unreachable endpoints and irregular maintenance windows as major contributors to long patching delays; outright installation failures remained low in the telemetry.
  • Country-level Microsoft patch medians ranged from about 4.2 days in Mexico to 14.8 days in Japan, while some markets had P90 delays measured in months.
  • Recommendations include reviewing lagging devices weekly, treating reboot completion as a defined workflow, using staged rollouts, tracking OS and application patching separately, and monitoring endpoint reachability and agent health.

Article Details

Publisher
Acronis
Report Period
H2 2025
Scope
Patch deployment timing and status for Microsoft and third-party applications in Acronis telemetry, with a focus on SMB and MSP operations.
Key Statistics
  • Microsoft patches: median installation time was 185 hours (7.7 days); P90 was 926 hours (38.6 days).
  • Third-party patches: median installation time was 136 hours (5.7 days); P90 was 597 hours (24.9 days).
  • Microsoft patch status: 49.6% New/Pending, 44.9% Obsolete, 3.6% Installed, 1.1% Reboot required, and 0.7% Failed.
  • Third-party patch status: 51.9% New/Pending, 43.2% Obsolete, and 4.0% Installed.
Recommendations
  • Manage patching to the P90 tail and review stale pending, reboot-required, and repeatedly delayed endpoints weekly.
  • Make reboot completion a defined workflow, with user notifications, limited deferrals, and scheduled forced reboots for persistent deferrers.
  • Use staged rollouts, beginning with a 5%–10% pilot ring before broader deployment.
  • Report OS and application patching separately, including their medians and tails.
  • Standardize endpoint configurations where possible, enforce endpoint check-in requirements, and monitor agent health continuously.

Vendors

Products

Related Articles