[Bug]: Horizontal wheel volume control triggers Windows Task View unexpectedly

[FQZ2333]

Pre-flight checklist

• I searched existing issues and this is not a duplicate.
• I am on the latest release or a recent master build.
• I quit Logi Options+ before running OpenLogi (the two apps fight over HID++ access and only one can own a receiver at a time).

Which part of OpenLogi?

GUI (desktop app)

OpenLogi version

0.6.22

Operating system

Windows

OS version & architecture

Windows11 26H1 28120.2546, x64

Device model

MX Master 3S

How is the device connected?

Logi Bolt receiver

Affected area(s)

• Device discovery / detection
• Button remapping
• DPI control
• SmartShift
• Per-application profiles
• Battery status
• Settings / configuration (TOML)
• Auto-update
• Menu bar / tray
• Other

What happened?

1. Open the software and navigate to button/wheel remapping settings.
2. Assign the horizontal wheel to “Volume Up” (for one direction) and “Volume Down” (for the opposite direction).
3. roll the horizontal wheel in either direction.

Expected behavior: The system volume should increase or decrease accordingly, with no other actions triggered.

Actual behavior: The volume does change, but Windows Task View (the virtual desktop overview) also opens immediately after each roll. It appears as if the horizontal wheel is sending the Win + Tab shortcut or triggering the Task View button.

Steps to reproduce

1. Open the software and navigate to button/wheel remapping settings.
2. Assign the horizontal wheel to “Volume Up” (for one direction) and “Volume Down” (for the opposite direction).
3. roll the horizontal wheel in either direction.

Expected behavior: The system volume should increase or decrease accordingly, with no other actions triggered.

Actual behavior: The volume does change, but Windows Task View (the virtual desktop overview) also opens immediately after each roll. It appears as if the horizontal wheel is sending the Win + Tab shortcut or triggering the Task View button.

Diagnostics report

### OpenLogi Diagnostics

**App**
- OpenLogi (GUI): v0.6.22 (release)
- Agent: v0.6.22 (connected)
- IPC protocol: GUI 10 / agent 10
- Inventory: ready
- OS: Windows (x86_64)
- Locale: zh-CN (UI: follow system)
- Accessibility: granted · Input hook: installed
- Launch at login: yes · Menu bar: yes · Update check: on
- Running from: source build (dev)
- Config: schema 3 · 2 configured device(s) · thumbwheel 100

**Assets**
- Source: user cache · Index: loaded (210 models) · User cache: present
- Cache path: C:\Users\21061\.local/share/openlogi\assets · Bundle assets: absent

**Devices (3)**
- MX Master 3S — mouse (codename: MX Master 3S)
  - Connection: Logi Bolt receiver · Online: no · Battery: 60% (discharging, full)
  - Capabilities: buttons=yes, pointer=yes, lighting=no
  - Model: receiver:39c9c141742607e9:slot:1 (wpid: b034, model-ids: b034/0000/0000, ext-model: 00)
  - Transports: BTLE
  - Render: mx_master_3s · Slot 1
- MX Master 3S — mouse (codename: MX Master 3S)
  - Connection: Logi Bolt receiver · Online: no · Battery: 60% (discharging, full)
  - Capabilities: buttons=yes, pointer=yes, lighting=no
  - Model: receiver:39c9c141742607e9:slot:2 (wpid: b034, model-ids: b034/0000/0000, ext-model: 00)
  - Transports: BTLE
  - Render: mx_master_3s · Slot 2
- MX Master 3S — mouse (codename: MX Master 3S)
  - Connection: Logi Bolt receiver · Online: yes · Battery: 60% (discharging, full)
  - Capabilities: buttons=yes, pointer=yes, lighting=no
  - DPI: 1000 dpi (range 200–8000, 157 steps)
  - Model: receiver:39c9c141742607e9:slot:3 (wpid: b034, model-ids: b034/0000/0000, ext-model: 00)
  - Transports: BTLE
  - Render: mx_master_3s · Slot 3

**Receivers (1)**
- Logi Bolt Receiver (VID 046d / PID c548)

openlogi list output

Logs

macOS permissions (if applicable)

• OpenLogi has Accessibility permission (needed to remap buttons via the event tap).
• OpenLogi has Input Monitoring permission (needed for Bluetooth-direct devices and capture).

[linear-code]

OLG-175