1315539 - Firefox Developer Edition (Windows 64-bit version, 6 November 2016) fails to start (couldn't load XPCOM) on Windows 10 Pro, build 14393

Status: RESOLVED DUPLICATE of bug 1315530

(Firefox :: Untriaged, defect)

Description

[bf2006a]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:49.0) Gecko/20100101 Firefox/49.0
Build ID: 20161019084923

Steps to reproduce:

I performed my usual daily update of Firefox Developer Edition on the morning of 6 November 2016.  Following the update, the browser failed to start, displaying a pop-up with the error message "Couldn't load XPCOM."  The same happened after a system reboot.  I removed the Developer Edition, and then reinstalled it, but received the same error message.  This had not happened before on this machine with the Developer Edition, which had been successfully updated the previous day.  The Developer Edition has been updated and the machine rebooted several times since the last updates to the operating system.  Firefox 49.0.2 functions normally on the same system.


Actual results:

The browser failed to start, displaying only a pop-up window with the error message "Couldn't load XPCOM." After each attempt, the System Event log displayed a new error of the following form:

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          11/6/2016 10:20:10 AM
Event ID:      10016
Task Category: None
Level:         Error
Keywords:      Classic
User:          SYSTEM
Computer:      ***
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="0">10016</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2016-11-06T15:20:10.439010100Z" />
    <EventRecordID>9754</EventRecordID>
    <Correlation />
    <Execution ProcessID="760" ThreadID="2020" />
    <Channel>System</Channel>
    <Computer>***</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="param1">application-specific</Data>
    <Data Name="param2">Local</Data>
    <Data Name="param3">Activation</Data>
    <Data Name="param4">{D63B10C5-BB46-4990-A94F-E40B9D520160}</Data>
    <Data Name="param5">{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}</Data>
    <Data Name="param6">NT AUTHORITY</Data>
    <Data Name="param7">SYSTEM</Data>
    <Data Name="param8">S-1-5-18</Data>
    <Data Name="param9">LocalHost (Using LRPC)</Data>
    <Data Name="param10">Unavailable</Data>
    <Data Name="param11">Unavailable</Data>
  </EventData>
</Event>


Expected results:

The Firefox Developer Edition browser should have started and functioned normally.

Comment 1

[TMart]

It broke for me on two computers with Windows 10, too, with todays update.