Error message when opening word doc: "Not Implemented" (Word for Windows)

Hi,

When I try to access a word doc from the folder, after clicking on it an error appears that only says "Not Implemented".

I have restarted and updated my computer and used the repair function for Microsoft word, but to no avail. I am fortunately able to access the document by first opening word then opening the document that way, but I would like to simply find the file I am looking for and open it that way. 

Thank you for your help.

My wife is having the same issue. It is an intermittent issue that comes and goes, sometimes as quick as her calling me into her sewing room, it will not act up. Other times, it happens for a while. Nothing seems to fix it outright and it is really frustrating.

1. She has Microsoft Word 365 and is on the current version
2. The documents are located in My Documents, which is under One Drive.
3. The only add-in installed on Word is Acrobat. I have disabled it, restarted Word, and that did not fix the issue.
4. All documents will open with the Open command from the inside word, but they open with 'Compatability Mode', even with documents that have been created with this version of Word. This is very inefficient for her because she works with documents all day long.
5. I have repaired Word a couple of times. This doesn't fix it either.
6. I have added My Documents to the Trusted Sites.

This is been a problem that I have not been able to find a fix.

The same problem has started back up again now, smh.

Same problem for me, since seven days or so (since last windows update ?).

Also with Excel.

I have Office 2016 on Windows 10.

Note: no problem ever with documents on desktop itself !

Thanks for help. It's very frustrating.

Is the doc on the local PC or?

Can you open Word itself and create a new doc?

Hold the Cntrl key when starting word/that doc to force safe mode, if all OK then

Within Word>File>Options>Add-ins>Manage Com Add-ins>Go....... what is listed whether active or not?

It is NOT document related, it is something to do with the shell handler for Microsoft365 documents.