Jump to content











Photo
- - - - -

VHD_WIMBOOT - Apply and Capture of WIM Files for OS in VHD

ramdisk grub4dos svbus wimlib windows 10 ssd usb wim wimboot vhd

  • Please log in to reply
109 replies to this topic

#1 wimb

wimb

    Platinum Member

  • Developer
  • 2557 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 26 March 2019 - 09:08 PM

Posted Image

File Name: VHD_WIMBOOT - Apply and Capture of WIM Files for OS in VHD
File Submitter: wimb
File Submitted: 26 Mar 2019
File Updated: 24 Apr 2019
File Category: Tools

VHD_WIMBOOT - Apply and Capture of WIM Files for OS in VHD

Download VHD_WIMBOOT.zip is Encrypted with password = bootwimb
-
Thanks to karyonix, alacran, Wonko the Sane, tinybit, yaya, chenall, cdob, JFX, steve6375, ReTokener, synchronicity, schtrom and Microsoft :)

Click here to download this file

#2 wimb

wimb

    Platinum Member

  • Developer
  • 2557 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 26 March 2019 - 09:10 PM

VHD_WIMBOOT - Apply and Capture of WIM Files for OS in VHD

 

VHD_WIMBOOT-2019-03-26_150940.png == W10x64-RAM-HelloWorld-2019-03-01_155130.png == VHD_WIMBOOT-2019-03-28_081215.png

 

Manual Attached File  VHD_WIMBOOT.pdf   500.28KB   57 downloads

 

:cheers:

 

Download:  VHD_WIMBOOT and WinNTSetup

 

Step 1 is use WinNTSetup to do Fresh Install of Win10x64 in VHD located on your Internal System Drive according to page 2 of the pdf Manual

Step 2 is use VHD_WIMBOOT to wimboot CAPTURE New WIM file from that VHD so that the capture is WimBoot compatible and contains only 1 Index

Step 3 is use VHD_WIMBOOT to APPLY that Captured New WIM File to New VHD

Step 4 is Boot with that New VHD from Boot Manager Menu as FILEDISK Or Boot that New VHD from Grub4dos Menu as RAMDISK

 

The Button WIM Info will give useful info about your WIM file

 

The Button Upd WimBOOT can be used after copy of VHD + WIM set to other drive to make the set bootable again

 

The Button Make Boot will make the boot entries on Target Boot Drive

- VHD boot entry in Boot Manager Menu for booting as FILEDISK - in BIOS mode and in UEFI mode

- VHD boot entry in Grub4dos Menu for booting VHD from RAMDISK - in BIOS mode only

- For booting from USB with Portable SSD then After BIOS beep press F8 Or F11 to arrive at BIOS Boot Menu and select your boot device

 

An Expandable VHD will load much faster into RAMDISK, since only the space occupied by files of 600 MB needs to be loaded.

It Expands then to the maximum VHD Size of 3.9 GB and giving the RAMDISK of that size a lot of FREE Space.

When booting such Expandable VHD as FILEDISK then the FREE Space is useful and needed for Install of drivers for New Hardware.

When booting the VHD + WIM set from Portable SSD connected via USB to various hardware, then we collect a lot of driver info in the System Registry.

After the eXPerience of various machines, then it is useful and needed to CAPTURE new WIM File that will contain the additional driver and program files.

APPLY of that New WIM File to the selected VHD File will result in the original available FREE Space in the VHD.

 

It is good to use initially a VHD Size of 25 GB booting as FILEDISK and use the FREE Space to collect drivers and install new extra programs and Windows Update.

Then after CAPTURE we can APPLY to small VHD of Size about halve of the available RAM

e.g. 3.9 GB for a 8 GB RAM machine and 1.5 GB for a 4 GB RAM machine.

Such small Expandable VHD is then Universal and can be used to boot on any machine fast into RAMDISK.

 

LZX Compression can be used in CAPTURE to make WIM files of smaller size.

Roughly with LZX the time to CAPTURE is doubled and the WIM Size is 30% smaller so that it saves for a 9 GB WIM file about 3 GB.

 

More Info is in UEFI_MULTI  topic and is given by alacran in WIMBOOT Topic and Compression and RAMBOOT Topic



#3 alacran

alacran

    Silver Member

  • .script developer
  • 925 posts
  •  
    Mexico

Posted 27 March 2019 - 12:58 AM

This time I builded W81x64_ES_1.vhd expandable (1.5 GB Max.) on running OS 10x64 Pro 1709, using your v1.5:

 

I'm sorry to tell you on external BCD Optin is not selected, also same on internal BCD, additionally HD and Partition to boot from are not selected on internal BCD, attached pictures.

 

