Windows 10: Echo Issue with all Conferencing software on Virtual machine

Recently upgraded to Win 10 build 2004 and a problem has become very pronounced with other people on a conference call saying they have an echo while talking unless I mute my mic. I am using a full headset with both sound and a microphone, so it's not a speaker/mic issue.

My setup is roughly this. I have an older laptop that I mainly use to connect to a virtual machine. There is a VPN connection also to get onto my work network. I then run almost everything on the virtual machine. I also pass through my microphone from my laptop to the virtual, and before the upgrade I did not get complaints about the echo. I use Microsoft Teams a lot, and it is very noticeable there.

Before I go further, I have done all steps in this document: https://support.microsoft.com/en-us/office/your-audio-device-may-cause-an-echo-124e3b6c-6d01-4db2-94a3-75c0ecc289c3?ui=en-us&rs=en-us&ad=us.

In my testing today, I ran teams directly on the laptop and the echo was not there. So I think this means it is something to do with the pass through to the virtual. I also tested on Zoom and the echo was there, although slightly less.

One other thing we noticed while testing today is that there is a significant delay on the virtual. It seems like it's about 3 seconds between me talking and others hearing it. This delay was also gone when I ran Teams directly on my laptop.

So what steps can I take to resolve this? I really don't want to have to run 2 instances of Teams.

:)

 

Installing a Virtual Machine in Windows 10

Step #1 is to decide which virtual machine software you wish to install.

The three most popular choices are:

• VirtualBox (from Oracle)
• VMWare Workstation Player (from VMWare); and
• Hyper-V (from Microsoft)

Once you've made your choice you can find detailed, illustrated instructions for installing each one on the internet.

As a personal suggestion: You might find it easier to use either VirtualBox or VMWare Workstation Player. Hyper-V is more complicated to setup.

Between VirtualBox and VMWare, I think you'll find VirtualBox more user-friendly, and it has the advantage of allowing you to create checkpoints - backups of your virtual machine - whereas to do that in VMWare you'll need to upgrade to their (expensive!)
paid version.

 

BSOD when launching Virtual Machine

Hi,



Thank you for writing to Microsoft Community Forums.



I appreciate your effort on this. I understand how difficult it could be when the computer doesn’t work as it is supposed to, we will look into this for you. Please reply with the following details to assist you with the appropriate troubleshooting
steps:

• Which application are you using to create Virtual Machine?
  
• Does the issue occur only when launching a Virtual Machine?
  
• Have you reinstalled Windows on the computer?
  
• What is the make and model of the computer?
  

I have analyzed the dump files shared by you. Since the issue occurs when you launch Virtual Machine, I suggest you to try disabling the VMWare USB Arbitration Service and check if that helps. Please follow the steps mentioned below:

1. Press Windows key + R, to open
   Run dialog box.
   
2. Type services.msc and click on
   OK.
   
3. Look for the VMWare USB Arbitration Service and double click on it to open
   Properties.
   
4. Select Disabled from the drop down for
   Startup and Stop the service.
   
5. Click on Apply and OK.
   

Please reply with the status of the issue, we will be glad to help you further.



Regards,

Nikhar Khare

Microsoft Community - Moderator

 

Clean install of W10 not possible in Virtual Machine.


Please get a cup of coffee, lean back and think an answer for these two questions. Take your time, then check the answers below the questions:

Questions:

1. If you do a clean install of let's say Windows 10 Insider Build 10525 on a totally new computer which has never had an activated Windows 10 on it, does it activate?
2. If you do a clean install of Windows 10 Insider Build on a computer where the underlying Windows 10, upgraded from a qualifying old operating system has already been activated, does it activate?

Answers:

1. No, of course not.
2. Yes, of course.

Why do you think that a virtual machine would make any difference? You have tried to install Windows 10 on a totally new machine which has never had an activated Windows 10 installed, therefore the Microsoft activation servers block the activation due invalid machine ID. In the highlighted part in below quote you admit your mistake yourself, plain and simple, yet you when doing this wrong draw conclusion that even if done correctly it would not work:

What you have tried is essentially the same as if you took a brand new real physical PC without any operating system, which has never had any operating system, and then installed Windows 10 Insider Preview wondering why it does not activate! Virtual Machines behave exactly the same way; if you want to clean install Windows 10 Insider Preview and get it activated you must do it on an existing virtual machine, one which has already had an upgraded Windows 10 activated. This "computer", the virtual machine, its machine ID is marked on activation servers as valid and activated and it will of course activate.

Be it a virtual machine or a physical computer, you cannot activate a clean installed Windows 10 Insider Preview on a totally new machine. How difficult can this be to understand?

When clean installing Windows 10 Insider Preview on a computer which has already had a previous Windows 10 Insider activated, you do not use the product key! It will be asked twice, once before the installation starts and once after the last reboot to OOBE phase. In both cases you skip the product key and your Windows will be automatically activated.