Vbox Communication Sound Cards & Media Devices Driver Download For Windows 10

Host: Windows 7, Virtual box 5.1.20, Guest: Windows 10 Pro Replying to billikumar: I am finally able to get the audio working by doing the following, Looks like the problem resides in the HD Audio Driver. Shut down the windows 10 VM. Open the Settings navigate to Audio section Change the 'Host Audio Driver' to 'ALSA Audio Driver'. Team Collaboration Idea Management Web Conferencing Employee Communication Tools. Pulse PulseAudio Sound Server iec958:CARD=Intel,DEV=0. Additionally, there are cards for the following vowels: uh, ah, ee, oh, and oh. On each card is a picture of a mouth showing how to produce the sound, as well as a picture to help remind your students what sound they are working on! For example, the /b/ sound card has a ball so you can verbally prompt with “buh buh buh like a ball bouncing”. For some configurations of VB, I can get sound output, but still no input. I've upgraded VirtualBox to the lastest version (as of today - 5.1.22), and have upgraded several times over the life of this problem. Each time I have installed the corresponding guest additions.

If your host operating system is configured for sound, you can enable sound for a virtual machine. Currently PCM (Pulse Code Modulation) sound output and sound input are supported. That is, VMware GSX Server supports any application that produces sound without using MIDI. Synthesizer sound output, game controllers, and joysticks are not supported.

Cards

The virtual sound device is compatible with a Creative Technology Sound Blaster 16 audio device. It supports sound in Windows 95, Windows 98, Windows NT, Windows 2000, Windows XP, Windows .NET Server and Linux guest operating systems. (See below for information on using sound in a virtual machine running Windows .NET Server or Windows XP as a guest operating system.)

The sound device is disabled by default and must be enabled in the Configuration Editor.

Vbox communication sound cards online

To enable sound support for a virtual machine:

  1. Configure sound on your host operating system. Refer to the documentation for your particular operating system for instructions.
  2. Select File > Open and open the virtual machine configuration file (.cfg) you want to modify.
  3. Select Settings > Configuration Editor from the console.
  4. From the list of devices, select Sound.
  5. Select the Start Connected option if you want the sound to be enabled when the virtual machine powers on.
  6. Under Device, enter the path to the sound device you want to use.
  7. Click Install.

Note: Your sound card must be working in your host operating system in order to use sound in the virtual machine.

If you do not have sound on your host, or if it is used by another application, an error message appears when you try to run the virtual machine and the sound device is disconnected. Use the Devices menu entry to reconnect it.

Enabling sound for guest operating systems

You must configure the guest operating system to use the VMware virtual sound device. This device is compatible with a Creative Technology Sound Blaster 16.

For Windows .NET Server and Windows XP guest operating systems:

Windows .NET Server and Windows XP do not automatically detect and install drivers for ISA sound cards, such as the Creative Sound Blaster emulated in a virtual machine. Follow these steps to configure sound in a Windows .NET Server or Windows XP guest operating system:

  1. Click the Printers and Other Hardware link in the Windows Control Panel (Start > Settings > Control Panel).
  2. In the See Also pane, click Add Hardware, then click Next.
  3. Select Yes, I have already connected the hardware, then click Next.
  4. In the Installed Hardware list, select Add a new hardware device, then click Next.
  5. Select Install the hardware that I manually select from a list (Advanced), then click Next.
  6. Select Sound, video and game controllers, then click Next.
  7. Select Creative Technology Ltd. in the Manufacturer list and Sound Blaster 16 or AWE32 or compatible (WDM) in the list of devices, then click Next.
  8. Click Next.
  9. Click Finish.
Online

For Windows 2000 guest operating systems:

  1. Double-click the Add/Remove icon in the Windows 2000 Control Panel.
  2. From the Add/Remove Hardware Wizard dialog box, select Add a New Device and click Next.
  3. From the Find New Hardware screen, select No, I want to select the hardware from a list and click Next.
  4. From the Hardware Type screen, select Sound, video and game controllers from the list and click Next.
  5. From the Select a Device Driver screen, select Creative from the manufacturers list and select Sound Blaster 16 or AWE32 or compatible (WDM) from the models list, then click Next.
  6. From the Start Hardware Installation screen, click Next to install the Sound Blaster 16 drivers.
  7. From the Completing the Add/Remove Hardware Wizard screen, click Finish and reboot the virtual machine. Sound should be working the next time the virtual machine's guest operating system boots.

For Windows 95 and Windows 98 guest operating systems:

