The current Bitdefender version, build number link.

@gur_helios

Hello.

The text in the box says it all:

So, uninstall the Bitdefender program using the Uninstall Tool:

It will completely remove the program.

Regards.

🙄😂

Yes @Scott you are right, it's coming 😎

Got it this afternoon 😀

Salute Uwe

Hi Scott

Yes, a restart was needed.

My laptop is still waiting for Build 27.0.16.86. It is still stuck on Build 26.0.36.193, two build versions behind. My desktop has the current build. I went so far today as to uninstall my Malwarebytes Premium, do a reinstall of BD Total Security, and then reinstall MBP. What a pain and no joy! The laptop is still stuck on Build 26.0.36.193. I only fire up my laptop once a week to do updates, backups, and scans. So, I wasted an hour and got nowhere.

How long does it take these "wave" rollouts to hit every subscribed computer?

Both computers are running Windows 11 Pro, fully updated. SFC scan is clean.

Regards,

Phil

@RedsFan

Thank you for your reply. I am reluctant to uninstall and reinstall again, removing and reinstalling Malwarebytes Premium. It is a pain.

The real question that I have, since Bitdefender reinstalled itself, is how long do the Build updates take to roll out to everyone?

I followed the advice on the BD Support Page about doing a reinstall. It recognized my laptop as being registered and kept my exceptions, which is a great improvement to the product! Once reinstalled, my laptop was registered, and all is good, except I can't seem to force an update to the latest build.

@Alexandru_BD

Do you have any information to share to assist me and others who wait for Build updates? How long does it take for a full rollout? What is the best way to proceed? Would it not be a good idea to enhance the product to permit users to initiate Build Version updates via an option in the program?

Submitted for your consideration and comments.

Thank you, and have a great day.

Regards,

Phil

@Scott @Alexandru_BD

Just after I posted my last comment, I kept manually initiating "Check for Updates." FINALLY, the current Build downloaded and installed. Alleluia! I was two versions behind on my laptop, at least three weeks.

I am hoping that Alexandru_BD can shed some light on the rollout times, and if BD will consider adding an option to permit users to initiate a Build Update as an option within the program. This is the second time that my laptop has had to have BD uninstalled and reinstalled to get it caught up. The first time, about a year ago, it was six weeks behind!

Have a great day. Thank you to all who have responded and hopefully will respond to share this information with all of us.

Regards,

Phil

@Scott

I have never used Avast, so I can't comment on its functionality, but any enhancements to BD that would improve the delivery time for Build Updates has my vote!

A year ago, when my laptop got six weeks behind, I was forced to reinstall BD to resolve that, just like this time. There has to be a better way . . .

Regards,

-Phil

Hello,

A bit late to the party here, but I'll share with you a few insights on product updates.

Bitdefender updates daily, and it frequently updates its signatures multiple times within a day. However, when it comes to product updates that involve changing the version number, they occur less frequently, typically once every 4 weeks. The new build is rolled out in batches for several reasons and the duration in which it propagates to all users is influenced by several factors.

Rolling out updates in batches allows developers to mitigate potential risks. If a critical bug or issue is discovered after an update is released, it could affect all users if the update was pushed to everyone at once. By releasing updates in smaller batches, developers can closely monitor the impact and address any issues that arise before the update is pushed to a larger audience. Even with thorough testing, it's challenging to predict how software will behave in all possible user environments, and considering that operating sytems experience changes of their own. By deploying updates to a smaller subset of users initially, developers can observe how the update performs in real-world scenarios and identify any unexpected issues that might not have been detected during testing.

Distributing updates to a large user base all at once can put a significant load on servers and infrastructure. This can lead to slow download speeds, service disruptions, and other technical problems. By releasing updates in batches, the load is distributed more evenly, reducing the strain on resources.

In summary, rolling out updates in batches is a strategic approach that allows developers to manage risk, ensure quality, gather feedback, and provide a smoother transition for users. It's a careful balance between making improvements and minimizing potential disruptions or issues. Yes, sometimes it may take a little longer for the latest build to reach your device, but we must take into account any possible hiccups along the way and also the amount of time required to apply any necessary changes and hotfixes, so it's difficult to tell exactly how long it will take for the update to reach all devices. AND there is a huge Bitdefender user base, I can tell you. There is always a forecast, of course, but it's not set in stone and some updates may also be postponed to include other improvements that were not available during the first deployment.

By default, Bitdefender performs automatic updates when you turn on your computer and every hour after that. When an update is detected, it is automatically downloaded and installed. It is not mandatory to reinstall the product in order to benefit from the latest build and there is a manual update option to check for new releases anytime. Considering this, another option to initiate a Build Update would conflict with the existing one and would serve the same purpose.

Regards,

Alex

@Alexandru_BD

Thank you for much for your reply. That confirms what I thought: my laptop was twice seriously overdue for a Build update that was not happening for it but did for my desktop within the time frame you have stipulated.

The reinstalls must have "shaken something loose" and permitted the Build updates to occur for my laptop (Dell XPS 15 7590). Still, it was a major time commitment. I think that we both agree that such things should not occur that necessitate a reinstall to resolve. Not sure why BD keeps picking on my laptop . . . ? SFC scans are clean.

Have a great weekend.

Regards,

Phil

Okay... then it's not just me. Hope it will be fixed soon. That is at least a little reassuring.

Yeah... after the update, the firewall works again. A reboot is not needed. 😀👍️