That is a drawback to WinFE, in that some programs will have limitations unless you can find which missing OS files are missing from the WinFE to copy to the system. Sometimes, including C++ and/or dotnet in the build solves these problems.
Well, I tried the obvious and ran DependencyWalker, and all but two were on the mounted image (comctl32.dll and profuis292ad32.dll); I found and copied the former but had no luck anywhere with the latter. Next stop - C++????
Easy enough to try. Just check the box in WinBuilder. It adds a little meat to the build, but actually is needed to run more varied programs under WinFE.
I guess that's really going to be my next attempt - WinBuilder. I've been building my disks using the AIK-only methodology and installing only those apps that are supposed to be portable (no dependencies, supposedly). Trying to work my way through WinBuilder has been difficult since I can't find a definitive documentation source from which to start; it seems too scattered, with no prerequisites, etc., that I can easily find. Addtionally, there seem to be a lot of assumptions of existing knowledge about the product that I don't (currently) have. Even the compiled help files don't seem to work. I'll continue to dig, but if someone has a "this is what you need, this is where you start, this is how it goes" place for me to begin, I'd really appreciate it. If not, I may end up writing one (somewhere down the road). Once a tech writer, always a tech writer.
Thanks.
Brett, by the way, the "AIK-only methodology" I mentioned earlier is from your excellent guide.
A new and faster/easier WinFE build is available. Less than 5 minutes to create a WinFE iso. http//
If you ever spent more time than you wanted in building WinFE, this one solves that problem. Thanks to Misty at reboot.pro for putting this together.