Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

Avatar for Username

חיפוש בתמיכה

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.

מידע נוסף

אשכול זה הועבר לארכיון. נא לשאול שאלה חדשה אם יש לך צורך בעזרה.

Belgium eID 1.0.16 extension is responsible for d3d9window message

  • 2 תגובות
  • 6 have this problem
  • 4 views
  • תגובה אחרונה מאת 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

כל התגובות (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.