SCCM

Upgrade to Windows 10 20H2 using ConfigMgr – Master Guide

In this post I will cover the steps to upgrade to Windows 10 20H2 using ConfigMgr. The Windows 10 20H2 update KB4562830 is released and you can upgrade to Windows 10 20H2 using ConfigMgr. The 20H2 update is also known as Windows 10 October 2020 Update.

The Windows 10, version 20H2 comes with new features for select performance improvements, enterprise features, and quality enhancements. Most of all, Windows 10 20H2 is an H2-targeted release. It will be serviced for 30 months from the release date for devices running Windows 10 Enterprise or Windows 10 Education editions.

Like 1909 update, the Win 10 20H2 is available as enablement package. On a Windows 10 machine, you can download and install Windows 10 20H2 October 2020 update via Windows Update as well.

To upgrade to Windows 10 20H2 using ConfigMgr, you can either use the servicing plans or deploy the 20H2 feature update or enablement package. SCCM admins can deploy the Windows 10 20H2 enablement package to upgrade Windows 10 2004 to 20H2.

Since the update 20H2 is very new and I would not recommend deploying this update directly on to end user devices. You may probably test the 20H2 update deployment on few machines and if they work well, you can then work on phased deployment plan.

Important – If you are running Windows 10, version 2004 and haven’t installed the September 8, 2020 updates, you will not see the version 20H2 enablement package on your device.

Options to Upgrade to Windows 10 20H2 using ConfigMgr

So if you have decided to upgrade to Windows 10 20H2 using ConfigMgr, there are few things to consider. Based on your current Windows 10 version, the deployment method varies.

  • Upgrade Windows 10 1909 and earlier builds to Windows 10 20H2 – If you have a device running Windows 10, version 1909 or an earlier version such as Windows 10 1903, do not deploy the enablement package. That’s because the enablement package is not meant for older builds. Furthermore you cannot install the enablement package on these devices manually. In this case you must deploy a Windows 10 20H2 feature update and perform the upgrade to version 10 20H2.
  • Upgrade Windows 10 2004 to Windows 10 20H2 – If you are running Windows 10 version 2004 on your devices, you can deploy the Windows 10 20H2 enablement package. The version 20H2 enablement package KB4562830 updates from version 2004 to version 20H2 with a single restart, reducing the update downtime.

Windows 10 20H2 Feature Update vs Enablement Package

So just to make it more clear, the below info will help you to decide which update to deploy.

  • Feature Update to Windows 10 Version 20H2 x64-based systems 2020-10 via Enablement Package – Install this update to enable the Windows 10 Version 20H2 feature set for Windows 10 Version 2004 devices. It is only applicable to Windows 10 Version 2004 devices that have installed the 2020-10 or later Cumulative Update. After you install the KB4562830 update, you will have to restart your computer.
  • Feature update to Windows 10 (business/consumer editions), version 20H2 – Deploy this update using ConfigMgr to upgrade your Windows 10 1909 and earlier builds to version 20H2.

Windows 10 20H2 Upgrade Prerequisites

You must have the following prerequisites installed before you upgrade to Windows 10 20H2 using ConfigMgr

Download Windows 10 20H2 Feature Update

If you have set up your Software Update Point correctly, you should find the Windows 10 20H2 feature update in the updates list. If you don’t, manually run the software updates sync.

Run the Software Updates Synchronization and open the wsyncmgr.log file on site server. You should see the Windows 10 20H2 updates in the list.

Feature Update to Windows 10 Version 20H2 x64-based systems 2020-10 via Enablement Package
Feature Update to Windows 10 Version 20H2 x64-based systems 2020-10 via Enablement Package
Synchronizing update d6d35b34-003a-4825-b46f-231c6b70158c - Feature Update to Windows 10 Version 20H2 x64-based systems 2020-10 via Enablement Package

In the Configuration Manager console, go to Software Library\Overview\Windows 10 Servicing\All Windows 10 Updates. Right click Feature update to Windows 10 version 20H2 and click Download.

Download Feature update to Windows 10 version 2004
Download Feature update to Windows 10 version 20H2

Create a new deployment package. Specify the name as Windows 10 20H2 Deployment Package and define the package source. Click Next.

Create Windows 10 20H2 Deployment Package
Create Windows 10 20H2 Deployment Package

Specify the distribution points or distribution point groups. Click Next.

Add Distribution Points
Add Distribution Points

Nothing to change on Distribution Settings page. So click Next.

Specify Package Distribution Settings
Specify Package Distribution Settings

We will download the Windows 10 20H2 updates from internet. Click Next.

Download 20H2 Feature Update from Internet
Download 20H2 Feature Update from Internet

We have successfully downloaded Windows 10 20H2 feature update. Click Close.

Download Software Updates wizard
Download Software Updates wizard

If you want to know the size of Windows 10 20H2 feature update, it’s 3.77 GB. It’s a big update, and you should find two files within that folder. An ESD file and WindowsUpdatebox.exe file.