alacran

Attached Thumbnails

  • Internal BCD v1.5.png
  • Internal BCD v1.5 Pro.png


#4 wimb

wimb

    Platinum Member

  • Developer
  • 2557 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 27 March 2019 - 06:14 AM

I'm sorry to tell you on external BCD Optin is not selected, also same on internal BCD, additionally HD and Partition to boot from are not selected on internal BCD, attached pictures.

 

 

The Disk setting on Internal BCD corresponds to device boot and is according to solution given by karyonix which is booting OK.

 

Do you need the Optin Setting ? I can add that easily in the program.

 

And what occurs when you try to boot ? I expect it is all working OK. 

 

Updated VHD_WIMBOOT Version 1.6 is online which gives the nx OptIn setting



#5 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 326 posts
  •  
    Italy

Posted 27 March 2019 - 06:53 AM

my dear wimb, 

I just got hold of the latest vhd_wimboot. I have been running the wim+vhd combo for quite a few weeks now, always baking wim's and vhd's with gimagex and winntsetup respectively. I would like to know the main practical differences between vhd_wimboot and winntsetup, as well as whether the former covers the function of gimagex as well in capturing the state of a windows install (which I call wim-baking). 

thanx in advance

nino



#6 wimb

wimb

    Platinum Member

  • Developer
  • 2557 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 27 March 2019 - 07:20 AM

I just got hold of the latest vhd_wimboot. I have been running the wim+vhd combo for quite a few weeks now, always baking wim's and vhd's with gimagex and winntsetup respectively. I would like to know the main practical differences between vhd_wimboot and winntsetup, as well as whether the former covers the function of gimagex as well in capturing the state of a windows install (which I call wim-baking). 

thanx in advance

 

 

GImageX is working with Microsoft WIMGAPI whereas VHD_WIMBOOT is using wimlib for Capture taking modified WimBootCompress.ini into account.

WinNTSetup does not have Capture functionality and in Apply then the Grub4dos entries are not made and the Boot Manager menu entry needs additional corrections.

 

VHD_WIMBOOT is an all in one solution and has also the Update WimBoot button useful to Update VHD+WIM combination when relocating to other drive.



#7 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 326 posts
  •  
    Italy

Posted 27 March 2019 - 08:12 AM

Tx wimb,
So, let us say I have normally booted my usual vhd+wim combo and am now surfing the web, happen to find some software I wanna try out. I'll download and install it. At that point the install data reside on the vhd, not on the wim, right?
If so, I now would like either to bake a new wim+vhd combo incorporating the recent change or append the recent change to the already existing wim. Which is the better thing to do? And how shall I practically proceed via vhd_wimboot?

#8 wimb

wimb

    Platinum Member

  • Developer
  • 2557 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 27 March 2019 - 08:21 AM

After Install of Software in VHD you can do Capture with VHD_WIMBOOT to save that software also in the WIM Archive

 

If desired You can Apply the new WIM File to the same VHD where the program will offer to Format the VHD first.

 

In this way you re-gain the free space in the VHD and make a better WIM File containing your software.


  • antonino61 likes this

#9 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 326 posts
  •  
    Italy

Posted 27 March 2019 - 08:51 AM

Thanks, Wimb.
Are there any parameters in the procedures that I should apply to the end that u have just mentioned?



#10 wimb

wimb

    Platinum Member

  • Developer
  • 2557 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 27 March 2019 - 01:37 PM

Thanks, Wimb.
Are there any parameters in the procedures that I should apply to the end that u have just mentioned?

 

No



#11 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 326 posts
  •  
    Italy

Posted 27 March 2019 - 01:43 PM

ok one more question, when u say "save that software also in the wim archive", do u mean "in  a fresh wim archive" or in the same as the one I have already. I am asking u this question because I have to know whether to bake a new wim file or use the same for the update, which would entail my prior saving the existing wim before all the procedures lest something should go wrong; if it is a new wim file I have to bake, I will not go to the trouble of saving the one I already have.

nino



#12 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 326 posts
  •  
    Italy

Posted 27 March 2019 - 02:13 PM

sorry wimb, no need to answer, I have just booted off a fresh vhd I made thru vhd_wimboot, which, in my view, makes u a genius of wim+vhd automation. everything went spick and span, no flaws, everything configured automatically. my congrats. One other question: does the system dir have to be ?:\wimboot perforce? can't it be, let us say, ?:\ (the root of the drive)? If it can't, no prob? U have just spared me the trouble of testsigning, configuring under conventional bootmgr, configuring under g4d, and what not. My congrats again, man!



