We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Wątek został zarchiwizowany. Jeśli potrzebujesz pomocy, zadaj nowe pytanie.

Belgium eID 1.0.16 extension is responsible for d3d9window message

  • 2 odpowiedzi
  • 6 osób ma ten problem
  • 2 wyświetlenia
  • Ostatnia odpowiedź od 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

Wszystkie odpowiedzi (2)

ideato
ideato
more options

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

tomvdp
tomvdp Zadający pytanie
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.