SCCM Versions, Build Numbers

SCCM Versions, Build Numbers, Console, and Client Details

Written By

Prajwal Desai

Last Updated

January 30, 2026

Posted In

This post lists all the SCCM versions, build numbers, console version numbers, site and client version numbers. The latest SCCM (aka ConfigMgr) current branch build numbers and version numbers are updated with every new release.

Every Configuration Manager current branch release has a unique build number, version number, console version number, and full version number associated with it. In addition, every major SCCM version also updates the client agent version.

The hotfix updates, if they include client agent fixes, will also update the client agent version number. Look at the list of all the SCCM hotfixes and rollup updates released for every version of the current branch.

Install and Update Third Party Applications with Patch My PC
Install and Update Third Party Applications with Patch My PC

SCCM Current Branch Release Cycle

The SCCM CB release has been changed to one update per year. As per the SCCM new release cadence, Microsoft will release only one current branch update every year instead of two. This change will come into effect after the release of Configuration Manager version 2609.

By releasing a single SCCM current branch update per year, Microsoft believes that it will reduce ConfigMgr deployment management. SCCM administrators will have one less upgrade to do. This modification will enable Configuration Manager to continue releasing high-quality updates while having a longer development cycle to respond to important customer feature requests.

List of SCCM Versions and Build Numbers

The following table lists the following details about the latest ConfigMgr current branch release:

Version or HotfixFull Version NumberBuild NumberClient VersionConsole VersionBaseline Version
SCCM 25095.0.9141.100091415.00.9141.10115.2509.1036.1200YES
Hotfix Rollup KB32851084 for 25035.0.9135.100091355.0.9135.10135.2503.1083.1500NO
KB34503790 Revised Security Update5.0.9135.100091355.0.9135.10065.2409.1183.1500NO
KB33177653 Update for 25035.0.9135.100091355.0.9135.10065.2409.1183.1500NO
KB32480179 hotfix for 25035.0.9135.100091355.00.9135.10015.2503.1083.1000NO
SCCM 25035.0.9135.100091355.00.9135.10015.2503.1083.1000NO
KB30385346 Hotfix Rollup for SCCM 24095.0.9132.100091325.00.9132.10235.2409.1183.1400NO
SCCM 2409 Hotfix KB308330535.0.9132.100091325.00.9132.10135.2409.1183.1000NO
SCCM 24095.0.9132.100091325.00.9132.10115.2409.1183.1000NO
SCCM 2403 Rollup KB282041605.0.9128.100091285.00.9128.10305.2403.1171.2400NO
SCCM 2403 Hotfix KB29166583 5.0.9128.100091285.00.9128.10145.2403.1171.1600NO
SCCM 2403 Hotfix KB284587465.0.9128.100091285.00.9128.10145.2403.1171.1600NO
SCCM 2403 Hotfix KB282903105.0.9128.100091285.00.9128.10055.2403.1171.1600NO
SCCM 24035.0.9128.100091285.00.9128.10055.2403.1165.1000YES
SCCM 2309 Hotfix Rollup KB258584445.0.9117.100091175.00.9122.10185.2309.1113.1900NO
SCCM 2309 hotfix KB261298475.0.9117.100091175.00.9122.10075.2309.1109.1300NO
SCCM 23095.0.9117.100091175.00.9117.10025.2309.1109.1300YES
SCCM 2303 Hotfix KB247196705.0.9106.100091065.00.9106.10225.2303.1089.1300NO
SCCM 2303 Hotfix KB247212085.0.9106.100091065.00.9106.10185.2303.1089.1300NO
SCCM 2303 Hotfix KB210104865.0.9106.100091065.00.9106.10155.2303.1089.1300NO
SCCM 23035.0.9106.100091065.00.9106.10005.2303.1089.1000YES
SCCM 2211 Hotfix KB166438635.0.9096.100090965.00.9096.10245.2211.1061.1300NO
SCCM 22115.0.9096.100090965.0.9096.10005.2211.1061.1000NO
SCCM 2207 hotfix KB151524955.0.9088.102590885.0.9088.10255.2207.1048.2600NO
ConfigMgr 2207 Hotfix KB155990945.0.9088.101390885.00.9088.10075.2207.1048.1700NO
SCCM 2207 Hotfix KB154987685.0.9088.101290885.00.9088.10075.2207.1048.1700NO
SCCM 2207 Hotfix KB149784295.0.9088.100090885.00.9088.10075.2207.1048.1700NO
SCCM 2207 Hotfix KB149599055.0.9088.101090885.0.9088.10105.2207.1048.1700NO
SCCM 22075.0.9088.100090885.00.9088.10075.2207.1048.1700NO
SCCM 2203 Hotfix KB142444565.00.9078.102590785.00.9078.10255.2203.1063.2400NO
SCCM 2203 Hotfix KB144800345.00.9078.100790785.00.9078.10065.2203.1063.1500NO
SCCM 2203 Hotfix KB139530255.00.9078.100790785.00.9078.10065.2203.1063.1500NO
SCCM 22035.00.9078.100090785.00.9078.10065.2203.1063.1400YES
SCCM 2111 Hotfix KB128960095.00.9068.100090685.00.9068.10265.2111.1052.2500NO
SCCM 2111 Hotfix KB129595065.00.9068.100090685.00.9068.10125.2111.1052.1700 NO
SCCM 2111 Hotfix KB127097005.00.9068.100090685.00.9068.10085.2111.1052.1700NO
SCCM 21115.00.9068.100090685.00.9068.1005 5.2111.1052.1700NO
SCCM 21075.00.9058.100090585.00.9058.10125.2107.1059.2000NO
SCCM 21035.00.9049.100090495.00.9049.10085.2103.1059.1700YES
SCCM 20105.00.9040.100090405.00.9040.10105.2010.1093.1800NO
SCCM 20065.00.9012.100090125.00.9012.10155.2006.1026.1800NO
SCCM 20025.00.8968.100089685.00.8968.10215.2002.1083.1700YES
SCCM 19105.00.8913.100089135.00.8913.10005.1910.1067.2100NO
SCCM 19065.00.8853.100088535.00.8853.10065.1906.1096.1500NO
SCCM 19025.00.8790.100087905.00.8790.10055.1902.1085.1500YES
SCCM 18105.00.8740.100087405.00.8740.10035.1810.1075.1300NO
SCCM 18065.00.8692.100086925.00.8692.10035.1806.1074.1200NO
SCCM 18025.00.8634.10008634  YES
SCCM 17105.00.8577.10008577 NO
SCCM 17065.00.8540.10008540 NO
SCCM 17025.00.8498.10008498 YES
SCCM 16105.00.8458.10008498 NO
SCCM 16065.00.8412.10008412 YES
SCCM 16025.00.8355.10008355 NO
SCCM 15115.00.8325.10008325 YES
SCCM Versions Build Numbers

