Re: Bridged adapter is broken in both 4.3.18 and 4.3.20
Posted: 7. Apr 2015, 06:53
Why the VirtualBox team? Why not the Kapersky team?
Because it's VirtualBox software that needs to provide a better (meaningful) warning message not crash "silently": the current error message is not helpful for both user and community (no one could provide any reasonable advice) (no, "reinstall with run-as-administrator is not a reasonable advice").BillG wrote:Why the VirtualBox team? Why not the Kapersky team?
And because it's virtualbox that relies on some state that is triggered by disable-enable kaspersky's filter.
If virtualbox could run fine after kaspersky filter disable-enable, then it's virtualbox that is in charge for the reporting.
Just checked the first advice
well - the error message and logs should have contained info about the state of the filter (it was installed successfully) so that we weren't adviced to reinstall VBox or reboot our PCs without real reason and with no purpose.You don't have the bridging driver installed. Always using "Run as administrator" when installing VirtualBox on a Win64 host.