Brand new version of Avast Driver Updater product is now available in Beta (20.1.139)!
In this phase of a product lifecycle it is very important to get as much feedback as possible therefore we would like to ask you to help us with testing.
What’s new in Avast Driver Updater product?
4,500,000 drivers: We have a much larger database of drivers than in the previous product.
Safety checks: Our threat lab checks every single driver before it gets to your PC to ensure safety and security for your devices.
Brand new setup and update technology: We improved the installation and update user experience.
Brand new and easy to use UI: It has never been easier to update your drivers.
Execute the installation package and go through the wizard to install the product.
The product shall guide you or you can freely navigate through it and try it on your own to see how it works.
Please try as much features as you can to see how they work and check whether there are any bugs or unexpected behavior.
If you find any bugs during testing, please create a new thread in this forum section.
Please provide us also with feedback about what you like most and what you would change.
Since we aim to deliver the best Driver Updater product - would you add anything that is missing? Do not hesitate to share your feedback![/ol]
Known issues
If you already have Avast Driver Updater installed on your PC - do not reinstall it with this Beta version or otherwise you would lose your current license. Proper license migration will be resolved in the public version in couple weeks.
I have a good news for you:), luckily it was not a crash but rather an error because the update of a particular driver failed.
The reason for that, as we found out, was a missing signature file on AKAMAI server due to which the update could not be verified on the client side and it failed.
The problem was already resolved, so it should work now.
thank you for your suggestions, they are very valid.
Ad revert, we are already exploring how to do that so it will be most likely added in some update after release of the first version.
Ad sorting, this is a very good idea and we will definitely look into it.
if you could send us the logs once again it would be appreciated.
Even though I assume it will be most likely the same problem as Bob already discovered, I would rather make sure.
thank you for trying it again however we are still working on a solution for the problem reported by Bob.
I honestly don’t know what might cause that you Asyn are not able to induce the problem on your side again, maybe something was changed on the backend side, I have to check it out.
