On several Win7 Systems all Firefox Crash at start. Also in safe-mode.. Resetting to Default also doesn´t solve the Problem.
thanks for following up with us!從原來的回覆中察看解決方案 👍 1
In the address bar, type about:crashes<enter>. Note: If any reports do not have BP in front of the numbers/letters, click it to submit them.
The crash report is several pages of data. We need the report numbers to see the whole report.
Using your mouse, mark the most resent 7 - 10 crash reports, and copy them. Now go to the reply box below and paste them in.
(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)
Product Firefox Release Channel esr Version 38.6.0esr Build ID 20160120213330 OS Windows 7 OS Version 6.1.7601 Service Pack 1
sysfer.dll = Symantec CMC Firewall
IPSEng32.dll = Symantec Intrusion Detection
Download the current full installers for your Norton programs and save them.
After rebooting the computer, run a registry scanner. Then run the installers.
hi.. i disabled symnatec completly and same Thing happens..
we are just testing latest rapid pattern updates if they solve the Problem.
hi, another affected user at https://support.mozilla.org/en-US/questions/1138691 confirmed that the issue was caused by a signature update of norton.
we have just installed the latest rapid pattern updates for Symantec Endpoint Protection 12.1.6 MP5 . It Dates back to 12.09.2016 Release 31 and the problem is still there.. still looking at it... I updates the esr release on one Workstation to latest Version and the problem has gone.
i think old esr release and actual pattern files triggers the problem.. new esr and actual pattern files doesn´t have the Problem..
just opened a case with symantec.. will update on this shortly..
We did a rollback of the IPS Signatures to 09.09.2016 .. Seems to solve the problem at the Moment...
Response from Symantec: Advise the affected customers to update their IPS content to Seq: 160912013 (September 12th, 2016 rev. 13 to resolve the issue)
seems to work now...
thanks for following up with us!