

- MY USB HEADSET FOR SKYPE IS GOING THROUGH MY SPEAKERS HOW TO
- MY USB HEADSET FOR SKYPE IS GOING THROUGH MY SPEAKERS WINDOWS 7
- MY USB HEADSET FOR SKYPE IS GOING THROUGH MY SPEAKERS WINDOWS
And going back to the Properties window also shows the device name remained as The device still said it was named "Speakers". But, when it went back to the main window (*the screenshot above) "Headset" clicked Apply, which seemed to work, and then clicked Exactly the same as the Laptop speakers do. Properties button there is a TextBox at the top of the Window where you can edit the device's name, which currently says If I left-click the Headset device in that same window and click the
MY USB HEADSET FOR SKYPE IS GOING THROUGH MY SPEAKERS WINDOWS
Given what I described above, it seems like Windows is giving the USB Headset the SAME name as the Laptop speakers causing Windows to be confused. * I think that has something to to with the Device "Name ". *In the screenshot you can see the Laptop Speakers (*2nd device in list) is playing a sound, signified by the green bars, but right clicking the Headset device shows that device is "Testing", when that's not what I chose to test. This was taken while the test sounds were playing through the laptop speakers and I R-clicked the Headset device. Then, while leaving that right-click menu up, once the sounds stop from the laptop speakers it switches back to just "Test" it says "Stop Testing" like it's testing through that device. "Speakers" while the sound is still playing for the Laptop speakers, instead of it saying " Test ", a sound begins playing and if I can quickly go and right click on the Headset Now, what is happening is that when I right-click the Laptop "Speakers" and I click on Which will cause a sound to be played through that specific device. And I noticed Windows is giving my headset the SAME name as the laptop's speakers.įrom the Playback Device s window you can right-click each device and click In there they talk about theĪudio device's Names.
MY USB HEADSET FOR SKYPE IS GOING THROUGH MY SPEAKERS HOW TO
The link above talks about how to set the default audio device. I just discovered something today that I think might be causing the issue. Levels tab of this same Properties window is completely empty. "No Jack Information Available" in the Jack Information section of that tab. Propertie s button, the General tab displays Also, not sure if it means anything, but if I click onto the headset icon in the screenshot above and click the Doing any of these steps removes the red X from the speaker icon on the taskbar OR- clicking the Disable button on that device in Device Manager. If I unplug the headset from the USB port -OR- I go to the VMWare Menu: Virtual Machine > Removable Devices > Plantronics C320 > Disconnect (Connect to Host) This by right-clicking the speakers and clicking the "Set as Default Device" Also, it lists the headset as the default device, and I am unable to change Then, doing the same for the headset does nothing, don't hear anything. "Test" successfully tests the speakers and I can hear the sounds from the laptop's speakers. Right-clicking the laptop speaker icon and clicking ( *screenshot below), I can see my Speakers and the Headset listed there. If I right click the speaker icon with the X and go to the Playback Devices menu sounds from the Win7 VM) whether the headset is connected or not. However, sounds through the regular speakers seem to work just fine If I unplug the Headset the red "X" disappears from the speaker icon instantly. Once the USB headset is connected to the VM the speaker Icon in the notification area of the taskbar gets a red X thrown over it, and hovering the mouse over it, it says (*not sure exactly when or what caused it to start doing this). This has worked just about everytime I have connected it to the Win7 VM without problems until a few weeks ago
MY USB HEADSET FOR SKYPE IS GOING THROUGH MY SPEAKERS WINDOWS 7
I have a Plantronics USB Headset that I have used many many times on this Windows 7 Guest OS, for things like the Cisco IP Communicator. *Sorry for the long post, I tried to include everything I have tried and seen regarding this issue.
