Zotero experienced an error updating your document.

benjapatk · August 13, 2024

I'm using Microsoft Word and got an error message saying, "Zotero experienced an error updating your document." This problem also occurs in an empty Word document. I have already followed the troubleshooting steps and reinstalled Zotero, but I could not solve the problem.

How to solve this issue?

Report ID: 183408569

dstillman · August 13, 2024

https://www.zotero.org/support/kb/could_not_find_a_running_word_instance

benjapatk · August 13, 2024

I followed the link mentioned above, but I still encountered an error message.

https://s3.amazonaws.com/zotero.org/images/forums/u14784307/wgwq4s9j71h2msml4go4.png

dstillman · August 13, 2024

Can you provide another Report ID and a screenshot of the UAC settings pane after restarting your computer?

benjapatk · August 13, 2024

https://s3.amazonaws.com/zotero.org/images/forums/u14784307/1ecrd542zfk3qqmebc1e.png

ReportID: 1010859437

adomasven · August 13, 2024

You should move your UAC settings one step up and restart your computer, then see if it works.

benjapatk · August 13, 2024

I followed the guideline above and press "yes" in this notification.
https://s3.amazonaws.com/zotero.org/images/forums/u14784307/8quz5lldnjx64zlqknn7.png

However, I still got the same error message.
https://s3.amazonaws.com/zotero.org/images/forums/u14784307/yo2l558vzqybdw7pyi9v.png

adomasven · August 13, 2024

No, you should not enable Zotero or Word to run as administrator (that checkbox should remain unchecked). You should set your UAC level higher and restart your computer. You should not get a prompt saying "Do you want this application to make changes to your computer?" when running either Zotero or Word.

benjapatk · August 13, 2024

I followed the previous comment, and I received this message after restarting and reopening Zotero.

https://s3.amazonaws.com/zotero.org/images/forums/u14784307/1dv47yy9384wijuw5v0v.png

Now it works fine. Thank you so much!

dstillman · August 13, 2024

Wait, so you're no longer getting the "module record has unexpected status" error?