Hi All,

I have a Windows ISO called "Windows.iso". Is there
a way to look inside the iso (easily done) and check what
build, release it is?

Many thanks,
-T

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

T <[email protected]d> wrote:

I have a Windows ISO called "Windows.iso". Is there
a way to look inside the iso (easily done) and check what
build, release it is?

See my reply to your "22H2 iso download" thread. I gave some info on
how to look at the properties of setup.exe file in the ISO image to get
the build version, and DISM commands on finding what editions of Windows
are in the ISO image (which edition depends on the license key or
product ID used to activate), and the service pack (since the core build
of 19041 has been the same since the 2004 version with the applied
service pack level indicating the later amended build on install).

My last sentence in my prior post in your other thread was supposed to
be "God, I hate drinking Microsoft's muddy waters for information."

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 8/22/24 10:41 PM, Big Al wrote:

On 8/22/24 08:38 PM, T wrote:

Hi All,

I have a Windows ISO called "Windows.iso".  Is there
a way to look inside the iso (easily done) and check what
build, release it is?

Many thanks,
-T

These are from some notes I've made.  They're data 2021.  I don't see anything dangerous, take it
with a grain of salt.

Would help to post the info too.

1: Look in the ../Windows/System32 folder for a file called "ntoskrnl.exe".
If this file exists, it is at least an NT based system.

Now do a properties and examine the details for a product version.

4.x: NT 4.x
5.0: Windows 2000
5.1: Windows XP
5.2: Windows 2003 Server or Windows XP-64-bit
6.0: Windows Vista
6.1: Windows 7
6.2; Windows 8
6.3: Windows 8.1
10.0: Windows 10

This does not however tell you which flavor of those systems (Pro, Home, etc). On one device I see 6.2.9200 so I can assume this is a Windows 8 disk.

2: Or, to make it even easier, you can open the file ../Windows/System32/license.rtf
with Word pad. Guess what, it tells you EXACTLY what system is installed.
On that same drive above, this file said "WINDOWS 8 PRO"

=========================================================

Another way is to use DISM command.

Mount the ISO (in Windows 10: right click, mount), browse to the "sources" folder and locate the
biggest file in that folder.
Assuming that the biggest file is called "install.wim" and assuming that the ISO was mounted
as drive "L", for instance, then run cmd (command prompt) as administrator
[in Windows 10: Winkey + X, Command prompt (Admin)]
and type (or paste) this command:

dism /Get-WimInfo /WimFile:L:\sources\install.wim /index:1

then hit Enter.


--
Linux Mint 21.3, Cinnamon 6.0.4, Kernel 5.15.0-119-generic
Al

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 8/22/24 08:38 PM, T wrote:

Hi All,

I have a Windows ISO called "Windows.iso".  Is there
a way to look inside the iso (easily done) and check what
build, release it is?

Many thanks,
-T

These are from some notes I've made. They're data 2021. I don't see anything dangerous, take it
with a grain of salt.
--
Linux Mint 21.3, Cinnamon 6.0.4, Kernel 5.15.0-119-generic
Al

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 8/22/24 19:43, Big Al wrote:

Another way is to use DISM command.

Mount the ISO (in Windows 10: right click, mount), browse to the
"sources" folder and locate the
biggest file in that folder.
Assuming that the biggest file is called "install.wim" and assuming that
the ISO was mounted
as drive "L", for instance, then run cmd (command prompt) as administrator [in Windows 10:  Winkey + X,  Command prompt (Admin)]
and type (or paste) this command:

dism /Get-WimInfo /WimFile:L:\sources\install.wim /index:1

then hit Enter.

My largest install.esd. And the command worked perfectly.

Thank you!

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

[snip]

4.x: NT 4.x 5.0: Windows 2000 5.1: Windows XP 5.2: Windows 2003 Server
or Windows XP-64-bit 6.0: Windows Vista 6.1: Windows 7 6.2; Windows 8
6.3: Windows 8.1 10.0: Windows 10

I remember a very early Windows 10 that had an internal version number of
6.4

[snip]

--
Mark Lloyd
http://notstupid.us/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, 8/22/2024 8:38 PM, T wrote:

Hi All,

I have a Windows ISO called "Windows.iso".  Is there
a way to look inside the iso (easily done) and check what
build, release it is?

Many thanks,
-T

When you're finished with your MediaCreationTool, you
set the name of the ISO to something memorable. This is the
11 OS version, similar to what a Linux user might fetch with a browser.
The MediaCreationTool version might have 7 OSes on it.

S:\DVD\Win11_23H2_English_x64.iso

Name: Win11_23H2_English_x64.iso
Size: 6705289216 bytes (6394 MiB)
SHA256: 71A7AE6974866603D366A911B0C00EACE476E0B49D12205D7529765CC50B4B39

*******

If we use Al's recipe, the index is the selector for a version of
OS on the disc. Typically index:6 is Professional. There is an XML
file inside the install.wim or install.esd, with the mapping.

dism /Get-WimInfo /WimFile:D:\install.wim /index:1

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792 <=== release number of the tool itself... ignore this

Details for image : D:\install.wim

Index : 1
Name : Windows 11 Home
Description : Windows 11 Home
Size : 18,417,288,351 bytes
WIM Bootable : No
Architecture : x64
Hal : <undefined>
Version : 10.0.22621
ServicePack Build : 2428
ServicePack Level : 0
Edition : Core
Installation : Client
ProductType : WinNT
ProductSuite : Terminal Server
System Root : WINDOWS
Directories : 26612
Files : 112612
Created : Sun, 10/1/2023 - 3:04:55 AM
Modified : Sun, 10/1/2023 - 3:49:22 AM
Languages :
en-US (Default)

The operation completed successfully.

*******

ntoskrnl.exe

File version 10.0.22621.2428 <=== Both W10 and W11 use 10.0.

*******

After an installation, there may be a package
that carries out "enablement". That should
change the version to 22631 (23H2) which is
the nominal release we thought we were getting.
Depending on whether a patch of some sort goes
in, the point release number could rise above 2428.

Similar weirdness happens on Win10. The release
might be stamped 19041, when it is really 19045, and
19045 could show in the "winver.exe" output.

*******

Today, Microsoft is not much better at release
control, than it was back in the days files
were identified by the number of bytes in the file.

If you were to extract all the files on the DVD
and check the build info, you might find a mish-mash
of numbers. Apropos of nothing. By grabbing the kernel
file, at least that gets patched pretty regularly.

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)