Path: ...!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Paul <nospam@needed.invalid>
Newsgroups: microsoft.public.windowsxp.general
Subject: Re: Win7 support:
Date: Sat, 31 Aug 2019 00:38:13 -0400
Organization: A noiseless patient Spider
Lines: 123
Message-ID: <qkctji$hq$1@dont-email.me>
References: <qihiik$u34$1@dont-email.me> <8c5bb65b-39f5-4766-8ba6-2ff85f53db1a@googlegroups.com> <qjjtc3$35q$1@dont-email.me> <cf78de0f-6ef1-4fe9-841d-90ad86317a47@googlegroups.com> <qk419p$hb9$1@dont-email.me> <f26409d2-3059-4d64-8007-fed11cba952f@googlegroups.com> <qk47ed$kc6$1@dont-email.me> <f5303f07-0a77-46e3-b169-7509d79957c3@googlegroups.com> <qk4r6g$ea0$1@dont-email.me> <587b36a6-0fdc-46d3-9cb8-cfe67ed582ff@googlegroups.com> <qk6lpg$bok$1@dont-email.me> <3c42965f-46ff-48c1-a6bc-c314d4cafdef@googlegroups.com> <qk7a9o$i0a$1@dont-email.me> <01f19585-68ef-4566-80ca-fa5caa2bd888@googlegroups.com> <qk8n5v$knp$1@dont-email.me> <d8b8de0d-ac1c-4a80-bcb2-d6268474b9d6@googlegroups.com> <qk99dm$c47$1@dont-email.me> <8f681fdb-e009-431b-a01d-333060052290@googlegroups.com> <12a60b92-ad16-413f-a592-1c0d9d5071e4@googlegroups.com> <qk9tts$m1u$1@dont-email.me> <99940d70-9e03-4de6-8479-c39ee14c243e@googlegroups.com> <qka6hq$pfu$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sat, 31 Aug 2019 04:38:11 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="187ef325eee1748afe9ba8196212de2c";
	logging-data="570"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX185FGpQH+u34WYJGiU4w2fwFix7AZ1YwoQ="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:q5R/xYmS625vhIo6KU6Iljqjw0A=
In-Reply-To: <qka6hq$pfu$1@dont-email.me>
Bytes: 5628

Paul wrote:
> Robert in CA wrote:
>>> I considered the possibility the disc could have
>>>
>>>     sources\install.win
>>>     sources\install.esd
>>>
>>> and there are two commands in the posting, one for a
>>> .wim disc and one for a .esd disc. I think your disc
>>> could be .esd , at least the 1903 one, as the .esd
>>> happens to fit on single-layer media while the .wim
>>> version does not.
>>>
>>>     dism /Get-WimInfo /WimFile:D:\sources\install.wim /index:1
>>>     dism /Get-WimInfo /WimFile:D:\sources\install.esd /index:1
>>>
>>> The D:\ assumes that is your optical drive. If the drive
>>> letter is something different, substitute the correct drive
>>> letter into the command.
>>>
>>> The discs have multiple index values. Windows Home might
>>> be index 1. Windows Pro might be index 2. If you can get
>>> the command to work with index 1, you can then try index 2
>>> for fun. I think Windows Pro is "typically" around
>>> index 4 or so. Just as a guess. All we really wanted
>>> was the "version number" of the disc, to prove it was
>>> 1903, which would save you having to do additional downloads.
>>>
>>>    Paul
>>
>>
>> I tried it again with the same results:
>>
>> https://postimg.cc/5jXrZZR1
>>
>> https://postimg.cc/yJffGPhk
>>
>> https://postimg.cc/1fxvb4Fc
>>
>> https://postimg.cc/SnkDN5Dn
>>
>> https://postimg.cc/p91ZCdxj
>>
>> https://postimg.cc/RWgQC0WY
>>
>> https://postimg.cc/p5QzwVNq
>>
>> Robert
> 
> OK, so this one gave you a *different* error.
> 
> https://postimg.cc/SnkDN5Dn
> 
>    Error 11  "An attempt was made to load a program with an incorrect 
> format"
> 
> I reproduced that here. I get the same result. Grrr.
> 
> And really, this takes all the fun out of it. Torturing
> you with 7ZIP is never going to work - I'd hoped this method
> would be easier. Thanks, Microsoft.
> 
> The reason I was expecting this to work, is I
> got the impression the ESD in this case, wasn't
> encrypted.
> 
> *******
> 
> OK, I give up :-)
> 
> Let's do it by size.
> 
> While your DVD is in the tray, navigate to the
> sources folder. This is what I used to test.
> 
> Win10-64bit-mediacreation-1903-7OSes.iso
> 
> It's a cheesy way to ID it, but it avoids a lot of unnecessary
> crappy methods to get an answer. I don't think anyone
> wants to download a WADK kit to do this... Compare
> the size listed here, to the one I got. Should be pretty
> close (within a few bytes). No two ESD files are exactly
> the same, and I cannot begin to estimate the possible
> size differences for you. The ones so created, likely
> have different date stamps inside. Which could change
> the length of the file (as well as the checksum).
> 
> 3,346,473,984 bytes  for the x64 Win10 Mediacreation install.ESD file.
> 
> https://i.postimg.cc/d11s8jsY/1903-Media-Creation-x64.gif
> 
>    Paul

I found another way to do it.

https://wimlib.net/

    # wimlib v1.13.1 Windows binaries (32-bit)

    https://wimlib.net/downloads/wimlib-1.13.1-windows-i686-bin.zip

    # wimlib v1.13.1 Windows binaries (64-bit)  <=== useful for your machines

    https://wimlib.net/downloads/wimlib-1.13.1-windows-x86_64-bin.zip

Inside the file, you will find

    wimlib-15.dll
    wimlib-imagex.exe

You can copy those out of the ZIP download, to your downloads folder.

    cd %userprofile%\Downloads

    wimlib-imagex info D:\sources\install.esd

It seems to handle ESD or WIM files better than Win7 DISM.

The 32 bit version even ran on WinXP :-)

It says the release on my test ISO is 18362 (which is 1903 Win10).

    Paul