You may cancel your Bitdefender subscription from Bitdefender Central or by contacting Customer Support at: https://www.bitdefender.com/consumer/support/help/
Thank you for your understanding.
Bdts 2016 Security Center Won't Open After Upgrade
After doing a Windows 10 upgrade and waiting for a few hours, I got the notice there was a new version of Bitdefender Total Security available. It apparently included an upgrade from BDTS 2015 to 2016 BDTS. It didn't ask me if I wanted to upgrade to 2016, but even if it had asked, I would have let it upgrade to 2016.
The result mostly works except for the Security Center which fails to open. I've attached a file with several event log error events. They are all more or less the same.
Error 9/17/2015 8:15:48 PM Application Error 1000 (100)
Faulting application name: seccenter.exe, version: 20.0.18.1034, time stamp: 0x55f0552a
Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f83ff
Exception code: 0xc0000409
Fault offset: 0x0000000000074a30
Faulting process id: 0x1bb8
Faulting application start time: 0x01d0f1a72adc89fc
Faulting application path: C:\Program Files\Bitdefender\Bitdefender 2016\seccenter.exe
Faulting module path: C:\Program Files\Bitdefender\Bitdefender 2016\MSVCR120.dll
Report Id: 466a029e-2a29-41d1-a0a2-c6cf4b4686c5
Faulting package full name:
Faulting package-relative application ID:
Log Name: Application
Source: Application Error
Date: 9/17/2015 8:15:48 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ...PII deleted...
Description:
Faulting application name: seccenter.exe, version: 20.0.18.1034, time stamp: 0x55f0552a
Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f83ff
Exception code: 0xc0000409
Fault offset: 0x0000000000074a30
Faulting process id: 0x1bb8
Faulting application start time: 0x01d0f1a72adc89fc
Faulting application path: C:\Program Files\Bitdefender\Bitdefender 2016\seccenter.exe
Faulting module path: C:\Program Files\Bitdefender\Bitdefender 2016\MSVCR120.dll
Report Id: 466a029e-2a29-41d1-a0a2-c6cf4b4686c5
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-09-18T00:15:48.000000000Z" />
<EventRecordID>2211</EventRecordID>
<Channel>Application</Channel>
<Computer>...PII deleted...</Computer>
<Security />
</System>
<EventData>
<Data>seccenter.exe</Data>
<Data>20.0.18.1034</Data>
<Data>55f0552a</Data>
<Data>MSVCR120.dll</Data>
<Data>12.0.21005.1</Data>
<Data>524f83ff</Data>
<Data>c0000409</Data>
<Data>0000000000074a30</Data>
<Data>1bb8</Data>
<Data>01d0f1a72adc89fc</Data>
<Data>C:\Program Files\Bitdefender\Bitdefender 2016\seccenter.exe</Data>
<Data>C:\Program Files\Bitdefender\Bitdefender 2016\MSVCR120.dll</Data>
<Data>466a029e-2a29-41d1-a0a2-c6cf4b4686c5</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
I also get random BSODs including:
KMODE_EXCEPTION_NOT_HANDLED
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
KERNEL_SECURITY_CHECK_FAILURE
These did not occur before the upgrade. They didn't start occurring until after several uninstall/resinstall/repair attempts were made on BDTS 2016. This may or may not be BDTS 2016.
This is the third computer I've upgraded to Windows 10. Only one of the other two has Bitdefender on it, but when I upgraded it, it stayed at BDTS 2015 - though it was an upgraded version (19.2.0.151). That machine was not having the issues this latest upgraded one had, so I uninstalled Bitdefender Total Security 2016 and installed Bitdefender Total Security 2015 on this machine. So far, no errors, the Security Center opens as expected and there have been no BSODs yet. (Too early to call that last one though.)
Comments
-
Almost forgot. When I went to Bitdefender Central with BDTS 2016 installed, there was a white on gray INSTALL BITDEFENDER button. The other two PCs I have Bitdefender on (one Windows 10 and one Windows 8.1) no longer show up under My Devices.
After uninstalling BDTS 2016 and installing BDTS 2015 in its place, Bitdefender Central claims that Protection [is] not installed.
I beg to differ.
0 -
Doesn't it make you all warm and fuzzy inside seeing the 'Your Are Protected' sign? Its is just as well these ****** kiddies aren't responsible for looking after anything precious of mine or has any value in money and time terms.....
0 -
After doing a Windows 10 upgrade and waiting for a few hours, I got the notice there was a new version of Bitdefender Total Security available. It apparently included an upgrade from BDTS 2015 to 2016 BDTS. It didn't ask me if I wanted to upgrade to 2016, but even if it had asked, I would have let it upgrade to 2016.
The result mostly works except for the Security Center which fails to open. I've attached a file with several event log error events. They are all more or less the same.Error 9/17/2015 8:15:48 PM Application Error 1000 (100)
Faulting application name: seccenter.exe, version: 20.0.18.1034, time stamp: 0x55f0552a
Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f83ff
Exception code: 0xc0000409
Fault offset: 0x0000000000074a30
Faulting process id: 0x1bb8
Faulting application start time: 0x01d0f1a72adc89fc
Faulting application path: C:\Program Files\Bitdefender\Bitdefender 2016\seccenter.exe
Faulting module path: C:\Program Files\Bitdefender\Bitdefender 2016\MSVCR120.dll
Report Id: 466a029e-2a29-41d1-a0a2-c6cf4b4686c5
Faulting package full name:
Faulting package-relative application ID:
Log Name: Application
Source: Application Error
Date: 9/17/2015 8:15:48 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ...PII deleted...
Description:
Faulting application name: seccenter.exe, version: 20.0.18.1034, time stamp: 0x55f0552a
Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f83ff
Exception code: 0xc0000409
Fault offset: 0x0000000000074a30
Faulting process id: 0x1bb8
Faulting application start time: 0x01d0f1a72adc89fc
Faulting application path: C:\Program Files\Bitdefender\Bitdefender 2016\seccenter.exe
Faulting module path: C:\Program Files\Bitdefender\Bitdefender 2016\MSVCR120.dll
Report Id: 466a029e-2a29-41d1-a0a2-c6cf4b4686c5
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-09-18T00:15:48.000000000Z" />
<EventRecordID>2211</EventRecordID>
<Channel>Application</Channel>
<Computer>...PII deleted...</Computer>
<Security />
</System>
<EventData>
<Data>seccenter.exe</Data>
<Data>20.0.18.1034</Data>
<Data>55f0552a</Data>
<Data>MSVCR120.dll</Data>
<Data>12.0.21005.1</Data>
<Data>524f83ff</Data>
<Data>c0000409</Data>
<Data>0000000000074a30</Data>
<Data>1bb8</Data>
<Data>01d0f1a72adc89fc</Data>
<Data>C:\Program Files\Bitdefender\Bitdefender 2016\seccenter.exe</Data>
<Data>C:\Program Files\Bitdefender\Bitdefender 2016\MSVCR120.dll</Data>
<Data>466a029e-2a29-41d1-a0a2-c6cf4b4686c5</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
I also get random BSODs including:
KMODE_EXCEPTION_NOT_HANDLED
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
KERNEL_SECURITY_CHECK_FAILURE
These did not occur before the upgrade. They didn't start occurring until after several uninstall/resinstall/repair attempts were made on BDTS 2016. This may or may not be BDTS 2016.
This is the third computer I've upgraded to Windows 10. Only one of the other two has Bitdefender on it, but when I upgraded it, it stayed at BDTS 2015 - though it was an upgraded version (19.2.0.151). That machine was not having the issues this latest upgraded one had, so I uninstalled Bitdefender Total Security 2016 and installed Bitdefender Total Security 2015 on this machine. So far, no errors, the Security Center opens as expected and there have been no BSODs yet. (Too early to call that last one though.)
I undergo exactly the same issue. I raised a ticket to the Bitdefender Support Team: 2015112421560001
I hope they will find something soon !0
