Este site está com funcionalidades limitadas enquanto realizamos manutenção para melhorar sua experiência de uso. Se nenhum artigo resolver seu problema e você quiser fazer uma pergunta, nossa comunidade de suporte pode te ajudar em @FirefoxSupport no Twitter e /r/firefox no Reddit.

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Belgium eID 1.0.16 extension is responsible for d3d9window message

  • 2 respostas
  • 6 têm este problema
  • 4 visualizações
  • Última resposta de 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

Todas as respostas (2)

more options

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

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.