New
#1331
Please try this version of modify-pese 18.05.23
Last edited by Kyhi; 23 May 2018 at 12:42.
Please try this version of modify-pese 18.05.23
Last edited by Kyhi; 23 May 2018 at 12:42.
My Guess is that the winload file is corrupted during extract or capture by wimlib
You can try mounting the boot.wim with DISM
make your file changes
unmount and commit the changes with DISM
Command Prompt Admin
md C:\Temp\Mount
Note: Copy Boot.wim to C/Temp
Dism /Mount-Image /ImageFile:"C:\Temp\boot.wim" /Index:1 /MountDir:C:\Temp\Mount
Note: Update Program Files in C/Temp/Mount
Dism /Unmount-Image /MountDir:C:\Temp\Mount /Commit
Rename original Boot.wim - Boot.wim.bak
Copy Updated Boot.wim into Sources folder
Last edited by Kyhi; 23 May 2018 at 14:28.
I am booting legacy. VMWare UEFI mode is not booting both modified and the WinPESE original ISO. UEFI boot result on VMWare with unmodified original ISO:
I have uploaded the re-compiled version of the original iso to Google Drive. As I said in my previous post, I used modify-pese 18.05.23, I didn't add or remove any files from the original ISO, and it is giving this error. I don't know what is getting corrupted in the iso: https://drive.google.com/open?id=15N...7V36PIanMDgEQL
When I use dism for mount / unmount and commit, and then re-create iso with "modify-pese 18.05.23" (with option 4), the ISO is booting without a problem.
But when I mount with dism, add some new softwares to the iso, unmount and commit with dism, and then re-create iso with "modify-pese 18.05.23" (with option 4), the iso is giving this error.
This is a very strange problem. I really want to know, when you edit the original x86 winpese wim, add new softwares to it, commit and rebuild the iso, don't you get any errors? Which os, os build and architecture (x32 or x64) are you using on your pc?
Thank you.
You could try doing it manually.
1.Use an isohandler to copy the boot.wim out of the iso.
2. Then use 7-zip gui to add your new program files to the wim. (You can also probably add desktop/startmenu links to your new programs. I use pecmd for that - not sure what KYHI has used.)
3. Use the isohandler to replace boot.wim in the iso and save as something.iso
If you haven't got an isohandler, gburner trial is fully functional for 30 days.
gBurner - A powerful CD, DVD and BD burning software
Last edited by SIW2; 23 May 2018 at 17:43.
If KYHI used winbuilder to make his thing, then my adapted version of pecmd.exe will be in there. If so, you can add links in pecmd.ini.
Example to add desktop link
LINK %Desktop%\Macrium,x:\Program Files\Macrium\Reflect.exe
To add link to startmenu
LINK %StartMenu%\BootTools\BootIce,x:\Program Files\Booticex64.exe
Thank you very much for the informations.
Error re-produce:
- Open boot.wim file with 7zip.
- Export "Program Files" folder located in boot.wim to a temp folder (for example to "C:\WinPE\Program Files").
- Delete "Program Files" folder located in the boot.wim.
- Re-add "C:\WinPE\Program Files" folder into the boot.wim.
- Rebuild the iso with gBurner or with the any other tools.
- The iso fails to boot.
Can you re-produce this problem?
Thank you.
I think I found the solution. When a big data is deleted from the wim and it is re-copied, fragmentation (empty holes) occurs in the wim file. The wim size increases from 1 GB to 1.6 GB after deleting and re-copying the same data.
After modifying the file I did wimoptimize with the command below and now it is working:
wimoptimize boot.wim --recompress
Thank you very much.
Last edited by Makiko; 24 May 2018 at 04:46.
I have another question. Is it possible to update a WinPE version?
Win14393PESE_x86 ISO v170116 seems Windows 10 Version: 1607 - RedStone 1 (Build: 14393 ).
Can I update it to Version: 1803 - RedStone 4 (Build: 17134.1)? If I integrate all windows updates to the wim, will it be Version: 1803?
Thank you.