If you have plans to create a Windows 10 wimboot install by means of DismMountService, to avoid issues during applying on wimboot mode before capturing a WIM image it is recommended to do the following:
1 .- Install Windows 10 OS on a VHD fixed size VHD (see NOTE-4 and NOTE-5) by means of DismMountService, you will have to create a entry on the BCDs of your PC located on EFI\Microsoft\Boot\BCD and/or Boot\BCD, now we can use DMS to create the boot files/folders and edit them with BootIce using as a guide the pictures located on:
"WimBootCompress Installs\BCDs\On PC"
If you prefer you can do it also manually, see: https://docs.microso...ions-techref-di
Download attachment with the WimBootCompress.exe and pictures on folder BCDs.
2 .- Boot to the Windows 10 OS on the VHD that will be used as source for create the WIM image file.
3 .- Install all your required drivers, Office and other software, but DO NOT install SvBus driver.
4 .- Run from the VHD WimBootCompress.exe, it is a SFX file (selfextracting file), it will copy WimBootCompress.ini to C:\Windows\System32 folder overwriting previous version (if any). Run again DMS from the VHD and this time installing the boot files/folders to the VHD (wich is C: in this moment), and edit them with BootIce using as a guide the pictures located on "WimBootCompress Installs\BCDs\On VHD"
WimBootCompress.ini into the SFX file:
5 .- Reboot to your main full OS on the PC or Win10XPE_x64, mount the VHD and capture the OS (as a standard WIM image) by means of DismMountService.
6 .- Dismount the VHD, create a new fixed size VHD and install from previously captured WIM, don't forget to select Wimboot mode when applying the OS on your virtual drive.
7 .- If you made a wimboot install on a VHD, It is recommended to make a FFU image of the VHD right now before unmount it, this will let you rebuild the VHD in seconds if required.
NOTE-1: This is WimBootCompress-W10X.ini renamed, taken from the great tool made by wimb: VHD_WIMBOOT
NOTE-2: The main pourpose of this modified WimBootCompress.ini is to reduce the size on MB used on the target drive.
NOTE-3: The installs made by means of DismMountService are NOT valid for RAMBOOT (only valid for CSM/MBR, not valid for UEFI), even if SvBus driver was previously installed on the source OS, since the SvBus driver will be a pointer to the source WIM file and grub4dos requires it uncompressed. If you want to make your new wimboot install to be RAMBOOT capable do as on OPTIONAL:
NOTE-4: For faster booting it is also possible to use a dynamic VHD (expandable), since the begining, it is also capable to RAMBOOT after installing SvBus driver as on OPTIONAL but it can't RAMBOOT if compressed by lz4.
NOTE-5: The FFU previously created (on No. 7 and also on No. 8) from a fixed size VHD allow us to Apply it to a new created dynamic VHD,
8 .- After booting your wimboot VHD for the first time install SvBus driver, and reboot to your main full OS on the PC or Win10XPE_x64, mount the VHD and modify the BCDs on Boot\BCD on your PC and into the VHD as required, no need to worry about the BCDs on EFI\Microsoft\Boot\BCD because RAMBOOT is only possible on CSM/MBR, see attached pictures on folder BCDs, make a new FFU image and dismount it.
9 .- Now it is time to boot as RAMBOOT by means of grub4dos, assuming you have on your BCD an entrance for \grldr.mbr, just add to your menu.lst the following:
10 .- A fixed size VHD allow us to compress it using lz4_compressor, see: http://reboot.pro/fi...compressor/thenour menu will be like this:
If Rambooting from a fast device as an SSD use expandable VHDs, they have very good speed and a resonable saved espace, do no require any additional compression, they are capable to Ramboot and also can be booted from Windows bootmanager, so it is not a big issue if they can't boot as Filedisk using grub4dos.
If Rambooting from a not so fast device as an SSD, we have the alternative to use LZ4 compressed VHDs, wich are the faster option and also save more espace than any other option, but they are only usefull for Rambooting, we can not boot them as Filedik using grub4dos or from Windows Bootmanager, this limitations also apply to GZ compression.