SCCM 2012 R2 and Older Build Numbers

The table below contains all the build numbers and version information for SCCM 2012 R2 and previous releases. Note that these versions have gone out of support.

SCCM ReleaseVersionBuildKB
SCCM 2012 R2 SP1 CU45.00.8239.15018239KB3195483
SCCM 2012 R2 SP1 CU35.0.8239.14038239KB3135680
SCCM 2012 R2 SP1 CU25.00.8239.13018239KB3100144
SCCM 2012 R2 SP1 CU15.00.8239.12038239KB3074857
SCCM 2012 R2 SP15.00.8239.10008239 
SCCM 2012 R2 CU55.00.7958.16047958KB3054451
SCCM 2012 R2 CU45.00.7958.15017958KB3026739
SCCM 2012 R2 CU35.00.7958.14017958KB2994331
SCCM 2012 R2 CU25.00.7958.13037958KB2970177
SCCM 2012 R2 CU15.00.7958.12037958KB2938441
SCCM 2012 R2 Hotfix5.00.7958.11017958KB2905002
SCCM 2012 R2 RTM5.00.7958.10007958 
SCCM 2012 SP1 CU55.00.7804.16007804KB2978017
SCCM 2012 SP1 CU45.00.7804.15007804 
SCCM 2012 SP1 CU35.00.7804.14007804 
SCCM 2012 SP1 CU25.00.7804.13007804 
SCCM 2012 SP1 CU15.00.7804.12027804 
SCCM 2012 SP15.00.7804.10007804 
SCCM 2012 RTM5.00.7711.00007711 
SCCM 2012 R2 and Older Build Numbers

Find SCCM Version

The SCCM build number is unique for every release and gets updated with every major release. The build number won’t change after installing the hotfixes. There are multiple ways to check the installed version of SCCM, and they are described below.

Method 1: Configuration Manager Console

Use the following steps to find the SCCM version number of the current branch:

  • Launch the ConfigMgr Console.
  • Click About > Configuration Manager.
  • In the About Microsoft Configuration Manager window, you see the Version Number.
Find SCCM Version using console
Find SCCM Version using console

Method 2: Windows Registry

