You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
Have upgraded to Catalina on a mid 2015 macbook pro and now MS Word (office 365 16.30) is not working correctly. Unable to highlight and select text. Freezes, lags, refuses to select correctly and/or weird display glitches. Have run checks on mac and reinstalled office but problem persists. Any fixes?
MacBook Pro
Same mid-2015 MBP, same problem. Happens for me on both Microsoft Word 16.30 and 16.31. I get what looks like a ~10sec lockup upon text selection in Word. During that time, mouse movements still render but the rest of the OS doesn’t visibly update until the lockup passes, at which point the screen is redrawn. Seems that it’s a graphics card issue: my system logs show Word causing a GPU Reset / DumpGPURestart each time. Evidently it’s not a hard lockup, as other applications seem to continue working while the screen is non-responsive.
From my testing, it appears the lockup only happens when the discrete graphics card is active (and despite the fact that the discrete card may have not been activated by Word, but rather, some other app). Note that any external display connected through Thunderbolt will automatically activate the discrete graphics card.
For now, a workaround is to ensure only the integrated graphics card is running, in which case Word seems to run smoothly.
Same mid-2015 MBP, same problem. Happens for me on both Microsoft Word 16.30 and 16.31. I get what looks like a ~10sec lockup upon text selection in Word. During that time, mouse movements still render but the rest of the OS doesn’t visibly update until the lockup passes, at which point the screen is redrawn. Seems that it’s a graphics card issue: my system logs show Word causing a GPU Reset / DumpGPURestart each time. Evidently it’s not a hard lockup, as other applications seem to continue working while the screen is non-responsive.
From my testing, it appears the lockup only happens when the discrete graphics card is active (and despite the fact that the discrete card may have not been activated by Word, but rather, some other app). Note that any external display connected through Thunderbolt will automatically activate the discrete graphics card.
For now, a workaround is to ensure only the integrated graphics card is running, in which case Word seems to run smoothly.
No. When Catalina updated to 10.15.1, I went from having 10-15 seconds of the computer hanging to having my computer reboot entirely and Bluetooth stop working until I did a hard reset.
So it's actually much worse.
I had MS Auto-update turned off, so I'm not sure how it ended up reverting to 16.30, but reinstalling Word 16.29 solved the problem once again.
I experienced the problem getting worse when I updated to 10.15.1 It actually crashes the entire machine, now if I drag an open word document from one screen to the next and highlight some text the computer crashes. I get what I assume is the equivalent of the windows blue screen of death but for a mac - something I've never seen before. The only work around is not to use a two screen set up when using Word. Or as I've taken to do now - only use Word on my ipad. Don't think this will be priority for either party to fix.
Have tested this and you are right it is when it is connected to a second monitor. So graphics card issue. Thank you so much for figuring this out!!
You might try asking in the Microsoft Product Help Communities.
Yes I’ve done this already - expecting they’ll probably point me to this forum. Asking in both places to maximise chances of help, long shot I know.
Downgrading to MS Word 16.29 also solves the issue. The problem only seems to manifest in Word 16.30.
Does the Word 16.30 issue resolve when updating to Catalina 10.15.1?
Microsoft Word 16.30 text selection via mouse not working
