Change name of install.wim

The only issue with this whole discussion is that the reasoning for wanting to rename install.wim in the first place was flawed. The actual issue at hand could be solved far more simply.

I'm at a loss to understand why rename or any of this other stuff is needed if you are using DISM.

Simply whether on a vhdx file or standard disk simply to install windows :

say the windows install iso is F: and the Windows pro image is index=6, and your target is Vol W
ensure there's an EFI partition - create one if not with space 100MB, and with diskpart give it a letter S

change to the sources directory -- cd f:\sources
then f:\

dism /Apply-Image Image /ImageFile:install.wim /index:6 /ApplyDir:W:\

when that finishes install the bootloader
cd W:\windows\system32

w:
bcdboot w:\windows /s S: /f UEFI

now reboot

"Seeeemples" !!!!

Cheers
jimbo

Why is it that when you put /compress as dism switch the file is bigger than if you don't . If I use /compress:max then the wim file is 4.0gig and the without 3.5gig.

I tried to install my 3.5gig windows 10 and got this error:

0x3e7
WinSetup is corrupt or nonexistant. How do I decorrupt it? I made new esd drives and have yet to test them.


The reasoning for creating a wim file using dism with an another names was to make sure that I used the right wim file to install proper version of windows 10.

Thank you for all your help, John

0x3e7
WinSetup is corrupt or nonexistant

when does that error appear?

winsetup.dll is in the sources folder of the installation media

winsetup.dll.mui is in the sources\en-us folder.

They are also in \windows\system32\oobe .

so it depends what you are doing and when that error appears as to which of the above files might be corrupt.

During install after it goes into dos level during an install . After the first install screen.

RBCC said:

Why is it that when you put /compress as dism switch the file is bigger than if you don't . If I use /compress:max then the wim file is 4.0gig and the without 3.5gig.

I tried to install my 3.5gig windows 10 and got this error:

0x3e7
WinSetup is corrupt or nonexistant. How do I decorrupt it? I made new esd drives and have yet to test them.


The reasoning for creating a wim file using dism with an another names was to make sure that I used the right wim file to install proper version of windows 10.

Thank you for all your help, John

John, I think that you are going about this all wrong. First, the /Compress switch is only used when you are capturing an image or exporting an image. As an example, if you have created a reference system and then sysprepped it, you would then boot from from alternative media and create an image from that sysprepped copy of Windows. It is then when creating the image that a /Compress:maximum is valid.

Also, you state that you are trying to do this in order to "install proper version of windows 10". I already answered how to do this earlier in the thread - add an ei.cfg file which will cause Windows setup to show you all the available editions of Windows.

Please bear in mind that the install.wim file already contains multiple editions of Windows such as Home, Pro, Workstation, etc. There is simply no reason whatsoever to have to do ANYTHING to the existing install.wim to access any of those editions.

John, in my earlier response I had asked you what it was that you were trying to accomplish and I explained how you could use the ei.cfg to achieve that purpose. Is there something more that I am not aware of? For example, are you trying to perform an unattended setup of Windows where you want to tell setup what edition of Windows you want to install? If so, please let me know.

I am EXTREMELY familiar with this topic and want to help but I need to know IN DETAIL what your goal is in order to able to give good advice.

Just as an example of how much I have done with this, I have written a program that uses DISM to extract Windows images, combine multiple Windows images into one, inject Windows updates and / or drivers into indows images including updating many editions at once, modify the metadata for Windows images, and much, much more. In order to do that I had to become extremely familar with this topic so I am confident I can answer your questions IF I have a full understanding of your goal.

So, some questions that you could answer:

How do plan to install Windows? Do you plan to boot from your installation media (for example, a flash drive), and select the edition of Windows to be installed? Or, was your intention to perform an unattended automatic installation of Windows?

I GUARANTEE that I can answer your questions if I have sufficient information

How do I plan to install windows :

From a USB installation windows setup drive.
Built from a esd drive.

Using disk part to create 2 partition. Copying from the esd USB everything but the sources folder to the x partition and copying to the y drive the sources folder and the ei.cfg file.
Winsetup.dll is in the "sources". What makes the error disconcerting. Is how does a file get corrupted?
Thanks in Advance
John

RBCC said:

How do I plan to install windows :

From a USB installation windows setup drive.
Built from a esd drive.

Using disk part to create 2 partition. Copying from the esd USB everything but the sources folder to the x partition and copying to the y drive the sources folder and the ei.cfg file.
Winsetup.dll is in the "sources". What makes the error disconcerting. Is how does a file get corrupted?
Thanks in Advance
John

John,

Ok, I think that I see where we are headed with this. Before I go any further, could you just check a few things for me so that I can provide to you the correct steps to take?

You note that you are building your image "from a esd drive". By this, I take it that you mean that you have an ISO image that uses install.esd file(s) rather than install.wim, is that correct?

Please do this: Double click your Windows ISO image to mount it. Tell me if you have an x64 and x86 folder located in the root of that ISO image. Once you are done checking that, you can eject the image if you like.

If you have what I suspect that you have, then we can get this resolved very easily for you .

John,

I have just one more question for you for now. Have you ever made your USB installation drive using the Windows Media Creation Tool? If so, will that media boot successfully on your machine? If so, I can make this process SO MUCH EASIER for you!

jimbo45 said:

I'm at a loss to understand why rename or any of this other stuff is needed if you are using DISM.

Simply whether on a vhdx file or standard disk simply to install windows :

say the windows install iso is F: and the Windows pro image is index=6, and your target is Vol W
ensure there's an EFI partition - create one if not with space 100MB, and with diskpart give it a letter S

change to the sources directory -- cd f:\sources
then f:\

dism /Apply-Image Image /ImageFile:install.wim /index:6 /ApplyDir:W:\

when that finishes install the bootloader
cd W:\windows\system32

w:
bcdboot w:\windows /s S: /f UEFI

now reboot

"Seeeemples" !!!!

Cheers
jimbo

Yesssssss... Once the desired image is applied you have just to activate the installation.

There is no need to rename anything just select the right index when restoring the image with dism and proceed to proper activation.