Jump to content











Photo
* - - - - 1 votes

WTG + WimBoot + VHDX powerful combination.

wimboot win to go vhdx winntsetup v3.6.1 usb to go usb booting

  • Please log in to reply
42 replies to this topic

#1 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 194 posts
  •  
    India

Posted 06 July 2014 - 11:14 AM

Hello Everyone.....

 

http://windowsforum.kr/review/5830280

 

In above tutorial I could not understand one thing- 

 

AFAIK, In WIMBoot method PC/USB  boot directly from 'install.wim', But in above tutorial USB contains both 'install.wim' and 'Windows81.vhdx'

 

Will 'Windows81.vhdx' be deleted after creating bcdboot in the USB Drive ?

 

OR I have to keep both 'install.wim' and 'Windows81.vhdx' in the USB Drive in order to boot from USB ?

 

How much min space USB Drive will occupy after creating whole setup ?

 

Can anybody please explain above tutorial in English ?

 

 

Thanks in Advance


Edited by devdevadev, 06 July 2014 - 11:19 AM.


#2 cdob

cdob

    Silver Member

  • Expert
  • 976 posts

Posted 06 July 2014 - 02:37 PM

AFAIK, In WIMBoot method PC/USB  boot directly from 'install.wim'

No, wimboot dosn't read directly from a wim file.
A helper partition is required, there are pointer files from this helper partition to the wim file.
This helper partition can be a vhd(x) partition too.
http://technet.micro...y/dn594399.aspx
 

Can anybody please explain above tutorial in English

Boot a Windows 8 with wimboot updates.
Copy install.wim to the USB disk.
Run WinNTSetup:
select the install.wim file as source, select the wimboot option
select the USB drive as boot drive
create a vhd(x) file at USB disk, mount the vhd as partition and format this if required
select this as target partition
and apply the image

#3 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 10,845 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 06 July 2014 - 02:43 PM

This (not very far from here ;)) seems to me like good English:

http://reboot.pro/to...-windows-to-go/

 

:whistling:

 

This may also help you:

http://bit.ly/1xAWITF

 

:duff:

Wonko


  • devdevadev likes this

#4 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 194 posts
  •  
    India

Posted 06 July 2014 - 03:13 PM

No, wimboot dosn't read directly from a wim file.

A helper partition is required, there are pointer files from this helper partition to the wim file.
This helper partition can be a vhd(x) partition too.
http://technet.micro...y/dn594399.aspx
 
Boot a Windows 8 with wimboot updates.
Copy install.wim to the USB disk.
Run WinNTSetup:
select the install.wim file as source, select the wimboot option
select the USB drive as boot drive
create a vhd(x) file at USB disk, mount the vhd as partition and format this if required
select this as target partition
and apply the image

 

tHANKS 4 Quick Reply...........

 

Currently I have just finish exactly the same procedure you currently posted. It means both 'install.wim' and 'Windows8.1.vhdx' are necessary in order to boot 'WTG'. I think I will have to use 'Dynamically Expanding VHD' file so that size of the whole setup will be as minimum as possible. Am I right ? 

 

AFAIU, Total size of the WTG will vary according to size of 'Windows81.vhdx' ?

 

i.e.    Size of 'install.wim' (Fixed) + Size of 'Windows8.1.vhd' (Vary depending upon installed softwares) ?

 

How much Disk Space (approx.) advantage 'WTG + WimBoot + VHDX' will provide over Normal 'WTG' and 'WTG + VHDX' ?

 

Which of the following three method will save maximum Disk Space ?

 

1-  WTG + WimBoot + VHDX

2-  WTG + VHDX

3-  Normal WTG

 

Which of the above method is best in term of 'Disk Space' , 'Speed' and 'Performance' ?

 

Thanks in Advance


Edited by devdevadev, 06 July 2014 - 04:12 PM.


#5 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 194 posts
  •  
    India

Posted 06 July 2014 - 05:54 PM

According to http://technet.microsoft.com/en-us/library/dn594399.aspx

 

