This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Belgium eID 1.0.16 extension is responsible for d3d9window message

  • 2 replies
  • 6 have this problem
  • 2 views
  • Last reply by tomvdp

tomvdp
tomvdp
more options

Because I have spend hours looking for a solution and finally found it, I thought I would share it here so others with a the same problem may find this.

After installing the necessary addon for the Belgian Taxonweb application, the Belgium eID extension, Firefox did not close anymore. Well the window closed, but the process remained active. When shutting down a message stated that a D3D9Window was still active.

After disabling the Belgium eID extension, all troubles went away...

Firefox 13.0.1 on XP sp2

Because I have spend hours looking for a solution and finally found it, I thought I would share it here so others with a the same problem may find this. After installing the necessary addon for the Belgian Taxonweb application, the Belgium eID extension, Firefox did not close anymore. Well the window closed, but the process remained active. When shutting down a message stated that a D3D9Window was still active. After disabling the Belgium eID extension, all troubles went away... Firefox 13.0.1 on XP sp2

All Replies (2)

ideato
ideato
more options

tomvdp, thanks for sharing your solution for your problem with us.

tomvdp
tomvdp Question owner
more options

To complete this: merely disabling the extension is not enough. I had to completely uninstall the Belgium eID application. Even starting Firefox in safemode resulted in the same problematic behaviour.