X
Tap here to go to the mobile version of the site.

Support Forum

on Win10 firefox ESR 52.8.0 does not run profile manager and goes straight to the browser ( need to use -no-remote -P )

Posted

5/2018 - win10 pro, version 1703.15063.786

win-key-R: firefox.exe -P, -p or -ProfileManager, does not run profile Manager, but starts the browser.

firefox.exe is located under: C:\Users\USER_NAME\AppData\Local\Mozilla Firefox\firefox.exe

I tried opening cmd prompt at the above location ( C:\Users\USER_NAME\AppData\Local\Mozilla Firefox\ )

 to run firefox.exe by hand and all supported firefox switches only result in the browser starting.I

I'll try searching the registry for firefox.exe and see if anything is there.

Warmest Regards, Robert

5/2018 - win10 pro, version 1703.15063.786 win-key-R: firefox.exe -P, -p or -ProfileManager, does not run profile Manager, but starts the browser. firefox.exe is located under: C:\Users\USER_NAME\AppData\Local\Mozilla Firefox\firefox.exe I tried opening cmd prompt at the above location ( C:\Users\USER_NAME\AppData\Local\Mozilla Firefox\ ) to run firefox.exe by hand and all supported firefox switches only result in the browser starting.I I'll try searching the registry for firefox.exe and see if anything is there. Warmest Regards, Robert

Modified by Robertwho

Chosen solution

Maybe do a desktop shortcut to the Firefox.exe and add the -P

Also one little mistake people do is try to start Firefox with the ProfileManager while Firefox is already running. It just opens up a new window instead. To run a second Firefox instance you would need the -no-remote switch and -P and start with a separate Profile.

https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Read this answer in context 0

Additional System Details

Installed Plug-ins

  • Shockwave Flash 28.0 r0

Application

  • Firefox 52.8.0
  • User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
  • Support URL: https://support.mozilla.org/1/firefox/52.8.0/WINNT/en-US/

Extensions

  • Application Update Service Helper 2.0 (aushelper@mozilla.org)
  • Cisco WebEx Extension 1.0.15 (ciscowebexstart1@cisco.com)
  • Clip to OneNote 5.0.1-signed.1-signed ({966762eb-7132-4081-ac70-20d20161ad96})
  • Flashblock 1.5.20 ({3d7eb24f-2740-49df-8937-200b1cc08f8a})
  • Multi-process staged rollout 1.10 (e10srollout@mozilla.org)
  • Pocket 1.0.5 (firefox@getpocket.com)
  • Privacy Badger 2018.4.23 (jid1-MnnxcxisBPnSXQ@jetpack)
  • uBlock Origin 1.16.0 (uBlock0@raymondhill.net)
  • Web Compat 1.0 (webcompat@mozilla.org)

Javascript

  • incrementalGCEnabled: True

Graphics

  • adapterDescription: Intel(R) HD Graphics 520
  • adapterDescription2:
  • adapterDeviceID: 0x1916
  • adapterDeviceID2:
  • adapterDrivers: igdumdim64 igd10iumd64 igd10iumd64 igd12umd64 igdumdim32 igd10iumd32 igd10iumd32 igd12umd32
  • adapterDrivers2:
  • adapterRAM: Unknown
  • adapterRAM2:
  • adapterSubsysID: 505117aa
  • adapterSubsysID2:
  • adapterVendorID: 0x8086
  • adapterVendorID2:
  • crashGuards: []
  • currentAudioBackend: wasapi
  • direct2DEnabled: True
  • directWriteEnabled: True
  • directWriteVersion: 10.0.15063.674
  • driverDate: 9-26-2017
  • driverDate2:
  • driverVersion: 22.20.16.4815
  • driverVersion2:
  • failures: [u'CP+[GFX1]: Potential driver version mismatch ignored due to missing DLLs 0.0.0.0 and 0.0.0.0', u'CP+[GFX1]: Potential driver version mismatch ignored due to missing DLLs 0.0.0.0 and 0.0.0.0', u'CP+[GFX1]: Potential driver version mismatch ignored due to missing DLLs 0.0.0.0 and 0.0.0.0', u'CP+[GFX1]: Potential driver version mismatch ignored due to missing DLLs 0.0.0.0 and 0.0.0.0']
  • featureLog: {u'fallbacks': [], u'features': [{u'status': u'available', u'description': u'Compositing', u'name': u'HW_COMPOSITING', u'log': [{u'status': u'available', u'type': u'default'}]}, {u'status': u'available', u'description': u'Direct3D11 Compositing', u'name': u'D3D11_COMPOSITING', u'log': [{u'status': u'available', u'type': u'default'}]}, {u'status': u'disabled', u'description': u'Direct3D9 Compositing', u'name': u'D3D9_COMPOSITING', u'log': [{u'status': u'disabled', u'message': u'Disabled by default', u'type': u'default'}]}, {u'status': u'available', u'description': u'Direct2D', u'name': u'DIRECT2D', u'log': [{u'status': u'available', u'type': u'default'}]}, {u'status': u'available', u'description': u'Direct3D11 hardware ANGLE', u'name': u'D3D11_HW_ANGLE', u'log': [{u'status': u'available', u'type': u'default'}]}]}
  • indices: [0, 1, 2, 3]
  • info: {u'AzureCanvasAccelerated': 0, u'AzureCanvasBackend': u'direct2d 1.1', u'AzureFallbackCanvasBackend': u'cairo', u'AzureContentBackend': u'direct2d 1.1'}
  • isGPU2Active: False
  • numAcceleratedWindows: 9
  • numTotalWindows: 9
  • supportsHardwareH264: Yes; Using D3D11 API
  • webgl2Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics 520 Direct3D11 vs_5_0 ps_5_0)
  • webglRenderer: Google Inc. -- ANGLE (Intel(R) HD Graphics 520 Direct3D11 vs_5_0 ps_5_0)
  • windowLayerManagerRemote: True
  • windowLayerManagerType: Direct3D 11

