Discussion in 'other anti-virus software' started by haakon, Sep 21, 2016.
I wish they would get the widget and excessive CPU usage fixed! That's been reported weeks ago!
With my computer it is solved. There was a update and then it was ok.
Both?? I still don't have my widget working
According to a BD forum member post 2017 was updated to 126.96.36.1997 with another user reporting the widget issue has been resolved.
No other details as of yet.
Thanks, I'll check when I get home.
I installed another trial on my Windows 10 1151 x64 test system.
The Widget is now OK.
And the firewall Paranoid mode issues I and some other BD forum members reported is resolved.
Can't comment on the excessive CPU use as I never experienced that.
That one was supposed to be fixed yes
In a departure from a near life-long convention of total purge of a previous version, I decided to use the resident BD Repair or Uninstall tool and selected "to install a different version."
I then ran the trial setup stub bitdefender_isecurity.exe and watched. Cold sweat. White knuckles...
Installed, updated (188.8.131.528 > 967) and activated with the remaining 221 days from my 2016 license with no other interaction but one click of a restart button.
Windows 7 HP SP1 x64
Initially released as 184.108.40.2068, the first maintenance upgrade to BS 2107 is 220.127.116.117.
Changelog, source BD Forum:
Is there any way to get Bitdefender's GUI starting up right after Windows startup and not after few minutes (default behavior)? It's quite annoying and I'm not getting purpose of this "feature".
No on the right after Windows startup. See posts #20-25 on page one of this thread.
You can open the GUI from the Start menu or the desktop icon.
Bitdefender Agent (productagentservice.exe) updated from v18.104.22.168 to v22.214.171.124.
Active Threat Control injectors avcuf32.dll & avcuf64.dll updated from v3.12.15080.6445 to v3.12.15976.6498.
The previous avcuf versions arrived on 07/14 for BD 2016 so this is the first injector update since the release of BD 2017.
FYI: Note that the ATC engine and components continue to use the Active Virus Control naming convention, most likely in perpetuity.
Some components updated to resolve a Firewall Error dialogue encountered during manual rule creation via ADD RULE which appeared when IS and TS was upgraded to 21.0.21967 last week, 10/27.
(Temporary workaround was to set Paranoid mode and run the program and allow or block as necessary and edit rule if needed.)
Updated from 126.96.36.1997 to 188.8.131.526
No changelog yet published.
The most notable changes logged/observed:
Bitdefender Security Service (vsserv.exe) upgraded from 184.108.40.2068 to 220.127.116.116.
Wallet Agent (bdwtxag.exe) upgraded from 18.104.22.1681 to 22.214.171.1246.
Quarantine Core (quarcore.dll)
Files Shield (vshield.dll)
Plugin Container (bdplugin_sc.dll)
Ransomware Protection Console Plugin (bdrwpsp.dll)
Antivirus Plugin (antivirus.dll)
Antiphishing Plugin (bdaphconp.dll)
I have just been updated to the latest version of bitdefender
I am using Bitdefender Antivirus plus 2017 with max settings in windows 10 pro AU. I disabled SSL scanning and wallet extension in firefox. Now I can use sandboxie with firefox 64bit. Everything is fine and runs light. Looking for a simple firewall that will alert for outbound connections but with no HIPS. I am thinking of trying tinywall or windows firewall control.
Source: BD Forum, posted today by Sorin G.
Is anyone having launching issues with Discord while using BD 2017?
Updated from 126.96.36.1996 to 188.8.131.521
Source: BD Forum, Sorin G.
Perhaps one of you BD super-users can answer a few questions for me.
I am testing compatibility between AppGuard's User Space policies and Bitdefender for our users.
Does anyone know if Bitdefender routinely updates from C:\Windows\Temp\bc_*\*.tmp ? Is the .tmp file for signature updates, module updates or both ?
The installer of the above executes from C:\Users\User\AppData\Local\Temp\*\installer.exe. I am not sure if the * part of the file path is randomly created.
BITDEFENDER BLACK GRAY FRIDAY...
I got one each of these in my BD Central account.
Hmmmmm. $31.99? $15.99? Decisions. Decisions.
My current IS license expires in April next year and I wasn't considering renewal until about then, but I can't pass up $15.99.
Especially since the current license (2016 & free upgraded to 2017) was snagged at $19.99 when a free 6-month license expired.
So $0.04 US a day. $0.02 each for my tower and laptop. It's almost free.
I think your question might be best answered in an AppGuard thread/forum.
I've been using BD personally and in the enterprise for well over a decade and never had reason to investigate that behavior.
Professionally, I always had user-base test systems and on my own systems I always offload TEMP and TMP user and system variables to a non-system partition.
Separate names with a comma.