# Slow mouse click response

**URL:** <https://community.folivora.ai/t/slow-mouse-click-response/48163>\
**Category:** Configuration Help & General Discussion\
**Tags:** mouse\
**Created:** [October 30, 2026, 2:41pm UTC](https://community.folivora.ai/t/slow-mouse-click-response/48163 "2026-10-30T14:41:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mythologies](https://community.folivora.ai/letter_avatar_proxy/v4/letter/m/c68b51/32.png) [@mythologies](https://community.folivora.ai/u/mythologies)\
**Post date:** [October 30, 2026, 2:41pm UTC](https://community.folivora.ai/t/slow-mouse-click-response/48163/1 "2026-10-30T14:41:36Z")

</div>

Hey everyone!

I've recently encountered some strange behaviour when using the MX Master 3S on macOS 27.0.1. When I start dragging a file, the left mouse button seems to register with a noticeable delay. As a result, another file may get selected, or the mouse may start selecting multiple files instead of dragging the intended one.

In the video you can see it happening – I click and hold the left button when the pointer is over the file.

The problem disappears after I restart Mac, but returns after a while.

---

<div class="post-metadata">

**Author:** ![Andreas\_Hegenberg](https://community.folivora.ai/user_avatar/community.folivora.ai/andreas_hegenberg/32/39221_2.png) [@Andreas\_Hegenberg](https://community.folivora.ai/u/Andreas_Hegenberg)\
**Post date:** [October 30, 2026, 2:46pm UTC](https://community.folivora.ai/t/slow-mouse-click-response/48163/2 "2026-10-30T14:46:10Z")

</div>

while I haven’t encountered something like this, Apple has fixed various drag related issues on macOS 27.2!

---

<div class="post-metadata">

**Author:** ![mythologies](https://community.folivora.ai/letter_avatar_proxy/v4/letter/m/c68b51/32.png) [@mythologies](https://community.folivora.ai/u/mythologies)\
**Post date:** [October 30, 2026, 2:51pm UTC](https://community.folivora.ai/t/slow-mouse-click-response/48163/3 "2026-10-30T14:51:01Z")

</div>

Whoops, somehow missed it, updating as we speak. We'll see it if the problem returns, thanks!