all new VirtualBox session hang when Skype for Business start a conference/meeting call

[blaine]

all new VirtualBox (after interface changed) session hang when Skype for Business start a conference/meeting call.

[blaine]

any update on this please? it is found that the latest 5.2.12.r122591 still having this issue. whole VirtualBox hang when Skype for Business join a Meeting Conference / ending a Meeting Conference.

[Socratis]

According to #17497, this has been resolved. Maybe this ticket should be closed as a duplicate of #17497 and the last one to be re-opened?

[blaine]

According to #17497, that is Audio issue which audio doesn't work. For my case above, whole VirtualBox is hang, while my conference audio is still functioning. Please assist to investigate. Thanks.

[blaine]

VBox.log

[blaine]

VBoxHardening.log

[blaine]

VBoxSVC.log

[blaine]

selectorwindow.log

[blaine]

please check if any of the log files help in this case. please also let me know if there is any file required that could help solving the issue. thanks!

[Socratis]

From your VBox.log

00:00:01.506076 Console: Machine state changed to 'Restoring'

Restoring a VM's state is not the best way to get all the available information. For example, I have no clue what version of the Guest Additions (GAs) you're running. The proper way to get a complete "VBox.log" is:

1. Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM (force close it if you have to).

2. With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".

3. Save only the first "VBox.log" and attach it to your response.

---

00:00:05.160673 GUI: 2D video acceleration is disabled
00:00:01.625807 VRamSize <integer> = 0x0000000001b00000 (28 311 552, 27 MB)

And so is the 3D acceleration. Shutdown the VM and enable them in the VM settings » Display. You'll also notice that the max VRAM might jump from 128 to 256 MB after that; max the VRAM as well. Then re-install the Guest Additions (GAs) in the guest.

---

00:00:01.625586 RamSize <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)

You might want to increase that to 2048 MB, you can definitely afford it.

---

00:00:01.625788 [/Devices/usb-xhci/0/Config/] (level 4)

Windows 7 does not have native support for USB3, have you installed the appropriate ​Intel USB 3.0 drivers?

---

From your VBoxHardening.log

2aac.1a48: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xcfffffff (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 21937820 ms, the end);

Now, that's an interesting and rather unusual Exit Code! Please read really carefully the following FAQ: ​Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas. Those are guidelines, you have to use your judgement...

I'd start by uninstalling (not simply disabling) Symantec, Malwarebytes and Avecto...

Finally, may I suggest something? It's usually better and faster, if issues get first addressed in the ​VirtualBox forums (more eyes). More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

So, if you can, please open a new thread in the ​Windows Guests section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number.