Audio input broken on Windows 10 v1709 hosts

[vbutilizer]

Audio input seems to be broken on Windows 10 v1709 hosts for any guest OS with the latest (didn't test for regressions) version of VirtualBox (5.2.8). I tested Win10 v1709 guests and modern Linux guests (Arch Linux). On an Arch Linux host with the latest VirtualBox a Win10 v1709 guest works fine. So this seems to only impact Windows hosts.

I've tried it on 3 completely different machines, an older Sandy Bridge era desktop, a modern desktop and a current laptop.

I've tried it on Realtek audio hardware with a 3.5mm microphone plug and a Logitech G533 wireless headset with a USB dongle. I tried disabling (from Device Manager) all other hardware devices except the Logitech device when testing this. I tried uninstalling the Realtek drivers as well.

I tried a clean install of the latest VirtualBox with a clean Win10 v1709 guest install with audio input/output enabled from the start.

Everything appears fine on the surface, audio input/output are enabled in VirtualBox settings, the devices appear in the guest, audio output works fine but audio input does not - there's only silence. The Windows Sound -> Recording dialog in the guest does not show any activity and "Listen to this device" does not result in any output. On the host itself it does work.

I didn't see a relevant looking ticket for this so I'm submitting a new one.

[vbutilizer]

VBox logs

[vbutilizer]

Just tried the latest test build and development snapshot and neither fixes this.

Audio output works on all, however.

[h2mo]

Add me. Exactly same observation, Win10-64 host, Win10-64 and Win7-64 guests. Simply reverting back to 5.1.30 without zero other changes (in particular no update of guest additions!) brought audio input back instantly.

Finally we have a nicely working audio output - but then the input is completely dysfunctional. :-(

[asaletnik]

Same here - Windows 10-64 v1709 host, Ubuntu 16.04 guest. Issue started after updating to 5.2.8. Reverting to 5.2.6 (keeping the GA at 5.2.8) made the audio input work again.

[garba]

Same here: 5.2.8 fixed the audio stuttering problems for me (playback is almost perfect now) but no audio input in the VM, will have to revert to 5.2.6 where I got poor audio playback but flawless audio recording.

[matthewls]

I've had similar issues using Windows 7, but believe I've improved (but not solved) audio using pulse audio control (pavucontrol) on the host Linux machine. The problem was not input or output, but the timing of each, with echoing, stuttering on the output and unreliable input (using the virtual machine for speech to text dictation). The main changes that seem to work or to increase the latency offset of both input and output to 10 ms, and increasing the I/O and CPU priority via the Linux host (renice and ionice). I decided to do that when I saw that the sound timing was worse in seamless mode than in normal windowed mode.

5.2.9 r121224

[matthewls]

I've had similar issues using Windows 7, but believe I've improved (but not solved) audio using pulse audio control (pavucontrol) on the host Linux machine. The problem was not input or output, but the timing of each, with echoing, stuttering on the output and unreliable input (using the virtual machine for speech to text dictation). The main changes that seem to work or to increase the latency offset of both input and output to 10 ms, and increasing the I/O and CPU priority via the Linux host (renice and ionice). I decided to do that when I saw that the sound timing was worse in seamless mode than in normal windowed mode.

5.2.9 r121224

Host audio remains perfect, and timing issues occurred whether recordings made in the VM were played in the vm or the host.

[h2mo]

Replying to matthewls:

I've had similar issues using Windows 7, but believe I've improved (but not solved) audio using pulse audio control (pavucontrol) on the host Linux machine.

Note this Ticket is not about a Linux host but Windows 10. There is not such thing as pavucontrol. In my case it's Realtek audio hardware and Realtek drivers.

[MK]

I had the similar issue with latest VirtualBox 5.2 and 5.1 (5.1.34_Ubuntu r121010) in Ubuntu 16.04 Host and Win7 Guest. Maybe the issue is related with Intel HD audio controller.

For me the following workaround worked:

1. Change the audio controller from Intel HD Audio into ICH AC97 in VirtualBox VM settings
2. Install the AC97 drivers in Windows guest (​http://www.realtek.com/downloads/downloadsCheck.aspx?Langid=1&PNid=23&PFid=23&Level=4&Conn=3&DownTypeID=3&GetDown=false)

[h2mo]

Replying to MK:

I had the similar issue with latest VirtualBox 5.2 and 5.1 (5.1.34_Ubuntu r121010) in Ubuntu 16.04 Host and Win7 Guest. Maybe the issue is related with Intel HD audio controller.

Please understand that this ticket is about a Windows 10 host (not some flavor of Linux) and Windows 10 guest (not Windows 7).

For me the following workaround worked:

1. Change the audio controller from Intel HD Audio into ICH AC97 and Host Audio driver to ALSA in VirtualBox VM settings
2. Install the AC97 drivers in Windows guest (​http://www.realtek.com/downloads/downloadsCheck.aspx?Langid=1&PNid=23&PFid=23&Level=4&Conn=3&DownTypeID=3&GetDown=false)

Tried it, but these drivers fail to install in a Windows 10 x64 guest: "Windows encountered a problem installing the drivers for your device".

[Roger Reghin]

@h2mo, I do agree with you that the problem is related to Windows 10 hosts, but the problem happens whatever guest OS you use, for instance, Windows 7 guests and Linux guests.

[Ransom]

Similar here – Win 10 Pro (1803) Host – Win 10 Pro (1803) Guest. VirtualBox does not install for the microphone (Intel HD Audio) the required digital jack but the 3.5 mm jack, so my implemented microphone of the Laptop does not work.

In other Guests of my VirtualBox – Win8.1x32-Home and Win 10 Pro x64 (1703) – under Sound\Recording the microphone is not even to see.

The bug still remains since 5.x.x.

[danowski]

The same here. Windows 10 Home host and Windows 10 Pro guest.

[durden0]

Same issue: Windows 10 Pro 1709 host - windows 7 guest

VirtualBox 5.2.8 r121009 (Qt5.6.2)

[JorgenCAB]

Still same issue with 5.2.12.r122591

No Audio input from a Windows 10 host is possible.

[Quad4]

Same issue with USB microphone. Windows 10...

[Denys Yurchenko]

Still same issue with 5.2.12.r122591

No Audio input from a Windows 10 host is possible.

[fabs]

Same issue with 5.2.12 r122591 Windows 10 Enterprise Host & Guest Please fix

[@…]

Same on VirtualBox 5.2.8 r121009 (Qt5.6.2).
HOST: Windows 10 (10.0.16299).
GUEST: Various Windows and Linux.

Audio OUT has improved a lot, no more rattling.
Audio IN doesn't pick up anything, even though microphone is detected and installed (built-in microphone of laptop).

arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 82801AA-ICH]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: I82801AAICH [Intel 82801AA-ICH], device 1: Intel ICH - MIC ADC [Intel 82801AA-ICH - MIC ADC]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

[johnalotoski]

Same issue (ie: audio out is ok, but no mic in is working on guest) with VirtualBox 5.2.12 r122591 (Qt5.6.2), Win7 Enterprise v6.1 build 7601 SP1 host and NixOS 18.03 guest on Lenovo T530 and Logitech USB headset mic model A-00057 or built in mic on laptop.

[VBoxUser12345]

Same issue, last working Version was Version 5.2.6 r120293 (Qt5.6.2) for WinXP-Guest (Win10-Host).

[Denys Yurchenko]

Same issue on VirtualBox 5.2.12 HOST: Windows 10 1803 GUEST: Ubuntu 14.0

[joschi]

Same Issue on Version 5.2.97 r124007 (Qt5.6.2) Windows 10Pro 1803 Guest: Android x86. At least the sound is working in this development build... I tried a workaround connecting the USB device directly but its lags beyond usable.

Kind regards Patrick

[Manoj Jain]

Hi, I have similar issue. Spend some time going thru blogs and possible fixes. But it didn't work. I have Version 5.2.14 r123301 (Qt5.6.2) VirtualBox installed on Windows 10. I have realtek Sound (Mic and Speakers) on my system. It is working fine on Windows 10 application.

I have installed Ubuntu 16.x as VM on virtual box. I have enabled Audio on VM - Both Audio input and output are enabled.

Test Audio devices on Ubuntu VM - 1) Test Speakers - aplay /usr/share/sounds/alsa/Front_Center.wav - I could hear sound Front Center. Means Speaker are working fine on Ubuntu VM.

2) Test Microphone - a) First see if recording device is active

