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)
I'm running Microsoft Word 16.67 on an M1 chip MacBook Pro with Mac OS 12.4 and I notice that in Word, I can't use the mouse to select text. I can point to text anywhere in the document, but when I left-click the mouse to select a block of text, nothing happens...the cursor moves with the mouse, but the text is not selected. The only way I can select text blocks is with the shift-arrow keys.
Prior to upgrading to my M1 MacBook Pro, I had a 2016 MacBook Pro that never had this problem.
I have other Microsoft apps installed on this computer, including PowerPoint, Excel and so on - none of these other apps have this problem...turns out only Word (and Outlook) have this issue.
This problem has existed for a few versions of Word now - I've been updating to the latest Word and MacOS versions and nothing seems to make a difference.
I saw another user ask a similar question and he was told to reboot into safe mode - I tried that with no success either.
Any idea what I can do about this?
A family of Microsoft word processing software products for creating web, email, and print documents.
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.
Answer accepted by question author
The version of macOS you cited [12.4] is behind on updates. Version 12.6 is current for Monterey. It's pointless to troubleshoot if all is not current. I'd suggest updating the OS followed by a Restart of your Mac. Once the OS is current the Restart seems to resolve the issue for most users who have reported the issue.