Office 2016 crashing when hyperlinks clicked

[themightymrp]

Noticed a number of people complaining this morning that when they click hyperlinks in Powerpoint documents, the programs crashes.

 

I've investigated and found that one of the new Office updates, KB4462238, is the cause of the issue. Uninstalling it fixes it. I've currently set it to remove via my WSUS server.

 

I love the description of the KB update on Microsoft:

 

"After this update is installed, clicking a hyperlink in an Office application, such as Word, PowerPoint, Excel, or Outlook, may cause the application to stop working. If you experience this issue, you can uninstall the update"

[FishCustard]

I'm guessing they only noticed this after release, given that the update's been pulled.

[themightymrp]

Ahh didn't know it had been pulled?

 

EDIT - just notice the line at the top of the KB page.

[themightymrp]

Is anybody else getting this problem even when the above update number isn't installed? I've got a small hand full of machines crashing on powerpoint hyperlinks and can't figure out if another update has mangled it or if this one from this thread has just left it in a bad state after removal?

[o1o1o1o1]

I am getting this problem on MY computer. The same file presents no problem on ANOTHER computer. I have tried rebuild. No luck.

[themightymrp]

I'm still seeing this on random machines, any thoughts?

[FishCustard]

Attach a debugger (e.g. windbg), get a crash dump, see where it's faulting perhaps? Happy to look at a crash dump.

[ComboSmith]

Hi,

 

Does anybody know of a fix for this? We haven't got the update installed anywhere, reinstalling Office does nothing. It is affecting all our machines running LTSC 1809

 

It does seem to load the link eventually if left completely alone but it can take a few minutes and clicking the mouse will cause powerpoint to crash. The event viewer can only tell me it was an unknown hang

[themightymrp]

If you install a flat copy of Windows and Office, with no updates at all, does it work then? If so I would have to assume another update, probably later than the one mentioned above, is causing the issue.