Version and build number are reported incorrectly after you build a new Windows Image file

Symptoms

You create a new Windows ImageĀ (WIM) file for Windows 10, version 1909 or 20H2. When you check the Windows version and build number of the new WIM file, the image metadata reports that the version and build numbers are from Windows 10, version 1903 or 2004 respectively.

For example, you create a new WIM file for Windows 10, version 20H2. To do this, you combine the latest cumulative update (LCU) for Windows 10, version 2004 (dated October 13, 2020 or a later LCU) together with the latest servicing stack update (SSU), and the feature enablement (eKB) pack for Windows 10, version 20H2. When you check the Windows version and build number, the image metadata reports that the version and build numbers are from Windows 10, version 2004.

Status

We are working to simplify this procedure for future releases so that the image metadata reports the correct version and build number.

More information

Windows 10, versions 1903 and 1909 share a common core operating system with an identical set of system files. Similarly, Windows 10, versions 2004 and 20H2 also share a common core operating system with an identical set of system files. Because of this, the image metadata on 1909 media will report the version 1903 build number of 18362 and image metadata on 20H2 media will report the version 2004 build number of 19041.

To determine whether the media is 1909 media, mount the image, run dism /get-packages and check whether the 1909 Enablement Package is installed. Specifically, look for a package named Package_for_KB4517245.

To determine whether the media is 20H2 media, mount the image, run dism /get-packages and check whether the 20H2 Enablement Package is installed. Specifically, look for a package named Package_for_KB4562830.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×