Yes ajith, I have varied reasons for using VB on a win host and whatever guests. I have linux guests and other this voxcommando win10 guest. I dont really think the host os should particularly matter?
I may migrate my VM to a different host. Previously I was using my Air and as an open mic system but again, the hw of my MBA is having a harder time keeping up over time. Currently my most flexible host that i want to mess around w/ w/o impacting other things is this win10 host.
The ability to backup/snapshot/migrate a VM to other host systems being another reason.
Snapshotting before installs and changes to test/troubleshoot such as this.
I will try to go over some of your suggestions but may be a bit I think another busy week ahead. Thanks for insight. It would be nice to get on that win10 host with lots of RAM/CPU and the RF range of the Amulet.
However that link I believe was based on the win10 tech preview, and my amulet works in win10 Natively.
I did try do change to the other audio controllers but those didn't seem to recognize the remote properly at all let alone the audio but I can try again.
So its a Win10 guest VM inside a Win10 host! Like Nime5ter, I too was under the impression you were running something else (Linux) as the host OS. I'm sure you'll have your reasons for the redundancy
Sadly, my experience is with VB on Linux hosts. I don't have a Win 10 machine to try it either.
I had a bit of struggle initially to make the Amulet mic work on Linux. (See beginning of this thread) Part of the problem was some permission related issues. I had to add my Linux host user to a "vboxusers" group. Now I'm wondering if the current problem is similar. Try running VirtualBox as Administrator, see if you can "allow" VB through UAC, etc. Also, try playing around with the VirtualBox Audio Controller. Try the solution in this link: stackoverflow.com/questions/28134018/microphone-in-windows-10-in-virtualbox
Check the Windows Event viewer logs on the guest OS as well as the host for any clues.
-Ajith