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
1025 replies to this topic

#501 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 30 August 2021 - 06:47 AM

So security is not to be deleted

#502 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 30 August 2021 - 06:48 AM

The captured wim file is 1.5gig

#503 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 30 August 2021 - 07:25 AM

Win_Reduce_Trusted-42 was used to apply your Custom_remove_files.txt and Custom_remove_folders.txt on my Mini-11x64.vhd with UsedSize = 2.6 GB

 

There is only a very small reduction and the UsedSize is then 2.4 GB

 

However, there is a more serious problem. After booting, I cannot login since the password is refused and the pincode does not work anymore.

 

I see in your Custom_remove_files.txt a lot of Security and Authentication files ....

 

Just exactly what I was expecting, a very little space gain and serious problems for blindly deleting too much.

So I was right, antonino61's additional cuts are not for general use, and they could work only to fit his preferences.

 

alacran



#504 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 30 August 2021 - 07:32 AM

All cuts or some cuts?

#505 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 30 August 2021 - 12:00 PM

To me wimb's lists are fine for general use, nothing critical is missed.

 

It is neccesary to understand when we have to stop cutting and don't make a mania of it.

 

I prefer a trustable OS in a decent size, than cut a few MB more and find troubles latter if I want to use some feature that was deleted just for saving a few MB.

 

alacran


  • wimb and antonino61 like this

#506 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 30 August 2021 - 02:14 PM

Right you are. Trying now without security and authentication lines, and with lines concerning services I have taken out.

#507 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 30 August 2021 - 04:54 PM

@ wimb

 

It is funny our good friend antonino61 is worry for peanuts, and I found an increase of about 200 MB in the used size of my Wimboot VHDs.

 

Using VHD_WIMBOOT v5.5, just recaptured my Mini-10x64-WB.vhd and Mini-8x64-WB.vhd, after adding to them about 2 MB of new portables I want to keep into the VHD, and after re-deploying both of them into their respective same VHD, found the used espace is about 200 MB bigger now, after some analysis I found there is a new line in:

 

WimBootCompress.ini under [PrepopulateList] section: \Windows\System32\DriverStore\FileRepository\*

So far all my VHDs are working very fine without the need to have FileRepository uncompressed or as a real file in case of Wimboot installations, is it required only for Win 11?

If so I kindly suggest to add a check box to let the user select the respective WimBootCompress.ini for Win 11, or if it is not very difficult to you, I think it could be better to implement the code to let VHD_WIMBOOT automatically use that option only if required.

In the meantime I will edit/replace the \VHD_WIMBOOT\makebt\WimBootCompress.ini used in the new 5.5 version of your program, as I don't have any interest in the Win11 beta version.

 

And to avoid recapture and reapply the VHDs I'm going to inject the WimBootCompress.ini into both WIM files with wimlib-clc

 

alacran



#508 wimb

wimb

    Platinum Member

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

Posted 30 August 2021 - 05:41 PM

Using VHD_WIMBOOT v5.5, just recaptured my Mini-10x64-WB.vhd and Mini-8x64-WB.vhd, after adding to them about 2 MB of new portables I want to keep into the VHD, and after re-deploying both of them into their respective same VHD, found the used espace is about 200 MB bigger now, after some analysis I found there is a new line in:

 

WimBootCompress.ini under [PrepopulateList] section: \Windows\System32\DriverStore\FileRepository\*

So far all my VHDs are working very fine without the need to have FileRepository uncompressed or as a real file in case of Wimboot installations, is it required only for Win 11?

If so I kindly suggest to add a check box to let the user select the respective WimBootCompress.ini for Win 11, or if it is not very difficult to you, I think it could be better to implement the code to let VHD_WIMBOOT automatically use that option only if required.
 

 

The new line in WimBootCompress.ini is indeed needed for Windows 11, where in my case about 14 installed drivers don't occur in drivers folder as usual.

These drivers only occur in the DriverStore\FileRepository where they need to be UnCompressed or as a real file in case of Wimboot installations.

I thought the increase in UsedSize was acceptable and most likely future versions of Windows 10x64 will have the same need for uncompressed DriverStore\FileRepository

 

I will consider a solution where different WimBootCompress.ini files will be auto used by VHD_WIMBOOT program.



#509 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 30 August 2021 - 06:30 PM

All cuts or some cuts?

Not those cuts, the other cuts.

 

:duff:

Wonko



#510 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 30 August 2021 - 07:53 PM

 

......most likely future versions of Windows 10x64 will have the same need for uncompressed DriverStore\FileRepository

 

I will consider a solution where different WimBootCompress.ini files can be used by VHD_WIMBOOT program.

 

I don't expect anything new or changes on Win10, they have a new baby now, and they will not care about the old baby anymore, as they usually do.  And if there is any mayor updete, it will be to intentionally make the 10 OS slower as also use to do, to promote the new version is better and faster as always.

 

If implement the use of different WimBootCompress.ini files in VHD_WIMBOOT program, becomes complicated to you, don't bother I can edit or replace the WimBootCompress.ini, very easily on future new versions, but in this case I suggest to make a comment on the PDF file, to let non advanced users know how to do it too.

 

alacran



#511 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 31 August 2021 - 01:37 AM

well, getting back to the cutting, I have found out that it was the remote procedure call part that was not to be taken out, not the security and authentication kinda thing, which I am still investigating, though. now proceeding with the exclusions in the unused programs and features and unused services department. the rest of the cutting must be ok.



