Open GoogleCodeExporter opened 9 years ago
the issue is reproducable even with the latest version of the dokan library
Original comment by jan.bier...@googlemail.com
on 21 Mar 2013 at 6:18
Whats the procedure to bump the priority of this? Get more people to vote for
it?
As it stands, anyone, & I repeat, anyone, using Bitdefender 2013 Antivirus or
Internet Security, cannot run XVM without causing a Blue Screen. The only way
to use xvm in this case is a total uninstall of Bitdefender 2013 (there was no
issue with the 2012 version), as just turning Bitdefender off, excluding
xvm+dokan files, anything else, doesn't work.
Support at Bitdefender have washed their hands of the problem claiming its an
issue from this end, regardless if its the case or not.
Can we get an ETA?
Thanks.
Original comment by deadpro...@gmail.com
on 12 Jun 2013 at 4:45
I have the same problem with XVM and Bitdefender. If I had known about it
earlier I wouldn't have bought Bitdefender.
Original comment by bavarian...@gmail.com
on 22 Jun 2013 at 11:38
I am also getting this issue everytime, with the same steps as above. I cant
use xvm/dokan libraries with bitdefender 2014.
Original comment by Edward.F...@3pillarglobal.com
on 2 Jul 2013 at 5:29
Same here, please help
Original comment by vidic.i...@gmail.com
on 4 Aug 2013 at 9:05
BD say they are releasing an update end of august to fix this issue. After
getting very little help from them i have started using g data internet
security, and my issue is gone. I will report back then when i retry the setup
with BD.
Overall customer support from BD is not helpful on this issue that everyone
seems to have.
Original comment by Edward.F...@3pillarglobal.com
on 5 Aug 2013 at 12:35
Any news on this subject? I have opened a ticket on august 31st on this matter,
haven't received an answer yet from Bitdefender.
Original comment by sun....@concepteers.de
on 2 Sep 2013 at 10:21
Same error with also Bitdefender 2014
If i uninstall bitdefender, the problem is solved.
Original comment by croto...@gmail.com
on 3 Sep 2013 at 11:45
Original issue reported on code.google.com by
jan.bier...@googlemail.com
on 15 Mar 2013 at 10:39Attachments: