Firefox version 68 will only open if "Run As Administrator".
Several users within our company are unable to use Firefox after the last update to version 68. Firefox will only open if "Run as Administrator" is selected. No error comes up. When clicking on it, nothing happens.
Below is what I have tried so far but have had no luck: 1. Uninstalling/reinstalling 2. Tried installing the ESR version. 3. Refreshed Firefox 4. Created a new profile.
None of the above solutions have worked. With that being said, each employee's laptop has 2 user accounts. There is an administrator account and the actual user account. The user's account does not have admin rights. Users that do have admin rights such as the IT staff, Firefox is working fine with version 68 (so far).
The users affected have either Windows 8/8.1 or Windows 10.
Any other suggestions would be greatly appreciated.
Thanks in advance!
Keazen oplossing
Firefox 68.0.1 has just been released.
Dit antwurd yn kontekst lêze 👍 0Alle antwurden (5)
hello, can you take a look in the system's eventlog if any related entries are showing up there once you attempt to start firefox?
I looked at the event log for one of the users (I'm assuming it will be the same for each person with this issue).
Below is the info that was returned. I also attached a screenshot of the application error.
Log Name: Application Source: Windows Error Reporting Date: 7/15/2019 10:58:48 AM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: Christy-HP Description: Fault bucket 2065814814549578549, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0
Problem signature: P1: firefox.exe P2: 68.0.0.7125 P3: 5d1fddd0 P4: sxwmon64.dll P5: 5.1.451.0 P6: 5af5705b P7: c0000005 P8: 000000000004814a P9: P10:
Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCEE0.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFDB.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFEB.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFE9.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD009.tmp.txt
These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_firefox.exe_8a8b20bfe26ed892800c36a53fa81914f8564ff_6049dfbe_269fd160
Analysis symbol: Rechecking for solution: 0 Report Id: 2e9ba1d5-454b-4341-8e2c-f25d218f20b6 Report Status: 268435456 Hashed bucket: 5f27698962ba67f40cab3fa0f0f79335 Cab Guid: 0 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-07-15T14:58:48.859766200Z" /> <EventRecordID>101147</EventRecordID> <Channel>Application</Channel> <Computer>Christy-HP</Computer> <Security /> </System> <EventData> <Data>2065814814549578549</Data> <Data>4</Data> <Data>APPCRASH</Data> <Data>Not available</Data> <Data>0</Data> <Data>firefox.exe</Data> <Data>68.0.0.7125</Data> <Data>5d1fddd0</Data> <Data>sxwmon64.dll</Data> <Data>5.1.451.0</Data> <Data>5af5705b</Data> <Data>c0000005</Data> <Data>000000000004814a</Data> <Data> </Data> <Data> </Data> <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCEE0.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFDB.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFEB.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFE9.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD009.tmp.txt</Data>
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_firefox.exe_8a8b20bfe26ed892800c36a53fa81914f8564ff_6049dfbe_269fd160</Data> <Data> </Data> <Data>0</Data> <Data>2e9ba1d5-454b-4341-8e2c-f25d218f20b6</Data> <Data>268435456</Data> <Data>5f27698962ba67f40cab3fa0f0f79335</Data> <Data>0</Data> </EventData>
</Event>
thank you. so it appears that your enterprise security software is attempting to hook into firefox and crashing it this way. we're tracking this in https://bugzilla.mozilla.org/show_bug.cgi?id=1553776 and the next firefox update (due to happen in the next couple of days) should contain a mitigation against this...
Thanks for the quick response. That's good to know. We will wait for the next update.
Keazen oplossing
Firefox 68.0.1 has just been released.