Limitations-

  • WIMBoot is available only for UEFI-based PCs running in UEFI mode (legacy BIOS-compatibility mode isn't supported).
     
  • WIMBoot is supported for solid-state drives and eMMC (Windows HCK compliant) drives. WIMBoot isn't supported on traditional drives that contain rotational components, or on hybrid drives that contain both solid-state and rotational drive components. WIMBoot works by taking advantage of the capability of solid-state drives to access different areas of the hard drive quickly.

    It's OK to have a secondary drive attached to the PC, and the secondary drive can contain rotational components. But the WIMBoot image and pointer files must all be located on the primary solid-state or eMMC drive.

 

And I have used following procedure (WTG + WimBoot + VHDX) suggested by 'cdob'

 

Boot a Windows 8 with wimboot updates.
Copy install.wim to the USB disk.
Run WinNTSetup:
select the install.wim file as source, select the wimboot option
select the USB drive as boot drive
create a vhd(x) file at USB disk, mount the vhd as partition and format this if required
select this as target partition
and apply the image

 

and currently my whole setup is exactly looking like this-

 

7d7d7e8327e2024625ff49f43f72edb7.png

 

 

I have created 'WTG + WimBoot + VHDX' combination in my Transcend JetFlash 780 3.0 USB Drive and it is booting perfect in my 'Dell Inspiron 1545' which is only BIOS/MBR type while WIMBoot is only for UEFI-based PCs and is support only solid-state drives and eMMC (Windows HCK compliant) drives.

 

I could not understand why 'WTG + WimBoot + VHDX' combination work in my case ?

 

Any reason PLEASE ?

 

 

Regards


Edited by devdevadev, 06 July 2014 - 06:02 PM.


#6 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 10,845 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 06 July 2014 - 06:23 PM

I could not understand why 'WTG + WimBoot + VHDX' combination work in my case ?

 

Any reason PLEASE ?

 

 

Regards

Would you be surprised about the possibility that the good MS guys simply LIED in that article you posted a link to?

It would not be the first time this happens, it won't probably be the last one.

 

:duff:

Wonko


  • devdevadev likes this

#7 cdob

cdob

    Silver Member

  • Expert
  • 976 posts

Posted 06 July 2014 - 06:57 PM

(legacy BIOS-compatibility mode isn't supported).

Translate not supported:
may work nontheless. Use at own risk. Don't ask, if it dosn't work.

Yes, wimboot works at BIOS.
 

WIMBoot is supported for solid-state drives and eMMC (Windows HCK compliant) drives. WIMBoot isn't supported on traditional drives that contain rotational components, or on hybrid drives that contain both solid-state and rotational drive components. WIMBoot works by taking advantage of the capability of solid-state drives to access different areas of the hard drive quickly.

It's works at a rotational hard disk, is not recommended because of access time.
Hence a JetFlash 780 is not supported too, slow access time.
Again use at own risk.
  • devdevadev likes this

#8 misty

misty

    Frequent Member

  • Developer
  • 410 posts
  •  
    United Kingdom

Posted 06 July 2014 - 07:20 PM

There are at least two existing reboot threads with lots of useful information about WimBoot -Regards,

Misty
  • devdevadev likes this

#9 cdob

cdob

    Silver Member

  • Expert
  • 976 posts

Posted 06 July 2014 - 09:25 PM

size of the whole setup will be as minimum as possible.

You may trim install.wim too.
http://technet.micro...y/dn621983.aspx
copy <DVD:>\sources\install.wim
Dism /Mount-Image /ImageFile:"install.wim" /Index:1 /MountDir:C:\ISO\mount
rd /s C:\ISO\mount\Windows\System32\Recovery
Dism /Optimize-Image /Image:C:\ISO\mount /WIMBoot
Dism /Unmount-Image /MountDir:C:\ISO\mount /Commit
Dism /Export-Image /SourceImageFile:install.wim /SourceIndex:1 /DestinationImageFile:wimboot.wim
del install.wim
A 3.3 GB amd64 install.wim drops to a 2.9 GB wimboot.wim.

 

Which of the above method is best ?

Again there is not ONE answer to this.
Try all three versions. Use the version you like most.
Other user may choose another one.

#10 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 194 posts
  •  
    India

Posted 07 July 2014 - 12:31 AM

A 3.3 GB amd64 install.wim drops to a 2.9 GB wimboot.wim.

 

Can I use 'WIMBoot.wim' as a Source in the 'WinNTSetup v.3.6.1' instead of 'install.wim' ?

 

 Will I have to use 'Dynamically Expanding VHD' in order to keep the size of the 'Windows81.vhdx' as minimum as possible so that there will be NO free space wastage within the 'Windows81.vhdx' ?

 

About methods you mentionned, here below a recap for future readers :

#1 Standard MS DISM way here (requires win8.1u1 winpe).

#2 CloneDisk wimgapi way here (requires win8.1u1 winpe).

#3 WimLib way here (does NOT require win8.1u1 winpe).

 

Cheers,

Erwan

 

@ erwan.I

 

Which of the following method is more better ( in term of occupied Disk Space ) in order to create smallest

'WTG + WimBoot + VHDX' Setup ?

 

1- WimLib way here (does NOT require win8.1u1 winpe).

2- WinNTSetup v3.6.1 way here

 

Note- WimLib way end up with a C drive occupied by only 250 MB (before 1st boot where pagefile.sys and hyberfil.sys will be created).

 

Thanks and Regards


Edited by devdevadev, 07 July 2014 - 12:57 AM.


#11 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 10,845 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 07 July 2014 - 06:53 AM

Doesn't WinNTSetup also use WimLib?

http://www.msfn.org/...v361/?p=1080527

:whistling:

 

 

:duff:

Wonko


  • devdevadev likes this

#12 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1,083 posts
  • Location:Nantes - France
  •  
    France

Posted 07 July 2014 - 07:14 AM

Can I use 'WIMBoot.wim' as a Source in the 'WinNTSetup v.3.6.1' instead of 'install.wim' ?

 

 Will I have to use 'Dynamically Expanding VHD' in order to keep the size of the 'Windows81.vhdx' as minimum as possible so that there will be NO free space wastage within the 'Windows81.vhdx' ?

 

 

 

@ erwan.I

 

Which of the following method is more better ( in term of occupied Disk Space ) in order to create smallest

'WTG + WimBoot + VHDX' Setup ?

 

1- WimLib way here (does NOT require win8.1u1 winpe).

2- WinNTSetup v3.6.1 way here

 

Note- WimLib way end up with a C drive occupied by only 250 MB (before 1st boot where pagefile.sys and hyberfil.sys will be created).

 

Thanks and Regards

 

Hi Devdevadev,

 

In terms of occupied disk space, I would say that wimlib vs wimgapi (+wimboot) will make no difference.

Indeed, a decompressed file will always take the same size.

 

It is only when creating the WIM file that this could eventually makes a diference.

Indeed, a compressed file's size may depend on the compression engine.

 

Regards,

Erwan.



#13 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 194 posts
  •  
    India

Posted 09 July 2014 - 02:11 PM

Hello Everyone.......
 
Is it possible to directly convert 'install.esd' file into 'WIMBoot.wim' ?  So that I can directly use 'WIMBoot.wim' file as a Source in 'WinNTSetup v.3.6.1' in order to create smallest 'WTG + WimBoot + VHDX powerful combination'.
 
Does anybody know about a Script/Tool/Commands/Method in order to convert  'install.esd' file into 'WIMBoot.wim' ?
 
Any help/Suggestion will be highly appreciated...........
 
Thanks in Advance
 
Regards.......

Edited by devdevadev, 09 July 2014 - 02:12 PM.


#14 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1,083 posts
  • Location:Nantes - France
  •  
    France

Posted 09 July 2014 - 02:38 PM

Hi Devdevadev,

 

I am not familiar with ESD format but I believe Wimlib-imagex can handle these files.

See here

The last 2 threads mention ESD.

 

Regards,

Erwan


  • devdevadev likes this

#15 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 194 posts
  •  
    India

Posted 09 July 2014 - 06:45 PM

 

 

Hi Devdevadev,

 

I am not familiar with ESD format but I believe Wimlib-imagex can handle these files.

See here

The last 2 threads mention ESD.

 

Regards,

Erwan

 

Hello Sir,

 

Can we use 'intall.esd' files for 'WIMBoot' in 'wimlib' way ?

 

Can you please provide us a Step by Step tutorial in your Official Site for creating 'Win8.1U1 - WIMBoot' from

 'install.esd -> WIMBoot.wimby using 'Wimlib' ?

 

           'install.wim' -> WIMBoot.wim' Conversion code via DISM is Here

 

What will be the 'Wimlib'  equivalent of  'install.esd' -> WIMBoot.wim' Conversion ?

 

And what code I should have to use in order to 'Capture Installation' and 'Apply' converted 'WIMBoot.wim' ?

 

Regards


Edited by devdevadev, 09 July 2014 - 07:11 PM.


#16 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 10,845 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 09 July 2014 - 07:15 PM

 

           'install.wim' -> WIMBoot.wim' Conversion code via DISM is Here

 

It is there, but it is also here:

http://reboot.pro/to...ation/?p=184217

where there is also the correspondent wimlib command :).

(and BTW that is the same thread that erwan.l just gave you a link to ;))

 