Along with SCCM build numbers, you can find SCCM full version details in the registry. On the SCCM server, open the Registry Editor and browse to the following path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup

Look for the value name “Full Version,” and that shows the SCCM full version number. For example, in the below screenshot, the full version of SCCM 2107 is 5.00.9058.1000. Do not modify any of those registry values, as they may interfere with Configuration Manager’s operation.

Find SCCM version from Registry
Find SCCM version from Registry

Find SCCM Build Number

There are multiple methods to find the build number of SCCM. To get the current SCCM build number, you can either look at the registry or the properties of the site server. Out of the two methods, you can quickly get the build number of ConfigMgr by going to the site server’s properties. Let us go over both of these methods for determining the build number.

Method 1: Windows Registry

Use the following steps to find the build number of SCCM using Registry:

  • On the SCCM server, launch the registry editor.
  • Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup and look for the UI Version.
  • The “UI Version” registry value represents the build number of the SCCM version.
Find SCCM Build Number using Registry
Find SCCM Build Number using Registry

Method 2: Site Server Properties

You can also find the SCCM build number in the site properties. In the Configuration Manager console, go to Administration > Overview > Site Configuration > Sites. Right-click the SCCM site and select Properties. On the General tab, you can find the build number of Configuration Manager.

Find SCCM Build Number using Site Properties
Find SCCM Build Number using Site Properties

Find SCCM Console Version Number

If you are tasked with finding the installed console version, there are multiple ways to do that.

Method 1: Configuration Manager Console

You can find the SCCM console version numbers by following the below steps:

  • Launch the SCCM console.
  • Click on the drop-down arrow near the home button.
  • Select “About Configuration Manager“.
  • The popup window shows the SCCM Console version along with the site version.
How to Check SCCM Console Version
How to Check SCCM Console Version Number

Method 2: Windows Registry

To retrieve the product code and version number of an installed console through the registry, open the Registry Editor and navigate to the specified registry path on the computer where the Configuration Manager console is installed. Here, the value of ‘AdminConsoleVersion‘ key shows the installed console version.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ConfigMgr10\Setup
Check SCCM Console version from the Registry
Check SCCM Console version from the Registry

Find the SCCM client version number

The exact client version running on your system can be determined with multiple ways. Let me show you those methods.

Configuration Manager Properties

  • On the computer, launch the Control Panel and select the Configuration Manager applet to launch it.
  • Under Configuration Manager properties, select the General tab.
  • In the General tab, you will find the full SCCM client version number.
How to find the SCCM Client Version number
How to find the SCCM Client Version number

PowerShell

To quickly check the installed ConfigMgr client version, simply execute the following command in the PowerShell window.

Get-CimInstance -Namespace 'ROOT\ccm' -ClassName 'CCM_InstalledComponent' | Where-Object {$_.Name -eq 'SmsClient'}

In the below image, the command output displays the installed client version.

Check SCCM client version using PowerShell
Check SCCM client version using PowerShell

Leave a Reply

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

