Up until this Win10 build, you could always setup portableapps as a default app using:
HKEY_LOCAL_MACHINE\SOFTWARE\Clients
or
HKEY_LOCAL_MACHINE\SOFTWARE\
And also adding their registry key path here
HKEY_LOCAL_MACHINE\SOFTWARE\RegisteredApplications
Then you needed the standard
HKEY_CLASSES_ROOT\
and HKEY_CLASSES_ROOT\
Ex.
HKEY_CLASSES_ROOT\FirefoxMAFF
HKEY_CLASSES_ROOT\FirefoxMHTML
HKEY_CLASSES_ROOT\FirefoxPortableHTML
HKEY_CLASSES_ROOT\FirefoxPortableURL
HKEY_CLASSES_ROOT\FirefoxPortable
HKEY_LOCAL_MACHINE\SOFTWARE\RegisteredApplications
Firefox Portable RegSz Software\Clients\StartMenuInternet\FirefoxPortable\Capabilities
HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\FirefoxPortable
With the example above, you only had to setup the portableapp like any other app for registering as a default handler. No longer will they register. You can use the Default Apps program builtin to Windows to associate an extension/protocol though to get make a portableapp default, but it will no longer showup in Win 10 interface to be a choice. (If you are using this method, it's best to scroll to the bottom and ONLY choose the htm protocol, not the .htm extension above, and definitely not url or the extension .url "IF" you browser hop alot -- leave those default)
Anyone know a new way or am I alone on this one? Using Firefox/Cyberfox/Waterfox "The Foxes" browser as the portable version along with logging into Mozilla.org, you have *Fox always exactly how you left it, with Mozilla.org providing backup redundancy. I NEED this!! Buuuut, I also browser hop too, so.... lol