:duff:

Wonko


  • devdevadev likes this

#17 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 194 posts
  •  
    India

Posted 10 July 2014 - 04:29 AM

It is there, but it is also here:

http://reboot.pro/to...ation/?p=184217

where there is also the correspondent wimlib command :).

(and BTW that is the same thread that erwan.l just gave you a link to ;))

 

:duff:

Wonko

 

Hello Sir,

 

Greeting of the Day........

 

Thanks for suggesting already checked link......... <_<

 

Actually I was asking for 'wimlib' command in order to directly convert 'install.esd' to 'WIMBoot.wim' (not to 'install.wim').

 

Can you please provide me 'wimlib' commands in order to directly convert 'install.esd' to 'WIMBoot.wim' ?

 

 

Thanks in Advance

 

Regards.... :worship: ....



#18 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1,083 posts
  • Location:Nantes - France
  •  
    France

Posted 10 July 2014 - 07:18 AM

what about : wimlib-imagex export install.esd 1 wimboot.wim --compress=maximum --check ?

(copy pasted from the mentionned wimlib-imagex thread)

 

The boot flag might be missing then.



#19 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 10,845 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 10 July 2014 - 12:34 PM

What about:

wimlib-imagex export install.esd 1 install.wim --compress=maximum --check
ren install.wim wimboot.wim

