/
/

How to Enable or Disable Audio Input in Windows Sandbox in Windows 11

by Mikhail Blacer, IT Technical Writer
How to Enable or Disable Audio Input in Windows Sandbox in Windows 11 blog banner image

Instant Summary

This NinjaOne blog post offers a comprehensive basic CMD commands list and deep dive into Windows commands with over 70 essential cmd commands for both beginners and advanced users. It explains practical command prompt commands for file management, directory navigation, network troubleshooting, disk operations, and automation with real examples to improve productivity. Whether you’re learning foundational cmd commands or mastering advanced Windows CLI tools, this guide helps you use the Command Prompt more effectively.

Windows Sandbox (WSB) is a useful built-in virtualization tool that is accessible in Windows 11 Pro, Enterprise, and Education. This program is useful for running untrusted applications in a computer environment without affecting the host system.

By default, WSB allows audio input, which means applications running in the sandbox can access the microphone. This is useful for testing software that requires voice commands, audio recording, or microphone usage.

However, there are specific situations where you should disable audio input in Windows Sandbox. For example, having microphone access is not ideal if you are running untested software, but it may be necessary when testing apps that need audio access. Thankfully, you can change this setting through Windows Settings, Group Policy Editor, and Registry Editor without having to enable or disable your computer’s microphone.

Methods to configure audio input in Windows Sandbox

📌 Prerequisites:

  • Your computer needs to be running Windows 11 Pro, Enterprise, or Education edition. WSB is unavailable on Windows Home.
  • You need administrator privileges to configure system settings.
  • Make sure you have access to the Local Group Policy Editor (for Pro, Enterprise, and Education).
  • WSB must be enabled in Windows Features. Access this option via Control Panel > Programs > Turn Windows features on or off, then check Windows Sandbox. 

📌 Recommended deployment strategies:

Click to Choose a Method 💻

Best for Individual Users

💻💻💻

Best for Enterprises

Method 1: Windows Settings x
Method 2: Group Policy Editor
Method 3: Registry Editor x

Method 1: Enable or disable audio input in Windows Sandbox via Windows Settings

📌 Use Cases:

  • This can be used on developer machines where users may want to control audio access per session.
  • You can ideally use this to test applications in WSB that rely on voice input.

📌 Prerequisites:

  • You need to have Windows 11 build 27686.1000 or later.
  • You will not need admin privileges to toggle this setting, but you must have elevated permissions to launch WSB.

Follow these steps to enable or disable audio input in WSB via Settings:

  1. Open Windows Sandbox.
  2. Next, look for and click on the three-dot menu in the upper-right corner of the Sandbox window.
  3. Find and select the Audio Input option and toggle it:
    1. Choose On to allow audio input in Windows Sandbox.
    2. Select Off to block audio input.
  4. Close and reopen Windows Sandbox to apply the change.

Method 2: Toggle audio input in Windows Sandbox using the Group Policy Editor

📌 Use Cases:

  • If you are an IT admin, you can use this to configure Windows 11 Sandbox settings in domain-joined systems.
  • Useful for enabling or disabling audio input across all Sandbox sessions to meet security policies.

📌 Prerequisites:

  • You can only utilize this method in Windows Pro, Enterprise, and Education.
  • Tweaking the Group Policy requires administrator privileges.

Here’s how to configure audio input in WSB via the Group Policy Editor:

  1. First, open the Group Policy Editor. Here’s how:
    1. Press Win + R to open the Run dialog.
    2. Type gpedit.msc and press Enter.
  2. On the left-hand side of the window, head to: Computer Configuration > Administrative Templates > Windows Components > Windows Sandbox.
  3. Double-click Allow audio input in Windows Sandbox in the right-hand pane.
  4. Next, in the policy settings window, select one of the following:
    1. Enabled – allow audio input in Windows Sandbox
    2. Disabled – disallow audio input
    3. Not Configured – Default behavior applies (audio input allowed)
  5. Click Apply, then OK.

Method 3: Using the Registry Editor to tweak audio input in Windows Sandbox

📌 Use Cases:

  • IT admins and users can use this method for computers without Group Policy access.
  • Ideal for advanced users or IT technicians setting up test environments.

