virtualbox.org

---

ModEdit; related ticket: #18182: Latest Insider Build Sound Driver Broke

---

Using Win 10 1803 Host VB 5.2.22 Win10 Guest Build 18298 just installed no audio output.
Guest configured Enable Audio: checked, Host Audio Driver: Windows Direct Sound, Audio Controller: Intel HD Audio, Extended Features: Enable Audio Output: checked, Enable Audio Input: Unchecked.
Sound icon in system tray has red X Hover text No Audio Device is Installed.
Device manager shows Audio device failed to install, event error codes 420, 400, 411.

Have tried to use alternate audio devices AHC97, and SoundBlaster but no change.
Previous Build sound appeared OK.

You're having problems with your "Windows Guest", not your "Windows Host". Moving to the appropriate area.

Do not change sound controllers at random. The Intel HDA is chosen for a reason; Win10 has drivers for it by default. You need to go in the Device Manager in your guest and see what's going on. Same with the Sound preferences. Don't change the VirtualBox settings...

Sorry if I posted in the wrong place.
I thought my post included all the relevant information.
To re-iterate
Guest configured Enable Audio: checked, Host Audio Driver: Windows Direct Sound, Audio Controller: Intel HD Audio, Extended Features: Enable Audio Output: checked, Enable Audio Input: Unchecked.
Guest Sound icon in system tray has red X Hover text No Audio Device is Installed.
Guest Device manager shows Audio device failed to install, event error codes 420, 400, 411.

If I have missed some important info please request it.

Your 2nd post run close to be deleted as a duplicate of your 1st one!
We need to see a complete VBox.log, from a complete VM run:

• 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).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

And I want to see what the Device Manager of your guest has to say about it. What happens if you try to search and (re)install the audio drivers?

I have done as instructed. In the zip file attached are also screenshots showing

1. The red X error indicator in the system tray.
2. The device manager display of the HDAC.
3. The result of checking the latest driver installed.
4. The sound settings obtained by right-clicking the red X icon and choosing sound settings.
5. The device manager overview.
6. The event viewer administrative events. There were no events logged for the date and time of the error which occurred while creating the VBox.log

Again If I have missed anything please ask.
This has happened on a VB 5.2.22 installed on a Win10 Host running 1809 as well as on the previous 1803 build.

For some reason the screen shots were not included in the zip file, sorry.
I think the problem was the size of the screenshots was too big, as they cannot all be attached here.
the files numbered 1 4 and 5 are attached see follow up reply for 6

File 6 attached here.
I will retake the screenshots - files 2 and 3 reduced in size and attach them in the next reply.

Files 2 and 3 attached

MacNala wrote:Win10 Guest Build 18298 just installed no audio output.

It seems that this is specific to build 18298. If you're not "paul.stejskal" from ticket #18182, then this is the 2nd report about that specific build. I can't download and confirm, no insider access. You'll have to wait I guess for a fix...

Tying the ticket and the discussion so they're coordinated...

Thanks for the update.
I have read ticket 18182 and the only difference it the host machine O/S his problem Linux my problem Windows 10 both 1803 and 1809.

Not clear where you expect the fix from?

If I get a fix from MS and it works I will report here (or would you prefer I update ticket 18182?

Have identical issue with this insider build

However, have also noticed that the Shared Folders functionality is disabled

NADight wrote:However, have also noticed that the Shared Folders functionality is disabled

Please don't defocus the discussion. Let's stick with the Sound issue, as the thread is appropriately titled. Open a new thread with a proper title for the Shared Folders issue...

MacNala wrote:the only difference it the host machine O/S

This is clearly not a host problem, this is an Win10 Insider Build problem. I honestly have no idea why Win10 r18298 lost the ability to install drivers for the most common sound card. Did anyone talk to Microsoft about this?

MacNala wrote:If I get a fix from MS and it works I will report here (or would you prefer I update ticket 18182?

Both actually would be nice of you. I track both the forums and the ticket, so if you don't do it, I'll have to do it for you...

I am in contact with MS but you know what it is like; they take for ever to reply and then misunderstand the problem.
I live in hope for a solution from somewhere.

I'll roll back a release and see if it still happens. I don't know if this is unique to this build, there is a new change in Windows that VBox devs need to code for, or what.

I had been running the previous preview release and the sound device was OK after the update it was not working.
It is difficult to see how an existing device is removed/disabled by an update of the Guest O/S but hat is what has happened.
Now installing a new win10 guest might be more enlightening when updated to 18928 or more correctly install Win10 18298 from an ISO.
Then in my simple way of thinking the device in the definitions of the guest virtual machine should install the HDA Controller and should then be found by the O/S and the correct driver installed. But with MS you never know!