Three Windows policy values control when Chrome updates download: a check cadence, a suppression window, and a version pin. Set all three through your existing management tooling — no new tool required.
Key takeaways
- auto-update check period override — minimum minutes between update checks (Google's worked example uses 480)
- update suppression — a quiet window (start time in 24-hour format + duration in minutes) during which nothing downloads or installs; holds across daylight saving changes
- version pin — the Chrome version (such as 90, 55.24 or 90.24.34) updates are allowed to reach; patches keep flowing within the series, but the jump to a new major waits for you
- Map your call calendar first, then set the suppression window, check cadence, and pin in that order; push to a small group and verify before rolling out
- This is timing control, not a substitute for security patching — build a recurring review step so pins and windows move deliberately
Why rep laptops keep updating at the worst time
A forecast call starts in the morning. Reps open their laptops. Chrome decides this is a good moment to pull an update. Bandwidth drops. The CRM tab reloads. Screens flicker mid-pipeline review.
You have seen this. Quarter-end reviews make it worse. Everyone is on the same call at the same time, so any slowdown hits the whole team together.
Google Update checks for new Chrome releases, downloads them, and installs them. None of this waits for your meeting to end.
The good news: Google documents the controls below for this behavior. Three numbers, set as Windows policies, change the picture. This post walks through each one, gives you the value to enter, and explains what happens on the other side.
This is a Google Chrome on Windows story. Apple devices use a different mechanism, and Windows quality updates follow their own policy path. Both are noted at the end so you can point colleagues to the right control.
What Google Update actually does on your machine
Google Update is the background service that keeps Chrome current. It checks, it downloads, it installs.
Three things matter for your forecast calls:
- How often it checks for a new release.
- When it is allowed to download and install.
- Which version is permitted for migration.
Each of those maps to a Windows policy you can push through your existing management tooling. Google documents all three on its Chrome Enterprise update management page.
Set them right and your reps' laptops go quiet during the calls that matter. Set them wrong or leave them at defaults, and you are gambling with bandwidth every quarter-end.
Let's take them one at a time.
Number 1: How often Google Update checks
The first control is the Auto-update check period override. It sets the minimum time between update checks.
The override sets a minimum gap between checks, and you can lengthen that gap.
The policy value is in minutes. Google's worked example uses 480 minutes — eight hours. The example spells out how the mechanism behaves: "For example, if you set the Auto-update check period override policy to change the minimum time period between update checks to 480 minutes, then each hour Google Update checks to see if the last update check was more than 480 minutes ago."
Read that carefully. Google Update still wakes up every hour. It just asks a question: has it been 480 minutes since the last check? If no, it goes back to sleep. If yes, it checks.
The practical effect for you: you can set a gap that suits your meeting schedule. Checks fall wherever that minimum gap lands, and the policy cannot pin them to a call window. So the gap alone will not keep checks out of your calls.
Choose the number from your calendar. The policy takes only a minutes value, so the gap is yours to tune.
One caution: a longer check period does not stop updates. It reduces how often checks run.
Number 2: When updates are suppressed
The second control is the update suppression window (start time and duration). This is the one that most directly stops downloads during a call.
You give Google Update a start time and a duration in minutes. During that window, updates are suppressed. Nothing downloads. Nothing installs. The machine stays quiet.
Google's documentation gives a clean example: "For example, if the start time is 22:00 and the duration is 480 minutes, the updates will be suppressed for 8 hours regardless of whether daylight savings time changes happen in between."
Two details worth noting in that sentence. First, duration is in minutes, not hours — 480 minutes equals eight hours. Second, the suppression holds across daylight saving transitions. Your window does not drift when clocks change. Set it once and it holds.
For a revenue leader running forecast calls at the same time each week, this is the lever. Set a suppression window that brackets your call schedule. Morning reviews, Monday pipeline calls, Thursday forecast — all covered by one window if they align. For restart behavior, see restart timers for a forecast call.
The start time is in 24-hour format. Pick a time that makes sense for your team's calendar and a duration long enough to cover the block. The policy holds during the window, full stop.
Suppression and the check-period override work together. One controls when Google Update looks. The other controls when it acts. Stack them and downloads and installs hold during the hours you name.
Here is how the three controls compare at a glance:
| Control | What it sets | Value format | Effect on your calls |
|---|---|---|---|
| Auto-update check period override | Minimum time between checks | Minutes, such as 480 | Checks run at the minimum gap you set, not at a chosen time of day |
| Update suppression window | Quiet window for downloads and installs | Start time (24-hour) + duration in minutes | No download activity during the window |
| Version pin | Which Chrome version updates are allowed | Version string, such as 90, 55.24 or 90.24.34 | Patches keep flowing in the pinned series; the jump to a new major waits for you |
The table covers the three numbers in this post. Each row expands below.
Number 3: Which version you allow
The third control is the version itself. Google Update will move a machine to whatever release matches the version rule you set.
Google accepts a few formats. From the documentation: "For example, entering 90, 55.24, or 90.24.34 are all valid values for Google Chrome."
That range of formats gives you real flexibility. A short value like 90 pins to a major version. A longer, more specific value narrows further. Pick the granularity that matches how tightly you want to control the fleet.
Why does this matter for a forecast call? Each update still means a download. Google notes: "Subsequent updates from one version to the next are approximately 10-15 MB."
If you pin your fleet's version, you decide when the move to a new major happens. It happens on your schedule, not during a pipeline review.
There is a second behavior to understand. When you pin a version, Google Update keeps taking updates until the next major appears — and then stops. Google states: "As with the other values, entering 90 will allow Google Update to continue getting released updates until the first version of 91 is released."
So a pin is not a freeze. It is a hold until a boundary. Once the boundary crosses, the machine waits for you to move the pin. That is exactly the control a revenue leader wants: patches keep flowing within the series, the big jump waits for your go-ahead.
Combine the pin with a suppression window and you get a second layer. Even if a boundary release exists, the download will not start during your quiet hours. Two independent controls, same goal.
How the three numbers work together
Stack all three and the behavior looks like this.
Google Update wakes up on your extended cadence. It sees the version pin. Within the pinned series, it is free to pull patches — but only outside your suppression window. When a new major appears, it stops at the pin boundary and waits.
You get patches without surprises. You get a quiet laptop during the call. You get a decision point at each major release, handled by your team instead of by a background service.
None of this requires a new tool. These are Windows policies. Push them through whatever management system already reaches your reps' machines. The values live in one place, and you change them when your calendar changes.
For a revenue team, the natural rhythm is this. Before the quarter opens, review the current pin and move it if you want the new major in play. Set the suppression window to cover your recurring forecast and review blocks. Set the check-period minimum gap in minutes to suit your team's rhythm. The policy cannot place checks at a chosen time of day. Revisit at quarter-end.
Setting this up before your next forecast call
Do the work in this order.
First, map your call calendar. Write down the hours your forecast calls, pipeline reviews, and quarter-end sessions occupy. These are the hours that must be silent. A forecast call setup checklist can help you list them.
Second, set the suppression window. Pick a start time before your first protected block. Choose a duration long enough to cover the last one.
Third, set the check cadence. Choose an Auto-update check period in minutes that sets the minimum gap between checks. Google's worked example uses 480 minutes, a starting point to tune.
Fourth, set the version pin. Decide which Chrome version your fleet sits on. Enter it in the format that matches how tightly you want to hold. Remember the pin holds until the next major appears.
Fifth, push the policies and verify. Apply them to a small group first. Confirm a rep's machine stays quiet during a test window. Then roll to the full team.
Sixth, calendar the review. Put a recurring note on your own calendar to revisit the pin and the windows. Chrome releases continue. Your settings need a periodic look.
That is the whole procedure.
What this does not cover
Three adjacent topics are worth naming so nobody points at the wrong control.
Apple devices use a different path. Apple's own documentation notes that software updates for Apple devices can be cached on a Mac running macOS 10.13 or later when Content Caching is turned on (Apple Support). If part of your team is on Apple hardware, that is the control to investigate — it is a caching mechanism, not a suppression window.
Windows quality updates follow their own policy engine. Microsoft publishes separate controls for pausing and resuming Windows updates (Microsoft Learn). For the pause side, see Windows update pause. One detail trips up administrators: "Although the device will resume quality updates after 35 days automatically, the pause check box will remain selected in the policy editor." The checkbox looks paused while the machine has already resumed — a reporting artifact, not a live hold. Check actual behavior, not just the editor state.
Pins and windows can delay security fixes. Suppressing updates and pinning versions means your fleet stays on a known release for a defined period. Patches within the series still flow when your window allows. The point is timing control, not update refusal. Build a review step so pins move deliberately, and set a separate, fast path for critical security releases.
The three numbers, one last pass
Set the check-period minimum gap in minutes. The policy cannot place checks outside call hours. Set the suppression window so downloads and installs hold during your protected blocks. Set the version pin so the big jump into a new major waits for your go-ahead.
Three numbers. One afternoon of setup. The calls and windows you configure stay quiet. Checks and pinned-version changes outside those windows can still bring updates into a call.
Start with your calendar, write down the hours you need protected, and push the policies before the next call. Your reps will notice the difference the first time a pipeline review runs without a mid-screen refresh.
FAQ
Will a long check period stop Chrome from updating entirely?
No. It only changes how often Google Update looks. Pair the check cadence with a suppression window to control when the download actually starts.
What happens if I pin a version and a critical patch arrives in the next major?
The pin holds until the first release of the next major appears, then the machine stops moving. You will need to raise the pin to let the new major land. That is by design — it forces a deliberate decision. The patch within the current series still arrives on your normal schedule. Plan a separate, fast path for critical security releases.
Does the suppression window block everything, or just downloads?
The window suppresses update activity — the download and install steps Google Update would otherwise run. It simply holds action until the window closes.
How long should the suppression duration be?
Long enough to cover your longest protected block from the moment it starts. Add buffer if other reviews bracket the call.
Does daylight saving time shift my suppression window?
No. Google's documentation says the suppression holds across daylight saving changes.
Can I set different windows for different teams?
Only if your management tool applies different values to different machines. The mechanism is the same; only the values change.
Where do I ask if my situation is not covered?
Your IT or endpoint management team owns the policy deployment. For questions about how a specific Chrome policy behaves, Google's Chrome Enterprise documentation is the reference.