#512 wimb

wimb

    Platinum Member

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

Posted 31 August 2021 - 08:57 AM

my preference is to keep as much functionality as possible and only remove those unneeded folders / files that are really space savers.

 

so removing services or files that don't use a lot of space is not the idea ....



#513 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 31 August 2021 - 05:13 PM

...unless functionality is guaranteed by portables, cmd's, bat's and/or reg's, as was initially suggested by the famous pundits here. Eg, I use nettime instead of windows time service, as it is not what windows does, but what windows lets u do by single unintegrated executables. Rather than a system, I see windows as a bios-to-desktop ferry, possibly to be turned into a hydrofoil or hovercraft; the rest is for us to do whatever we need. So I prefer windows to do as little as possible, having only its own immediate versatility triumph.

#514 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 02 September 2021 - 12:47 AM

well,  I can confirm that the disaster was due to actually 2 files concerning remote procedure call on the custom file removal list (just search for rpc*.dll and delete the 2 entries concerned, and it'll be ok).



#515 wimb

wimb

    Platinum Member

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

Posted 02 September 2021 - 07:47 AM

Update VHD_WIMBOOT-56 and Win_Reduce_Trusted-43

 

Download:  from wimb GitHub  -   VHD_WIMBOOT-56  and   SVBus-signed_2-E.zip  and  Win_Reduce_Trusted-43

 

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 .....

 

- Only in case of Windows 11 then \Windows\System32\DriverStore\FileRepository will be uncompressed by auto use of makebt\WimBootCompress-W11.ini as WimBootCompress.ini file

Capture in WimBoot mode replaces existing \Windows\System32\WimBootCompress.ini file in WIM file

so that next Apply will use that file to determine what folders and files will be uncompressed (or real files instead of pointers for Apply in WimBoot mode)

- In case of Windows 10x64 then in this way  \Windows\System32\DriverStore\FileRepository will not be uncompressed anymore which saves space

 

Mini-11x64_RAMDISK_2021-09-10_144053.jpg == W11x64_VHD_2021-09-11_095719.jpg == W11x64_VHD_2021-09-11_100159.jpg == Mini-11x64_RAMDISK_2021-09-11_150113.jpg


  • alacran and antonino61 like this

#516 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 02 September 2021 - 10:26 AM

tx wimb, will try that asap!



#517 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 05 September 2021 - 03:14 PM

moved the comment to get-alladafluff-out



#518 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 06 September 2021 - 05:36 AM

woops



#519 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 13 September 2021 - 02:14 PM

comment moved to get-alladafluff-out



#520 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 13 September 2021 - 11:02 PM

comment moved to get-alladafluff-out



#521 wimb

wimb

    Platinum Member

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

Posted 14 September 2021 - 05:42 AM

@antonino61

 

Your posts #517 - #520 belong to your own thread Get-alladafluff-out

 

Please do not post all your experiments in this thread VHD_WIMBOOT since it is becoming rather confusing.


  • antonino61 likes this

#522 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 14 September 2021 - 10:01 AM

Ok, I will.

#523 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 14 September 2021 - 10:22 AM

done


  • wimb likes this

#524 wimb

wimb

    Platinum Member

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

Posted 16 September 2021 - 05:02 PM

Update VHD_WIMBOOT-57 and Win_Reduce_Trusted-43 and WOF_Compress-41

 

Download:  from wimb GitHub  -   VHD_WIMBOOT-57  and   SVBus-signed_2-E.zip  and  Win_Reduce_Trusted-43 and WOF_Compress-41

 

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 .....

 

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.

 

In Windows 10x64 and 11x64 we have in my case the following list of drivers in the DriverStore that must be WOF UnCompressed

\Windows\System32\DriverStore\FileRepository\basicdisplay.inf_amd64_*\BasicDisplay.sys
\Windows\System32\DriverStore\FileRepository\basicrender.inf_amd64_*\BasicRender.sys
\Windows\System32\DriverStore\FileRepository\compositebus.inf_amd64_*\CompositeBus.sys
\Windows\System32\DriverStore\FileRepository\genericusbfn.inf_amd64_*\genericusbfn.sys
\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_*\nvlddmkm.sys
\Windows\System32\DriverStore\FileRepository\swenum.inf_amd64_*\swenum.sys
\Windows\System32\DriverStore\FileRepository\uefi.inf_amd64_*\UEFI.sys
\Windows\System32\DriverStore\FileRepository\ufxchipidea.inf_amd64_*\UfxChipidea.sys
\Windows\System32\DriverStore\FileRepository\umbus.inf_amd64_*\umbus.sys
\Windows\System32\DriverStore\FileRepository\urschipidea.inf_amd64_*\urschipidea.sys
\Windows\System32\DriverStore\FileRepository\urssynopsys.inf_amd64_*\urssynopsys.sys
\Windows\System32\DriverStore\FileRepository\usb4devicerouter.inf_amd64_*\Usb4DeviceRouter.sys
\Windows\System32\DriverStore\FileRepository\usb4hostrouter.inf_amd64_*\Usb4HostRouter.sys
\Windows\System32\DriverStore\FileRepository\vrd.inf_amd64_*\vrd.sys

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.

 

Mini-11x64_VHD_RAMDISK_2021-09-16_192852.jpg


  • alacran and antonino61 like this

#525 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 16 September 2021 - 05:35 PM

@ wimb

 

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

 

alacran







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

8 user(s) are reading this topic

0 members, 8 guests, 0 anonymous users