Upgrade to Windows 10 20H2 using ConfigMgr Snap8

Deploy Windows 10 20H2 Feature Update using SCCM

We will now deploy Windows 10 20H2 feature update. In the SCCM console go to Software Library > Overview > Windows 10 Servicing > All Windows 10 Updates. Right click Feature update to Windows 10 (business/consumer editions), version 20H2 and click Deploy.

Deploy Feature update to Windows 10 (business/consumer editions), version 20H2
Deploy Feature update to Windows 10 (business/consumer editions), version 20H2

On the General page, specify the deployment name. Next click Browse and choose a device collection. Click Next.

Specify Deployment Details
Specify Deployment Details

Specify the type of deployment which is either Available or Required. I am going to make this deployment Available for end users. Click Next.

Feature Update Deployment Settings
Feature Update Deployment Settings

On the Scheduling page, you can choose the software available time. Since I want the feature update 20H2 to appear ASAP in Software center, I will select As soon as possible. Click Next.

Specify Deployment Schedule
Specify Deployment Schedule

Specify the user experience for this deployment. Click Next.

Specify User Experience
Specify User Experience

Specify the download settings based on your requirements. Click Next.

Download Settings
Download Settings

Finally on the Completion page, click Close.

Feature Update Deployment Complete
Feature Update Deployment Complete

Upgrade Windows 10 1909 and earlier to Windows 10 20H2

In the above step you deployed the Windows 10 20H2 feature update to a Windows 10 device collection. This device collection consists Windows 10 1909 and earlier builds.

Since I have made the 20H2 feature update available in software center, the update will show up once the clients receive the deployment. All the user needs to do is select the Windows 10 20H2 feature update and click Install.

The installation time is not going to be quick as compared to enablement package installation. The device will restart in order to complete the Windows 10 20H2 upgrade.

Download Windows 10 20H2 Enablement Package

We will now download and deploy Windows 10 20H2 enablement package that simply upgrades Windows 10 2004 builds to version 20H2.

Navigate to Software Library > Overview > Windows 10 Servicing > All Windows 10 Updates. Right click Feature Update to Windows 10 Version 20H2 2020-10 via Enablement Package and click Download.

You can either deploy the update directly or download it first and then deploy. I prefer to download the update first and then deploy.

Correction – In the below screenshot, instead of download option the deploy option is highlighted by mistake.

Download Windows 10 20H2 Enablement Package
Download Windows 10 20H2 Enablement Package

Create a new deployment package by specifying deployment name and package source. Click Next.

Create Windows 10 20H2 Deployment Package
Create Windows 10 20H2 Deployment Package

In this step click Add button and specify the distribution points or DP groups. Click Next.

Select Distribution Points
Select Distribution Points

Select Download software updates from internet and click Next.

Download the Enablement Package from Internet
Download the Enablement Package from Internet

On the remaining pages, click Next and on Completion window, click Close.

Upgrade to Windows 10 20H2 using ConfigMgr
Upgrade to Windows 10 20H2 using ConfigMgr

The Windows 10 20H2 enablement package is only 86MB in size and hence you will notice that it doesn’t take much time to download on client machines.

Windows 10 20H2 Enablement Package Size
Windows 10 20H2 Enablement Package Size

Deploy Windows 10 20H2 Enablement Package using ConfigMgr

To deploy Windows 10 20H2 upgrade enablement package using ConfigMgr.

  • In the ConfigMgr console, go to Windows 10 Servicing and click All Windows 10 Updates.
  • Right click Feature Update to Windows 10 Version 20H2 2020-10 via Enablement Package and click Deploy.
Deploy Windows 10 20H2 Enablement Package using ConfigMgr
Deploy Windows 10 20H2 Enablement Package using ConfigMgr

On the General page, specify the deployment name. Click Browse and select a Windows 10 device collection running 2004 builds. Click Next.

Upgrade to Windows 10 20H2 using ConfigMgr
Upgrade to Windows 10 20H2 using ConfigMgr

Select the Type of deployment. In this case, I will select Required. I will schedule the update and let the user install it within specified days. If the user doesn’t install the update, it installs as per the deadline. Click Next.

Windows 10 20H2 Deployment Settings
Upgrade to Windows 10 20H2 using ConfigMgr – Deployment Settings

I will set the software available time to As soon as possible and installation deadline to end of the month. Click Next.

Windows 10 20H2 Deployment Schedule
Upgrade to Windows 10 20H2 using ConfigMgr – Deployment Schedule

Specify the user experience settings for the deployment and click Next.

Upgrade to Windows 10 20H2 using ConfigMgr Snap26
Upgrade to Windows 10 20H2 using ConfigMgr – User Experience Settings

Click Close.

Upgrade to Windows 10 20H2 using ConfigMgr Snap27

Upgrade to Windows 10 20H2 using ConfigMgr

Login to the Windows 10 2004 client machine. Wait until the deployment appears in the software center. The Windows 10 20H2 enablement package should appear in Updates tab.

