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.
I will try clean boot, the only thing is I would have to stay in clean boot for around 24 hours since a restart would temporarily fix the issue.
With this many people reporting the same problem (I just noticed it today - which brought me here) I doubt it's something unique to your computer a clean install will resolve. While it might help temporarily, a Windows Update or other common action, my guess is it's a MS problem and will return.
Just my guess...
Let's be clear: not everyone above should need to run sfc/scannow. Once again MS points the finger and doesn't solve the problem. OK folks: YOU BROKE IT YOU FIX IT.
I am having the same problem so it does look like a windows update issue as the photos do not open anymore from within a folder when clicked on. They only open when moved to the DESKTOP which is not at all ideal so there is definitely some bug in some software that needs a bug fix patch to restore the system to normal operation. Restarting the system fixes the problem temporarily but then it comes back. I request Microsoft staff to use your expert software engineers to provide a future WINDOWS UPDATE very soon that will fix this problem as it is widespread where I highly doubt that system repair or a clean boot will fix this problem. I thank you in advance if you are working right now on the bug fix.
I am having the same problem and none of your proposed solutions fix it. It just started happening on 10/30 or 10/31 after a windows update to the photos app.
I am having the same issue, just since the following Windows 10 update on Nov 1, 2024 ( a couple of days ago: 2024-10 Cummulative Update Preview.... Everytime I restart my computer, images from Explorer/all my files and folders, will open, but it is temporary each time. I also notice some updates with the Windows photos tool. So this must have been part of the update. This is obviously an update issue. Should I try to have Windows repair it or just uninstall the update? Hopefully a patch/updated update comes out quickly.
UPDATE 11/5/24: Found the issue, I think. The update just messed up the settings and removed it as the default app, leaving no app set. You need to readd Photos as the default. See screenshots...
Came here to say I'm having the same issue too. I did all the scans and it didn't fix the problem. I will wait for an update that fixes it I guess.
