Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems verifying Version information using DISM with .WIM files generated from MCT #375

Open
ntman1 opened this issue Aug 26, 2024 · 1 comment

Comments

@ntman1
Copy link

ntman1 commented Aug 26, 2024

When I try to verify even the latest 23H2 Windows 11 builds using the proscribed "dism /Get-WimInfo /WimFile::\sources\install.wim" I get build version 22621.2861 every time... Today when I ran the tool, I expected to get an ISO generated with 22631.4037 (2024-08-13) for a 23H2 build (am I wrong about this? does MCT build out the ISO with 22621.2861 and then slipstream the updates afterwards?).

I notice that MediaCreationTool11_23H2.exe is in the MCT folder. Does this get updated automatically? Or should I blow away the folder and have it generate it from scratch in order to get a newer version of 23H2?

@ntman1
Copy link
Author

ntman1 commented Aug 26, 2024

ISO Disk label is this "11_23H2_VOL_x64_en-us"

but "dism /Get-WimInfo /WimFile:j:\sources\install.esd /index:3"

Deployment Image Servicing and Management tool
Version: 10.0.22621.1

Details for image : j:\sources\install.esd

Index : 3
Name : Windows 11 Enterprise
Description : Windows 11 Enterprise
Size : 18,904,043,941 bytes
WIM Bootable : No
Architecture : x64
Hal :
Version : 10.0.22621
ServicePack Build : 2861

ServicePack Level : 0
Edition : Enterprise
Installation : Client
ProductType : WinNT
ProductSuite : Terminal Server
System Root : WINDOWS
Directories : 27042
Files : 114201
Created : 12/4/2023 - 3:03:41 AM
Modified : 8/25/2024 - 10:51:49 PM
Languages :
en-US (Default)

The operation completed successfully.

That build was done today... I wiped out the MCT directory and it recreated it as expected...

22621.2861 is clearly 22H2 - not 23H2...

https://support.microsoft.com/en-us/topic/december-12-2023-kb5033375-os-builds-22621-2861-and-22631-2861-90f983aa-efb6-4caa-9cab-7e5cfa00ed36

Is this a bug?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant