# Check existing Windows update offers before postponing a gradual rollout

> Does moving a gradual feature rollout's start date retract offers that devices already received?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:22:57+00:00
- Modified: 2026-09-10T02:11:18+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 1 minutes

## What you need to know

Does moving a gradual feature rollout's start date retract offers that devices already received?

## Potentially affected

Use this check when pausing expansion or revising a gradual feature-update rollout. Separate devices with an existing offer from those still waiting, and distinguish offer availability from installation progress.

## DSE recommendation

Base the intervention on current device states rather than a calendar edit alone.

## Article

## Source facts

For a gradual Windows feature rollout, moving the first-group date into the future leaves existing offers in place; newly added devices wait for the revised start. Changing rollout dates can reassign devices that have not yet received an offer. Removing a device from targeting triggers an attempted offer retraction, except when the device has already begun processing the update. [Microsoft Learn](https://learn.microsoft.com/en-us/intune/device-updates/windows/configure-rollout-options).

## Applicability

Use this check when pausing expansion or revising a gradual feature-update rollout. Separate devices with an existing offer from those still waiting, and distinguish offer availability from installation progress.

## DSE recommendation

Base the intervention on current device states rather than a calendar edit alone. Have the update owner identify the intended treatment for offered, processing, and not-yet-offered devices. Do not present a later start date as a universal stop command or promise that removing assignments can recall every update.

## Verification

In an approved pilot, inspect offer state before and after changing the schedule. Compare a device already offered the update with one awaiting a future group. Where targeting is removed, verify the actual resulting state and account for devices already processing the update. Preserve the original schedule, revised dates, and observations so support teams know which devices remain in progress.

## Official references

[Microsoft Learn: Configure Rollout Options for Feature Update Policies](https://learn.microsoft.com/en-us/intune/device-updates/windows/configure-rollout-options).

## Primary reference

- Name: Configure Rollout Options for Feature Update Policies - Microsoft Intune | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/intune/device-updates/windows/configure-rollout-options
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Check existing Windows update offers before postponing a gradual rollout,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-539-check-existing-windows-update-offers-before-postponing-a-gradual-rollout/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.