Windows 10 Spring Creators Update: Act fast to delay this big upgrade

Each time Microsoft rolls out a major upgrade to Windows 10, you have the option to wait a few months before you install it on PCs running Windows 10 Pro or Enterprise. But you have to act quickly.



Use these settings in Windows 10 version 1709 to defer the Spring Creators Update for a minimum of 90 days.




Note: This article has been completely revised for the latest Windows 10 feature updates. This revision covers version 1803 and was last updated 21-March-2018.]

Sometime in April, Microsoft's update servers will begin delivering the Windows 10 Spring Creators Update, version 1803, to current installations of Windows 10 that have been running for at least 30 days.

This is the latest feature update in Microsoft's new twice-a-year release cadence, and you should view it with the skepticism any initial public release of a new Windows version deserves. In a business setting, that typically means delaying the upgrade for a few months while you deploy the new release on a smaller number of test devices.

This deferral process is available only on PCs running business and education editions, such as Windows 10 Pro, Windows 10 Enterprise, and Windows 10 Education. Windows 10 Home does not offer any deferral options.

Over the course of several feature updates since the initial release of Windows 10 in 2015, Microsoft has tinkered with the interface for deferring feature updates. The steps I describe here assume that you have already installed the Creators Update, version 1709.

The good news is that you no longer have to mess with Group Policy settings to defer updates on a standalone PC. Instead, you can take your choice of three options, all available in the Windows 10 Settings app.

Go to Settings > Update & security > Advanced options to see all three options, which I have labeled in the screenshot on this page.

Option 1 allows you to choose a servicing channel (previously called a branch). The default setting is Semi-Annual Channel (Targeted), which corresponds to what was previously known as the Current Branch.

You can change this setting to Semi-Annual Channel (the new name for what was previously known as Current Branch for Business, as shown here. That defers feature updates until Microsoft declares them "ready for business deployment," a milestone that typically occurs about four months after the initial release.

Option 2 allows you to specify additional time after the official release to the channel you selected. You can delay the upgrade by up to an additional 365 days from its initial release date; in the example shown here, I've chosen a 90-day delay, which means that the 1803 feature update will not be offered to this PC until at least July 2018.

On any PC where you choose the full 365-day deferral and have opted in to the Semi-Annual Channel, you'll be spared any feature updates until sometime in mid-2019. (Here, too, this option is available only on PCs running business and education versions of Windows 10.)

Option 3 works independently of the feature update settings and allows you to defer the monthly cumulative security updates by up to 30 days. In this example I have chosen to delay these updates by 7 days to allow time for testing.

To make the equivalent changes on a corporate network using Group Policy, follow a slightly different set of steps.

Using Group Policy Editor, navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business. Open the policy Select when Preview Builds and Feature Updates are received, set it to Enabled, and then use the controls to choose your preferred branch. The options here are identical to those in Settings.

Just be sure to set a calendar reminder at least a week or two before the expiration date, because you won't receive any warning when the clock runs out. You'll simply see the update offered for installation, with no more options to delay or defer.

Comments are closed.

%d bloggers like this: