Constant Start-up Problem With Bd V10
Newbie here. I'm always having problems with BD V10 not starting up. I have BD installed on 2 notebooks along with Spy Sweeper. On my HP DV9000 BD works perfectly but on my HP DV8000 BD won't start up when I turn the computer on and I have to reboot the computer 5 out of 10 times to turn BD on. It always turns on when I reboot but this is a hassle and I can't figure out what the problem is. BD is updated and does update fine when it does turn on. Grateful for any input? Thanks
Comments
-
Hello farefinta,
I'm extremely sorry for the very late response.
This issue was discussed before on this forum. It's a high possibility that BitDefender does start everytime, but it cannot create the tray icon because of some Windows XP bugs regarding this. BitDefender is not the only application that has this problem (I experienced this issue about other few applications).
In simple words: sometimes, in certain conditions, the Windows shell process (Explorer.exe) stops responding for a few moments when the computer starts. This can happen because of multiple reasons:
- it looks for an IP (in case your IP is dinamically allocated by a DHCP server)
- it scans the network for computers, printers and other such services
- some application that you set to start with Windows freezes for a few moments
- etc...
As I said, this is more a Windows problem than a BitDefender problem, because when these freezes occur, the applications that try to create the tray icons will fail (because Explorer.exe is responsable for managing the tray icons).
You cannot do anything to fix this. What you can do, is to restart the applications that fail to create the icons, in this case, BitDefender. So open TaskManager, find the process bdmcon.exe and kill it. After that, restart the process from the shortcut on your Desktop, or from StartMenu.
Take note that this process is only related to the BitDefender interface. The actual protection is separated from this, and it won't be stopped by killing bdmcon.exe.
Please post if this fixes the issue.
Cris.0