AVG installation locks up Virtual Box version 5.1.26

[Bubba]

AVG installation locks up Virtual Box version 5.1.26

Please reply with suggestions to fix problem.

Thanks, Danny.

[Bubba]

I have to start Virtual Box in safe mode and remove the AVG program in order for Virtual Box to do a normal load.

[Bubba]

I am running Windows XP as Oracle Virtual Box on a Windows 10 computer.

[Dmitrii Grigorev]

Please clarify:

1. Do you mean antivirus software by saying "AVG program"?
2. Please replay your scenario and attach VBox.log to this ticket

[dannyo1]

LOG FILE

[dannyo1]

Yes; AVG antivirus.

When I try to install AVG antivirus the installation gets to 97%, sits for a few minutes, then fatal VM machine error with option to close VM or debug. I have to select debug and close VM then restart VM in safe mode and remove AVG program in order to restart VM.

This just started on two of our computers. Until now there has been no problem running AVG on the VM. I normally install the Test builds for the VM. Was running Test build 5.1.26, then loaded 5.1.25; same problem.

Log attached.

Really appreciate your help. Please reply as soon as possible. Thanks, Danny.

[Dmitrii Grigorev]

Hello Danny.

From the log you've attached I see that the problem experienced on such host OS: "Windows 10 Creators Update 15063". Did you have a chance to check if the problem reproduced on other host OS, Windows 7 for example?

[Socratis]

Replying to dannyo1:

Until now there has been no problem running AVG on the VM.

AVG recently started using hardware acceleration in their antivirus (VT-x). Since this is not available on a VM, this could be something to look at. Do you have older AVG versions that you could try?

[dannyo1]

Windows 10 is the only host machine I have.

Was there anything in the log file that would indicate what the problem might be?

Thank You, Danny.

[Socratis]

I thought that you were trying to install AVG on the guest, not on the host, therefore the host is not that relevant. I don't know if there should be anything in the log, you'd have to ask AVG.

Just because a program that runs in the context of VirtualBox has a problem, it doesn't make it a VirtualBox problem. You may be having an issue that has nothing to do with VirtualBox, so my suggestion would be to treat it as such, as a native problem with the OS or the application of the guest.

[Klaus Espenlaub]

dannyo1: I'm very unsure if this issue is actually with AVG. The problem in your log file is that something triggers the load of \Device\HarddiskVolume3\Program Files (x86)\Microsoft Office\OFFICE11\OUTLLIB.DLL in a VM process, and that doesn't look like AVG. Especially as it happened after almost 3 minutes of VM runtime.

So how did you come to the conclusion that AVG is actually causing the problem?

We need reliable information, also from the original reporter. Bare minimum is VBoxHardening.log in this context.

[dannyo1]

I ran scans with AVG Free and Malware Bytes; found nothing.

Decided to download and run AVG full trial. Used this AVG to tune computer. Decided to uninstall this version of AVG and reload AVG Free. That is when I could not install AVG.

All problems and work is on the Guest VM that is located on the windows 10 host.

I don't recall the exact events but that is close to what I did.

At this time I am working with bot VM and AVG on possible solutions.

There was a mention of a log file. Please tell me how to find and attach it in order to send to you.

THanks, Danny.

[Dmitrii Grigorev]

Hello Danny.

The required VBoxHardening.log should be near VBox.log (you've already attached one before). Please reproduce the problem and attach both files.

[Dmitrii Grigorev]

Hello Danny.

My PC at hand with Win10 does not have MS Office installed and the "suspicious" module OUTLLIB.DLL is missing. Meanwhile AVG antivirus can be installed/uninstalled on WinXP guest without any problems. So, the reasonable idea is to check the problem on a PC without MS Office :)

I was checking it on Host: Win10 64-bit 15063, VirtualBox 5.1.28

[dannyo1]

I attached 3 files.

I will remove MS Office and try again.

Thanks, Danny.