Bitdefender icon disappearing
brucine Posted messages 24411 Registration date Status Membre Last intervention -
Hello friends,
For the past week, I have been experiencing the following problem (see image)
the Bitdefender icon randomly disappears. It is useful as it allows for updates, displays the widget, etc.
Not finding any solution to get the little icon back, I reinstall Bitdefender each time. Well, it's not too heavy since the reinstallation only takes about ten minutes, but it remains frustrating. Being a "customer" with Bitdefender since 2018, in the older versions, it was simpler because everything was possible by opening the program, but today, you have to right-click on this small icon to access certain functions.
Could anyone help me?
Thank you in advance.
1 réponse
Hello,
You can right-click on your desktop > New > Shortcut (.LNK)
Target: C:\Windows\explorer.exe shell:::{05d7b0f4-2121-4eff-bf6b-ed3f69b894d9}
Try with the new shortcut, and a restart after to Always show the icon.
PS: Sometimes I have the same issue with the Comodo icon, but not the others.
Maybe you should contact Bitdefender and Comodo about this.
It's not normal that only their programs are missing.
Thank you for your response,
But I believe we are not understanding each other. I have no issue creating a new icon on the desktop, but it is the icon in the taskbar that disappears, and, as I mentioned in my previous message, this icon is essential because it allows certain operations that are not possible through the interface when the program is opened.
Thanks again,
Click on the new shortcut created, you'll understand what I mean...
Hello,
Note that you can access the same thing via Control Panel-Taskbar-Notification area-select.
Regarding Comodo, it doesn't prevent the icon from disappearing every now and then (nor from being able to use all its functions by "starting" the software, which is already running in the background).
As for BitDefender, I don't know if the functions are accessible through the executable (bdagent.exe); it has been reported (though it wouldn't be random) that it is intentionally launched by a scheduled task at startup with a delay to avoid consuming too many resources.