Windows 10 Image

I too noticed the DISM version was out of date. I don't think it's a problem.

As for doing a reset, you can alternately do an In-Place Upgrade, which will be up-to-date.
Repair Install Windows 10 with an In-place Upgrade






Here is the short version of the In-place upgrade tutorial...

DISABLE non-Microsoft:
a) antivirus software
b) firewall software
c) drive encryption software

Make a full OS backup with a program like Macrium Reflect (free)
Macrium Software | Macrium Reflect Free

Go here and get the Media Creation Tool and save it to your desktop.
https://www.microsoft.com/en-us/soft...load/windows10

RUN the Media Creation Tool and use it to: Create an ISO image... save IT to your desktop.
This will be the latest version of the ISO image. <------------------

For older ISO image versions, go here instead...
Download Windows 10 ISO File


Right click the ISO image and choose: MOUNT
Open File Explorer and you will see a new drive letter. It will look like a DVD optical drive.
Double click the new drive letter to open it.
Find setup.exe and double click it to start the in-place upgrade.

Choose the Keep personal files and apps option.

After it's all done... to UNmount the ISO image, right click the new drive letter and choose: EJECT.


The ONLY thing you will lose is some of your personalizations. Your programs and data will be intact.

Hello @engine987,

The ISO's that you can download are for the different builds etc. If MS were to update the ISO's every time there was a WU update, there would be hundreds of ISO's available, which as you can appreciate, is not viable.

I don't think it is a problem as DISM [ and SFC ] are using the System Core files etc.

You could always perform => How to Do a Repair Install of Windows 10 with an In-place Upgrade

I hope this helps.

engine987 said:

....what I meant is this: whatever DISM version is on your computer, if it's different than the Windows version running (my DISM version is 19041.572 whereas my computer is running version 19042.685), and a Windows update becomes available, in addition to updating the computer, why isn't it applied to the stored DISM version as well?

You are referring to this apparent anomaly.....



The major build 19041/19042 discrepancy is not significant. 2004 and 20H2 have the same system files so in this case they refer to the same build.

For the minor build number, it would seem that MS only update the minor build number of individual .exe files when they are replaced with an updated one by the current build. Have you checked the build number of explorer.exe in 19042.685? That's still on build 19041.662.



Other examples can be found that are an even older build.

My guess is that the form the DISM version is in is not compatible with applying an update; either that or Microsoft just decided not to do it!

My guess is that the functionality of DISM has not needed to be changed since 13th October 2020, build .572 so it hasn't been replaced.



If/when there is a bug fix or new function is added to DISM its .exe will be replaced and its build number will change, until then it will work as intended. The important thing for DISM to work correctly is that the WinSxS component store is fully up to date, and if it isn't then DISM will repair it and make it so.

engine987 said:

I recently ran DISM to scan the health of my image and noted that the image version is not the same as the Windows 10 version that is running. Is there any way to update the image so that it is the same as what is running? I would have thought that Microsoft would update the image as the various updates are installed. Is there any advantage to having an up-to-date image? Lastly, if I were to do a reset, I presume the out-of-date image would be used for the source?

Many utilities, such as DISM, report the "Kernel version" not the overall Windows version. So you might see, for example,
Deployment Image Servicing and Management tool
Version: 10.0.19041.572 - this is the Kernel version
Image Version: 10.0.19042.662 - this is the Windows {Image} version

Both Version 2004 [Build 19041] and Version 20H2 [Build 19042] share the same Kernel version 19041.
- This has been going on since Version 1903-1909 and seems likely to continue

Denis

This is currently only correct for Windows 10. See the next post for a version that works with both Windows 10 & Windows 11.

If you want an easily-run check of the Windows 10 Version rather than the Kernel Version then you can use this batch file.

ReportOSVersion.bat

Code:

:: This script retrieves & displays the Windows 10 OS Edition, Type [x64/x86], Version, Full build number
:: Each parameter is set as a variable value suitable for use elsewhere
:: Written by Denis, Try3  - www.TenForums.com

@echo off
prompt $g

:: Windows Edition
    Set UseExpresssion=Reg Query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "ProductName"
    for /F "tokens=*" %%X IN ('%UseExpresssion%') do Set OSEdition=%%X
    Set OSEdition=%OSEdition:*REG_SZ    =%
    ::echo %OSEdition%

:: Windows Type
    If Defined ProgramFiles(x86) (Set OSType=x64) Else (Set OSType=x86)
    ::echo %OSType%

:: Windows Version
:: Version 2009/20H2 introduced a new Registry entry to record Version number in the form 20H2 rather than the form 2009
:: This entry does not exist on earlier Versions so the old method is used first and the new method is then run for 2009/20H2 onwards
:: The repetition in code blocks seems to be the easiest way to handle the situation because referencing a non-existent Registry entry does not provide an easily-handled response such as an ErrorLevel
    
    :: The old command works for pre-2009 Versions [but now reports 2009 instead of the desired 20H2]
    Set UseExpresssion=Reg Query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "ReleaseId"
    for /F "tokens=*" %%X IN ('%UseExpresssion%') do Set OSVersion=%%X
    Set OSVersion=%OSVersion:*REG_SZ    =%
    ::echo %OSVersion%
    If %OSVersion% LSS 2009 GoTo BuildNo

    :: This command is only run for 2009/20H2 onwards to produce an output in the form 20H2
    Set UseExpresssion=Reg Query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "DisplayVersion"
    for /F "tokens=*" %%X IN ('%UseExpresssion%') do Set OSVersion=%%X
    Set OSVersion=%OSVersion:*REG_SZ    =%
    ::echo %OSVersion%

