Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Will only run in Widows Safe mode

  • 16 Mbohovái
  • 1 oguereko ko apañuái
  • 4 Hecha
  • Mbohovái ipaháva Bonecrusher

more options

New Firefox opens but will not connect, no error messages, and will not open "options". However if I boot to W7 "Safe Mode" runs OK. No problems with Internet Explorer or old Firefox.

New Firefox opens but will not connect, no error messages, and will not open "options". However if I boot to W7 "Safe Mode" runs OK. No problems with Internet Explorer or old Firefox.

Ñemoĩporã poravopyre

i see that bitdefender and trusster rapport are hooking into the process - perhaps two security tools at the same time are conflicting?

Emoñe’ẽ ko mbohavái ejeregua reheve 👍 1

Opaite Mbohovái (16)

more options

hi, do you have any particular third-party software in use that might interfere with firefox?

perhaps running a scan with different security tools like adwcleaner & eset online one-time scanner would be a good idea too.

more options

No third party I know of. AV is Bitdefender, and disable does not fix problem. As mentioned, problem hit with 57, 56 worked OK. I also tried 32 bit Firefox 57, since 56 was 32. No luck.

more options

could you try to trigger a manual crash and submit the report - maybe that can provide any clues if a particular third-party is hooking into the browser process for example. go to https://ftp.mozilla.org/pub/utilities/crashfirefox-intentionally/ and download crashfirefox.exe (or the 64 variant if you're running 57.0 64-bit), submit the report, and then go to about:crashes to catch the id of the submitted report (starting with bp-) to share this with us.

thank you

more options

Thanks, Can't do at this time. Will d/l that link and try tomorrow.

more options

I ran the crash, and submitted the report with the pop-up box, IDed with my email address. I cannot find a copy on my drive. Firefox would not go to "about:crashes", or to about anything. The freeze is on any address entry.

Moambuepyre Bonecrusher rupive

more options

If you submitted the report via the Mozilla Crash Reporter pop-up window, there are .txt files with crash report IDs in your profile folder.

  1. On the keyboard, press [Windows] The image "Windows key" does not exist. + [R]. This should bring up a Run window that contains a text field.
  2. In that text field, type %APPDATA% and press Enter. An explorer window should open.
  3. From that explorer window, double-click on the Mozilla folder, then double-click on Firefox and then on Crash reports. Double-click on submitted.
  4. Now, you should see a list of files that contain reports. Go to View > Arrange Icons by > Modified to get the most recent files at the top of the window.
  5. Open the most recent 5 files with a text editor and copy the IDs.
  6. Paste each ID with bp- into the reply window on the forums.
more options

Crash ID: bp-ced0b155-8770-4469-99b7-2046c0171117 Crash ID: bp-cfca528b-9eb8-4ea5-9c9b-412c81170913 Crash ID: bp-23e93f20-7690-440d-8f58-aa75b1170823 These are only crash reports 2017

more options

thank you - can you please try to remove/disable malwarebytes anti-exploit and see if this can make a difference?

more options

Disable Malwarebytes did not correct problem. About a year ago I made a change in advanced options. I do not remember what, was widely promoted to fix problem at that time. Is there a way to restore options to default?

more options

yes, a firefox refresh would set everything back to the default: Refresh Firefox - reset add-ons and settings

more options

Did not fix problem. I removed Malwarebytes from start list, rebooted, confirmed not running in app mgr. Firefox opened, but would not connect. I ran crash. Crash report:Crash ID: bp-072f205e-d000-4835-852f-0ddd30171117

more options

Ñemoĩporã poravopyre

i see that bitdefender and trusster rapport are hooking into the process - perhaps two security tools at the same time are conflicting?

more options

Problem solved, shut down Trusteer end-point protection and runs OK.

more options

great, thanks for reporting back - which version # of trusteer was running on your machine?

more options

Emerald Build 1307.111 is Trusteer version. I don't do anything with it, I think it was put in by some bank, probably Vectra, long ago.

more options

Emerald Build 1804.161 Has been issued by Trusteer, fixes problem. Would think they would send automaticly. After seeing many negative comments on net, have removed Trusteer. It appears to be a resource hog, and does not give level of protection greater than current AV packages. Thank You Mozzilians, outstanding help on an obscure problem.

Moambuepyre Bonecrusher rupive