> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.playability.gg/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Mute Physical Mouse and Keyboard Input on Windows

**Mute input** can stop selected physical keyboard or mouse input from reaching Windows applications while PlayAbility sends the replacement action. It is opt-in, disabled by default, and available only on supported Windows systems.

> **Important:** This feature uses a low-level input hook. Some games or anti-cheat software may treat input hooks as suspicious. Enable it only if you understand and accept that risk.

## Before you enable muting

1. Memorize the emergency shortcut: **Ctrl+Shift+Alt+F12**.
2. Close competitive or anti-cheat-protected games while configuring the feature.
3. Prepare a safe application, such as an empty text document, for the first keyboard test.
4. Make sure you can use another input to turn muting off if needed.

The emergency shortcut turns **Mute input** off everywhere while the hook is active.

## Unlock the mute controls

1. Open **Settings → Advanced**.
2. Find the **Mute input** card.
3. Turn on **Allow OS-level mute input**.
4. Read the confirmation about low-level hooks and anti-cheat software.
5. Select **I understand, enable**.

Unlocking the feature does not yet block anything. It makes **Mute this input** available in eligible mappings and exposes the main **Mute input** switch.

## Choose which mappings to mute

1. Open **Mapping** and select the profile you want to use.
2. Edit a mapping with a physical **Keyboard**, **Mouse**, or **Mouse Motion** trigger.
3. Turn on **Mute this input** below that trigger.
4. Save the mapping.
5. Repeat only for the physical inputs whose original action should be blocked.

Gamepad, face, head, voice, dwell, and cursor-stabilizer triggers cannot be muted at the operating-system level.

## Review the blocked inputs

1. Return to **Settings → Advanced → Mute input**.
2. Review **Inputs to mute (this profile)**.
3. Confirm that every listed key, mouse button, mouse movement, or wheel input is intentional.

A muted **Mouse Motion** mapping blocks physical mouse movement while muting is active. A muted scroll trigger can block the mouse wheel.

## Turn Mute input on

1. In the **Mute input** card, select the **Mute input off** button so it changes to **Mute input on**.
2. Alternatively, use the **Mute input** control in PlayAbility's right navigation area after the feature is unlocked.
3. Test one configured input in the safe application.
4. Confirm that the original input is blocked and the mapped PlayAbility output is sent.
5. Press **Ctrl+Shift+Alt+F12** once to confirm that the emergency shortcut turns muting off.

Repeat the final test before using the feature in a game.

## Turn muting off

Use any of these methods:

- Select **Mute input on** in Settings to turn it off.
- Use the **Mute input** control in the right navigation area.
- Open the system tray menu and select **Disable input blocking**.
- Press **Ctrl+Shift+Alt+F12** while the input hook is active.

Turning off **Allow OS-level mute input** also disables active muting.

## Verify safe operation

1. Turn muting on with only one test mapping configured.
2. Confirm that the original physical input is blocked.
3. Confirm that its remapped output activates and releases correctly.
4. Press **Ctrl+Shift+Alt+F12**.
5. Confirm that normal physical input returns before opening a game.

## Troubleshooting

### The Mute input section is missing

The feature appears only on Windows systems where OS-level input muting is supported.

### Mute this input does not appear in a mapping

- First enable **Allow OS-level mute input** under **Settings → Advanced**.
- Use a physical **Keyboard**, **Mouse**, or **Mouse Motion** trigger.
- The option is not available for other trigger types.

### The original input still reaches the game

- Confirm that **Mute input** is on, not merely unlocked.
- Check that **Mute this input** is enabled on the active profile's mapping.
- Review **Inputs to mute (this profile)**.
- Some applications use Raw Input or another input path that may bypass the hook.

### The remapped action is also missing

- Turn on **Main Output** and the required gamepad, keyboard, or mouse output.
- Confirm that the correct profile is active.
- Test the mapping with muting off first.

### The pointer or keyboard feels stuck

Press **Ctrl+Shift+Alt+F12** immediately. If PlayAbility is in the tray, use **Disable input blocking** from the tray menu.

## Limitations and safety

- Raw Input and anti-cheat behavior varies by game.
- Muting mouse motion affects the physical pointer while active; configure and test an emergency path first.
- Use the smallest possible list of muted inputs.
- Do not enable OS-level muting in an anti-cheat-protected game unless you accept the account and software risk.

## Related articles

- [Use Mouse and Keyboard Inputs or Remap Keys](https://help.playability.gg/en/article/use-mouse-and-keyboard-inputs-or-remap-keys-1i7zdg/)
- [Map Inputs to Keyboard Actions](https://help.playability.gg/en/article/map-inputs-to-keyboard-actions-b9pj1d/)
- [Map Inputs to Mouse Actions](https://help.playability.gg/en/article/map-inputs-to-mouse-actions-1fkp0wl/)
- [Recover from Stuck or Unexpected Inputs](https://help.playability.gg/en/article/recover-from-stuck-or-unexpected-inputs-187f6b2/)