arecord -l

List of CAPTURE Hardware Devices card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 82801AA-ICH]

Subdevices: 1/1 Subdevice #0: subdevice #0

card 0: I82801AAICH [Intel 82801AA-ICH], device 1: Intel ICH - MIC ADC [Intel 82801AA-ICH - MIC ADC]

Subdevices: 1/1 Subdevice #0: subdevice #0

b) Second record arecord -d 10 /tmp/test-mic.wav Recording WAVE '/tmp/test-mic.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono

I can see a test-mic.wav is created with size 80044 bytes -rw-r--r-- 1 xxxxxxxx xxxxxxxx 80044 Sep 24 13:18 /tmp/test-mic.wav

Now try to play the test-mic.wav file

aplay /tmp/test-mic.wav Playing WAVE '/tmp/test-mic.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono

@@@@@@NO SOUND@@@@@@@

Then I try another utils alsamixer

The results show -

@@@@No Mic device@@@@@@ - This seems to be problem

One Capture device

Please suggest the possible work around / solution for this long standing problem

Thanks Manoj

[pentagonik]

Please try the latest test build from the Testbuilds page.

Scroll down to the Latest test builds / 5.2.x builds section and download the build appropriate for your host platform.

Could you please supply the verbose VBox.log file as shown here: Investigating audio problems

Thank you!

[hhmmoo]

Seems like it finally got fixed in 5.2.20.

[pentagonik]

Thanks for your feedback!

[Denys Yurchenko]

Works in version 6.0.6.