Bdlog.txt In C:\ ?
Comments
-
Hi
Please pack that file in archive with the password infected and send me a PM with it.
If the file is too big to attach it, upload it on
or
and send me a PM with the download link.
We will analyze the information you sent and then reply with a possible solution in the shortest time.
Have a nice day.0 -
Hi,
it's just a normal log file that is generated every time the machine boot_s. There's nothing "infected" about it. It's annoying, because BD puts it in the root of the C drive. This should, if it really needs to be generated, go somewhere else, like in the BD program folder.
On my laptop it contains:2012-02-26 18:53:13.218 PROFILE [Midas stop] [0ms]
2012-02-26 18:53:13.218 PROFILE [stopProxies] [0ms]
2012-02-26 18:53:13.468 PROFILE [stop Drivers] [248ms]
2012-02-26 18:53:13.468 PROFILE [unload html] [0ms]
2012-02-26 18:53:13.468 PROFILE [Registration data] [0ms]
2012-02-26 18:53:13.468 PROFILE [NPCOMM_MSG_VSSERVDOWN NPC_BDAGENT_MAIN] [0ms]
2012-02-26 18:53:13.468 PROFILE [GM unload] [0ms]
2012-02-26 18:53:13.468 PROFILE [Vulner uninit] [0ms]
2012-02-26 18:53:13.468 PROFILE [Parental uninit] [0ms]
2012-02-26 18:53:13.468 PROFILE [WSACleanup] [0ms]
2012-02-26 18:53:13.468 PROFILE [Free SF] [12ms]
2012-02-26 18:53:13.468 PROFILE [uninitializeMultiUserSupport] [0ms]
2012-02-26 18:53:13.468 PROFILE [AntiPh & AS unload] [0ms]
2012-02-26 18:53:13.468 PROFILE [LogUnInit] [0ms]
2012-02-26 18:53:16.697 PROFILE [CM Stop & eventq uninit] [3s:216ms]
2012-02-26 18:53:16.697 PROFILE [npcomm uninit] [0ms]
2012-02-26 18:53:16.697 PROFILE [sTOP Received - time] [3s:479ms]
On my desktop, after deleting the current file and rebooting, it contains:2012-02-27 16:12:14.216 PROFILE [Midas stop] [0ms]
2012-02-27 16:12:14.216 PROFILE [stopProxies] [0ms]
2012-02-27 16:12:14.450 PROFILE [stop Drivers] [233ms]
2012-02-27 16:12:14.450 PROFILE [unload html] [0ms]
2012-02-27 16:12:14.450 PROFILE [Registration data] [0ms]
2012-02-27 16:12:14.450 PROFILE [NPCOMM_MSG_VSSERVDOWN NPC_BDAGENT_MAIN] [0ms]
2012-02-27 16:12:14.450 PROFILE [GM unload] [0ms]
2012-02-27 16:12:14.450 PROFILE [Vulner uninit] [6ms]
2012-02-27 16:12:14.450 PROFILE [Parental uninit] [0ms]
2012-02-27 16:12:14.450 PROFILE [WSACleanup] [0ms]
2012-02-27 16:12:14.450 PROFILE [Free SF] [0ms]
2012-02-27 16:12:14.450 PROFILE [uninitializeMultiUserSupport] [0ms]
2012-02-27 16:12:14.450 PROFILE [AntiPh & AS unload] [0ms]
2012-02-27 16:12:14.450 PROFILE [LogUnInit] [0ms]
2012-02-27 16:12:15.823 PROFILE [CM Stop & eventq uninit] [1s:364ms]
2012-02-27 16:12:15.823 PROFILE [npcomm uninit] [0ms]
2012-02-27 16:12:15.823 PROFILE [sTOP Received - time] [1s:607ms]
Please talk to your developers about this. It's annoying and really not to be expected of a well-designed program. Log files should go into a log folder in the program directory, IMHO.
Any updates regarding this much appreciated.0 -
Hello
Thank you for your feedback.
I will forward your request about this and if it will be approved, the location of that log will be changed (probably C:\Program Files\Bitdefender).
Take care.0 -
Hello
Thank you for your feedback.
I will forward your request about this and if it will be approved, the location of that log will be changed (probably C:\Program Files\Bitdefender).
Take care.
Please do and please also read posts more carefully in the future before replying with a standard reply. I think it should have been clear from my first post that there wasn't some unknown infection in place but a simple log file.
And yes, please let the developers know that IMHO it's not good practice to dump log files in the root of the drive.0 -
Hello
I have read carefully all your posts from this topic.
The password "infected" is a standard in the security industry when we need files from customers, even if they are clean or files from our product(that contain settings).
Thank you.0 -
I have the same file created. Is this normal operation then and nothing I need to be concerned about?
0 -
Hello
Yes, this behavior is normal. This file is created by our product in that location.
Don't' worry about it.
Take care.0 -
Hello
Yes, this behavior is normal. This file is created by our product in that location.
Don't' worry about it.
Take care.
Still exists a year later? This is very dissaponiting... a year and a half is more than enough time to fix this0 -
Yup cant stand it actually canned Bit-defender cause I was sick of looking at it !
0 -
I too have this log file created on my SSD, Writing to a SSD Shoddy work bitdefender.
0 -
Is this thing still not fixed after 3 years? I just installed the BitDefender Internet Security 2015 and got the same files at the root of the disk. It does it on my SSD, and I do not like it.
Though it could be a bug, as I deleted them and they did not reappear after this.
Anyone from BitDefender mind shed some light on it?
Thanks!0 -
Though it could be a bug, as I deleted them and they did not reappear after this.
The file does reappear next time you restart your pc.
0 -
I've got the same txt file sitting in the root of my C drive. Wondering what the it was, my search ended here.... looks like 7 years still isn't enough time for BitDefender to adjust their software to have this log located in a more appropriate location. That's to bad. This is the first time I've ever purchased a anti-virus program instead of using random free ones. My though process behind this was better safety and better customer service. The inability to fix this almost decade old complaint from their customers, as minor as it seems, is rather concerning.1 -
The first email in this chain is dated 2012. Now it's September 2020 and the issue is no different. Obviously the developers are in no hurry about fixing this.
0