:BuildNo
:: Windows Build - this includes the full build number
    Set UseExpresssion=Ver
    for /F "tokens=*" %%X IN ('%UseExpresssion%') do Set OSBuild=%%X
    Set OSBuild=%OSBuild:*10.0.=%
    Set OSBuild=%OSBuild:~0,-1%
    ::echo %OSBuild%

:: Report results
    echo %OSEdition% %OSType% Version %OSVersion% Build %OSBuild%
Pause at end during testing

I use this batch file as a subroutine to set variables for other scripts.
- I have added a final display of all the parameters so that the script can be useful on its own.
- I have remarked out but not removed the echos I used during testing
- I have added a pause at the end so the result stays onscreen [for testing purposes]. You can remark that line out if you are using the batch file to set variables for other scripts.


Denis

If you want an easily-run check of the Windows 10 or the Windows 11 Version then you can use this batch file.
I've written this as a combined Windows 10 & Windows 11 script so that the same version can be run without alteration on both these OSes.

I last tested this revised script on
Windows 10 Home x64 Version 22H2 Build 19045.3930
Windows 11 Home x64 Version 23H2 Build 22631.2715

ReportOSVersion.bat

Code:

:: This script retrieves & displays the Windows 10 & Windows 11 OS Edition, Type [x64/x86], Version, Full build number
:: Each parameter is set as a variable value suitable for use in other scripts
:: All parameters are displayed at the end so they can be selected and copied if desired
:: Written by Denis, Try3 - www.TenForums.com www.ElevenForum.com
:: and the Windows Edition section was re-written to use an excellent suggestion by garlin

:: I never bother with @echo off but others seem to like it
:: I prefer to see everything in case I need to debug a script
@echo off

prompt $g

:: Windows Edition
    Set UseExpresssion=PowerShell.exe "Get-WmiObject -Class Win32_OperatingSystem | select Caption"
    for /F "tokens=*" %%X IN ('%UseExpresssion%') do Set OSEdition=%%X
:: Remove the leading word from the variable value
    Set OSEdition=%OSEdition:~10%
    ::echo %OSEdition%

:: Windows Type
    If Defined ProgramFiles(x86) (Set OSType=x64) Else (Set OSType=x86)
    ::echo %OSType%

:: Windows Version
:: Windows 10 Version 2009/20H2 introduced a new Registry entry to record Version number in the form 20H2 rather than the form 2009
:: This entry does not exist on earlier Versions so the old method is used first and the new method is then run for 2009/20H2 onwards
:: The repetition in code blocks seems to be the easiest way to handle the situation because referencing a non-existent Registry entry does not provide an easily-handled response such as an ErrorLevel
:: This section also works in Windows 11

    :: The old command works for Windows 10 pre-2009 Versions [but now reports 2009 instead of the desired 22H2 etc]
    Set UseExpresssion=Reg Query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "ReleaseId"
    for /F "tokens=*" %%X IN ('%UseExpresssion%') do Set OSVersion=%%X
    Set OSVersion=%OSVersion:*REG_SZ    =%
    ::echo %OSVersion%
    If %OSVersion% LSS 2009 GoTo BuildNo

    :: This command is only run for 2009/20H2 onwards to produce an output in the form 20H2
    Set UseExpresssion=Reg Query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "DisplayVersion"
    for /F "tokens=*" %%X IN ('%UseExpresssion%') do Set OSVersion=%%X
    Set OSVersion=%OSVersion:*REG_SZ    =%
    ::echo %OSVersion%

:BuildNo
:: Windows Build - this includes the full build number
    Set UseExpresssion=Ver
    for /F "tokens=*" %%X IN ('%UseExpresssion%') do Set OSBuild=%%X
    Set OSBuild=%OSBuild:*10.0.=%
    Set OSBuild=%OSBuild:~0,-1%
    ::echo %OSBuild%

:: Report results
    echo %OSEdition% %OSType% Version %OSVersion% Build %OSBuild%
Pause at end during testing

I use this batch file as a subroutine to set variables for other scripts.
- I have added a final display of all the parameters so that the script can be useful on its own.
- I have remarked out but not removed many of the echoes I used during testing
- I have added a pause at the end so the result stays onscreen [for testing purposes]. You can remark that line out if you are using the batch file to set variables for other scripts.


Denis

Docfxit,

Yes. The instructions are in the file itself so you can read through them in Notepad.
ReportMajorParametersOfTargetOS.bat

The tool was discussed in
Get Edition, Version, Build of a system image or network computer - TenForums

"I know there is a way to load the registry hive but I don't know how to do that."
My own short reminder for this topic is to run these [sample] commands as Admin

Code:

reg load HKU\Fred C:\Users\SomeAccountOrOther\ntuser.dat
reg load HKU\FredClass C:\Users\SomeAccountOrOther\AppData\Local\Microsoft\Windows\UsrClass.dat

reg unload HKU\Fred
reg unload HKU\FredClass

and I use Reg commands instead of loading hives using RegEdit because I find it easier to avoid errors by loading the hive first and then running RegEdit to edit it.
- I use names (like Fred) for the added Hive because they stick out like a sore thumb in RegEdit & this also helps to guard against making mistakes.
- You might well not need to load the Classes hive. I think I have only ever done so as an exercise. I include it in my note because I know I'll forget it otherwise.
- You can see the full list of Hives & their locations in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\hivelist but do note that, despite being an HKLM Key, it only lists the current user.

I also described this method for opening other user hives in
my example of using an offline Registry hive in RegEdit - TenForums


Other hives can also be loaded within RegEdit [instead of using Reg commands] but I have seen others report making mistakes when trying to do so & getting themselves into an awful tangle. I thought I had written out & posted an illustrated procedure for this but cannot find it. All I seem to have kept is the MS guide to doing this -
Load or Unload Registry Hives - MSDocs



All the best,
Denis