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
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

79 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2017-04-17T17:14:59+00:00

    Thanks for that. Rolling back would be preferable to me than a reinstall!

    I'm  going to wait to see if there's a patch. Given it's two Microsoft products that cause the crash, I'm hopeful.

    Andy

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-04-19T11:17:39+00:00

    In my case, the issue happened with the base installation of Office 2016 (x86), along with the most recent updates (16.0.4498.1000). I couldn't revert back to 1607, and was forced to do a clean install. I figured I'd give 1703 a shot, so I booted up with that and got Windows installed, and then Office 2016. The problem occurred immediately, before I had gone through and updated any device drivers (so it was using drivers that Windows already had), and my printer wasn't on so I can at least rule that out. I wasted two days getting my computer back on 1607, and am deferring the update until it's resolved.

    That said, in case this actually helps, here is a list of all of the hardware on my machine:

    Motherboard: ASRock Z97 Pro4 (LGA 1150)

    Chipset: Intel Z97

    CPU: Intel Core i7-4790K

    LAN: Intel I218-V

    Audio: Realtek ALC892

    Video: MSI GeForce GTX 750 Ti

    HD: Samsung SSD EVO 850

    HD: Seagate Barracuda ST2000DM001 (x2)

    Mouse: Microsoft IntelliMouse Explorer 3.0

    DVD-R: Samsung SH-S223F (x2)

    Monitor: Dell 2407WFP-HC

    I guess I could have tried uninstalling most of these drivers, but given the fact that updating every single one of them with the most recent version didn't help, I figured I'd just be wasting more of my time.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-04-19T13:39:08+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.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-04-19T15:38:58+00:00

    I'm using a bog standard Dell laptop. I have no external hardware to remove!

    All I did was install the creators update and Office immediately started misbehaving. The OP said he could resolve the problem by rolling Windows back from the creators update. Looks pretty conclusive to me that something involved with the creators update is responsible. It's possible that messing about with hardware causes something to get reinstalled that fixes the issue (looks like a DLL incompatibility to me), but that's not going to work for me.

    When you say a 'clean install' do you mean Office 365? I'm prepared to give that a try if you can let me know how to do it. As it happens, I got an automatic Office 365 update which rolled me back a version from 1703 to 1702. Presumably the update process got messed up or there's been a reversion.

    Andy

    Was this answer helpful?

    0 comments