BUG - External hard drives won't eject with Bitdefender


Bitdefender is preventing me from ejecting a USB mass storage device.  This was not a problem before the 2019 upgrade.  How do I fix this.


The application \Device\HarddiskVolume3\Program Files\Bitdefender\Bitdefender Security\vsserv.exe with process id 2020 stopped the removal or ejection for the device USB\VID_1058&PID_1020\574343315535353138343230202020.

Tagged:
«1345

Comments


  • It shouldn't be scanning anything because I have it set to "ask every time" and it didn't ask.


     


  • Hi, 


     


    Is the USB device plugged in when the computer starts? 



  • 8 hours ago, Sergiu C. said:



    Is the USB device plugged in when the computer starts? 



    Normally no.  But I may have rebooted with the device (external hard drive) attached.  Don't remember for sure now.


  • I tested this a little more.


    If I have Scan-Flash-Drives set to Disabled, then Bitdefender doesn't cause any trouble.


    If I have Scan-Flash-Drives set to Ask-Every-Time, then when I plug in a USB hard drive Bitdefender doesn't ask to scan, but then Bitdefender also prevents ejection of the USB hard drive.

  • Jay-ZJay-Z
    edited September 2018


    I'm having this same exact issue and I disabled scanning everything under the Drives and Devices tab. This started on 9-3-18 at 8:15 pm according to the event logs.  Anything I connect to my computer through USB will not stop blinking and the only way I can remove the devices is to shutdown my computer and remove them!  None of my externals are connected to my computer at startup!  I manually connect them as needed and used!  I've tried 4 different External Hard Drives at every USB port on my computer and Thumb Drives as well and none of them will Safely Remove via the windows process.  I figured I'd check the event log and see if any flags came up.  This is what showed up in my latest attempt in the event log:


     


    The application \Device\HarddiskVolume2\Program Files\Bitdefender\Bitdefender Security\vsserv.exe with process id 884 stopped the removal or ejection for the device USB\VID_0BC2&PID_3322\NA8X70T8.


     


    I'm running Windows 7 64-Bit and I have the most current version of Internet Security 2019 installed!  This never caused a problem for me in the past and I just renewed for my 2nd year using your software!  Any help would be greatly appreciated!  Thanks and all the Best!!!


  • I can confirm this too.


  • Hi, 


     


    The issue has been reported to our development team. Thank you. 


  • Hi


    For me it seems to happen when the drive has a recycle bin, and so Windows treats like a fixed drive. Cannot figure how to change this for a drive. 


    Cheers!


  • I am having the same problem as Jay-Z...Every device I connect to a USB port just blinks constantly non stop.  This started after the upgrade to BD Total Security 2019.  This issue makes keeping my external USB Hard Drive connected a concern as I do not know if this is causing the drive any harm.


    Please fix this issue as soon as possible.


    Thank you.


  • After doing some research and I found a Windows 10 work around to stop BDTS 2019 from causing anything connected to USB to continually blink.


    Open "Service.exe" find "Windows Management Instrumentation" and "Right Click" on the service and select "Restart"...wait for the process to finish and close "Services.exe"


    The connected blinking USB devices should stop blinking and work as usual.  You will however have to preform this procedure the next time you restart Windows 10 but it does work until then.  Hope this helps some people until they find a permanent fix for this issue.  Good Luck


     

    Screenshot (35).png


  • I have had the same issue since the update in the beginning of September. If I try to eject a USB drive it says it's in use on both my Windows 7 system and Windows 10 system, both are running Bit Defender Total Security 2019. If I disable Bit Defender I have no issues. It's September 12th... when is this getting fixed?


     


     



  • 17 hours ago, street_lethal said:



    I have had the same issue since the update in the beginning of September. If I try to eject a USB drive it says it's in use on both my Windows 7 system and Windows 10 system, both are running Bit Defender Total Security 2019. If I disable Bit Defender I have no issues. It's September 12th... when is this getting fixed?


     


     



    Same issue here, which is quite annoying.


    This behaviour prevents my scanner to save files on a usb-stick - so I have to to shut down the computer to use the scanner *argh*.


    The tipp from above works too: Start a command prompt "cmd" (as admin) and type "net stop winmgmt" and then "net start winmgmt". So this problem is solved until next reboot...


    I made a ticket as I didn't find the issue on the german forum. Now I look forward for a solution!

  • edited September 2018


    Restarting Windows Management Instrumentation doesn't fix the issue on Windows 7. I tried it.


     


    Edit, I tried it again and it did work this time.


     


    It would be nice if they just fixed the issue.


  • A Note to Developers


    I think the problem is you are detecting which drives are fixed without testing whether they are USB removable drives. (Some removable drives have the DRIVE_FIXED bit set in hardware).


    You then set up file handles to monitor the drive so preventing their release.


    You will find the following useful


    https://stackoverflow.com/questions/1665969/c-sharp-getdrives-with-type-fixed-but-without-usb-harddisks


    Hope that helps



  • 10 hours ago, Moggy said:



    A Note to Developers


    I think the problem is you are detecting which drives are fixed without testing whether they are USB removable drives. (Some removable drives have the DRIVE_FIXED bit set in hardware).


    You then set up file handles to monitor the drive so preventing their release.


    You will find the following useful


    https://stackoverflow.com/questions/1665969/c-sharp-getdrives-with-type-fixed-but-without-usb-harddisks


    Hope that helps



    This is neither a problem, nor a solution, in current situation BD is setting up a handles to the roots of all partitions at startup and never releases them.. So detecting USB drives would only be a cover up for much bigger problem. Imagine having 2 drives, main SSD for system and additional HDD for files that you use rather rarely, like once per day. In this type of situation you would want HDD to be working only when you're using it, right? You rather should... because the hdd drive spinning all the time is slowly killing itself without any reason, and with BD it happens even if it's completly empty.. Previously you was able to disable the drive in the system to prevent this, but now it's not possible. As you can see nobody cares about "details" like this.

    Reason is probably very simple and it's sometimes called "lazy programming", devs are getting a task, they're lazy so they do it "the easy way" which means that they only care about the result and "verified/closed" response from testers. I would bet a lot, that devs implementing this, knew from the beginning how it will be working, but some of them simply don't care about stuff like that, their task is closed, if there will be some issues reported then probably somebody else will have to deal with it. I'm a dev too, sadly I know a lot about this kind of "developers",  you will encounter them in every IT company. And sadly this is my last year with BD, I'm tired of this problems that other products somehow don't have...


    And BTW, the solution with restarting winmgmt will not work for everyone (me included)..

  • edited September 2018


    I've moved on as well to a different security arrangement because the current BD is unlivable when hotplug discs, USB disks, and flashdrives are used frequently.  I liked BD but this issue is a killer for me on all my systems.  


    I submitted a support ticket on this around 3-Sept and it still is not fixed.  That is pretty slow support response IMO <_<


  • Support...Do we have any kind of ETA on a fix for this issue?


    Thank you in advance.



  • 15 hours ago, SageWolf said:



    Support...Do we have any kind of ETA on a fix for this issue?


    Thank you in advance.



    They know about it for at least a year (main problem with handles) and they made it even worse in BD 2019, so you can expect some changes in BD 2020 :D (flip a ###, they can fix it or make it even worse once again)


    Or the other option: fix will be ready in a few hours when some big website (or youtuber) will point this out in a review.


  • If this problem is not solved quickly then is BD exit for me <img class=" data-emoticon="" src="https://us.v-cdn.net/6031943/uploads/ipb_attachments/emoticons/default_angry.png" title=":angry:" />


  • The same bug here on Windows 10. Bitdefender knows it 07/09/2018 (see item from Bitdefender here above) and no solution on 22/09/2018. Version 2019 is full of bugs.


  • I made a support ticket with a detailed description.


    The first response told me, how to eject a usb stick using windows!!! Arrrgh...


    So I wrote again and added even videos of this strange behaviour... Now I'm waiting!


    I'll inform about the answer - if there will be one.


    This makes BD almost not usable and they should think about a refund or extend the subscription!


  • Bonjour


    Même problème chez moi depuis la mise à jour vers Bitdefeder 2019.


    Impossible d'éjecter "proprement" un disque externe USB. Communication incessante entre Bitdefender et le disque.


    J’ai 2 licences de 5 postes, essentiellement utilisés par des personnes âgées et/ou non geek. Elles sont en panique. Je leur ai même demandé de fermer le PC avant de débrancher leur disque dur externe de sauvegarde. (Je n’ose pas imaginer le crash d’un disque où est stocké leur vie …)


    Après mise à jour vers 2019 + Un-Install + Re-Install 2019,  je confirme que c’est bien Bitdefender 2019 qui est bugé. (Des tentatives de changement du setup n’ont rien fait)


    Je suis client Bitdefender depuis près de 10 ans et c’est la première fois que j’ai un doute concernant ce produit. J’avoue qu’il est sidérant qu’une telle marque n’ait pas résolu ce problème depuis début Septembre 2018


    Ce problème est un problème majeur car il peut aller jusqu’à la destruction de disque contenant des informations importantes.


    A l’équipe Bitdefender …. Faite vite car sinon vous allez perdre des clients.


  • Very sorry. Just realizing that I am on an English forum


    All in all, same concern on my side. This is unnacceptable as this concern was raised beginning of the month, can générate HDD crash and is still not fixed.


    To Bitdefender team : You better fix this asap because if not your are going to lose customers.  


  • i have the same Problem since weeks!!!


    59,95€ for your Buggy Software!!!!


    very Bad Support!!!


    When will you fixed the Problem?


  • Same problem here. Why does it take BD-devs so many weeks to solve this issue.


    Is there a way to revert to BD 2018 and prevent auto updating to BD 2019? My license is valid for another 832 days :( 

  • edited September 2018


    EDIT


    Wrong post



  • On 9/18/2018 at 7:16 PM, SageWolf said:



    Support...Do we have any kind of ETA on a fix for this issue?


    Thank you in advance.



    Unfortunately no ETA at this time, though the issue is considered a high priority one. 


  • They are spending weeks doing nothing to resolve this simple and stupid issue and locking us all in past our 30 days so we can't get a refund!  Maybe by Christmas it will be fixed at this rate!!!

  • EJSEJS
    edited September 2018


    8 hours ago, Sergiu C. said:



    Unfortunately no ETA at this time, though the issue is considered a high priority one. 



    We are paid customers, so we want to have at least an option to go back to the older version, wich was working ok.


    This version $#@^%, it already demoledged one of my USB harddrives !!!! <img class=" data-emoticon="" src="https://us.v-cdn.net/6031943/uploads/ipb_attachments/emoticons/default_angry.png" title=":angry:" /> <img class=" data-emoticon="" src="https://us.v-cdn.net/6031943/uploads/ipb_attachments/emoticons/default_angry.png" title=":angry:" />

This discussion has been closed.