A family of Microsoft word processing software products for creating web, email, and print documents.
I'll send a question about this to the Office team, and I'll post back with more information as soon as I receive it.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Split from this thread.
I have the same issue on a brand new Dell XPS. What's interesting to me is that I only see the issue on hyperlinks within Office apps like Word and Outlook. Everywhere else the cursor behaves normally.
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.
I'll send a question about this to the Office team, and I'll post back with more information as soon as I receive it.
I believe I have noticed this problem in an occasional non-MS application. The paint.net free photo editing program springs to mind. (For what its worth...)
The fact that the problem occurs even outside Office programs points back to the display driver as a possible culprit, or a Windows update, or a combination of factors.
It took a while, but I have now seen this happening, occasionally, on a computer from HP (Probook 430 G4) whose default scaling (in Windows Settings) is set to 150%.
Please report back in this forum if a solution is found.
I have a user with the same issue with a Surface Pro, Office 365, Logitech mouse, 1920x1080@100%.
All drivers and software up-to-date.
Thank you for your response.
Coincidentally, the phone support people sent me here quite some time ago. Their suggestions for fixing the issue were the standard, basic, expected answers. ("Have you downloaded the current video drivers?" Yes. "Have you updated your computer?" Yes. "Have you uninstalled and reinstalled [insert piece of hardware]?" Yes.) When they got to the "completely reinstall Windows and all of your software" we were done talking.
Oddly, despite my belief and suggestion that this issue started after switching from a 1600x1200 monitor at 100% scaling to a 3840x2160 monitor with 150% scaling, no one has pursued that direction. NOTE: I have two systems (i5 and i7, both Win10, both mid to high end Nvidia cards) that were both running 1600x1200 at 100% scaling and were changed to 3840x2160 at 150% scaling, and BOTH systems have this issue. This too is an odd coincidence?
:)