Jump to content











Photo
- - - - -

How to swap install.wim/install.esd/install.swm* during installation?


  • Please log in to reply
4 replies to this topic

#1 Zoso_The_Internet_Tard

Zoso_The_Internet_Tard

    Silver Member

  • Advanced user
  • 538 posts
  • Interests:An investigation is underway to determine whether Trump has any ties to America.

Posted 11 May 2017 - 04:28 PM

I have a handful of ISOs, containing different editions of Windows. I currently make Easy2Boot imgPTN files from each ISO. But it would be more convenient to combine them all into a single imgPTN. How can I swap out these files, depending on which edition I want to install? Can it be done with a script, so that setup installs from the correct file? Or would I better better off creating a custom mega wim/esd/swm* that contains all the editions? I could always split them into swm since the file would be huge. I would also need to be able to run the setup in either legacy or BIOS mode. I spend alot of time installing and configuring Windows for others, so this would be very convenient.

 

Thanks!



#2 steve6375

steve6375

    Platinum Member

  • Developer
  • 6597 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted 11 May 2017 - 04:47 PM

Convert one of the Windows 10 x86 ISOs to a .imgPTN file (FAT32) using Chandra's Split_WinISO utility.

Use the MPI button and not the other button.

When asked about winpeshl.ini and setupcmd.cmd - say YES.

 

This will create .imgPTN file and a modified boot.wim.

 

Now copy all other Install.wim files over and rename as required.

 

Now edit the \auto.cmd file to pick any XML file you want and any install.wim you want.

 

Setup can be told what wim file to use with /installfrom:(path) option

see https://technet.micr...6(v=ws.10).aspx

 

Now this will make either an x86 or x64 .imgPTN file. Repeat to make another .imgPTN file for the other type.

 

However...

Personally, I would just make a FAT32 WinPE .imgPTN file which can 32-bit or 64-bit boot.

http://www.rmprepusb...ual-32-64bit-pe

Then you boot in any mode - use \e2b\Switch_e2b.exe or one of the other scripts in that same folder to switch back to the E2B partition - now you can run WinNTSetup from the E2B drive and pick any ISO on the E2B drive and any XML file (if you wish).



#3 Zoso_The_Internet_Tard

Zoso_The_Internet_Tard

    Silver Member

  • Advanced user
  • 538 posts
  • Interests:An investigation is underway to determine whether Trump has any ties to America.

Posted 11 May 2017 - 07:17 PM

Thanks for the info. I personally only use x64 original MSDN ISOs that I get from torrents and file-sharing sites, then compare the hash against what is on MSDN. Windows installed from MSDN sources are generally not already activated, so they either have to provide their own key or activate another way (how they go about that, I could care less). I have rarely had to install x86 Windows for anyone, nearly everyone I know has x64-capable hardware, but if I do then I just create a standalone USB drive for that install. I assume that the x86 instructions you're giving will work for x64 too. But why, exactly, do you say to use x86? I've always assumed that you need to use an x64 ISO to install an x64 Windows, and an x86 ISO to install an x86 Windows. For installing via command-line I just use 10's WAIK tools, obtained via GetWAIKTools. This one WAIK alone works for everything from Vista to 10 as well as the Server editions.

 

For splitting WIMs into SWMs I just use WinToolkit, split into 3000MB chunks, with a custom EI.cfg and PID.txt when necessary. That particular chunk size seems to work well, when combined with one or both of the config files.

 

In the CMD file can I specify an ESD or SWMs, in addition to regular WIMs? XML file? Where are those?

 

When you mention WinNTSetup, you say you can pick any ISO. But don't you mean imgPTN? In my original I said "I would also need to be able to run the setup in either legacy or BIOS mode". But I meant legacy or UEFI mode.

 

I don't have much of a use for PEs, except maybe to restore a backup in an emergency or other repairs/maintenance, I much prefer to use the regular Windows setup in combination with ImageX and BCDBoot.

 

On a side note, do you know how I can get Windows to automatically assign drive letters of my choice, then run an unattend answer file? I have a file called relocate.xml that I use to move C:\Users from C drive to another partition. It also handles the Registry edits. But I would like for this to run automatically during install, or immediately after rebooting into the initial setup wizard. The method I use now involves manually entering Audit Mode during initial setup, then changing drive letters as appropriate, then using CMD to process the script. I found it on TenForums, works quite well as it seems to be officially supported on 10 as of a certain build (cant remember which one), it even survives upgrades, repair install/refresh/reset.

 

Thanks!



#4 steve6375

steve6375

    Platinum Member

  • Developer
  • 6597 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted 11 May 2017 - 07:29 PM

So just use Chandra's Split_WinISO on a 64-bit Win 10 ISO. I only said x86 as an example.

Then proceed as I described.

AFAIK, you can specify ESD and .SWM files for Setup.

 

But if you are familiar with WAIK tools, you can use DISKPART scripts to partition the target drive and DISM or ImageX to apply the image.

 

If you are MBR booting, just use the E2B menu system

If you want to UEFI-boot - you need to switch in a .imgPTN image for FAT32.

 

 

re. WinNTSetup

You copy all you ISOs to E2B in the normal way.

You copy WinNTSetup.exe's etc. as described in link I gave to E2B drive

You have a .imgPTN file - in your case it could be a converted 64-bit Win 10 Install ISO with the \sources\install.wim deleted.

You switch to the .imgPTN file and boot to WinPE

You press SHIFT+F10 to get to console and \e2b\Switch_E2B to restore the E2B partition (it is easier if you boot to a 'decent' WinPE that has Explorer and a Desktop!)

Now you run WinNTSetup.exe from the E2B partition.

WinNTSetup allows you to pick any ISO (it will mount it for you) and any XML file (if you are using one).

You can also pick a Diskpart script file and it will execute it for you to partition the target drive first.



#5 Zoso_The_Internet_Tard

Zoso_The_Internet_Tard

    Silver Member

  • Advanced user
  • 538 posts
  • Interests:An investigation is underway to determine whether Trump has any ties to America.

Posted 11 May 2017 - 07:50 PM

Thanks for the clarification.

 

I don't trust diskpart to partition anything except maybe a flash drive, for everything else I use GParted. For applying the image I use ImageX (I know it's deprecated and DISM superceded it, but it works fine so I'll keep using it), then BCDBoot to install boot files. Microshaft is such a fuckup of a company, half the time they get shit wrong, so I don't really trust their tools.

 

For moving my Users folder, the drive letter for the new location must be assigned in advance, or the script will fail. As of now I run Sysprep from Audit mode, but am looking for a quicker way.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users