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)
I've been having this issue since shortly before installing the latest Windows Update last week. Any time I click on a photo within Windows Explorer, a message pops up that simply lists the file path and says "Not Implemented".
This started happening before I installed the update, and it was only upon restarting my computer to solve the issue that the update was installed (I tend to procrastinate updates).
The issue appears to be caused by Explorer. Downloading any random image with my Chrome browser and opening the image from the downloads list successfully opens the image, as does viewing images from within the Photos app itself.
Restarting Explorer from task manager fixes the issue temporarily, but it has always reoccurred after some time. So that's not a permanent fix and having to restart Explorer at least once a day is not ideal. I'm more just worried that this could be the precursor to or symptom of something much more serious. I've never had this problem before, and most issues like this are resolved with a full restart.
I don't know what to do.
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.
Same problem. Same lack of solution. When I install another app and tell Window to use that as the default app, it opens the image. Then when I double click the next image, it fails again and acts like I didn't change the default app or something. There is no way for me to double-click a JPEG and get it to open except putting it on the desktop.
I don’t have a solution, but I’ve figured out the exact steps to make it happen (at least on my computer):
I encourage everyone to go to https://support.microsoft.com/en-us/home/contact and create a service request. If Microsoft has to spend staff resources ($) responding to 300 service requests, they’ll be more likely to fix it. If they hear from no one, they won’t fix it.
Diane wrote: "You need to readd set Photos as the default."
Did that permanently solve the problem? By that I mean, if you keep File Explorer open and try 30 minutes after the last successful opening of a photo, does it work?
I think I may have found a fix. Not to the problem, but just a fix to be able to open my photos.
I opened the current Photos app, went to settings within the app window, scrolled down to where it has an option to download and use Photos Legacy and downloaded it. Once it was installed, I clicked on any photo and that asked my what app I wanted to use to open it. I chose the Photos Legacy app and then checked the box at the bottom to make that my default. Seems to be working so far.
Did that permanently solve the problem? By that I mean, if you keep File Explorer open and try 30 minutes after the last successful opening of a photo, does it work?
I think I may have found a fix. Not to the problem, but just a fix to be able to open my photos.
I opened the current Photos app, went to settings within the app window, scrolled down to where it has an option to download and use Photos Legacy and downloaded it. Once it was installed, I clicked on any photo and that asked my what app I wanted to use to open it. I chose the Photos Legacy app and then checked the box at the bottom to make that my default. Seems to be working so far.
Did that permanently solve the problem? By that I mean, if you keep File Explorer open and try 30 minutes after the last successful opening of a photo, does it work?
I've rebooted, and it still works. I've had to do it for every single file type so far; i.e., jpg, gif, png, etc. This is still clearly an introduced problem, and someone from MS should respond to this thread and tell us what's going on, how/if it's going to be rectified moving forward, or if moving back to legacy applications is going to be the default.