Note: If you have never installed a Sound Blaster 16 Card in this Windows system previously, you need a Windows 95 or Windows 98 installation CD-ROM.

  1. Launch Add New Hardware from the Windows Control Panel.
  2. Click Next.
  3. Select Yes for Do you want Windows to search for new hardware?
  4. Click Next.
  5. Click Next again.
  6. Windows should run the auto-detection and say it is ready to finish.
  7. If prompted to do so, insert the Windows CD-ROM into the drive and click OK.
  8. Click Finish.

If you have problems with Windows auto-detection, add the device manually.

  1. Launch Add New Hardware from the Windows Control Panel.
  2. Click Next.
  3. Select No for Do you want Windows to search for new hardware?
  4. Click Next.
  5. Select Sound, video and games controllers.
  6. Click Next.
  7. Select Creative Labs Sound Blaster 16 or AWE-32.
  8. Click Next.
  9. Click Finish.

For Windows NT guest operating systems:

Note: If you have never installed a Sound Blaster 16 Card in this Windows NT system previously, you need a Windows NT 4.0 installation CD-ROM.

  1. Launch Multimedia from the Windows NT Control Panel.
  2. Click the Devices tab.
  3. Click the Add button.
  4. Select the Creative Labs Sound Blaster 1.X, Pro, 16.
  5. Click OK.
  6. Insert the Windows NT 4.0 CD-ROM in the CD-ROM drive when prompted.
  7. Specify D:I386 (or another drive if D: is not your CD-ROM drive).
  8. Click OK.
  9. Configure the Sound Blaster base I/O Address to 220.
  10. Click OK.
  11. Complete the Sound Blaster 16 Configuration.
  12. Click OK.
  13. When prompted to restart, select Restart Now.

For Linux guest operating systems:

Refer to the documentation for your particular Linux distribution. You may need to install additional software packages on your system to support sound. When configuring the sound, use the following parameters:

  • IO Port -- 0x220
  • IRQ -- 5
  • 8-bit DMA -- 1
  • 16-bit DMA -- 7

Known Sound Limitations With VMware Products

  • Sound support is limited to Sound Blaster compatible PCM (Pulse Code Modulation) output. This includes the ability to play .wav, .au and Real Audio formats.
  • MIDI sound is not supported.
  • Game ports/joysticks are not currently supported.
  • Sound does not work well with several games, especially fast, interactive games.
  • VMware GSX Server does not support the DirectSound capabilities of DirectX within a virtual machine.

Troubleshooting Sound

For information on troubleshooting sound issues with VMware GSX Server, see Issues with enabling sound.

Related topics:

© 2001-2002 VMware, Inc. All rights reserved.

I've been unable to get sound input working on my windows 10 guest for some time now. I don't honestly know at what point the problem arose, as I rarely use this guest anyway, and even more rarely need sound input. Unfortunately, now I really need the sound to work as a new client uses a microsoft-only web-conference tool.
The symptoms (I should note that my host's sound works just fine) are one of several situations. In most configurations, when windows boots, there's a little red X over the loudspeaker icon in the tool-tray thingy. If I click on this, it launches some kind of diagnostic tool which ponders for a while, then says something on the lines of 'I've installed a new driver, reboot' but when I reboot, the whole thing is the same. For some configurations of VB, I can get sound output, but still no input.
I've upgraded VirtualBox to the lastest version (as of today -- 5.1.22), and have upgraded several times over the life of this problem. Each time I have installed the corresponding guest additions. I have tried Intel, Soundblaster and HC-er,whatever hardware emulation, and also OSS, ALSA, and Pulse.
I can get *output* but only output using Pulse and the Intel hardware emulation. If I select ALSA and ... I forget which, but one of the hadware emulations, I get evil sound that's about half-speed, but also no input. With OSS, the boot process for the VM gets a VB message saying that no sound could be opened, and while windows thinks it's making sounds (volume controls show, that kind of thing) there's no output.
In the VM settings, audio shows as enabled, but of course there's no separation between input and output. When configured in Pulse/Intel mode, in the pulse volume control tool, it shows the VirtualBox / Windows 10 in the recording devices tab, and shows a moving VU meter (which is almost insulting, really! ) See the attached image.

Sound Cards 7.1

Screenshot from 2017-07-14 17-35-21.png (24.33 KiB) Viewed 43333 times
Sound cards creative
Any suggestions? This seems really odd, and is certainly frustrating now that it actually matters to me!
TIA

Vbox Communication Sound Cards App

Simon