(09-05-2024, 08:08 PM)Fergie86 Wrote: incidentally, in finally finding a solution to this problem, I almost immediately stumbled upon another, or rather, upon a new pitfall. Once I had applied Froggie's tips, I immediately created a new/fresh Bootable WinPE ISO file with HBS, and it worked a treat. But a note of caution: apparently the building process each time creates a new WinPE.WIM file in the folder C:\Program Files\Hasleo Backup Suite\bin/WADK\Windows Preinstallation Environment\amd64. And so my old problem would return.
@Fergie86, there really isn't an "old problem" that returns. Let me try and explain...
When you build your 1st Emergency Disk (ED), Hasleo needs to get a hold of either the currently released Microsoft.com building blocks or Hasleo's OPE file... both are the same version of the basic WinPE build (version 2004). So it doesn't really matter which one you use to make an ED... once you have the building blocks (Microsoft.com or OPE), Hasleo builds a "vanilla" WinPE (prior to adding what it needs for its WinPE) and leaves that built vanilla WIM in the /amd64 folder for any future use in ED building. The only reason they offer the OPE option is to keep you from having a lengthy download from Microsoft.com, if the building blocks don't currently exist, in case you need to build a new ED. What this means is one you have built the "vanilla" WIM you don't need to do it anymore unless MicroSloth changes its reference WIM... which for Hasleo's needs, hasn't been done for 4-years (remember, version 2004 <April 2020>). It will continue to work well into the future. Again, once the reference is built, no more downloads or OPE access is required.
So now we have a vanilla WinPE build, Hasleo takes that and adds all the software needed to produce a Hasleo WinPE.iso that winds up in the \bin folder... that is a modified vanilla WinPE that now contains all the needed Hasleo stuff for BOOTing functionality and is now a real ED configuration. Hasleo uses that for ED building (UFD or ISO) and doing a LIVE restoration of a locked partition (OS partition mostly).
So you can see, at this point, Hasleo has its vanilla WinPE.wim reference in its \amd64 folder. If any additional EDs are needed, it uses that reference (or the WinPE.iso in the \bin folder, if available) for building and won't ask anymore for either a Microsoft.com or OPE availability. That's why we needed to DELETE all that stuff above to make it build anew once again (using downloads or OPE... definitely not always needed at all). You can produce new EDs at will without any other stuff... it will all be resident in the Hasleo installation when you need it.
Be aware, after any uninstall/install or update/upgrade, all the above references will disappear... the next ED build will require some sort of download/OPE access to rebuild everything once again... the OPE, if you use it, will eliminate any Microsoft.com download time which can be significant in some cases. Hope the above "mini tome" makes all this a little bit easier to understand.