Virtual Box, Virtual machine won't start after installation of F-Secure antivirus

Discussions about using Windows guests in VirtualBox.
Post Reply
gnick
Posts: 1
Joined: 28. Nov 2017, 17:45

Virtual Box, Virtual machine won't start after installation of F-Secure antivirus

Post by gnick »

Hi,

After installation of F-Secure Antivirus, Vbox virtual machine won't start. Unfortunately I can't deinstall antivirus because it is a company PC and it is against the rules ~:(

Tried reinstalling Vbox. Didn't help. Tried 4.x versions, latest 5.x and latest dev build.
Tried creating new virtual machine. The same problem happens.

I have attached hardening log and error screenshot.

Help please :)

Windows 10

Currently installed Vbox version: Version 5.2.2 r119230 (Qt5.6.2)


F-Secure versions:
F-Secure Client Security Premium 12.32 build 113
F-Secure Anti-Virus 9.52 build 239
F-Secure Automatic Update Agent 9.02 build 107
F-Secure User Interface 14.00 build 102
F-Secure Management Agent 10.10 build 105
F-Secure ORSP Client 1.2.13 build 113
F-Secure Network connections 9.10 build 108108
F-Secure Email Scanner 8.00 build 109
F-Secure DeepGuard 5.0 build 707
F-Secure Online Help 3.03 build 677
F-Secure Client Security Premium Customization 12.10 build 103
F-Secure Web Traffic Scanner 3.01 build 276
F-Secure Browsing Protection 2.01 build 483
F-Secure Internet Shield 9.10 build 108
F-Secure Device Control 1.10 build 103
F-Secure Software Updater 2.20 build 1617
Attachments
VBoxHardening.zip
hardening log
(20.73 KiB) Downloaded 13 times
Error that happens when starting virtual machine
Error that happens when starting virtual machine
error.png (14.7 KiB) Viewed 1283 times
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Virtual Box, Virtual machine won't start after installation of F-Secure antivirus

Post by socratis »

gnick wrote:Unfortunately I can't deinstall antivirus because it is a company PC and it is against the rules ~:(
Then either have F-Secure exclude VirtualBox from its scanning, or talk to the F-Secure people and tell them that they have to sign their programs correctly. There is no way around it. And if anybody asks for the details, point them to Diagnosing VirtualBox Hardening Issues. They'll know what to do. And why... ;)
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply