Two Windows update windows matter for rep laptops before quarter-end: a 35-day pause for quality and feature updates, and a 30-day quality defer. Log both start and expiry dates so no rep's machine surprises them during the final week of the quarter.
Key takeaways
- The pause holds back quality updates for up to 35 days from when you set the value, then expires on its own and the device scans Windows Update
- Feature updates follow the same 35-day rule on Windows 10 version 1703 and later, but the pause checkbox stays selected in the policy editor even after the pause ends
- The defer (DeferQualityUpdatesPeriodinDays) holds quality updates for up to 30 days from the update's release date, not from when the policy applied
- A pause applied late can still reach a total of 35 days by configuring a later start date
- Log start and expiry dates for each device in one shared sheet and review at the start of each quarter to flag any expiry landing mid-quarter
Why this matters before quarter-end
You manage a team of reps who live on Windows laptops. Quarter-end is when deals close and forecasts get signed off. The last thing you want is a laptop pulling down updates mid-push. Windows gives you pause settings. Two of them matter for planning. One runs 35 days. One runs 30 days.
You need to log both. You need to know when each one expires. That way no rep's machine surprises them during the final week of the quarter.
The Configure Windows Update client policies page at Microsoft Learn is the source for the rules below. Read it once and you will know the maximum time your team can hold updates back.
The 35-day pause you should log first
This is the main pause. You set it on a device. The device stops taking quality updates for up to 35 days from the moment you set the value.
When the 35 days are up, the pause expires on its own. The device then scans Windows Update and takes whatever quality updates apply. Microsoft states this plainly: "After 35 days have passed, the pause setting will automatically expire and the device will scan Windows Update for applicable quality updates."
That is the window you write on your calendar. Set it on the first day of your quarter and it expires about five weeks later.
Feature updates follow the same 35-day rule
Windows 10 version 1703 and later let you pause feature updates for 35 days too. The Microsoft page puts it this way: "In Windows 10, version 1703 and later versions, you can pause feature updates to 35 days, similar to the number of days for quality updates."
One detail catches teams off guard. The device resumes feature updates after 35 days on its own. The pause checkbox in the policy editor stays selected. The page warns: "Although the device will resume feature updates after 35 days automatically, the pause check box will remain selected in the policy editor."
So the checkbox does not tell you the pause is still live. Your log tells you. Check your own dates, not the box.
Extending a pause that started late
Sometimes you apply the pause policy after the start date already passed. You can still stretch the pause. The page says you can extend it "up to a total of 35 days by configuring a later start date."
The total stays 35 days. A later start date shifts the window. It does not give you a longer hold.
The 30-day quality defer you should log second
The second window is a defer, not a pause. You set the DeferQualityUpdatesPeriodinDays value. The device then holds quality updates for up to 30 days from their release.
Microsoft's wording: "You can defer receiving these quality updates for a period of up to 30 days from their release by setting the DeferQualityUpdatesPeriodinDays value."
The clock here runs from the update's release date. Not from the day your policy applied. That difference matters when you plan a quarter.
If a quality update ships early in your quarter, a 30-day defer keeps it off your rep's machine. If it ships later, the defer may run past your quarter-end. You will want to know which case you are in.
The two windows side by side
| Window | What it holds back | Length | Clock starts |
|---|---|---|---|
| Pause | Quality updates | Up to 35 days | From when you set the value |
| Defer | Quality updates | Up to 30 days from release | From the update's release date |
| Pause | Feature updates | Up to 35 days | From when you set the value |
What "up to" actually means for your log
Both figures say "up to." Microsoft gives you a ceiling, not a guarantee. The pause runs no longer than 35 days. The defer runs no longer than 30 days from release.
Treat those as your maximum hold. Log the start date. Add 35 for a pause, or find the release date and add 30 for a defer. The earlier date is the date your laptop may resume updates.
If you want a safety margin, log a shorter window. The ceiling is fixed. Your plan does not have to sit right on it.
Planning the pause around your quarter
Pick the day you apply the pause. Count 35 days forward. See where it lands.
If it lands after your quarter-end, the pause covers the days from the set date until it expires. If it lands before, you need a different start day or you need to accept that updates will resume mid-quarter.
The same exercise works for the defer. Find the release date of the quality update in question. Add 30 days. Compare that date to your quarter-end. For how quarter-end deals are grouped, see Pipeline, Best Case, Commit: Forecast Categories Explained.
Ask your IT team how a pause interacts with other update policies they already run. They will know what is already configured on your fleet.
What happens when a pause expires
A paused device does not sit idle forever. When the 35 days end, the pause drops. The device scans Windows Update. It installs whatever quality updates apply.
If that expiry date falls on a Monday morning before a big demo, your rep will feel it.
Map the expiry dates onto your team's calendar. Block out the first hour after any expiry for update time. Simple habit, few surprises.
Feature updates behave the same way. They resume after 35 days even though the editor still shows the box checked. Do not rely on the editor to tell you what is live.
Tracking pause dates across a team
You manage many laptops. Each one has its own pause start date. Each one has its own expiry.
Log them in one place. A shared sheet works. For related log habits, see Close date change log: why the date moved. Columns for rep name, device ID, pause start date, pause expiry date, defer expiry date.
Review the sheet at the start of each quarter. Flag any expiry that lands inside your quarter. Decide then whether to shift the start date or accept the update.
This is the whole discipline. Three dates for each device. One place to see them. A weekly glance.
Quality updates and feature updates
Quality updates are the smaller, more frequent ones. Your pause and your defer both target these.
Feature updates are the larger, less frequent ones. The 35-day pause also covers these on Windows 10 version 1703 and later.
If you only track one kind, track quality updates. They land more often. They are more likely to interrupt a selling day.
When to start the pause for best coverage
Start the pause early in your quarter. A single 35-day pause covers only about the first five weeks of a quarter.
Start it late, and it expires before your close. Then your reps take updates during the final stretch.
Work backwards from your quarter-end date. Subtract 35 days to find the earliest start day that still reaches it. Coverage from the quarter's first day needs a start no later than quarter-start, and 35 days cannot span the whole quarter.
For the defer, work from the release date of the quality update you are worried about. Add 30 days to get the defer's end date, then compare that date to your quarter-end. That tells you whether the defer alone covers you.
Logging the dates in your own words
Your log entry does not need technical language. Write it the way you would say it out loud.
"Laptop A: quality pause set October. Expires November. Feature pause set October. Expires November."
"Laptop B: quality defer running from release date. Expires 30 days after release."
The goal is that any manager on your team can open the sheet and know, in ten seconds, whether a laptop is paused or live.
Handling a pause applied after the start date
You cannot always act on day one. A new rep joins mid-quarter. Their laptop needs a pause now.
The Microsoft page covers this case. You can push the total to 35 days by configuring a later start date.
So the new rep still gets a full 35-day hold. Their window simply starts later. Log their start date separately. Their expiry will differ from the rest of the team.
The checkbox trap in the policy editor
The policy editor shows a pause checkbox. After 35 days, the device resumes feature updates. The checkbox still looks selected.
Do not use the editor as your source of truth. Use your log. The editor lags the real state of the device.
This one detail saves teams from a common mistake: assuming a pause is still active because the box looks checked.
A simple review rhythm that works
At the start of each quarter, open your pause sheet. Look at every expiry date. Flag the ones inside the quarter.
Talk to your IT team about any laptop with an expiry that lands mid-quarter. Ask them what other policies are in place.
Mid-quarter, do a quick spot check. Confirm that no laptop quietly resumed updates without your notice.
End of quarter, archive the sheet. Start a fresh one. The discipline is small. The payoff is a calm final week.
Illustrative example: pause and defer dates
Suppose a rep's laptop gets a 35-day pause on day 1 of the quarter. The pause expires on its own about five weeks later, and the laptop scans Windows Update after that. A quality update released on day 10 can be deferred for 30 days from its release date, so that defer runs past the pause's expiry. Write both start and expiry dates in the sheet, and it shows which updates the laptop can take before quarter-end.
Your next step today
Open your shared sheet today and add one row for each device. Record its pause start date, pause expiry date and defer expiry date, then flag any expiry that falls inside the quarter.
Quick answers before you close the tab
Which figure should I put on my quarter plan first? Log the 35-day quality pause. It is the primary hold on a rep's laptop.
Does the defer run from the day I set it? No. The defer runs from the quality update's release date, and it runs up to 30 days.
Will the pause keep running if I forget about it? No. The pause expires on its own after 35 days. The device then scans Windows Update and installs what applies.
Is the pause checkbox a reliable indicator? No. After 35 days the device resumes feature updates while the checkbox stays selected in the policy editor. Trust your log.
How late can I set a pause and still reach quarter-end? Subtract 35 days from your quarter-end date to find the earliest start day that still reaches it. A single 35-day pause cannot cover a full quarter.
What about a laptop that joins the team mid-quarter? You can still reach a total of 35 days by configuring a later start date for the pause policy.
Related guides: Dynamics restore: 4 windows to log before quarter-end · Backup recovery: 4 figures to check before quarter-end · Commission accrual: 3 mistakes before quarter-end close.