Jump to content











Photo
* * * * * 1 votes

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

ramdisk grub4dos wimlib svbus windows 10 ssd usb wim vhd wimboot

  • Please log in to reply
543 replies to this topic

#526 wimb

wimb

    Platinum Member

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

Posted 4 weeks ago

Thanks my friend, but you forgot to put a link to download WOF_Compress_Trusted-41

 

 

Yes you are right and I have added the Download Link  :)


  • alacran and antonino61 like this

#527 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1141 posts
  •  
    Italy

Posted 4 weeks ago

thanx again, wimb, I will try this one too. in the meantime, I am trying to find out what subfolders in windows, windows\syswow64 and windows\system32 can be taken out with no hindrance to the system. my syswow64 now has only the en-us subfolder, for instance, but I will deal with it in more detail in get-alladafluff-out as we agreed.



#528 alacran

alacran

    Gold Member

  • .script developer
  • 2204 posts
  •  
    Mexico

Posted 4 weeks ago

 

In SYSTEM registry HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services the installed drivers can have ImagePath value beginning with \SystemRoot\System32\DriverStore\

In that case UnCompress of System32\drivers folder is not sufficient when the install mode for Apply of WIM file is Compact LZX

Instead of UnCompress of the entire DriverStore folder we can look in the SYSTEM registry what installed drivers have ImagePath referring to DriverStore and then decide to UnCompress those drivers.

This approach is already working in WinNTSetup and is now also applied in VHD_WIMBOOT-57 and WOF_Compress-41

to avoid Boot problems as occur for Windows 11x64 in case of LZX Compressed nvlddmkm.sys Kernel Mode driver.

This approach is used instead of modifying WimBootCompress.ini file [PrepopulateList] section so that these DriverStore drivers become WOF UnCompressed.

 

Most of these drivers are very small (less than 100 kB) so that UnCompress has no effect in the UsedSize.

An exception is the NVIDIA Kernel Mode driver nvlddmkm.sys which is about 31 MB UnCompressed.

In Mini-10x64 this driver does not occur since we use there the Microsoft Basic Display Driver to Save space.

 

File VHD_WIMBOOT-57\makebt\wim_info\ImagePath_DriverStore_List.txt gives in your case after Apply the DriverStore drivers that were WOF UnCompressed for this purpose.

 

 

So I assume this approach is required mainly for Win 11, and should work fine in case of Compact mode installations.

 

But not in case of Wimboot mode installations, as those files will not be real files and could not be decompressed.

 

Suggestion:

 

Once you create the list of files that require to be uncompressed (Compact mode) or real files and not pointers (Wimboot mode), after apply the OS to the VHD, use wimlib-imagex wimextract command (or equivalently wimlib-imagex extract), to extract the files on the list from the WIM file to the VHD.

 

In this case you could add a second pass of wimlib-imagex (using wimextract) to extract only those files mentioned on the list to the VHD and overwrite the previous pointer files.

 

Or even better use wimextract in both cases to be consistent, this way we can also avoid modifications to the WimBootCompress.ini file [PrepopulateList] section.

 

alacran

Attached Files


  • antonino61 likes this

#529 wimb

wimb

    Platinum Member

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

Posted 4 weeks ago

So I assume this approach is required mainly for Win 11, and should work fine in case of Compact mode installations.

 

But not in case of Wimboot mode installations, as those files will not be real files and could not be decompressed.

 

 

I think it works in Compact and in WimBoot mode.

 

I think in WimBoot mode WOF UnCompress of WOF pointer file results in UnCompressed real file



#530 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1141 posts
  •  
    Italy

Posted 4 weeks ago

Hi Wimb, I gather this version compresses the captured wim more than before, but it also applies it to the resulting vhd in a less compressed fashion than before. is there anything I am missing out upon? 

As for win10 vs win11, I do not see much of a difference, but for the cosmetics of the taskbar, which might as well be done without for some. but u said u identified the windowsapps concerned (a few more than there should be, though, for what it is worth). for portability u do need to leave the repository uncompressed, but those like me who took most of the content of the folder out, they were already uncompressed ok without so much loss in unused space. do u think that the expansion of the applied vhd's can be ascribed to all these modifications? my 2.1gb wim yielded a 3.9gb vhd, to be almost comfy with unused space (just half a gig). now I will try the wimboot version and let u know.



#531 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1141 posts
  •  
    Italy

Posted 4 weeks ago

