Xoferif said

Is 69.0.3497.81 profilemanager bugged?

To open ProfileManager from a windows shortcut, the 'target' is 
"C:\Program Files\Mozilla Firefox\firefox.exe" -P -no-remote

With FF not running: 
-P opens ProfileManger
-P "profilename" opens ProfileManger

With FF running: 
-P opens a new instance.
-no-remote -P opens ProfileManager
-no-remote -P "notopenedprofilename" opens ProfileManger
-no-remote -P "openedprofilename" says FF is not responding

FF is not not responding.  Bug?

This forum mangles the posters text... maybe that's whats wrong with the code?

In the case that Firefox is running, was Firefox with or without the -no-remote switch ?

Initially FF was run with only -p <profile name>

I closed all the windows, then used only -no-remote to open both profiles. It worked.