Jump to content

wimb

Developer
  • Posts

    977
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Netherlands

Posts posted by wimb

  1. Update Download:   Make_WinPE_Trusted-97 -  E = file Encrypted with pw=bootwimb

    - Cleanup of File_List files - Removal of duplicates in file entries

    - SMALL_Add_Install_Files_10.txt improved with extra 30 MB PE Size so that Desktop DPI Setting is working with DPIScalingMFCApp.exe

    It means in fact that SMALL = WinXShell Version and LARGE = Explorer Version have almost the same List of Added files from install.wim

    Advantage is a much better PE  Desktop now also for the SMALL = WinXShell Version with adjustable DPI Setting :thumbup

    Windows 11 24H2 requires additional extra files to get Desktop DPI Setting working with DPIScalingMFCApp.exe

    For the time being this is considered as the final version ..... :cheerleader:

    But for sure new adjustments will be needed when New Windows ISO Versions arrive ... :wacko:

     

  2. Update Download:   Make_WinPE_Trusted-96 -  E = file Encrypted with pw=bootwimb

    - Tmp_System Registry files are generated from install.wim SYSTEM Hive and are applied 

    so that Update of PE SYSTEM Registry Hive with 14 Control and 48 Services Registry Keys originates from the actual ISO Source.

    - Also PE SYSTEM DriverDatabase is Updated with netvwifibus.inf Registry Keys in case BOOT.WIM is used as PE BOOT Source.

  3. Booting with PE WIM file from RAMDISK is non-persistent.

    It means the changes are never saved and booting with such Windows 10/11 x64 in PE_*.wim file is always the same.

    Follow procedure described on page 3 of Manual  VHD_Compact.pdf

    How to use Make_WinPE program - Make PE file boot.wim from Windows 10/11 x64 ISO file for Booting from RAMDISK 

    Prepare first your USB Portable SSD as described on page 1 of the Manual by using USB_FORMAT program

    In Make_WinPE program you can select the USB Boot Drive as Boot Drive for the PE_*.wim file that you are going to create

    In Make WinPE program you can select USB NTFS Drive as WinPE Drive. The created PE*.wim file is copied to folder WinPE on WinPE Drive.

    I hope this is what you are looking for, Or do I misunderstand your question.

     

    On the other hand If you Install Windows 10/11 x64 in VHD then the changes after booting are persistent.

    Such Windows To Go in VHD is booting as FILEDISK and behaves just as normal Windows.

    VHD loaded into RAM for booting as RAMDISK would be non-persistent, but is not supported.

    Instead use PE_*.wim file for booting from RAMDISK which is reliable and non-persistent.

     

  4. Update Download:   Make_WinPE_Trusted-92 -  E = file Encrypted with pw=bootwimb

    Update Download:   PE_Tools  version 3.1 with Portable Apps for WinPE

    Update Download:  Manual  VHD_Compact PDF 

    Make_WinPE - Make PE WIM file from Windows 10/11 x64 ISO file

    - Using PowerRun instead of AdvancedRun to Launch Make_WinPE_x64.exe as Trusted Installer 

      Enables to reduce program code and to reduce the time to make PE_*.wim file

    - Double-click Make_WinPE_PowerRun_x64.exe and Run Make_WinPE_x64.exe as Trusted Installer using Power Run

    PowerRun_2024-11-11_094428.jpg.d063374d0bb4981d853b135eb489ed0c.jpg

  5. Update Download:   Make_WinPE_Trusted-92 -  E = file Encrypted with pw=bootwimb

    Update Download:   PE_Tools  version 3.1 with Portable Apps for WinPE

    Update Download:  Manual  VHD_Compact PDF 

    Make_WinPE - Make PE WIM file from Windows 10/11 x64 ISO file

    - Using PowerRun instead of AdvancedRun to Launch Make_WinPE_x64.exe as Trusted Installer 

      Enables to reduce program code and to reduce the time to make PE_*.wim file

    - Double-click Make_WinPE_PowerRun_x64.exe and Run Make_WinPE_x64.exe as Trusted Installer using Power Run

    PowerRun_2024-11-11_094428.jpg.d063374d0bb4981d853b135eb489ed0c.jpg

     

  6. PE_Tools  version 2.8 with Portable Apps for WinPE - After booting with PE_*.wim file

    - Save Info gives HWIDs for Missing Drivers collected in file WinPE_HWIDs_Info.txt in folder PE_Tools\Drivers_Info

    1. Run Install_Drivers_from_Export_Folder.exe on PE Desktop

    2. Select Drivers Export subfolder e.g. System, MEDIA Or Net 

    3. pnputil.exe is auto used to Install non-Microsoft Drivers as earlier Exported by WinNTSetup

    WinPE_Missing_Drivers_2024-10-24_083846.thumb.jpg.648d9805442bf220aeb927d1d39eb00c.jpg

    Install_Drivers_from_Export_Folder.exe is used to Install Missing System and MEDIA Drivers - Audio OK

    WinPE_Audio_2024-10-24_084838.thumb.jpg.660d214b98f307d2cc0e79c8e3a99a7b.jpg

     

  7. UEFI_MULTI can Add Boot Image files like .wim and .vhd to EFI Boot Manager Menu of Internal SSD Disk.

    As Example is shown to Add PE_19041_264_US_L_32.wim file to EFI Boot Manager Menu on EFI Drive Z: normally used to Boot Encrypted Drive D: with Windows 11 x64

    Here Drive C: is from Windows 10 x64 Installed by WinNTSetup in 65 GB VHD file located on Encrypted Drive D:

    In this way we have MultiBoot of PE WIM from RAMDISK and Windows 10 x64 in VHD as FILEDISK and Windows 11 x64 in Encrypted Drive.

    In this MultiBoot configuration WIM and VHD files are located on Encrypted Drive D: of Internal SSD Disk.

    So even in case booting from USB is Not allowed we have a solution to boot easily with PE WIM file from RAMDISK to escape boot problems.

    Than we can decide to Repair or Apply an earlier Captured System Backup WIM file in VHD by using WinNTSetup in PE environment.

    UEFI_MULTI_2024-10-22_095734.jpg

     

    Screenshot After booting with Windows 11 x64 from Encrypted Drive C: 

    Win10_W2.vhd file with Windows 10 x64 in VHD and folder WinPE with PE WIM files are located on Encrypted Drive

    UEFI_MULTI_2024-10-23_112226.thumb.jpg.4fddf6db24766d931dcb211bc74550d5.jpg

     

  8. PE WIM files are Not meant to be installed in VHD and it is normal that WinNTSetup refuses to Install PE_*.wim files.
    The normal way of booting PE WIM files is by loading the PE_*.wim file into RAMDISK and then booting with Windows PE.
    In Make_WinPE you can Select the Boot Drive and the WinPE Drive and then an entry is made in your BootManager Menu.

    Booting from Internal SSD Harddisk Or from USB portable SSD with your PE_*.wim file are both supported.
    Also UEFI_MULTI portable app can be used to make Windows BootManager Menu entries for your PE*.wim files.

    The main purpose of booting with PE_*.wim from RAMDISK is to be in environment where you can use WinNTSetup to Install Win 10 / 11 x64 wim files on your internal SSD harddisk partition or in VHD located on NTFS partition.

    More Info in Manual VHD_Compact PDF

  9. PE WIM files are Not meant to be installed in VHD and it is normal that WinNTSetup refuses to Install PE_*.wim files.
    The normal way of booting PE WIM files is by loading the PE_*.wim file into RAMDISK and then booting with Windows PE.
    In Make_WinPE you can Select the Boot Drive and the WinPE Drive and then an entry is made in your BootManager Menu. Booting from Internal SSD Harddisk Or from USB portable SSD with your PE_*.wim file are both supported.
    Also UEFI_MULTI portable app can be used to make Windows BootManager Menu entries for your PE_*.wim files.

    The main purpose of booting with PE_*.wim from RAMDISK is to be in environment where you can use WinNTSetup to Install Win 10 / 11 x64 wim files on your internal SSD harddisk partition or in VHD located on NTFS partition.

    More Info in Manual VHD_Compact PDF

  10. Update Download:   Make_WinPE_Trusted-87 -  E = file Encrypted with pw=bootwimb

    Make_WinPE - Make PE WIM file from Windows 10/11 x64 ISO file

    Download Manual  VHD_Compact PDF and   PE_Tools  with Portable Apps for WinPE

    Credits and Thanks to homes32  aka  Jonathan Holmgren  for making PhoenixPE 

    - Added more Drivers for support of various Intel Core CPU microarchitectures such as Alder Lake, Tiger Lake and Ice Lake

    - Add_Drivers folder has separate support folders 10_x64 and 11_x64 for Windows 10 / 11 x64

    - Added Portable App  Install_Drivers_from_Export_Folder.exe  - also available in makebt folder
      1. Select Drivers Export subfolder e.g. System, MEDIA Or Net
      2. pnputil.exe is auto used to Install non-Microsoft Drivers as earlier Exported by WinNTSetup

    Make_WinPE - PE with PE_Tools and WinNTSetup Apply in VHD an earlier Captured WIM file

    WinPE_Apply_2024-09-30_101719.thumb.jpg.a2cbb7945e649d6ba1fe59332afa61ad.jpg

     

    Info about Windows To Go VHD - Auto Install of Drivers on other Hardware
    1. Enable Updates in Update Blocker and then Reboot computer to Activate Download of Drivers
    2. Wait until Auto Download and Install of Drivers has finished
    3. In Windows Update Blocker Disable again Updates to prevent the growth of Used Size in VHD

     

  11. On 8/17/2024 at 9:36 AM, bbq said:

    Loving Make_WinPE myself since I've been running WinPE on a daily basis.

    On page 3 of VHD_Compact PDF, just wondering if the Enterprise flavor were OK instead of Home? Even the oldest ones could still be downloaded from Microsoft after so many years and therefore 19041.264 should be here to stay:

    Since we're simply extracting files inside either sources\install.wim or source\install.esd, the actual license of either Enterprise Evaluation or Home should work just fine.

    Even if any ISO images were removed at some point, we'll simply go for the official ESD images instead:

    https://pastebin.com/raw/PkGh0CUH

    https://forums.mydigitallife.net/threads/windows-10-esd-repository.59082/#post-992532

    https://forums.mydigitallife.net/threads/windows-11-esd-repository.83747/#post-1688616

    Thanks a lot for sharing extensive list of download links for Windows 10/11 x64 ISO files.

    Indeed Enterprise Evaluation Edition can be used in Make_WinPE to make PE WIM files for booting from RAMDISK.

    For me most testing was done with Professional Edition of Windows 10/11 x64, but it is very nice that I can also test now the Enterprise Evaluation ISO Edition.

    Everything works OK for Enterprise Evaluation of 19041.264 Version in my test as shown in these ScreenShots.

    Win10_Enterpr_Eval_2024-08-20_073702.jpg.1808ae0abbd3a80bb076e4adff0caffc.jpg     WinPE_264_Enterpr_Eval_2024-08-20_075845.thumb.jpg.5c0a37b67aac994bb54c1e58ed710e80.jpg

  12. 15 hours ago, Antonino said:

    hello again, good ol'wimb! long time no c. now pls tell us how to achieve the aboveAdd Drivers and Tweaks, Disable Windows Defender on existing Windows Installation and Windows_To_Go in VHD. could these things not be accomplished in the same way with the previous version of winntsetup?

    Existing Windows Installation can be modified with Additional Drivers and Tweaks by using Setup without having install.wim selected as Installation Source.

    I was not aware of this useful option and the previous version crashed on this point as Sonic mentioned earlier.

  13. Thanks for the very useful option to use Setup without selecting sources install.wim.

    It allows to Add Drivers and Tweaks e.g. Disable Windows Defender on existing Windows Installation e.g. Windows_To_Go in VHD :thumbup

     

×
×
  • Create New...