Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Natao arisiva ity resaka mitohy ity. Mametraha fanontaniana azafady raha mila fanampiana.

How do I get rid of this plugin container.exe.? It's driving me crazy.

more options

Whenever I try to open something in Firefox I get a window which says

Program:c\program files\Mozilla Firefox\plugin-container-exe. R6034. Microsoft visual C ++ Runtime Library. It is difficult to get rid of the box because it keeps returning. How do I get rid of it. Also my lap top runs so slowly now I'm at risk of dying of old age before it gets going.

Whenever I try to open something in Firefox I get a window which says Program:c\program files\Mozilla Firefox\plugin-container-exe. R6034. Microsoft visual C ++ Runtime Library. It is difficult to get rid of the box because it keeps returning. How do I get rid of it. Also my lap top runs so slowly now I'm at risk of dying of old age before it gets going.

All Replies (1)

more options

When a page uses a plugin, Firefox isolates that by running it in a separate program named plugin-container.exe. Are you having this problem on all pages, or is there any pattern? For example, if you start Firefox with a blank page, is that problem free?

To do that test, use the Start menu search box or Run command:

firefox.exe "about:blank"

Then try a page that you know uses Flash, such as Adobe's about page:

https://www.adobe.com/software/flash/about/

To restore your previous session (if you like), you then can use History > Restore Previous Session.

Did any of that trigger the error?