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)
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
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.
I'm still running Adobe reader XI so it's not due to an Adobe update. It's typical Microsoft creating bugs with their trashy updates and the MS techs who are clueless as to how the system operates so all they can suggest is to reinstall your operating system.
I peg it to the May Comprehensive Update for Windows 10. Didn't have the problem before that update. Since when is "#" not an acceptable character in a file name? I have thousands of files with "#" in the name and I don't want to have to go through and rename each one because MS messed up the preview function.
Continued searching and found out that Adobe had an update it did not automatically install. Once I updated, the "#" wasn't a problem. So you might want to check that if the files are .pdf files.
Very interesting. Yes, they were pdf files. I'm not upgrading my version of Reader so it was easier for me to rename the trouble files. If you do decide to rename your files, I strongly suggest getting a free program called Bulk Rename Utility (BRU). It has saved me a ton of work and the GUI is very detailed and well layed out. From the first time I used it, it all made sense. Thanks for the info.
I peg it to the May Comprehensive Update for Windows 10. Didn't have the problem before that update. Since when is "#" not an acceptable character in a file name? I have thousands of files with "#" in the name and I don't want to have to go through and rename each one because MS messed up the preview function.
Remember that the file is actually still there but just shows as an error. Windows 10 may well fix it in the next update - or am I too optimistic?
