Portable App Development

Error picture

Hello,
since Bart.S can no more work on creating MuseScore 3.x PortableApp (because Windows XP support was dropped by the underlying Qt infrastructure), I tried to step in and automatize the creation of the PortableApp for MuseScore future releases.
I think I managed to find and modify all the parts in the code which lead to saving files in user or system data folders and redirect them to the PortableApp folder. However, I still have a problem with Qt registry keys.

The above mentioned programs do not work on Windows PE.

They complain of missing DLLs.

Other apps (ex: Audacity) work fine.

Shouldn't a portableapp not require any other files except for those included in its folder?

My proposed portable app is written in c++ and is compiled with mingw32. I wrote and have full control of the source code.

At present all of the apps program, dependencies and data are in one directory. It works fine, even on a mac or Linux under wine. It is fully portable in that if you copy all of the files to any folder or usb stick the app still works OK.

mingw32 looks for its dependencies either in the same directory as the .exe or on the Windows PATH. How do I make it look in the App/Appname for these dependencies without altering the PATH?

I created TeamSpeakPortable and I don't know why but when I launch TeamSpeak 3.3.0 via the launcher (TeamSpeakPortable.exe) It didn't launch, its just opening (TeamSpeakPortable.exe) himself and self destruc (I checked in Process Hacker). The only thing that work for me is to change the compability of the application and put it 'Launch as admin' to the executable and add RunAsAdmin=force into the launcher.ini and then its decide to launch. But if I launch the executable ts3client_win32.exe directly it dosn't need admin permission to not self destruc.

why are x86 used when x64 versions exist in the official portable apps, so far ive found qbittorrent is x86 although a x64 version does exist, also irfanview, sumatra, filezilla and teamviewer are also 32-bit. I personally will have to install these apps or make my own portables before I use the x86 versions when there are better alternatives.
Lately many of the major software developers are dropping support for defunct 32 bit applications, just curious why these are even used here, maybe there should be a choice between both?

Some good news for Portable app lovers! Fortunately, running multiple versions of an app has been made simple by us: we derive portability from an app through the same thumb-drive. It is worth mentioning here that in doing so, the integrity of the Windows registry remains uncompromised!

Well, I've got some VST plugins with installers that unpack DLLs into my plugins folder, but these plugins store their data in user folder.
I'd like to make portable versions of them, but I don't know how. They don't have any EXEs, only DLLs.

When I am creating a new app in the Portableapps.com Format I extract this archive PortableApps.com_Application_Template_3.5.2.zip for begining the work. But when I create a new icon for the app and rename it appicon.ico and delete the old one it is reverting for the AppName one (with the arrow)... But only the preview become the logo of Portableapps and when I change a parent folder name's; it is becoming the real logo preview. Its like windows or something else keep a link to this file when I extract the file.

I have seen it's possible "force" an application to use a folder instead another...

How have I to set launcher's parameters for avoid the movement from portable folder to Appdata folder?

I have a folder Data/MyApp that must works like in AppData/Roaming/MyApp.

Thanks.

Where can I find tutorial documentation etc?