Both scripts get the WIM info which the thread is about So I shared the scripts I use to get that info and so far they have worked for me
I don't want to sound pedantic, but That's not even on the title of the thread. Wim info and correct build info (which the tread is about) are usually in sync, but may happen they aren't. They came from different places, wims may not contain an OS at all. Think to an ISO and it's label, you can label the W11 media as XP Pro, if you use a command that parses the ISO metadata you get XP Pro, which is a CORRECT info, but is very likely not what you want to know.
You are The scenario here is using UUP dump to create an ISO then simply checking the version and build afterwards
The scenario is that UUP dump can fail or have bugs and/or regressions, like everything else. Perhaps UUPdump has nothing to do with what the OP asked. What about reading the first couple of messages?
What you're not grasping is the reported version (from WIM) is often misleading, even for official MS ISO's. Don't believe it? Get W10 22H2 ISO from Software Downloads, it self-identifies as 19041 to both DISM & wim-imagelib since they both trust the WIM's data. It's known that 19042 thru 19045 ISO's all report as "19041". There's another problem where W11 pretends it's "10" instead of 11 for the major release. Depending solely on the high-level data, instead of inspecting the image's content will lead you to errors. 20H2 v2 ISO: Code: Index Name Arch Edition Version DISM ----- ---- ---- ------- ------- ---- 1 Windows 10 Home x64 Core 19042.631 19041.631 2 Windows 10 Home N x64 CoreN 19042.631 19041.631 3 Windows 10 Home Single Language x64 CoreSingleLanguage 19042.631 19041.631 4 Windows 10 Education x64 Education 19042.631 19041.631 5 Windows 10 Education N x64 EducationN 19042.631 19041.631 6 Windows 10 Pro x64 Professional 19042.631 19041.631 7 Windows 10 Pro N x64 ProfessionalN 19042.631 19041.631 8 Windows 10 Pro Education x64 ProfessionalEducation 19042.631 19041.631 9 Windows 10 Pro Education N x64 ProfessionalEducationN 19042.631 19041.631 10 Windows 10 Pro for Workstations x64 ProfessionalWorkstation 19042.631 19041.631 11 Windows 10 Pro N for Workstations x64 ProfessionalWorkstationN 19042.631 19041.631
I think that Dism /capture, just writes the info in the xml, that describes the WIM's content, based on the properties of ntoskrnel.exe and not the registry. In 10.0.19045.3031 the properties are still 19041.3031 And win 11 is 10.0.22000.xxxx not 11.0.22000.xxxx. So strictly speaking this is somewhat the correct info, something that used to be identical to what you retrieve in registry, then they just messed up the concept introducing those "virtual" builds in the registry w/o touching dism As for W11 v.s. W10, this is a much older problem. This is W10 build 9926, although the kernel version was already switched from 6.4 to 10.0, dism was still a bit confused, I'm sure that older versions with 6.4 kernel gave even funnier results.
thx much bro for the enlightenment, this is what I was looking for and found it even in a different tutorial. after a few weeks of trying it finally worked too, after backing up, tried to find the difference with WinMerge and saw the difference. but I tried drag drop ntuser.dat, system and default are even easier, what can't be just software because maybe there are differences in the installed software, are my steps with drag n drop correct and no problems bro?
Sorry but I don't understand your question. I have no idea about what you mean with "my step with drag and drop"
drag and drop I mean, I took ntuser.dat, default and system from someone else's install.wim and then I put it in my install.wim using 7-zip, is that ok?
Not exactly the cleanest thing to do. For one the "donor" wim may have components addedd/removed, so you may end with mismatched component list in software compared to what's actually installed. At the end that wim will work, but shouldn't be an excuse to not learn how to customize properly. Perhaps I dont think you can usw 7zip to replace a file in the wim, like in a .zip. You need to use dism mount the wim, commit the changes, rebuild the wim to avoid the wasted space and so on...