Modified Preferences

Misc

  • User JS: No
  • Accessibility: No
FredMcD
  • Top 10 Contributor
4271 solutions 59913 answers

Robertwho said

firefox.exe is located under: C:\Users\USER_NAME\AppData\Local\Mozilla Firefox\firefox.exe

Firefox.exe should be located in the Programs Folder. Please verify your information. +++++++++++++++++++++++++++++++++++++++++++ If you can't get the browser to open from the command line, Type about:profiles<enter> in the address bar.

''Robertwho [[#question-1217308|said]]'' <blockquote> firefox.exe is located under: C:\Users\USER_NAME\AppData\Local\Mozilla Firefox\firefox.exe </blockquote> Firefox.exe should be located in the Programs Folder. Please verify your information. +++++++++++++++++++++++++++++++++++++++++++ If you can't get the browser to open from the command line, Type '''about:profiles'''<enter> in the address bar.

Question owner

It has worked from this location C:\Users\USER_NAME\AppData\Local\Mozilla Firefox\firefox.exe for the past three weeks, so I'm guessing that corpIT has setup the run from path to be login based.

I rather check the oil before pulling the transmission out...

and as it's rapidly approaching 3pm on a Friday, I'm not about to break my firefox.

Robert

It has worked from this location C:\Users\USER_NAME\AppData\Local\Mozilla Firefox\firefox.exe for the past three weeks, so I'm guessing that corpIT has setup the run from path to be login based. I rather check the oil before pulling the transmission out... and as it's rapidly approaching 3pm on a Friday, I'm not about to break my firefox. Robert
GµårÐïåñ 5 solutions 65 answers

Sometimes in corporate environment, they load them as slim apps and control all (or most) of the settings via a policy that gets reset on each login, I have seen this done in several environments that I have encountered, there are some tricks you can do but could violate company policy, so you might want to check with your IT Admins and check and see how or if, they allow some user specific changes to be done so you can have a bit more control.

Sometimes in corporate environment, they load them as slim apps and control all (or most) of the settings via a policy that gets reset on each login, I have seen this done in several environments that I have encountered, there are some tricks you can do but could violate company policy, so you might want to check with your IT Admins and check and see how or if, they allow some user specific changes to be done so you can have a bit more control.

Question owner

let me test about:profile ....

let me test about:profile ....
James
  • Top 25 Contributor
  • Moderator
1602 solutions 11345 answers

Chosen Solution

Maybe do a desktop shortcut to the Firefox.exe and add the -P

Also one little mistake people do is try to start Firefox with the ProfileManager while Firefox is already running. It just opens up a new window instead. To run a second Firefox instance you would need the -no-remote switch and -P and start with a separate Profile.

https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Maybe do a desktop shortcut to the Firefox.exe and add the -P Also one little mistake people do is try to start Firefox with the ProfileManager while Firefox is already running. It just opens up a new window instead. To run a second Firefox instance you would need the '''-no-remote''' switch and -P and start with a separate Profile. https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Modified by James

Question owner

I think the installation path my be related to that it's FF ESR so ff does not collide with the other version of FF.

I think the installation path my be related to that it's FF ESR so ff does not collide with the other version of FF.

Question owner

firefox.exe -no-remote -P works - thanks for the fast response...

Warmest Regards, Robert

firefox.exe -no-remote -P works - thanks for the fast response... Warmest Regards, Robert

Question owner

note about:profile --> launch different profile fails to use -no-remote from the webpage and affects the current running FF instance's profile. ( Uggh !!! ) BUG...

note about:profile --> launch different profile fails to use -no-remote from the webpage and affects the current running FF instance's profile. ( Uggh !!! ) BUG...
James
  • Top 25 Contributor
  • Moderator
1602 solutions 11345 answers

The -no-remote switch is only used if you want to run a second instance of Firefox while a version of Firefox is already running. Forgot to mention that it should not be used with your default Profile.

The -no-remote switch is only used if you want to run a second instance of Firefox while a version of Firefox is already running. Forgot to mention that it should not be used with your default Profile.

Modified by James