This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
After a very recent update of MS 365, I have noticed that the Windows mouse option "Automatically move pointer to default button in a dialog box" is not working in Access and all others MS 365programs (Word, etc.).
On the contrary, the mouse option is working correctly in other non MS 365 programs.
Can anyone confirm that this is a recently introduced bug?
Thanks - Huaca2
======================
Microsoft® Access® para Microsoft 365 MSO (versión 2504 compilación 16.0.18730.20122) de 64 bits
Windows 11 23H2 (compilación de SO 22.631.5335)
======================
A family of Microsoft relational database management systems designed for ease of use.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
"Automatically move pointer to default button in a dialog box" is Still not working in Outlook, MS 365.
Yes, before posting, I checked and rechecked the Control Panel > Mouse > Pointer Options, without any success.
I have restored my MS Office installation and problem persists exactly the same.
I have noticed that the problem seems to occurs only with the new white & red or blue basic dialog boxs [yes/no/cancel, etc.].
I apologize for my unintended delay.
I have just followed your indications and chatted with MS contact support. Apparently, what seems to be a chatbot acknowledge the problem, but it do so by referring to this thread itself, so I'm not quite sure that the Office Team is really aware of the problem. In any case, it doesn't provide a suitable solution.
Let's hope for a quick official solution for this minor, but quite annoying, bug.
Thanks for your support.
I have been trying to address this for a few friends, including myself and found the same circumstances in M365. With everything set correctly, it works everywhere except in M365 applications.
I have been trying to address this for a few friends, including myself and found the same circumstances in M365. As you have found with everything set correctly, it works everywhere except in M365 applications.