Trace microphone redirection from host to guest, then test one plain field inside.

Why Virtual Machines Break voice input usually comes down to the path between the host and the guest session. The host owns the physical microphone. The virtual software decides whether to pass that device through, redirect it, or ignore it. The guest session sees only what the virtual software presents, and the app inside the guest sees only what the guest operating system exposes. A break at any of those three points produces the same result: the app records silence. Draw the three handoffs before you open a settings panel, because each one has its own switch. A drawing also shows which switch you have not touched, which is often the broken one.
There are two common approaches. Device passthrough hands the physical microphone to the guest, so the guest sees the real device and manages it directly. Redirection keeps the device on the host and forwards a stream to the guest, where it appears as a virtual input. Passthrough gives the guest more control but can conflict with host apps; redirection is simpler but depends on the host capture quality and can add delay. Choose one approach per device and write down which you chose, because mixing them creates echo and double capture. Passthrough can also grab the device away from the host while a call is running, so write that risk in the note.
Failures cluster at handoffs. The virtual software may not have permission to capture on the host, the guest may not enable the forwarded device, or the guest may enable it at a different level than the host. Each handoff has its own switch, and a switch that looks on in one place can be off in another. Check each point in order rather than changing several at once. A numbered drawing with a check mark beside each handoff is the fastest way to see which one is still unproven. A handoff that looks enabled on both sides can still fail if the names differ, so compare the exact device names.
Symptoms tell you which handoff is broken. Silence everywhere suggests the host is not capturing. A device that appears in the guest but produces nothing suggests the forwarding is connected but muted or at zero gain. Choppy input suggests a buffer or bandwidth problem. Crackle suggests a level or driver problem. Write the symptom next to the handoff, then test the switch that matches it. Two rounds of this narrow the fault faster than a full reinstall of the guest tools. A silent guest with a moving host meter points to redirection, not to the app. Check the meter before you check the app, because one meter read saves a reinstall.
Fix the host side first. Confirm that the physical microphone works in a host app before opening the virtual session. Note the input level and the device name the host uses. If the host cannot capture, the guest cannot receive anything, and every setting inside the guest is a distraction. Close host apps that might hold the device exclusively, then test the host again before moving on. Write the host result in the same note as the guest result so the two are compared side by side. A host test in a plain recorder is enough to prove the device works, so do not test in the call app first.
Open the virtual software device settings and enable microphone input for the guest. Select the specific host device rather than an automatic option, so a later change of default device does not silently break the path. If the software offers both passthrough and redirection, choose one and write down which you chose. Mixing the two on the same device is a common source of double capture and echo. Reopen the settings after a restart and confirm the choice survived, because some tools reset it when the guest shuts down. An automatic option can switch to a headset the moment it connects, so name the device to avoid the surprise.
Inside the guest, open the input settings and confirm that the forwarded device appears and is selected. Check the level and unmute it if needed. If the guest shows no device, return to the virtual software and confirm the redirection is still on. Some tools reset it when the guest restarts. Save the guest configuration if the software supports snapshots, and note the snapshot name so the setup can be restored in one step. A named snapshot is faster than a memory of which box was checked. A snapshot restored before a test is worth more than three guessed settings, so label it with the date.
Use a fixed restart order. Start the host, confirm the microphone works, start the virtual software, confirm redirection, start the guest, confirm the device, then start the app. A consistent order removes the doubt about which component was not ready. If a restart fixes the problem, record which component was started out of order, because that is the one to check first next time. Put the order in the team notes so a colleague does not invent a different sequence. A restart in the wrong order can leave the guest with no device at all, so follow the checklist literally and rewrite it if a step is ambiguous.
Test voice input inside the guest with a plain field. Open a simple text editor in the guest, start dictation, and say one sentence. Do not test in the app you care about first; a plain field removes the app from the list of suspects. If the plain field works, the path is good and any failure in the real app is an app-level issue. If the plain field fails, stay in the guest settings until it works. Write the field name and the guest build beside the result so a later test starts from the same place. A plain-field pass is the only proof that the path is ready for real work.
Check the guest operating system microphone setting. A guest session can apply its own permission decision to the forwarded device, and that decision may be off by default in a fresh image. Grant access for the app you use and retest. Save the image after the change so a new session starts in the working state rather than repeating the same step. Note the image name and date in the checklist, because a fresh image can quietly undo the grant. A fresh image is the most common reason a working setup regresses overnight, so note the image name in every row. The name is the only clue to the reset.
Measure delay with a stopwatch rather than a feeling. Say a short sentence and note the time until the text appears. A small delay is normal for redirection; a delay that grows across a session suggests a buffer or resource problem. If delay matters for your work, test passthrough as an alternative and compare the two numbers with the same sentence. Write both numbers in the same row so the trade-off is visible in one glance. A delay that only appears under load is a resource problem, not a redirection fault, so test with a shorter sentence to separate the two and write both numbers.
Retest after every image update. A new guest build can change the default device, reset a permission, or replace the sound driver. Keep the test sentence next to the image notes and run it before the session that matters. An update that breaks redirection is easier to fix before a deadline than during one. Schedule the retest on the day the image is published, not on the morning of the meeting. Keep the previous image available for a week after the update. If redirection breaks, restore it and compare the two sessions, because that comparison names the cause. Write it in the image notes.
When the work can stay on the host, keep the typing path there. Voiskey is an AI voice typing app for Mac and Windows that works at the system level: press a shortcut, speak, and text appears at the insertion point in any app or text field. On the host, it uses the microphone the host already manages, so you avoid the redirection chain entirely for drafts that do not need the guest session. That is often the fastest way to keep a deadline while the virtual setup is repaired. A host path also keeps working when the virtual software is restarting, which matters during a deadline.
Download Voiskey for Mac or Windows, install it on the host, and test the shortcut in a plain field. Then test it in the app you use for the same work outside the virtual session. If both work, you have a reliable path for notes, messages, and long drafts that do not depend on guest settings. Save the virtual session for the tasks that truly require it. Write the host path in the checklist so the fallback is not discovered during an outage. A fallback written in the checklist is used; one remembered in a hurry is not. Put the link beside the fallback.
The output is the reason to keep the path simple. Voiskey removes filler words, stutters, false starts, self-corrections, and grammar slips, and it adapts punctuation, formatting, tone, and word choice to the task. It learns names, jargon, acronyms, and spelling preferences, and it supports 100+ languages and translation. At up to 220+ words per minute, about five times faster than typing, it turns a spoken draft into something you can edit rather than rebuild. Review the result before pasting it anywhere, because polish and correctness are separate checks. A pasted draft can carry a replaced term into a document that is harder to correct, so keep the review step.
Keep the boundary clear. Voiskey types into the app in front of you on the host; it does not forward text into a guest session, and it does not repair redirection. If the text must land in a guest app, fix the host-to-guest path and dictate there. If the text can live on the host, use the shortcut and spend the saved time on the work itself. Write both paths in the same note so the choice is explicit rather than improvised. A single note that names both paths prevents an argument later. Update it when the guest image changes.
Standardize the setup so a new session starts in a known state. Write six checks: host microphone works, redirection enabled for the named device, guest device selected, guest level set, plain-field test passes, and the real app test passes. Put a version and a date on the checklist. A session that skips a check should be treated as unverified rather than assumed good. Keep the checklist where the session is launched, not buried in a folder three levels deep. A checklist that is longer than one page is a checklist nobody runs, so keep the six checks visible. Print it if the session launches from a desk.
Keep a working snapshot and a template of the virtual hardware settings. Save the snapshot after the plain-field test passes, and label it with the date and the guest build. When a session fails, restore the snapshot and retest before changing settings one by one. The comparison is faster and leaves a clean state for the next person. Name the snapshot with the guest build so an old snapshot is not mistaken for the current one. A snapshot with no label is a guess, not a recovery plan. Store one previous snapshot beside the current one, since two snapshots cover most mistakes.
Write ticket notes with the checklist results rather than a narrative. Include the host device name, the redirection type, the guest build, the test result, and the one setting changed. A support engineer can read that in seconds and see which handoff is in question. Add the Voiskey path as a workaround for host-side work, with a link to the download page in the team notes. A precise note also makes it clear when the problem is outside the guest entirely. A note with results is easier to support than a description of the symptom. Add the time of the session, because time narrows the window.
Review the checklist each quarter and after any change to the virtual software. Remove checks that never fail and add one only when a real incident would have been caught. Confirm that the snapshot still restores and that the test sentence still matches the current vocabulary. A checklist that is short, dated, and tested is the difference between a recoverable session and a lost afternoon. Assign the next review date before the meeting ends so the document does not quietly expire. A quarterly review is enough if the virtual software changes rarely, and an extra review after a major version keeps the dates honest. Keep the date at the top.
Voiskey does not change how a virtual session shares a microphone. It is an AI voice typing app for desktop computers that works at the system level: press the shortcut, speak, and text appears at the insertion point in any app or text field. Enable redirection in the virtual software first, then dictate in the app you are using.
Run it where you type. If the text must land in a guest app, fix the host-to-guest path and dictate there with a working microphone. If the work can happen on the host, Voiskey places text at the insertion point in any app or text field, which avoids the redirection chain for that draft.
The guest session is probably not receiving the microphone. Check that redirection is enabled for the named host device, that the device appears and is selected inside the guest, and that its level is above zero. Voiskey itself types at the insertion point, so silence points to the path before the app.
Confirm the host microphone, the redirection setting, the guest device, and the guest level in that order, then run one plain-field test. Press the Voiskey shortcut, speak a fixed sentence, and check the insertion point. Save a snapshot after the test passes, and recheck after every image update.

Download Voiskey for Mac and Windows to dictate on the host while the guest is repaired.
Use it across macOS, Windows, iOS, and Android