📌 Prerequisites:

  • To configure the registry, you will need administrator privileges.
  • The device that must be configured must be running Windows 11 version 24H2 or later.

Use these steps to change your audio input settings in WSB:

  1. Open the Windows Registry. 
    1. Press Win + R to open the Run dialog.
    2. Type regedit, and press Enter. 
  2. Next, navigate to the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Sandbox
  3.  Sometimes, the Sandbox key may not exist in the Windows path. You can manually create it using the following steps:
    1. Right-click the Windows key.
    2. Pick New > Key.
    3. Name it Sandbox. 
  4. Next, in the right-hand pane, right-click and choose New > DWORD (32-bit) Value. Name it AllowAudioInput.
  5. Double-click the new value and set the Value data (set to Decimal) to:
    1. 1 = This will allow audio input in Windows Sandbox.
    2. 0 = This will disable audio input in Windows Sandbox.
  6. Click OK, then close the Registry Editor.

⚠️ Warning: Be sure to follow the steps precisely, given that modifying the Windows Registry incorrectly can cause system issues.

⚠️ Things to look out for

Risks Potential Consequences Reversals
Editing the wrong registry key or doing it incorrectly This could break Sandbox audio and affect unrelated settings. Verify the path and correct invalid keys. Just in case, you can back up and restore your Registry.
Group Policy changes have no effect Audio input tweaks may not occur. Double-check the changes, verify, and run gpupdate /force.
Overriding user settings This will prevent users from toggling Sandbox audio in the interface. Be sure to communicate changes to users, especially in managed environments.

Additional considerations when toggling audio input in Windows Sandbox

Disabling audio input increases security

By turning off audio input, you will help protect the host computer from potentially malicious applications trying to access the microphone. This is crucial in environments that require enhanced security and privacy.

Enabling audio input is necessary for testing applications that require microphone access

If you’re testing applications that require voice input, speech recognition, or audio, enable audio input in the app. However, ensure you’ll only turn it on for trusted programs and scenarios.

Group Policy and Registry changes affect all users

When audio input in Windows Sandbox is configured using the Group Policy or Registry Editor, the setting applies throughout the system. It will override user-level tweaks and prevent users from changing the setting inside the Sandbox settings.

Enforce a consistent policy across settings

In enterprise and managed environments, be sure to apply the same configuration across all computers. This will ensure that the computers will behave consistently.

Restart the Sandbox when making changes

Note that audio input changes will not be implemented until WSB is closed and reopened. On certain occasions, especially after a Registry edit, you may need to perform a full system restart.

Configure audio input to match workplace needs and security

Tweaking audio input in Windows Sandbox adds a layer of security in lab and testing environments, which can be deactivated if necessary. There are several straightforward means to approach this task, from Windows Settings to the system-wide Group Policy and Registry Editor methods. You can implement these easily, whether you’re configuring a setting for an individual device or for an entire fleet of computers in a managed environment.

Related topics:

You might also like

Ready to simplify the hardest parts of IT?

NinjaOne Terms & Conditions

By clicking the “I Accept” button below, you indicate your acceptance of the following legal terms as well as our Terms of Use:

  • Ownership Rights: NinjaOne owns and will continue to own all right, title, and interest in and to the script (including the copyright). NinjaOne is giving you a limited license to use the script in accordance with these legal terms.
  • Use Limitation: You may only use the script for your legitimate personal or internal business purposes, and you may not share the script with another party.
  • Republication Prohibition: Under no circumstances are you permitted to re-publish the script in any script library belonging to or under the control of any other software provider.
  • Warranty Disclaimer: The script is provided “as is” and “as available”, without warranty of any kind. NinjaOne makes no promise or guarantee that the script will be free from defects or that it will meet your specific needs or expectations.
  • Assumption of Risk: Your use of the script is at your own risk. You acknowledge that there are certain inherent risks in using the script, and you understand and assume each of those risks.
  • Waiver and Release: You will not hold NinjaOne responsible for any adverse or unintended consequences resulting from your use of the script, and you waive any legal or equitable rights or remedies you may have against NinjaOne relating to your use of the script.
  • EULA: If you are a NinjaOne customer, your use of the script is subject to the End User License Agreement applicable to you (EULA).