Hyperlink insert crashes Office 2016 & Windows 10 Creators Update

Anonymous
2017-03-20T11:30:29+00:00

Hi,

After a lot of searching, I still cannot explain why all office software crashes when trying to insert a hyperlink when latest creators beta is installed (15060).

The crashes all relate to the same DLL ucrtbase.dll.

As soon as I rollback to actual windows version 14393.953 the issue is non existent.

Thanks for your input

Microsoft 365 and Office | Install, redeem, activate | For home | Other

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.

0 comments No comments
Answer accepted by question author
Anonymous
2017-09-12T01:40:41+00:00

But I use the god-mode all the time!  Windows 10/Office 365 is so incredibly buggy, that god-mode makes it easy to use the available tools there.  Why doesn't windows do that naturally, anyway?

I was unable to send an invoice today, thanks to Excel not working its hyperlinks, perhaps Excel's just atheistic?

Fix it, Microsoft.  Please.  NOW!

Hi,

Just put the God mode fille in a seperate folder rather than leaving it in your docs folder. Then you can use your hyperlinks in Excel.

Was this answer helpful?

40+ people found this answer helpful.
0 comments No comments

79 additional answers

Sort by: Oldest
  1. Anonymous
    2017-05-10T19:38:59+00:00

    Hello,

    As per the issue description, this can be due to the different hardware installed in your computer. Since the same issue has been resolved by removing external hardware on your computer, we can try to do it as an initial troubleshooting step and then we can proceed to a clean install before installing them back in. Refer to link for the steps in doing a clean install.

    Update us if this works for you.

    I gave 1703 another try, this time removing my nVidia GTX750 Ti video card, along with my two DVD drives, and it did not resolve the issue. At this point, the only external hardware I have are my Microsoft-branded mouse and keyboard. I can't dedicate anymore time to this, so I'm sticking with 1607 until I see a patch that specifically addresses this ucrtbase.dll crash.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-05-10T20:15:05+00:00

    Thanks for checking Andy.  There are two versions of Insider, Slow and Fast.  The option to submit reports to Outlook directly using File, Support, Contact Support is only flighted to Insider Fast. 

    Can you check if you could switch to Insider Fast to submit the issue?  In Outlook click File, Office Account, Office Insider.  See if you have the option to switch to Insider Fast.  If you are able to switch please confirm the repro on the Insider Fast build before submitting it. 

    I see. I'm sorry, but I'm seeing the problem on a production machine. I can't risk installing early and unsupported builds on it. Too many people rely on me.

    In the other thread one of the Microsoft people reported the bug directly. Can you do that? The fault is a hard one - I can reproduce it at any time and generate any diagnostics you need.

    Andy

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-05-19T08:56:34+00:00

    Same problem here with Windows 10 (b1703) + Office 2016.

    Naam van toepassing met fout: WINWORD.EXE, versie: 16.0.8067.2115, tijdstempel: 0x5918a7b7

    Naam van module met fout: ucrtbase.dll, versie: 10.0.15063.0, tijdstempel: 0xaf2e320b

    Uitzonderingscode: 0xc0000409

    Still no solution?

    Thanks.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-05-19T10:22:21+00:00

    This issue has been around for a while. Nobody can pinpoint the root cause of the issue. I just happened to find that it was caused by my Hauppauge card but some users had issues with SharePoint and their printers.

    This should not be on the Insider radar since it is related to RTM Windows and Office machines.

    Was this answer helpful?

    0 comments No comments