31 Comments

  1. Hello!
    What release of SCCM does client version 5.00.8853.1020 belong to?
    Somewhere between SCCM 1906 and 1910?
    I’ve seen it being installed from an installation of SCCM 2303 (Hotfix Rollup) and that seems a bit odd.

    Reply

  2. Hi Prajwal,
    How can I get SCCM version number from SQL Query. We have few SCCM back up DBs on SQL Server. Could you please let me know? Some dbs don’t have DBSchema table.

    Thank you
    Ram

    Reply
  3. Avatar photo Philippe B says:

    Hello,
    The Version for CurrentBranch 2309 is 5.00.9120.1000 and is not a baseline.

    best regards from Switzerland,

    Philippe

    Reply

  4. Good Day Prajwal,

    We have an environment that is running 1802, (yes, I know, ancient) and want to go to 2211. Based on my research, please correct me if I am wrong, this is the SCCM versions I need to upgrade to as part of the process to 2211: 1802 –> 1902 –> 2002 –> 2107 –> 2211.

    The above is for the server components. How about the client/end-points? – Do I need to step-upgrade them in a similar order? Or can I actually go from 1802 to 2211 (sccm client)?

    Thank you greatly for any help.

    Cheers,
    Tomas

    Reply

    1. You can use the upgrade path that you mentioned. Client upgrade can be done once you install the final version. You can either use automatic client upgrade or manually push the clients to device collections.

      Reply

  5. Hi Prajwal,
    Is it correct that the SCCM 2207 has exactly the same build as the SCCM 2207 Hotfix KB14978429?
    The patch between has a different build SCCM 2207 Hotfix KB14959905.
    So the patch level goes up and then again down.
    I can’t validate it but is seems wrong to me.
    Best Regards,

    Alex

    Reply

  6. Hi Prajwal, Which version of SCCM is compatible with Intune for a hybrid environment?

    Thanks

    Reply
  7. Avatar photo Massimo Vincenzi says:

    Hi Prajwal, thank you so much for your guides.
    The SCCM client 5.00.9088.1007 works with Windows 7?
    Thank you

    Reply

  8. Please Share step by step upgrade Version from 2010 to Latest Version without any issue or Impacts current setup.

    Reply

  9. We must be about due a 2102 release. Anyone know when it’s due? Just thinking ahead to ensure support of 21H1 once that’s released.

    Reply

    1. The ConfigMgr 2103 is the next release and it will be released soon. I mean very soon.

      Reply

  10. Hi Prajwal,

    My organisation are currently using console version 1802 and we are planning to upgrade it to higher version (stable one) . What is the version we should upgrade to ?

    Please give your expert advise.

    Reply

    1. It will be a two step upgrade. You can install SCCM 1906 update on sites that run version SCCM 1802, SCCM 1806, SCCM 1810, or SCCM 1902. You can begin upgrading to Configuration Manager 2010 on sites that run version SCCM 1906, SCCM 1910, SCCM 2002 or ConfigMgr 2006.

      1. Upgrade your Configuration Manager version 1810 to version 1906 first – https://www.prajwaldesai.com/sccm-1906-step-by-step-upgrade-guide/
      2. Upgrade SCCM 1906 to SCCM 2010 – https://www.prajwaldesai.com/sccm-2010-upgrade-guide/

      Reply

      1. For my organization that runs on 1902, would the process be the same?

        Reply
  11. Avatar photo Andy Shepherd says:

    Hi Prajwal, Thanks for all the work that you do!

    What is the best way to know when a new Config Manager version is released? My boss is adamant that we have the latest version as soon as it is available. Is there any kind of email or notification service I can sign up for that you know of?

    Thanks!!

    Andy

    Reply

    1. Microsoft publishes the information about the new update as when it gets released. Over Twitter you get some news about upcoming update. Apart from that I try my best to publish the new update information on my blog. You should also get a console notification about the new update available.

      Reply
      1. Avatar photo Andy Shepherd says:

        Thank you, Sir!

        Reply
  12. Avatar photo Tom Paget says:

    Hey Prajwal,

    Awesome content!

    Reply

  13. Hi there,

    Please help me, I want to upgrade SCCM Current Branch 1902 to the latest.

    Reply
  14. Avatar photo Michael Pal says:

    After a much heated discussion, I believe my organization is moving towards SCCM. My questions are as follows:
    -SCCM 2012 is being taught yet the exam has been retired-what version should I train for?
    -Microsoft has integrated SCCM into Endpoint Configuration manager-what version should we be looking at for installation on Windows server 2008 R2 or Server 2012 R2?..or are we purchasing MS Endpoint Configuration Manager 2019?
    Thank you for your responses.

    Reply

    1. SCCM 2012 is an expired product and you won’t be getting any updates for it. You should go with Configuration Manager current branch (latest version) if you decide to implement it across the estate. I will find out more info about exam and will update the answer.

      The windows server should be atleast Windows 2012 R2 and above. I always prefer to use the latest and stable version Of Windows server. You can also check the system OS requirements for specific version of Current Branch and go with that info.

      Reply
  15. Avatar photo Emrah Ozdemir says:

    Thanks for the info. I wonder is there any absolute dates for (production versions)
    I mean, there is tech preview versions 1908, 1909,1910 etc. But is it clear for new production version will be (lets say) 1911.
    Is there any standard ?

    Reply

    1. There are no absolute dates for production versions. Usually they are released for fast ring customers first and then made globally available.

      Reply

  16. I am having issues with updating to 1802. Its been about a month and my SCCM server is still downloading 1802. Plz help.

    Reply
  17. Avatar photo Mike Webber says:

    Don’t forget the 1802 Hotfix (KB4132447) version too?

    5.00.8634.1011

    Reply

Prajwal Desai

Prajwal Desai is a highly accomplished technology expert and an 11-time Dual Microsoft MVP (Most Valuable Professional), specializing in Microsoft Intune, SCCM, Windows 365, Enterprise Mobility, and Windows. As a renowned author, speaker, and community leader, he is widely recognized for sharing his in-depth expertise and insights through his blog, YouTube channel, conferences, webinars, and other platforms.