#13 wimb

wimb

    Platinum Member

  • Developer
  • 2557 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 27 March 2019 - 02:54 PM

sorry wimb, no need to answer, I have just booted off a fresh vhd I made thru vhd_wimboot, which, in my view, makes u a genius of wim+vhd automation. everything went spick and span, no flaws, everything configured automatically. my congrats. One other question: does the system dir have to be ?:\wimboot perforce? can't it be, let us say, ?:\ (the root of the drive)? If it can't, no prob? U have just spared me the trouble of testsigning, configuring under conventional bootmgr, configuring under g4d, and what not. My congrats again, man!

 

Thanks for testing and happy that you like the program.

 

The folder for WIM files does not need to be Wimboot. Any Root root folder max 8 chars is allowed e.g. sources would be ok as well.


  • antonino61 likes this

#14 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 326 posts
  •  
    Italy

Posted 27 March 2019 - 03:02 PM

btw, at the end of it all, I have 1 vhd that vhd_wimboot overwrote + 2 wims, one is the one I had before, the other in ?:\wimboot, named W10x64_US_1.wim. I thought the latter was the one involved in the new combo, so I tried to delete the one I already had (install.wim): --> the system prevented me from deleting it, which made me understand that this wim was the file involved in the new combo instead. at that point I moved W10x64_US_1.wim elsewhere just to see whether the system allowed me to do it, which it did. now its size is smaller than install.wim, which stayed about or exactly the same size, I honestly did not look before, so I do not know. what shall I do with W10x64_US_1.wim, as the system does not seem to care about it?



#15 wimb

wimb

    Platinum Member

  • Developer
  • 2557 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 27 March 2019 - 05:23 PM

The file W10x64_US_1.wim must be the result of a Capture, since in that case such filenames are auto created in folder Wimboot (hardcoded) on selected System Drive.

After Capture you can select that WIM file and use it for Apply to your VHD file, which can be selected existing VHD file or otherwise New VHD file is created.

 

For Apply the WIM file must be in root folder max 8 chars of System drive.

 

For Capture the WIM file is auto named and created in folder Wimboot on System Drive

 

I think it is not logical to have hardcode folder name Wimboot for Capture, whereas for Apply it is any root folder of max 8 chars on System Drive.

 

So I will change this in the program so that also for Capture the folder is determined by the System Drive folder selection.


  • antonino61 likes this

#16 wimb

wimb

    Platinum Member

  • Developer
  • 2557 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 27 March 2019 - 08:28 PM

Update VHD_WIMBOOT Version 1.7

 

- Capture of WIM files occurs in selected folder of System Drive - select any root folder with name max 8 chars

- After Capture then direct Apply is possible by selecting the WIM file and using the earlier selected VHD file

 

Download:  VHD_WIMBOOT


  • antonino61 likes this

#17 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 326 posts
  •  
    Italy

Posted 27 March 2019 - 09:23 PM

thanks again, where do I get it?

btw, there is still that issue whereby, no matter how often I have updated wim and vhd, and filled the wimboot dir with successive wims, the original install.wim in the root dir (d:\ in my case) still remains the unmovable and undeletable one (permanently in use), whereas I might as well sweep out the whole winboot dir with the whole series of wims in it. I have had the feeling that apart from automating the boot process (which is an excellent thing), I ain't doing nothing to the wim, and I am probably doing something to the vhds, that again seem to be hopelessly attached to the original wim on the root dir (install.wim).

nino



#18 wimb

wimb

    Platinum Member

  • Developer
  • 2557 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 27 March 2019 - 09:28 PM

thanks again, where do I get it?

 

Same place as before in the Downloads Tools section as given in first post

 

Download:  VHD_WIMBOOT



#19 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 326 posts
  •  
    Italy

Posted 27 March 2019 - 09:48 PM

nothing doing, wimb, it still imposes choosing or making a dir on the root, and I think I have always had only this version, which I got hold of early this afternoon.



#20 alacran

alacran

    Silver Member

  • .script developer
  • 925 posts
  •  
    Mexico

Posted 27 March 2019 - 10:33 PM

@ wimb

 

The Disk setting on Internal BCD corresponds to device boot and is according to solution given by karyonix which is booting OK.

 

Do you need the Optin Setting ? I can add that easily in the program.

 

And what occurs when you try to boot ? I expect it is all working OK.

 

Updated VHD_WIMBOOT Version 1.6 is online which gives the nx OptIn setting

 

And what occurs when you try to boot ? I expect it is all working OK.

 