well the lz4-compressed vhd is 2.8gb. and the wim+vhd combo scenario is analogous to, if not more drastic than, the previous one: the wimboot vhd cannot be smaller that 2.5gb with a near-comfy 800megs unused space (looks like a standalone vhd). I hope it is faster enough to justify the space taken. 



#532 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1141 posts
  •  
    Italy

Posted 4 weeks ago

well, here I am on the lz4. it is as fast as before, the only difference being larger size. now I will try the combo. 

the combo is the aforesaid 2.1gb(wim)+2.5gb(vhd), which is 4.6gb overall, larger size than the 3.9gb standalone vhd. the 2.5gb vhd of the combo I managed to gz it to 600megs (which would make an overall 2.9gb). now I will tell u how fast it is in a bit.

well here I am from the wimboot version of the contraption - then again, just too big, with all that may ensue in terms of speed. maybe used space does not grow, but that is not to say that it used to grow that much earlier on - with all our pruning, used space bulging was almost a thing of the remote past before as well. the only space gain that I have seen is in the initial wim file 2.1gb, as I said at the outset.



#533 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1141 posts
  •  
    Italy

Posted 4 weeks ago

btw, I happen to find something out during vhd compression - the lz4 type leaves the used/unused space ratio intact, whereas the gz type changes the unused space from 500megs to 1.32gb and this space is bound to remain unused for long. let me try shrinking the vhd from 3.9gb to 3.5gb and then re-gz'ing it and see if it leaves decent unused space in the end. 



#534 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1141 posts
  •  
    Italy

Posted 4 weeks ago

well folks, I managed to squeeze the full vhd to 2.9gb and gz it to 2.45gb. I will  tell u how much unused space it will leave (as ramdisk and if possible as filedisk too). in the meantime, the wimboot vhd was applied at 1gb and gz'd to 435mg. c u in a bit.



#535 wimb

wimb

    Platinum Member

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

Posted 4 weeks ago

Update VHD_WIMBOOT_Trusted-58 and Win_Reduce_Trusted-43 and WOF_Compress-42

 

Download:  from wimb GitHub  -   VHD_WIMBOOT_Trusted-58  and   SVBus-signed_2-E.zip  and  Win_Reduce_Trusted-43 and WOF_Compress-42

 

Download File E = Encrypted PassWord = bootwimb   and SVBus PassWord = reboot.pro

 

Manual:   VHD_WIMBOOT.pdf

 

Always Shut-Off AntVirus Software and Disable Windows Defender when working with signed SVBus driver !!
otherwise wimlib and Boot errors will occur .....

 

- WOF UnCompress of single driver file instead of driver folder in DriverStore for drivers where Services ImagePath contains \SystemRoot\System32\DriverStore\

 

This Saves a lot of space (0.6 GB) in case of \Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\nvlddmkm.sys NVIDIA Kernel Mode driver

 

The Function _Wof_Uncompress_ being used requires to be Trusted Installer, so we now use VHD_WIMBOOT_Trusted.cmd to Run VHD_WIMBOOT_x64.exe as Trusted Installer.

 

WOF UnCompress of WIM-Backed pointer file results in UnComressed real file.

 

WimBoot and Compact LZX mode of Win11x64 are booting OK

 

WOF Status List as made with WOF_Compress-42

; WIM-Backed ; T:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\NvIFROpenGL64.dll
; WIM-Backed ; T:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\nvinfo.pb
; WIM-Backed ; T:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\NvInstallerUtil.dll
; 0 ; T:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\nvlddmkm.sys
; WIM-Backed ; T:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\nvldumd.dll
; WIM-Backed ; T:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\nvldumdx.dll
; WIM-Backed ; T:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\nvlicensings.dll


  • alacran and antonino61 like this

#536 alacran

alacran

    Gold Member

  • .script developer
  • 2204 posts
  •  
    Mexico

Posted 4 weeks ago

 

- WOF UnCompress of single driver file instead of driver folder in DriverStore for drivers where Services ImagePath contains \SystemRoot\System32\DriverStore\

 

This Saves a lot of space (0.6 GB) in case of \Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\nvlddmkm.sys NVIDIA Kernel Mode driver

 

The Function _Wof_Uncompress_ being used requires to be Trusted Installer, so we now use VHD_WIMBOOT_Trusted.cmd to Run VHD_WIMBOOT_x64.exe as Trusted Installer.

 

WOF UnCompress of WIM-Backed pointer file results in UnComressed real file.

 