Select the Feature Update to Windows 10 Version 20H2 x64-based systems 2020-10 via Enablement Package and click Install.

Upgrade to Windows 10 20H2 using ConfigMgr
Upgrade to Windows 10 20H2 using ConfigMgr

The installation was quick and the Restart option appeared in just few minutes. Click Restart to finish the Windows 10 20H2 upgrade.

Upgrade to Windows 10 20H2 using ConfigMgr
Upgrade to Windows 10 20H2 using ConfigMgr

Login back to the client computer and run the winver command to find the Windows 10 version and build details. If you see Windows 10 version as 20H2, smile and start preparing a plan to deploy to update to rest of the machines in your setup. Hope the steps to upgrade to Windows 10 20H2 using ConfigMgr helps.

Upgrade to Windows 10 20H2 using ConfigMgr
Upgrade to Windows 10 20H2 using ConfigMgr

Prajwal Desai

Hi, I am Prajwal Desai. For last few years I have been working on multiple technologies such as SCCM / Configuration Manager, Intune, Azure, Security etc. I created this site so that I can share valuable information with everyone.

Related Articles

19 Comments

  1. Hello, how much disc space is needed to perform a upgrade to 20h2 using service plan?
    I see that the update is 3.77 but I think that is needed more space to descompress it and to manage the updates.

    Thanks!

  2. SIR My client machine running in 2004,I try to upgrade to 20H2
    But it is not happening, But i can able to upgrade 1803 to 20h2
    Please provide assistance

  3. Hi Prajwal Desai,

    I’m trying to test to install 20H2 via feature updates using SCCM. I have followed the steps you’ve provided above but when I click to install the updates in software center. After downloading it will show “Failed” with error code 0x80246002(-2145099774). Would you be able to share your thoughts about this.

    TIA

  4. That’s strange, I just deployed “Feature update to Windows 10 (business editions), version 20H2, en-us x64” to 2 machines – A test Laptop and a Test Virtual Machine.

    Software center shows “Installed” and it installed pretty quick… yet when i run ‘winver’ it still says the same version. I deployed it to a Microsoft Windows 10 Pro 1909 OS Build 18363.1379 and an Enterprise version same build..

    I then ran the Feature update manually that I downloaded from Microsoft since this didn’t work, and the install took a lot longer, which is expected.. and it upgraded successfully.. but the problem is I want to deploy this to hundreds of machines through SCCM but it doesn’t seem to work. Any ideas?

    1. I’ve found this to be due to the feature update checking for critical updates in the background, pre-installation. If I use the media creation tool and the ‘/dynamicupdate disable’ switch it flies through the install. I’m having to build an app in SCCM now to deploy 20H2 as you cannot manipulate this setting via SCCM as a software update, so far as I can tell. This was especially prevalent for us as we have a group policy in place for dynamic updates throttling comms to Microsoft for updates to 10kbps. For some reason this update check falls outside of config manager (although all other windows updates are deployed via SCCM) and can go directly to Microsoft.

  5. i have issues trying to deployn Servicing Plan W10 20H2:
    Status: Failed to install update(s)

    Error Code: 0X00000000
    Error Code: 0X87D01107
    Error Code: 0X87D00664
    ————————————

  6. I have pushed the feature to all of my win 10 2004 versions, they have the January cumulative and service stack updates but none show the new version.

  7. Hello,
    After deploy Feature update to 20h2 to Windows 2004, Sccm says completed but in fact Windows doesn’t update to 20H2.

  8. Hello,
    I have same issue:
    “I have deployed 20H2 feature upgrade however none of none of the clients gets installed with updates, infact in machine end no scan has initiated in WUAHANDLER.LOG. However machine showing in compliant. ”
    My client has Windows ver2004.
    Where I can find the log which describe the problem?

    Thanks

  9. Deploying featured update failed with the following error Error 0XC1900208 and after checking the compdata it shows hardwaretype “generic” is causing the failure how can I get this fixed

  10. I have deployed 2004 feature upgrade however none of none of the clients gets installed with updates, infact in machine end no scan has initiated in WUAHANDLER.LOG. However machine showing in compliant.

  11. Hi, I deployed 20H2 upgrade, in deployment status show that all computers are compliant but any have the update installed. Also not show update in the software center.

  12. I deployed the update to some computers, but neither one of them had the update, but the compliance says 100% compliant.
    thats weird

  13. Now we are using Microsoft Edge installed on Windows 1809.
    We have version of Edge 85. I traid upgrade through SCCM like on this article. After upgrade to 20H2 Edge was downgraded to version 84. 
    It there some way how upgrade without downgrade Edge?
    Thank you

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button

Thanks for Supporting PrajwalDesai.com

We deliver articles on Configuration Manager, Intune, Windows Servers and other technologies at no cost to you. To do this, we display ads from only trusted partners. To continue on our site, simply turn off your ad blocker or whitelist this site and refresh the page.