Skip to content
ENExplore Calculators

Patch Window Calculator

Size a maintenance window: waves, patch and reboot time, validation, expected rollbacks and whether the work fits the outage you were given.

About Patch Window Calculator

Patching time scales with the number of waves, not the number of hosts: doubling parallelism halves the elapsed time until you hit the limit of your change tooling or your tolerance for simultaneous outage. The two fixed blocks — pre-change snapshots and post-change validation — dominate small batches, which is why patching 20 hosts rarely takes a third as long as patching 60. Windows are approved in hours, and the change that overruns is the one that gets your patching programme throttled to quarterly — plan the rollback time in from the start.

Formulas

Patch Window

Waves = ceil(hosts ÷ parallelism); window = pre-checks + waves × (install + reboot) + validation + expected failures × rollback time, all in minutes and divided by 60.

waves
Sequential batches of hosts
parallelism
Hosts patched simultaneously
expected failures
hosts × failure rate
rollback
Minutes to restore one failed host

Rollback allowance

Expected failures = hosts × failureRate ÷ 100, and rollback time is added serially because a failed host is usually recovered by hand while the next wave waits.

Worked example

With the default values below, Patch Window Calculator returns Total Window Needed of 13.45. Change any input above and every figure here is recalculated in your browser.

Inputs used

Hosts to patchaccepts 1–100,000 hosts
240 hosts
Hosts patched in parallelaccepts 1–5,000 hosts
10 hosts
Patch install time per hostaccepts 1–480 minutes
12 minutes
Reboot and service-up time per hostaccepts 0–240 minutes
6 minutes
Pre-change checks and snapshotsaccepts 0–600 minutes
30 minutes
Post-change validation and smoke testsaccepts 0–600 minutes
45 minutes
Expected failure rate per hostaccepts 0–100 %
5 %
Rollback time per failed hostaccepts 0–480 minutes
25 minutes
Approved outage windowaccepts 0.5–72 hours
6 hours

Results

Total Window Needed
13.45 hours
Patch Waves
24
Patching and Reboot Time
7.20 hours
Expected Failed Hosts
12.0 hosts
Headroom in the Window
-7.45 hours
Windows Needed
3
Fit Against the Approved Window
Does not fit — split into 3 windows of about 80 hosts

Step by step

  1. 1Values used
  2. 2Patch Window
  3. 3Rollback allowance
  4. 4Total Window Needed= 13.45 hours
  5. 5Patch Waves= 24
  6. 6Patching and Reboot Time= 7.20 hours
  7. 7Expected Failed Hosts= 12.0 hosts
  8. 8Headroom in the Window= -7.45 hours
  9. 9Windows Needed= 3

Assumptions and limits

  • The result is derived only from the 9 inputs listed above. Anything not among them is not part of the calculation.
  • In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
  • Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

Frequently Asked Questions

How is Patch Window calculated?

Waves = ceil(hosts ÷ parallelism); window = pre-checks + waves × (install + reboot) + validation + expected failures × rollback time, all in minutes and divided by 60. Patching time scales with the number of waves, not the number of hosts: doubling parallelism halves the elapsed time until you hit the limit of your change tooling or your tolerance for simultaneous outage. The two fixed blocks — pre-change snapshots and post-change validation — dominate small batches, which is why patching 20 hosts rarely takes a third as long as patching 60.

Why does Patch Window matter?

Windows are approved in hours, and the change that overruns is the one that gets your patching programme throttled to quarterly — plan the rollback time in from the start.

What values do I need to enter?

This calculator takes 9 inputs: Hosts to patch, Hosts patched in parallel, Patch install time per host, Reboot and service-up time per host, Pre-change checks and snapshots, Post-change validation and smoke tests, Expected failure rate per host, Rollback time per failed host, Approved outage window. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Should I raise parallelism to fit the window?

Only up to the point where a simultaneous failure is survivable. If ten hosts patch at once and the update is bad, ten hosts are down and your rollback allowance has to cover all ten. Keep parallelism below the redundancy of the cluster.

Why is validation time as long as patching?

Because the change is not finished when the package installs; it is finished when the service is proven healthy. Skipping validation is how a patch window becomes a Monday-morning incident with no clear cause.

Related Calculators

Patch Window Calculator (Vulnerability Management)