This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi,
Starting this afternoon, when I copy an paste an HTML-based wiki file (from Zendesk) into Word, I see the attached error.
I perform this operation numerous times, and never saw this notice until today. I have Word 365 Win10.
The problem does not occur when I paste a Confluence page.
Can someone clarify this message for me? What do they mean by "Choosing YES will enable updating all fields in this file..." What fields? And are they talking about the source file or target file?
Thanks!
Stephen
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.
This is a bug in the current build - Microsoft is aware if the issue and working on a fix - but I have no ETA for when it will be fixed.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
leusel365 wrote on 11/16/21
<<
microsoft called me today, it is a bug and should be fixed in the next release. Let's wait and see if it's true.
>>
There have been several Office and Windows 10 updates since then and the problem sadly still exists. I'm still running two machines, one with all the current updates, so I know it's still not working right, and another machine that is rolled back to a previously working version with Office updates turned off, so I can get some work done without this annoying error. That's all I know as of today.
I have the same issue. This bug is a nuisance that Microsoft needs to correct.
Welcome to group. Sadly it's been 6 months+ and Microsoft, for whatever reason, has decided to ignore this error, and has not yet fixed it. I agree. Very annoying!