komtur ✭✭

Looks like I found another solution to this problem. 😎 Total Security is up to date and everything works fine. The problem was only with "stuck" update message. I solved it by changing Total Security's language to Polish (I'm in Poland). I have used Total Security in English version so far. The messages are already correct…

I have Windows 10 Home Edition (1909, the latest, fully updated). I've also seen this problem on our other computers.

The problem is gone. I can't reproduce in now. The problem was in version 24.0.12.72 in my case. Currently I already have version 24.0.14.80 and uninstallation of VPN does not generate any problems. Thanks for your response!

It seems to me that the problem was that the procedure of uninstalling VPN service always ends with an error visible in the first post. After the fresh installation of Total Security, the VPN service is automatically installed. At least that's what happened to me today. I don't need this service either, so I uninstalled it…

That's right, I'm looking forward to the results. The problem is not particularly serious, but it is still a bit irritating... This is especially true because the same problem has already existed in the past and has been fixed. I don't remember if it "solved itself" because something was changed in Opera or it was solved…

I have done a report on our another computer (the same problem with Opera). Ticket number is 2019101916140002. The problem occurs only on computers where Total Security is installed. Computers with other antivirus software do not have this problem. This is strange at all, because changing the "Web attack prevention"…

A more detailed description was sent by e-mail. Thanks!

In addition to the information about the current version, we could also write about news and corrections that we have noticed. There is probably no official changelog for home editions(?) Or maybe I can't find it... It is possible that some changes should not be communicated for security reasons, but many of the fixes…

Generally, the latest version should probably appear automatically, as part of the automatic update. But it's probably always a process that doesn't happen to everyone at the same time. I still have 23.0.14.61.

OK. The problem is resolved after update and restart. But build number in my case is still 23.0.14.61. I haven't read exactly from this happiness. It's about the version of a particular file. Everything is fine. 

The way they work remains quite unusual. Zero information. No messages informing about the progress. Nothing. Will it take another week? A month? Quarter?

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.

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…

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…

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…

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…

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…

My happiness was premature. This problem is indeed related to the fast start option. With the fast start turned off, the problem of continuous disk reading occurs after each boot.

It is a mystery for me. After two days the problem of constant disk reading is gone. I didn't do anything special. I just started my computer after two days. Still the same build. Strange. I have to take a look at it in the near future. 

This problem seems to be much more complicated. Sometimes after booting the computer there is no continuous reading of the disks. In most cases, however, this happens. I start the computer and everything is fine. After restarting the problem returns... or not. I can't discover the rule. Previous build was "stable" - the…

3 minutes ago, DAN57150 said: Do we belong to the few lucky ones ? I have NO problems any more ( BDTS2019 23.0.11.48 - Windows 10 -1809 - 17763.55) In my case the problem returned. As I edited the previous post - after one more restart the problem returned. I have the same configuration as yours.

It seems a little weird. One of my computers after a few restarts started to behave correctly (no continuous readings, I can remove USB drives). So the problem seems to be partially solved. At least for some configurations (?). Maybe it's the result of updating to 23.0.11.48, and then some additional updates? Edit: a few…

So we are still waiting. The first post about this problem was on September 3! If it didn't apply to me, I would even find this situation funny...

49 minutes ago, SageWolf said: I understand Bitdefender is most likely working on a solution but the lack of information provided to us customers is mind boggling. That's right. I understand that the problem can be (contrary to appearances) very complicated but it would be good if someone informed, even generally, what is…

I looked here after a few days and I can still see that nothing is happening. Is this problem so difficult to solve? Why does it take so long? Why nobody tells us what's going on? We still have version 23.0.10.31. Strange.

Nothing has changed so far. No fixes. Interesting - will there be some big, collective update or are they working so hard on this one particular patch? 

I still use a trick to restart the service: net stop winmgmt, and then net start winmgmt. It eliminates the problem with constant reading of disk C: at least. But how long can we wait?

I am also in IT. And I am also very angry about this situation. And I have quite a lot of experiences with various antivirus programs. To be honest, I had problems with all of them. Not only Bitdefender is causing problems. I have seen much worse problems / crashes than the one we are now writing about... First of all, I…

I don't think it makes sense to fall into hysteria. It is indeed a nasty slip-up, but let's give the Bitdefender a chance. I hope, however, that they will correct this mistake relatively quickly. Bitdefender is still one of the most effective programs in its class. This does not change the fact that testing the program…

22 hours ago, Sergiu C. said: Unfortunately no ETA at this time, though the issue is considered a high priority one.  Well, it doesn't sound good. The problem is really annoying, it's not a negligible small thing. It looks as if we are all using a beta version, not the final software... I hope that the fixed version…