Share via

File Not Found Error In Preview but the File IS There

Anonymous
2022-03-21T19:35:46+00:00

Never seen this message before. Win 10 Preview Pane. I get an error that says "File Not Found Error It may have been moved, edited, or deleted"

ERR_FILE_NOT_FOUND

I'm getting this in one particular folder and it's sub folders. The file will open

Windows for home | Windows 10 | Files, folders, and storage

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

33 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-05-24T17:52:35+00:00

    Thank You! My file did have a # in the File Name, I deleted it/renamed the file with the # and the Preview problem was fixed!

    22 people found this answer helpful.
    0 comments
  2. Anonymous
    2022-05-26T03:21:13+00:00

    THANKS! I was having this issue too. Deleted the # and it works great. Your simple observation just saved me hours of frustration trying to follow all the worthless "fixes" offered by the MS experts. I love how they all say they will stay and help you but as soon as they run out of canned replies they vanish.

    12 people found this answer helpful.
    0 comments
  3. Anonymous
    2022-06-05T02:48:28+00:00

    Thank you, it worked.

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2022-06-08T23:33:50+00:00

    You're a Genius. This worked like a charm

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2022-06-13T21:01:34+00:00

    OMG, you are a genius, thank you. This has been bugging me for a while but I haven't tried to do anything about it until now because it's only a minor annoyance. As a matter of fact, it's unlikely I'm going to bother changing all those filenames, but I'm thrilled to know why it's happening.

    This is a new-ish problem, because I have had a # in a certain type of pdf file name foreverrrrr and this never happened until fairly recently (a few months at most, I think). Don't know if was caused by a recent Acrobat update or something else, but it definitely did not always do this.

    1 person found this answer helpful.
    0 comments