WimBoot and Compact LZX mode of Win11x64 are booting OK

 

WOF Status List as made with WOF_Compress-42

; WIM-Backed ; T:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\NvIFROpenGL64.dll
; WIM-Backed ; T:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\nvinfo.pb
; WIM-Backed ; T:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\NvInstallerUtil.dll
; 0 ; T:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\nvlddmkm.sys
; WIM-Backed ; T:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\nvldumd.dll
; WIM-Backed ; T:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\nvldumdx.dll
; WIM-Backed ; T:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\nvlicensings.dll

 

Good work wimb, and it is a very good espace saving, basically only required *.sys files are decompresed now.

 

By the way I'm glad to know if a pointer file is decompresed it becomes a real size file, I never thought it was possible, but it is good you tested that.

 

alacran


  • wimb and antonino61 like this

#537 wimb

wimb

    Platinum Member

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

Posted 4 weeks ago

Good work wimb, and it is a very good espace saving, basically only required *.sys files are decompresed now.

 

By the way I'm glad to know if a pointer file is decompresed it becomes a real size file, I never thought it was possible, but it is good you tested that.

 

 

Both WimBoot and Compact Mode are based on using WOF driver.

So it is not so strange that WOF UnCompress of WimBoot pointer file results in UnCompressed real file.

 

Luckily everything can be followed easily by making WOF Status lists e.g. of DriverStore by using WOF_Compress-42

Never thought that this program when developing it would become so useful.

Always Disable Windows Defender when using WOF_Compress, since that saves a lot of time.

; WIM-Backed ; T:\Windows\System32\DriverStore\nl-NL\xusb22.inf_loc
; WIM-Backed ; T:\Windows\System32\DriverStore\nl-NL\ykinx64.inf_loc
;
;
; End of List WOF Status 
; Processed Files       = 2279
; Used Size Drive T: = 0.61 GB
; Time  = 1 sec


  • antonino61 likes this

#538 alacran

alacran

    Gold Member

  • .script developer
  • 2204 posts
  •  
    Mexico

Posted 4 weeks ago

So I assume if we run VHD_WIMBOOT from a Win10XPE_x64, we can run the *.exe file directly as we are already TI on Win10XPE_x64.

 

JFYI my assumption that pointer files were not able to become in real files with real size and real content, was because I have used 7-zip for this, and it extracts a pointer file from a Wimboot VHD as file of the real size but the file is empty.  So it is also important to remember ONLY WOF_Compress is capable to decompress pointer files as real files.

 

Yes, I'm totally agree WOF_Compress is a fantastic tool, very useful to deal with all related to WOF driver compression and decompression. I'm very glad I asked you to make this program on Post No. 23 of the old thread about it, where all related to this great tool started. WofCompress tool for Win7 - Win10

 

Once again thanks very much for all your very useful programs. They made our lives easier.

 

alacran


  • wimb and antonino61 like this

#539 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1141 posts
  •  
    Italy

Posted 4 weeks ago

This one works like a charm!!!


  • wimb likes this

#540 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1141 posts
  •  
    Italy

Posted 4 weeks ago

compression-wise, let me insist that the gz one receive the attention it deserves - 2.2gb filedisk (from an original 3.5gb). gz has longer compression times than  lz4, but far shorter decompression ones and overwriting facilities which come in handy. see it for urselves.



#541 wimb

wimb

    Platinum Member

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

Posted 4 weeks ago

So I assume if we run VHD_WIMBOOT from a Win10XPE_x64, we can run the *.exe file directly as we are already TI on Win10XPE_x64.

 

JFYI my assumption that pointer files were not able to become in real files with real size and real content, was because I have used 7-zip for this, and it extracts a file of the real size but the file is empty.  So it is also important to remember ONLY WOF_Compress is capable to decompress pointer files as real files.

 

Yes, I'm totally agree WOF_Compress is a fantastic tool, very useful to deal with all related to WOF driver compression and decompression. I'm very glad I asked you to make this program on Post No. 23 of the old thread about it, where all started. WofCompress tool for Win7 - Win10

 

 

You are right, but you can also use VHD_WIMBOOT_Trusted.cmd since it will recognise PE environment and then straight launch VHD_WIMBOOT_x64.exe

 

Indeed very good that you asked me to make WOF_Compress program at the time that the whole WOF stuff was rather new to me ....


  • alacran likes this

#542 wimb