:dubbio:

 

:duff:

Wonko


  • devdevadev likes this

#20 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1,083 posts
  • Location:Nantes - France
  •  
    France

Posted 10 July 2014 - 04:30 PM

might even be worth adding --boot to make the wim file bootable:

 

wimlib-imagex export install.esd 1 wimboot.wim --compress=maximum --check --boot

 

Not sure the rename part (as mentionned by Wonko) is needed since wimlib should create a brand new file on exporting? hence one can choose its destination file name?

 

That discussion should be on the wimlib thread :)



#21 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 10,845 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 10 July 2014 - 04:43 PM

Not sure the rename part (as mentionned by Wonko) is needed since wimlib should create a brand new file on exporting? hence one can choose its destination file name?

Sure :), I was obviously joking, the point being "what's in a name"? :dubbio:

http://en.wikipedia...._smell_as_sweet

 

:duff:

Wonko



#22 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1,083 posts
  • Location:Nantes - France
  •  
    France

Posted 10 July 2014 - 05:47 PM

Sure :), I was obviously joking, the point being "what's in a name"? :dubbio:

http://en.wikipedia...._smell_as_sweet

 

:duff:

Wonko

 

Excellent quote (again)  :worship:



#23 cdob

cdob

    Silver Member

  • Expert
  • 976 posts

Posted 10 July 2014 - 07:24 PM

'install.wim' -> WIMBoot.wim' Conversion code via DISM is Here

No, it's not about conversion to wimboot.
It's about a small wimbootable file, applyedd with WinNTSetup.

http://technet.micro...y/dn621983.aspx
To convert use: Dism /Export-Image /WIMBoot
This creates a bigger wimboot file. Some files are expanded or less compressed, could be less cpu usage at boot.
No, I don't know details.

#24 synchronicity

synchronicity

    Frequent Member

  • Advanced user
  • 122 posts
  •  
    United States

Posted 11 July 2014 - 12:19 AM

You can use the --compress and/or --chunk-size options to wimlib-imagex to choose a different compression format.

 

The default for exporting, capturing, or appending in --wimboot mode is XPRESS compression with 4096 byte chunks.

 

This can be changed to XPRESS with 8192, 16384, or 32768 byte chunks, or LZX with 32768 byte chunks, while still being compatible with Microsoft's WOF driver, which implements the functionality used for "WIMBoot".


  • devdevadev likes this

#25 devdevadev

devdevadev

    Frequent Member

  • Advanced user
  • 194 posts
  •  
    India

Posted 11 July 2014 - 01:14 AM

abbodi1406 made a script for this:
http://forums.mydigi....l=1#post903619

basically you capture an empty directory as wim maximum compression and then you export recovery compression to 2nd index, then delete the first index.
Since you cannot combine the compression types, the result will be converting the recovery compression to max compression.

Example script ran from extracted iso's sources\ directory:

 

Code-

mkdir c:\temp
dism /capture-image /capturedir:c:\temp /imagefile:install.wim /compress:max /name:"Bogus index"
for /l %%x in (1,1,24) do (
dism /export-image /sourceimagefile:install.esd /sourceindex:%%x /destinationimagefile:install.wim /compress:recovery
)
dism /delete-image /imagefile:install.wim /index:1
rd 
c:\temp

 







Also tagged with one or more of these keywords: wimboot, win to go, vhdx, winntsetup v3.6.1, usb to go, usb booting