I started a separate thread, but just wanted to mention here for those watching this one that after the update my Windows Defender (in Win 8.1 x64 Media Center Edition) came on. It’s always shut itself off in the past when Avast was on task. Disabling it manually works around the issue, but it would be nice if that weren’t necessary.
Hi, this problem is fixed - no new certificates with duplicate ids will get created. However you need to get rid of the old ones - the easiest way to do this is a clean reinstall.
Don’t know what version you are currently at, but the problem is fixed via vps update for all versions SP0 and SP1. In the same time, even if it wasn’t, disabling Https scanning in case you’ll ever observe any problems is just one checkbox click away.
New update installed, all setting are gone no possibility to install old setting >:(.
Also not possible, as the app disappears after 2 seconds I open it. I´m not assumed about that change.
What is “SP1” ? 2015.10.0.2208 ?
The problem just appeared when upgrading to 10.0.2208.
I don’t have time for experiments.
Sorry, but had to (temporarily) uninstall Avast.
The problem with VirtualBox in Avast is not the first, and the operability of the VirtualBox is more important to me…
Updated from avastUI on my win7 netbook with the previous release 10.0.2206 - everything appears to have gone well.
Note: This update also appears to have resolved the Hardened Mode Exclusions (on my XP system) in relation to those file paths that were displayed in the old 8.3 file format.
I am sorry to hear that. However, I just tried to reproduce your scenario and doing uninstall and then clean install of both VirtualBox and Avast resolves the issue.
SP1 is 10.0.2208. It is possible, that the issue occurred during the upgrade process from 10.0.2206. Clean install of 10.0.2208 solves the problem.
Just one more question. Did the Avast uninstall resolved the issue with VirtualBox or was it necessary to re-install VirtualBox as well?
Installed .2208.712 already yesterday, where it appeared on the beta thread. Just thinking it was a quick “HotFix” of the last beta version.
OK- now it is the final version and still running comfortably smooth and flawlessly! 8)
Really, after Avast uninstalling (avastclear.exe I tried also) I had to use VB installation recovery.
Avast uses VB-code to implement the Sandbox sevice. Obviously, some of the modules or their registration data (actively used COM-technology) came into conflict with VB-infrastructure. Your developers need to be more careful when “VB is near”.
These problems led to the loss of my working time. Various experiments would only aggravate it.
Don’t worry, I’ll probably be back (maybe tomorrow).
Thank you. Sorry for my English.