Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

XPCOM couldn't load; also, MSDMO.dll error

  • 3 답장
  • 109 이 문제를 만남
  • 1 보기
  • 최종 답변자: opalite

more options

I am running on Windows 7 x64, and whenever I try to use a version of Firefox newer than 17.0.1, I get the "couldn't load XPCOM" error, followed by two instances of "FlashPlayerPlugin11_5_502_149.exe - Bad Image: C:\Windows\system32\msdmo.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support."

Then Firefox closes. Every time I try to open it, this happens; it is unusable until I uninstall Firefox, delete the folder in Program Files, and reinstall 17.0.1.

The MSDMO.dll error shows up even in 17.0.1; I'm not sure whether they're related, but in 17.0.1 only one instance of it shows up shortly after I open FF, and then FF works normally.

The MSDMO error has been showing up since sometime last summer, but doesn't seem to interfere with much.

I am running on Windows 7 x64, and whenever I try to use a version of Firefox newer than 17.0.1, I get the "couldn't load XPCOM" error, followed by two instances of "FlashPlayerPlugin11_5_502_149.exe - Bad Image: C:\Windows\system32\msdmo.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support." Then Firefox closes. Every time I try to open it, this happens; it is unusable until I uninstall Firefox, delete the folder in Program Files, and reinstall 17.0.1. The MSDMO.dll error shows up even in 17.0.1; I'm not sure whether they're related, but in 17.0.1 only one instance of it shows up shortly after I open FF, and then FF works normally. The MSDMO error has been showing up since sometime last summer, but doesn't seem to interfere with much.

모든 댓글 (3)

more options

Certain Firefox problems can be solved by performing a Clean reinstall. This means you remove Firefox program files and then reinstall Firefox. Please follow these steps:

Note: You might want to print these steps or view them in another browser.

  1. Download the latest Desktop version of Firefox from http://www.mozilla.org and save the setup file to your computer.
  2. After the download finishes, close all Firefox windows (click Exit from the Firefox or File menu).
  3. Delete the Firefox installation folder, which is located in one of these locations, by default:
    • Windows:
      • C:\Program Files\Mozilla Firefox
      • C:\Program Files (x86)\Mozilla Firefox
    • Mac: Delete Firefox from the Applications folder.
    • Linux: If you installed Firefox with the distro-based package manager, you should use the same way to uninstall it - see Install Firefox on Linux. If you downloaded and installed the binary package from the Firefox download page, simply remove the folder firefox in your home directory.
  4. Now, go ahead and reinstall Firefox:
    1. Double-click the downloaded installation file and go through the steps of the installation wizard.
    2. Once the wizard is finished, choose to directly open Firefox after clicking the Finish button.

Please report back to see if this helped you!

more options

You can use the System File Checker to check if font files are missing or corrupted.

Open a cmd.exe window as Administrator:
Start, click Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

After the cmd.exe prompt, type: sfc.exe /scannow

System Files - SFC Command - Vista Forums:

more options
  • I ran the System File Checker; it says msdmo.dll is corrupt and can't be fixed because the source file in store is also corrupt.
  • I think that I was actually wrong about the MSDMO and XPCOM errors being related; they're probably just showing up at the same time. The MSDMO error routinely shows up when I load the website imo.im, and I usually have a pinned tab of that site. So although the msdmo error is irritating and confusing, it is probably not actually tied to the xpcom error.
  • I'm still tooling around with the clean install, but so far it isn't working at all. I've also tried installing in an entirely different folder; no luck there, either.

글쓴이 opalite 수정일시