ChrisPE already uses winpeshl.ini to start the selected shell - and may also contain other entries depending on which scripts/options have been selected in the build. For now you can manually edit this file after successfully completing a build. Edit the file (\ChrisPE.Files\ROOT\Windows\System32\winpeshl.ini) and then use the Post Config > Advanced Options > Inject ALL Files option to add the modified file and any other files manually added to \ChrisPE.Files\ROOT\ to boot.wim. You may want to (re)build an .iso afterwards? Use the Media Creation > Create ISO script and press the small Run Script button to the right of the title bar.
Hello thank you for your help i did not see it in the boot of chrispE montage dism Mount the winpesh.ini is not dand the boot.wim I actually find it in ChrisPE_files \ Root .... thank you I can put my password, and lock chrispE to protect my boot again thank you all
Which tool is used to create portable of packet sniffer / capture tool (wireshark) formerly named (tshark). Example : Enigma Virtualbox or Turbo Studio or others . If turbo studio formerly named Spoon Studio then Which filters were used in security tab to build wireshark protable. Have you made portable yourself or you downloaded that portable via third party . I suggest to use eitherRecovery Environment / Forensic Environment Based Bootable iso rather using Pre Installation Environment & be sure to build RE / FE using Win10 1903 Winre.wim as source os. Winre.wim is there inside directory system32 then recovery of your install.wim indexes of your choice either home or pro or ent .