Didn't tested at the time, I changed BCD as the usual we were using since the begining, I didn't expect it to Ramboot the way it was, but now just ran a new test, this time with your new v1.7 and saw Optin is selected now on both BCDs, but internal BCD location of HD and Partition remain same way, this time I decided to test it this way as you said, then rebooted the PC and it Rambooted flawlessly.

 

Congratulations, all is working very fine, I also tested capture on v1.6 and it was working very fine.

 

alacran


  • wimb likes this

#21 wimb

wimb

    Platinum Member

  • Developer
  • 2557 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 28 March 2019 - 05:14 AM

nothing doing, wimb, it still imposes choosing or making a dir on the root, and I think I have always had only this version, which I got hold of early this afternoon.

 

Sure if you only select System Drive then it will make folder Wimboot on System Drive and use that folder.

 

But you can click on any root folder max 8 chars on System Drive and then that folder is used.

 

You need version 1.7 which was presented yesterday evening in your time ....

 

Download:  VHD_WIMBOOT

 

VHD_WIMBOOT-2019-03-28_081215.png



#22 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 326 posts
  •  
    Italy

Posted 28 March 2019 - 10:06 AM

same thing, wimb: it seems to capture, apply and bcd configure fine, but the useful wim stays my original one on root, which it will not consider compatible and suggests new capture; these new captures can be applied to existing or new vhds, or wimboot can be updated, which is the only function that seems to work. the resulting vhds will not boot as a result of registry incomplete transfer (bsod stuck at ...\system32\system), the only ones that boot are the original vhds linked to the original install1.wim file out of the wimboot dir (on the root dir).



#23 wimb

wimb

    Platinum Member

  • Developer
  • 2557 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 28 March 2019 - 10:22 AM

same thing, wimb: it seems to capture, apply and bcd configure fine, but the useful wim stays my original one on root, which it will not consider compatible and suggests new capture; these new captures can be applied to existing or new vhds, or wimboot can be updated, which is the only function that seems to work. the resulting vhds will not boot as a result of registry incomplete transfer (bsod stuck at ...\system32\system), the only ones that boot are the original vhds linked to the original install1.wim file out of the wimboot dir (on the root dir).

 

Step 1 is use WinNTSetup to do fresh Install of Win10x64 in VHD located on your Internal System Drive according to page 1 of the pdf manual

Step 2 is use VHD_WIMBOOT to Capture New WIM file from that VHD so that the capture is WimBoot compatible and contains only 1 Index

Step 3 is use VHD_WIMBOOT to Apply that Captured New WIM File to New VHD

Step 4 is Boot with that New VHD from Boot Manager Menu as FILEDISK Or Boot that New VHD from Grub4dos Menu as RAMDISK

 

If your install1.wim is not WimBoot compatible, then it means probably that it was never wimboot captured from a VHD and may be still contains other Indexes than  1 only  :unsure:
 
The Button WIM Info will give useful info about your install1.wim file
That Info you might share with us to give more info on the problem ....
 
Attached File  wiminfo.txt   1.32KB   51 downloads


#24 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 326 posts
  •  
    Italy

Posted 28 March 2019 - 11:08 AM

Perfect!!! Everything went fine, by following ur steps in detail. i got rid of my old install.vhd and the thingy booted perfect both conventionally (bootmgr as filedisk and g4d as ramdisk, which I am now on). Now, one more thing, relying on ur patience:

I left everything at default values, one of which was 3.9 as the size of the expand vhd, with the compressiong box unticked. the result was about 800mb used space and 4gb total space. the loading in ram was fast and smooth, mostly limited to the used space, as the counter visibly skipped the freespace, but the ram it occupies according to resmon.exe is a 4gb greyspace. Shall I stay like this, or try and shrink the vhd by 50%, which was the usual size of my old ones? viz, if the 4gb of occupied ramspace are there to no avail, I would sooner shrink the file, otherwise I would leave it as it is. 

nino



#25 wimb

wimb

    Platinum Member

  • Developer
  • 2557 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 28 March 2019 - 11:27 AM

Good  :)

 

You have a lot of RAM in your machine, so the 3.9 GB is no problem at all.

The FREE Space can be quite useful when booting on other machines to allow install of drivers for that hardware.

 

It is all a matter of personal preference and dependant on what hardware you have and where and how you want to use it.

If you would have a machine with only 4 GB RAM then it is needed to reduce the VHD Size to 1.5 GB suitable for RAMDISK booting.


  • antonino61 likes this





Also tagged with one or more of these keywords: ramdisk, grub4dos, svbus, wimlib, windows 10, ssd, usb, wim, wimboot, vhd

1 user(s) are reading this topic

1 members, 0 guests, 0 anonymous users


    happyasr