wimb

    Platinum Member

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

Posted A week ago

Update VHD_WIMBOOT_Trusted-60 and Win_Reduce_Trusted-44

 

Download:  from wimb GitHub  -   VHD_WIMBOOT_Trusted-60  and   SVBus-signed_2-E.zip  and  Win_Reduce_Trusted-44

 

Download File E = Encrypted PassWord = bootwimb   and SVBus PassWord = reboot.pro

 

Download:  Win11 ISO from Microsoft  -  Win11_Language_x64.iso  5GB

 

Manual:   VHD_WIMBOOT.pdf

 

Always Shut-Off AntVirus Software and Disable Windows Defender when working with signed SVBus driver !!
otherwise wimlib and Boot errors will occur .....

 

- Update UEFI Grub4dos (= Grub4efi Or G4E) - grub4dos-for_UEFI-2021-09-08.7z
- Windows 11 compatibility improved by force booting VHD with recent Boot Manager of Windows 11

- Adding Windows 11 VHD will Update Windows Boot Manager to version of Windows 11

- Avoiding Windows Boot Manager Error 0xC0000428 - winload.efi signature can't be verified

 

- Win_Reduce_Trusted - Changed remove of DriverStore folders using folder names with trailing * instead of full  folder name

The complex folder names in DriverStore are changing rapidly with Updates and Windows versions

With the trailing * solution it is not needed anymore to change the folder names in remove_sub_DriverStore.txt

 

Win_Reduce_Trusted-44\Win_reduce\File_List\remove_sub_DriverStore.txt

; Adjust to your needs - Only rules with leading backslash and trailing * are used - Wildcards like * and ? are Not allowed inside Folder Names
;
\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_*
\Windows\System32\DriverStore\FileRepository\helloface.inf_amd64_*
;
W11x64_2021-10-03_145700.jpg == W11x64_WB_2021-10-03_153529.jpg == Mini-11x64_RAMDISK_2021-10-03_154502.jpg

  • antonino61 likes this

#543 wimb

wimb

    Platinum Member

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

Posted A week ago

Update Win_Reduce_Trusted-45

 

Download:  from wimb GitHub  -  Win_Reduce_Trusted-45

 

Download File E = Encrypted PassWord = bootwimb

 

Download:  Win11 ISO from Microsoft  -  Win11_Language_x64.iso  5 GB

 

Manual:   VHD_WIMBOOT.pdf

 

- Win_Reduce_Trusted - Changed to keep WindowsApps folders using folder names with trailing * instead of full  folder name

The complex folder names in WindowsApps are changing rapidly with Updates and Windows versions

With the trailing * solution it is not needed anymore to change the folder names and we can use now for Windows 10 and 11 keep_WindowsApps.txt

 

- Reducing Windows 11 LZX UsedSize from 5 GB into 2 GB in only 40 seconds - a lot easier and faster than MSMG Toolkit  :)

  Reduce Windows footprint - creates a slimmed down or bloat-free Windows

 

Win_Reduce_Trusted-45\Win_reduce\File_List\keep_WindowsApps.txt

; Adjust to your needs - Only rules with leading backslash and trailing * are used - Wildcards like * and ? are Not allowed inside Folder Names
;
\Program Files\WindowsApps\Microsoft.SecHealthUI_*
\Program Files\WindowsApps\Microsoft.UI.Xaml.*
\Program Files\WindowsApps\Microsoft.VCLibs.*
\Program Files\WindowsApps\Microsoft.WindowsNotepad_*


  • antonino61 likes this

#544 wimb

wimb

    Platinum Member

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

Posted A week ago

Download:  Win11 ISO from Microsoft  -  Win11_Language_x64.iso  5 GB

 

Microsoft_Downloads_2021-10-05_184154.jpg

 

Download:  WinNTSetup v5.0   and   Manual:   VHD_WIMBOOT.pdf

 

The New Beast has arrived .... Smaller and Faster than Windows 10x64 and OK for Install of all drivers and for booting from USB 3.1 ....  B)

 

It would be better when most WindowsApps integrated since Windows 8 (the Bing Apps, ZuneMusic and Xbox and more ...  :wacko:

were Not preinstalled, but just available in the WindowsStore like e.g. Spotify App and Scanner App for the very few that wishes these Bing Apps.

 

W11x64_NL_2021-10-05_160157.jpg == Mini-11x64_LU_2021-10-05_183333.jpg


  • antonino61 likes this





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

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users