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

Anonymous
2020-09-15T16:03:06+00:00

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.

Microsoft 365 and Office | Word | For home | Windows

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

78 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-10-21T11:05:29+00:00

    The program found corrupted files and repaired them.

    The issue was off ... until this morning !

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-10-20T18:27:43+00:00

    Ok, I found the administrator mode for command prompt.

    The command is running now

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-10-20T18:24:46+00:00

    In the command prompt, I wrote : DISM.exe /Online /Cleanup-image /Restorehealth

    but it tells me that my admin rights are not elevated enough (error 740).

    It's strange because my account is admin.

    Was this answer helpful?

    0 comments
  4. Stefan Blom 352.3K Reputation points MVP Volunteer Moderator
    2020-10-20T18:13:15+00:00

    I am not familiar with Forticlient, but you could run the System File Checker to ensure that system files haven't been damaged (see https://support.microsoft.com/en-us/windows/using-system-file-checker-in-windows-10-365e0031-36b1-6031-f804-8fd86e0ef4ca).

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-10-20T17:43:15+00:00

    No cleaning software.

    But, I remember now that the issue began about the same time that I uninstall Forticlient, the procedure of which being quite complicated (asystem engineer I know did it, cause I couldn't on my own). May be should I ask him ...

    Was this answer helpful?

    0 comments