BUG - Constant disk read/write while Bitdefender is installed

2456

Comments

  • komturkomtur ✭✭
    edited October 2018


    I think this is because "our" fix (winmgmt restart) was performed with "fast start" on. Probably "fast start" stores a lot of settings, so when the computer was turned on again , the Bitdefender's state was the same as after the fix was made. When the fast start option is turned off, the computer performs a cold start every time -  all settings are "reset", so the fix with the service restart stops working...

  • edited October 2018


    I found an easier "workaround". Instead of stopping/starting the service (and all the dependent services), we can instead pause and resume the management service like this:


    @echo off

    net pause Winmgmt

    net continue Winmgmt


    This method does not depend on if you have IA storage or some other controller.


    I hope a fix will get released soon because it is very annoying.

  • BDAlexSBDAlexS
    edited October 2018


    1 hour ago, komtur said:



    I think this is because "our" fix (winmgmt restart) was performed with "fast start" on. Probably "fast start" stores a lot of settings, so when the computer was turned on again , the Bitdefender's state was the same as after the fix was made. When the fast start option is turned off, the computer performs a cold start every time -  all settings are "reset", so the fix with the service restart stops working...



    Not sure what you mean.


    Fast start caches your most frequently used applications and processes so they start first with windows. A process needs to be running all of the time however to monitor what apps and processes are most frequently used, so they can be cached first (from the users activity). My theory is that BD may have been chasing this process.


    It doesn't make any sense to me that there would be an issue with fast start off. Of course I may simply be supplying a red herring and it's for nothing to do with fast start.

  • komturkomtur ✭✭
    edited October 2018


    23 minutes ago, BDAlexS said:



    Fast start caches your most frequently used applications and processes so they start first with windows.


    It doesn't make any sense to me that there would be an issue with fast start off. Of course I may simply be supplying a red herring and it's for nothing to do with fast start.



    Maybe fast start stores the state of my computer achieved after the fix? So after next start the fix is still "active".

    In my case, if fast start is turned off, the problem of continuous reading always occurs.


    Anyway, I hope they'll finally fix this annoying problem...



  • 14 minutes ago, komtur said:



    Maybe fast start stores the state of my computer achieved after the fix? So after next start the fix is still "active".

    In my case, if fast start is turned off, the problem of continuous reading always occurs.


    Anyway, I hope they'll finally fix this annoying problem...



    If fast start is off then it's completely off and will effect nothing and do nothing especially a reboot. Nothing should effect BD. So that's really strange.

  • komturkomtur ✭✭
    edited October 2018


    When fast start state is on, I can use the fix and then power off. After next start (power on, not just restart) the problem does not occur. But it is only in case when fast start is enabled. That's why I think fast start, when enabled, can "store" the result of the fix. When fast start is turned off, the problem occurs every time I start my computer, regardless of whether I used a fix before shutdown. This may be a specific case (?). I would have to check this more thoroughly to be sure.



  • 53 minutes ago, komtur said:



    When fast start state is on, I can use the fix and then power off. After next start (power on, not just restart) the problem does not occur. But it is only in case when fast start is enabled. That's why I think fast start, when enabled, can "store" the result of the fix. When fast start is turned off, the problem occurs every time I start my computer, regardless of whether I used a fix before shutdown. This may be a specific case (?). I would have to check this more thoroughly to be sure.



    You should probably read this and perhaps do some googling on how fast start works:


    https://whatsabyte.com/windows/windows-10-fast-startup/


     


    When it's off it's off. Simple as that. I'm not sure what you are on about sorry.


  • I'm experiencing this problem regardless of the Fast Start on or off - mine was/is off, I personally don't think it is needed with SSDs.

    Still manually restarting Windows Management Instrumentation at each start.



    To Support,

    Please update us on this. Can you tell us of ETA new product update to fix this?

    Regards,

     

  • komturkomtur ✭✭
    edited October 2018


    5 hours ago, bqpd said:



    Still manually restarting Windows Management Instrumentation at each start.



    Just pause the winmgmnt service for a moment. There is no need to restart. Someone has already written about it here.


     



    20 hours ago, BDAlexS said:



    You should probably read this and perhaps do some googling on how fast start works:


    https://whatsabyte.com/windows/windows-10-fast-startup/



    Thanks for the link! ;)


    "Fast Startup is a combination between the normal shutdown and Hibernate function. Your Windows 10 PC will shut down normally, as usual, close all running apps and log off all users.Now, the state of Windows is similar to the state when you boot it up but haven’t logged into any user yet. However, all necessary Windows features and drivers are loaded and ready to use. Therefore, Windows will save this state to the hibernation file, and then power off the computer."


    This explains the correlation with the "problem of constant reading" in my case. With Fast Startup enabled I restart (or pause for a moment) the service and the problem of constant reading disappears. From that moment I can turn the computer off and on and the problem does not occur again. Fast Start (when enabled) retains the effect of the fix in my case. When Fast Startup is disabled  the computer starts "from scratch" each time and any saved settings disappear. But of course Fast Start itself is not directly related to the problem.


    Anyway, we are waiting for the final fix.


  • I've finally been forced to reboot my main PC due to a lockup, so it's now also running the 2019 version with the abovementioned issue. It says Bitdefender Total Security 2019 Build 23.0.10.31. Is this the latest version, or is there an update available?

  • BDAlexSBDAlexS
    edited October 2018


    10 minutes ago, [email protected] said:



    I've finally been forced to reboot my main PC due to a lockup, so it's now also running the 2019 version with the abovementioned issue. It says Bitdefender Total Security 2019 Build 23.0.10.31. Is this the latest version, or is there an update available?



    Probably a good idea to read the thread before posting (see first post here for your answer, 23.0.11.48 is being discussed throughout).



  • 3 hours ago, BDAlexS said:



    Probably a good idea to read the thread before posting (see first post here for your answer, 23.0.11.48 is being discussed throughout).



    Thanks, I know this, but with everything that's happened so far (not much in terms of fixes) I wasn't sure if perhaps they'd decided to backdate the app. At this point nothing would surprise me.


    I've applied the update, but won't have an opportunity to reboot again before tomorrow.



  • 14 hours ago, komtur said:



    Just pause the winmgmnt service for a moment. There is no need to restart. Someone has already written about it here.



    Eh, komtur, there is indeed no need to be rude.

    You sounded like pause is the only right way available to stop it. If you say so please state any disadvantages of just restart.

    I don't have a script made up I just do manual restart from Services, restart is a click less than using pause/resume.

     

  • komturkomtur ✭✭
    edited October 2018


    I really didn't want to be rude... :( Sorry if you received it like that. 

    Green456 a few posts above explained quite well why his method is better than that of restarting the service. In my case, pausing the service is faster and does not interfere with dependent services. But it is still a temporary solution. Today's update (requiring a restart of the computer) of Bidefender did not help.


  • Hi,


    I have bought BitDefender Total security 2018.


    It worked fine.


    Now, with the 2019 version that I did not buy but was installed without asking anything, it is destroying my drives. I see that without protection, I have no more bugs. Do you think you'll compensate your customers?


  • komtur, no worries, guess I misread your reply, I apologise for my misunderstanding. :unsure:

    The restart option it seems, at least in my system, is not interfering with anything important, but then I am not 100% sure of that however.



    This bug has been known for at least 6 weeks without a fix, this is pretty awful for Bitdefender's reputation.

    Will you please, Support, update us on this?


  • I agree 'bqpd', we need an update from support.


    It's been six days since we've heard from Sergiu C.


    So please can we have a progress update from support?


     

  • edited October 2018


    If you do the net pause command too soon after a logon then it won't work.  Maybe because the service is still starting when I logon.


    If you do it a bit later it will work. Maybe a Timeout command should be added in the script when it runs.

  • edited October 2018


    Can someone please tell me how do you check and see the bitdefender's constant disk access?


    I just updated bitdefender 2018 to 2019 and the version is : 23.0.11.48  The only way I thought of


    was to open windows task manager and bitdefender disk activity shows 0 MB/s . Rarely it shows 


    0.1MB/s but goes back to 0 again and stay on zero. The process is called "Bitdefender Security Service"


    So it seems that this problem is non existing for me! Unless there is another way to check and test!?


    I rebooted and restated windows few times and still get same results.

    Untitled.jpg



  • 5 hours ago, vampgirl said:



    Can someone please tell me how do you check and see the bitdefender's constant disk access?


    I just updated bitdefender 2018 to 2019 and the version is : 23.0.11.48  The only way I thought of


    was to open windows task manager and bitdefender disk activity shows 0 MB/s . Rarely it shows 


    0.1MB/s but goes back to 0 again and stay on zero. The process is called "Bitdefender Security Service"


    So it seems that this problem is non existing for me! Unless there is another way to check and test!?


    I rebooted and restated windows few times and still get same results.


    Untitled.jpg



    The easiest way to check is by plugging in a USB flash drive with an LED light indicator. If the light continues to blink long after the on-access scan, and doesn't stop, you're also affected by this issue.


    That being said, out of 19 machines, some on Windows 7 a couple on 8 and most on 10, I haven't come across a single machine that isn't affected by this bug.


  • Sorry, my bad. I thought that the disk access was with the internal system drive. I tested with a usb device and the


    Led Light blinks non stop! So it's not fixed for me either :(

  • BDAlexSBDAlexS
    edited October 2018


    I can confirm USB card eject is fixed. However the USB card flashes all the time, it's difficult to nail down if this is BD or not (it's not the search indexer btw, I'm using a SD card I formatted with zero files).


    With the USB card out there is still a heck of a lot of I/O going on, see attached pic showing task manager (and custom columns).

    The read/write count never stops going up. I left this for an hour.


    My system is SSD only.


    Windows 10 17134.345


    BD 2019 - 23.0.11.48


    BD you need to optimize this thing for performance and fast!


    Capture.PNG

  • edited October 2018


    12 hours ago, BDAlexS said:



    I can confirm USB card eject is fixed. However the USB card flashes all the time, it's difficult to nail down if this is BD or not (it's not the search indexer btw, I'm using a SD card I formatted with zero files).


    With the USB card out there is still a heck of a lot of I/O going on, see attached pic showing task manager (and custom columns).

    The read/write count never stops going up. I left this for an hour.


    My system is SSD only.


    Windows 10 17134.345


    BD 2019 - 23.0.11.48


    BD you need to optimize this thing for performance and fast!


    Capture.PNG



    I think it is BD related. You can use SysInternals/MS ProcessMonitor and check for WmiPrvSe.Exe (the WMI process) access to the thumb drive. You will see that WMI is enumerating something regarding encrypted drives. It opens a handle to the drive, sends some control commands to the device driver and then closes it again. You can see in the displayed stacks that the close statement is going through one of BD's drivers. However, the stack of the open call is not hooked up as it seems.


    <sarcasm>Will the next version do RGB?</sarcasm>

  • edited October 2018


    You have to check the Performance tab, not Processes tab.


    Click the Performance tab then click on a disk to see that it's constantly reading about 24,5 KB/s. If you don't see it in the main tab it's because it doesn't read enough to be shown in MB unit with a unique decimal. ;-)


    Remember that it's ALL disks thare are affected, not only external ones.

  • edited October 2018


    After more than a month USB problem is solved but constant disk read is still here, in my case  2 SSD and 2 HDD and all of them are being accessed constantly at 28-49 KB/s. My family members were using BD too, I've to uninstall it from all the laptop's.


    Funny thing is this antivirus after updating to 2019 has given me more hard time than any virus ever did, Users are not able to switch back to 2018 and don't get me started about all the false positives, Blizzard client getting quarantined etc. in poorly tested 2019 version. 


    I've already stopped using BD after USB eject bug and came back to see if constant read issue is solved or not which is a major problem that needed to be addressed and fixed in few hours if not few days after final release but after more than a freaking month still not solved, looks like BD needs an extra few months or years to solve it, i still have almost 220+ days of subscription left but i'm done for good. Anyways switching back for other AV's who are less buggy than this and never coming back to this junk defender even though maybe it's fixed after few months or next year.  <img class=" data-emoticon="" src="https://us.v-cdn.net/6031943/uploads/ipb_attachments/emoticons/default_laugh.png" title=":lol:" />

  • Paul.RPaul.R ✭✭✭
    edited October 2018


    Same problem on macOS too.


    Screen Shot 2018-10-21 at 14.02.33.png


  • This can be a very complex problem. It turns out that it occurs in different operating systems, possibly they have to make some fundamental changes. It's very bad that it takes so much time and there is no trace of what's going on. It is strange that nobody noticed it during the tests.

  • BDAlexSBDAlexS
    edited October 2018


    On 10/20/2018 at 6:22 AM, Green456 said:



    I think it is BD related. You can use SysInternals/MS ProcessMonitor and check for WmiPrvSe.Exe (the WMI process) access to the thumb drive. You will see that WMI is enumerating something regarding encrypted drives. It opens a handle to the drive, sends some control commands to the device driver and then closes it again. You can see in the displayed stacks that the close statement is going through one of BD's drivers. However, the stack of the open call is not hooked up as it seems.


    <sarcasm>Will the next version do RGB?</sarcasm>



    I was mainly interested to see if the main drives were effected (e.g. C Drive).

    I gave full steps to repro ages ago by searching for the external drive letter in Processor Monitor, however my steps no longer work with the new version.

    I tried following your steps but they were not detailed enough, I could not find such handle and how it related to a BD driver. I do know my way around Process Monitor. Would it be possible to provide detailed steps to repro ?


    Thanks.


  • Here you can see my disk 1 (drive F: and G:) and there is a constant reading og 49 kb/sec (it is a Danish Windows 10).


     

    read error.jpg

  • BDAlexSBDAlexS
    edited October 2018


    7 hours ago, svenohrberg said:



    Here you can see my disk 1 (drive F: and G:) and there is a constant reading og 49 kb/sec (it is a Danish Windows 10).


     


    read error.jpg



    It shows that something is doing something, being devils advocate it could be file indexing for instance. I would like to see a set of steps and/or a screenshot that demonstrates that the Bitdefender process is at fault (which seems most likely, just trying not to make assumptions).

This discussion has been closed.