question

TimButterworth-5424 avatar image
0 Votes"
TimButterworth-5424 asked JennyFeng-MSFT answered

Wufb 1809 feature update path to 20H2

Hi There,

We have just started using Windows Update for Business to manage Windows updates and Feature updates and have some 1809 devices we'd like to update to 20H2 using this method. The problem we're having is that the test device wants to go 1809 -> 1903 -> 1909 -> 20H2 rather than 1809 -> 20H2. Is this expected behaviour? Is there a way round this?

The test device is not using WSUS and has the correct policy applied in the registry:

HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate

BranchReadinessLevel REG_DWORD 16: for Windows 10, version 1703: systems take Feature Updates for the Current Branch (CB); for Windows 10, version 1709, 1803 and 1809: systems take Feature Updates from Semi-Annual Channel (Targeted) (SAC-T); for Windows 10, version 1903 or later: systems take Feature Updates from Semi-Annual Channel

The deferment period for feature updates is set to 60 days after release.

As far as I can tell, the test device should be looking for the current feature update straight away, but 20H2 isn't picked up until 1909 has installed.

Thanks,

Tim

windows-10-general
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

JennyFeng-MSFT avatar image
1 Vote"
JennyFeng-MSFT answered

@TimButterworth-5424
Hi,
Yes, this is expected behavior.
Windows Update for Business devices running older versions will still see their policies honored after they update to a newer version; the old policy keys will continue to exist with their values ported forward during the update. Following the update to a newer version, only the old keys will be populated and not the new version keys, until the newer keys are explicitly defined on the device by the administrator.
If you need to skip a version (for example, update fall release to fall release) use the Select the target Feature Update version setting instead of using the Specify when Preview Builds and Feature Updates are received setting for feature update deferrals.

You could refer to the following official article to use group policy to configure Windows Update for Business:
https://docs.microsoft.com/en-us/windows/deployment/update/waas-wufb-group-policy
Hope above information can help you.

============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.