Creating a BOOTABLE WinPE ISO File of HBS v. 4.9.1

[Fergie86]

Due to circumstances beyond my control, I haven't been able to respond to or to apply Froggie's suggestions, but I managed to find time to try out his suggestions a few minutes ago, and hey presto: they work! 

So, many, many thanks to Froggie (a very intriguing alias, I have to admit); without his expertise I would still be tearing my hair out. ....

incidentally, in finally findinga 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.

In other words, should I again wish to create a new/fresh Bootable WinPE ISO file, it would be necessary to delete this new WinPE.WIM file first, or else I'would be stuck again!

Incidentally, talking about pitfalls or problems: I actually ran into a new one (surprise surprise). So far, I have always created HBS WinPE ISO files by using an OPE file, rather than downloading the WinPE Components from the Microsoft site. So I decided to give this last method a try (always useful to having a few more strings to one's bow ...) . Well, the process of creating WinPE ISO file seemed to work fine, until at the very last moment, when the process was suddenly aborted with the rather cryptic error message:

"Failed to run system API (0x166001500000003)". Does anyone have a clue as to the provenance of this message?

Once more, many, many thanks to Froggie!

[admin]

Due to circumstances beyond my control, I haven't been able to respond to or to apply Froggie's suggestions, but I managed to find time to try out his suggestions a few minutes ago, and hey presto: they work! 

So, many, many thanks to Froggie (a very intriguing alias, I have to admit); without his expertise I would still be tearing my hair out. ....

incidentally, in finally findinga 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.

In other words, should I again wish to create a new/fresh Bootable WinPE ISO file, it would be necessary to delete this new WinPE.WIM file first, or else I'would be stuck again!

Incidentally, talking about pitfalls or problems: I actually ran into a new one (surprise surprise). So far, I have always created HBS WinPE ISO files by using an OPE file, rather than downloading the WinPE Components from the Microsoft site. So I decided to give this last method a try (always useful to having a few more strings to one's bow ...) . Well, the process of creating WinPE ISO file seemed to work fine, until at the very last moment, when the process was suddenly aborted with the rather cryptic error message:

"Failed to run system API (0x166001500000003)". Does anyone have a clue as to the provenance of this message?

Once more, many, many thanks to Froggie!

Regarding the error 0x166001500000003, please click "" > "Save log file" to open the save log file dialog, save the log file and then send it to us via email at [email protected], and we will resolve it as soon as possible. Thanks.

[Froggie]

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.

[Fergie86]

Thanks a lot, Froggie - again! Fantastic what you know about the innards of HBS, quite stunning, really - makes me all the more curious whether you can explain the other problem I encountered when I for a change tried to download the WinPE Components from the Microsoft site, and got the error message: "Failed to run system API (0x166001500000003)"

What could possibly have gone wrong here and where shoud I be looking for an answer/solution? Many thanks in advance!

[admin]

Thanks a lot, Froggie - again! Fantastic what you know about the innards of HBS, quite stunning, really - makes me all the more curious whether you can explain the other problem I encountered when I for a change tried to download the WinPE Components from the Microsoft site, and got the error message: "Failed to run system API (0x166001500000003)"

What could possibly have gone wrong here and where shoud I be looking for an answer/solution? Many thanks in advance!

This error usually means that you have deleted the C:\Program Files\Hasleo\Hasleo Backup Suite\bin\WADK\Windows Preinstallation Environment\amd64\WinPE_OCs folder, and you should delete all the files in that folder instead of deleting the folder.