Pair the office host over Bluetooth first, then connect the gaming PC to the documented USB receiver in its 2.4GHz mode. After both connections work, identify the model-specific control for switching between profiles. This setup can remove a second keyboard, mouse, and cable set from a shared desk, but the exact profile count and hotkey behavior depend on the model. Confirm those details for both peripherals before expecting one synchronized switch from a wireless gaming keyboard mouse combo.
Map the setup before pairing
The clearest starting map is gaming PC → USB receiver → documented 2.4GHz mode, and work laptop → Bluetooth profile. A second office computer can use another Bluetooth profile only when the keyboard and mouse manuals confirm that capacity. Once each host has a clear path, one wireless gaming keyboard mouse combo can serve two jobs without making the active connection a guessing game.
The clean-desk connection map
Place the receiver on the gaming host and reserve Bluetooth for the office host. Pair the office device with the keyboard and mouse according to each product's instructions. Then label the gaming receiver, work laptop, and any second office host in your setup notes. This small record makes the next switch easier because you know which connection you are selecting.
A tri-mode label does not automatically mean the keyboard and mouse share profiles or switch together. One peripheral may use a separate control, and some models may support only one Bluetooth host. For a practical overview of stored device channels and mode choices, see this tri-mode switching guide, but use the exact model manual for your own controls.
The compatibility check before setup
Check both peripherals before pairing. The keyboard and mouse must each support the connection paths you need, and the office host must support Bluetooth. Confirm the number of Bluetooth profiles, whether one profile covers one device or a set, and whether the keyboard and mouse switch independently.
The supplied M3 mouse record verifies 2.4GHz, Bluetooth, and USB-C connectivity for that mouse, along with manufacturer-listed 1000 Hz report rate and 1 ms latency claims. Those mouse-only facts do not verify the wireless modes, profile count, or switching control of an M82 keyboard. If you are reviewing a particular set, use the bundle details as a starting point, then confirm the keyboard documentation. Continue once both peripherals pass the connection and control checks.
2.4GHz vs. Bluetooth: choose the path by task
Choose the documented receiver path for gaming when the product supports that mode, and choose Bluetooth for a supported office host. These terms describe connection methods, not separate frequency bands: Bluetooth operates in the 2.4 GHz band, while a gaming mode may use a dedicated USB receiver. Bluetooth technical details also explain that initial pairing stores connection information for later use.
| Connection path | How it connects | Best fit | Verify before setup | Switching implication |
|---|---|---|---|---|
| Receiver-based 2.4GHz | Dedicated USB receiver to host | Gaming PC when documented | Receiver support and mode control | Select the receiver profile or mode |
| Bluetooth | Direct pairing with a Bluetooth host | Office laptop or other supported host | Bluetooth support and profile capacity | Select the documented Bluetooth profile |
For gaming, the receiver path is a task-based choice when the product documentation assigns that mode to the gaming host. Do not treat the frequency label alone as proof of lower latency. Also, do not extend a mouse-only latency specification to the keyboard or the complete set. For office work, Bluetooth reduces receiver swapping because the host stores the pairing, provided the peripheral remains powered and within range.
If desk simplicity is your main goal, this clean desk combo guide can help frame questions about receivers, battery needs, and connectivity. It does not replace the exact profile and switching specifications for a particular model.
Pair the office device and connect the receiver
Pair the Bluetooth office device, connect the gaming receiver, and test each peripheral on every intended path before trying to switch. This order creates a working baseline and helps show whether a later failure comes from pairing, receiver detection, or profile selection.
Pair the Bluetooth office device first
Turn on Bluetooth on the office host and put the keyboard or mouse into the product-documented discoverable mode. In Windows, select the device under Bluetooth settings and complete the prompts. Microsoft's Windows pairing instructions cover keyboards and mice, including enabling Bluetooth, making the accessory discoverable, selecting it, and completing pairing.
Pair the keyboard and mouse separately unless the product instructions explicitly describe them as one shared Bluetooth device. After each pairing, type a short phrase and move the pointer so you know which peripheral is active.
Connect the gaming receiver second
Plug the documented receiver into the gaming PC. Set the peripheral to its documented receiver-based 2.4GHz mode, then test keyboard input and mouse movement separately. Keep this step model-specific: do not use an assumed universal button, dial, or keyboard shortcut.
If you are using a laptop dock or hub, keep the receiver on the host path specified by the product instructions. The receiver must be detected by the gaming host and associated with the correct peripheral mode, not merely powered.
Record the active host for each profile
Write down the intended map in one line: gaming PC, receiver path; work laptop, Bluetooth profile; second office host, additional documented profile if available. Note whether the keyboard and mouse use shared or independent controls. A simple connection flow keeps the active path visible:
Gaming PC → USB receiver → 2.4GHz mode
Work laptop → Bluetooth profile
Optional office host → another documented Bluetooth profile
Switching control → exact model instruction
Run the documented switching workflow
Use this general sequence after both paths work independently. The supplied evidence confirms tri-mode connectivity for the M3 mouse, but it does not provide a verified M82 keyboard hotkey, profile number, or synchronized keyboard-and-mouse switching behavior. Retrieve those controls from the selected model's official documentation instead of guessing.
- Wake or power on the keyboard and mouse.
- Select the documented receiver mode or Bluetooth profile you want to use.
- Activate the product-documented switching key, button, or dial. If the keyboard and mouse have separate controls, switch each one according to its own instructions.
- Wait for the target host to reconnect, then test both devices. On the office host, type a short phrase and move the pointer.
- Before gaming, return to the documented receiver profile and verify keyboard input and mouse movement on the gaming PC.
A successful switch means both devices respond on the intended host, not merely that one indicator changed. Until the keyboard manual confirms its control, treat keyboard switching and synchronized switching as model-specific steps rather than established features of the complete set.
Troubleshoot the stage that failed
Start with the first stage that failed. A Bluetooth pairing problem needs a different action from an undetected receiver, and neither automatically proves that the switching control is defective.
If Bluetooth pairing fails
Confirm that the office host supports Bluetooth, the peripheral has power, and it is within range and in its product-documented discoverable mode. Toggle Bluetooth off and on, remove the device, and add it again if necessary. Then check the Bluetooth adapter or device driver. Microsoft's Windows troubleshooting checks also advise keeping a sluggish Bluetooth peripheral away from nearby unshielded USB 3.0 devices, which can be a possible source of interference.
If the receiver is not detected
Confirm that the receiver is plugged into the intended gaming host and that the peripheral is set to its documented receiver mode. This is a receiver branch, not automatically a Bluetooth problem. If the host still does not detect it, follow the exact model's receiver-pairing or recovery instructions. Do not apply a generic Bluetooth reset to a receiver failure.
If switching or reconnection fails
First verify the selected profile rather than repeating an unknown hotkey. Check whether the keyboard and mouse switched independently, then confirm that each is assigned to the intended host. For Bluetooth reconnection, revisit power, range, Bluetooth status, and driver state. If the problem remains, consult the model documentation for its profile-selection behavior. A tri-mode label alone cannot identify the correct profile or prove synchronized switching.
FAQs
Can one Bluetooth slot connect both the keyboard and mouse?
It depends on the product's device architecture. One Bluetooth profile may represent one peripheral rather than a complete keyboard-and-mouse set. Check the exact manual for profile count and whether the slot is shared before pairing both devices.
Why does the mouse pair while the keyboard does not?
The two peripherals may have different wireless modes or separate pairing controls. A mouse's tri-mode specification does not establish the keyboard's capability. Check the keyboard's supported Bluetooth mode first, then put that device into its documented discoverable state.
What should I do when the 2.4GHz receiver is not detected?
Treat it separately from Bluetooth pairing. Confirm the receiver is connected to the intended gaming host and set the peripheral to its documented receiver mode. If it remains absent, use the exact model's receiver instructions rather than assuming a universal reset.
Why does the set reconnect to the wrong device after switching?
More than one saved host can make the active profile unclear, especially when the keyboard and mouse use separate controls. Verify the selected profile on each peripheral and use the documented profile-selection control instead of an assumed universal hotkey.
Sources
- Microsoft Support. Pair a Bluetooth device.
- Microsoft Support. Fix Bluetooth problems.
- Intel. How Bluetooth works.
