If you only checked download from Microsoft.com and not the use the off-line WinPE option, the resultant winpe.iso (located in Hasleo's "bin" folder)will be built from Microsoft's downloaded WinPE offering (after the download) not the offline WinPE option.
To use the offline winpe option you must have the previously mentioned OPE file resident (somewhere on your System) before you do the build. This may be done by using Hasleo's OffLine WinPE download page HERE. Once you have it present, then you can build the offline version of the recovery media.
The WinPE OffLine file (.OPE) is used during the build (just like it would use the downloaded Microsoft option or the WinRE option) and stored where Hasleo stores all the rest of its build results. Since newly installed versions remove the legacy stored stuff, all new versions will require a build using that OPE file once again. If you're producing new recovery media without changing the HBS installed media, then any new recovery media will be the same as the one 1st created after a new install.
One of the main reasons I use the OPE installation is because only 1-download is required and the result is stored on your System for Hasleo to use when building a fresh recovery media (using the OffLine option). Currently Hasleo forces users to re-ADD their BOOT media when installing new versions. If doing so, that process will build a new reference "winpe.iso" for the Hasleo "bin" folder. That file will be the result of how you do the build... WinRE, downloaded WinPE or use offline WinPE.
As far as Certificate compliance is concerned, Hasleo is best at answering this question. On your LIVE System, they talk of 2011 being removed and 2023 added. If this is how 2023 is implemented then only the 2023 version of Hasleo will work after the installation and cert removal. I have seen discussions when users have added the 2023 entry but not removed the 2011 entry... this should allow both to work under SECURE BOOT. Personally, I never engaged SECURE BOOT. The problems it created in the early days with both Windows and Linux (which I also use) were not worth worrying about the risk of running my Systems without SEURE BOOT.
To use the offline winpe option you must have the previously mentioned OPE file resident (somewhere on your System) before you do the build. This may be done by using Hasleo's OffLine WinPE download page HERE. Once you have it present, then you can build the offline version of the recovery media.
The WinPE OffLine file (.OPE) is used during the build (just like it would use the downloaded Microsoft option or the WinRE option) and stored where Hasleo stores all the rest of its build results. Since newly installed versions remove the legacy stored stuff, all new versions will require a build using that OPE file once again. If you're producing new recovery media without changing the HBS installed media, then any new recovery media will be the same as the one 1st created after a new install.
One of the main reasons I use the OPE installation is because only 1-download is required and the result is stored on your System for Hasleo to use when building a fresh recovery media (using the OffLine option). Currently Hasleo forces users to re-ADD their BOOT media when installing new versions. If doing so, that process will build a new reference "winpe.iso" for the Hasleo "bin" folder. That file will be the result of how you do the build... WinRE, downloaded WinPE or use offline WinPE.
As far as Certificate compliance is concerned, Hasleo is best at answering this question. On your LIVE System, they talk of 2011 being removed and 2023 added. If this is how 2023 is implemented then only the 2023 version of Hasleo will work after the installation and cert removal. I have seen discussions when users have added the 2023 entry but not removed the 2011 entry... this should allow both to work under SECURE BOOT. Personally, I never engaged SECURE BOOT. The problems it created in the early days with both Windows and Linux (which I also use) were not worth worrying about the risk of running my Systems without SEURE BOOT.