Did you reboot after resetting default to the Photos app? I had to do that extra step then it worked for me
"Not Implemented" when clicking on photos in Windows Explorer
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.
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.
147 answers
Sort by: Oldest
-
Anonymous
2024-11-06T13:13:35+00:00 -
Anonymous
2024-11-06T19:04:44+00:00 Everyone should go to https://support.microsoft.com/en-us/home/contact and start a service request.
-
Anonymous
2024-11-07T01:48:37+00:00 I did this (set as default) and it fixed it temporarily (with a reboot), but now, a day later, Photos is still set as the default but I have the same problem again....UGH
-
Anonymous
2024-11-07T04:40:56+00:00 did this BUT it happened again!
-
Anonymous
2024-11-07T16:47:35+00:00 While the "Photo viewer" app may not be set, this does not resolve the issue. As is mentioned by LookinAround a reboot was required. Well it was the reboot that fixed the issue for him as rebooting restarts explorer.exe which as we all know resolves the issue...for a little while. I implemented this "fix" and it did not work. I rebooted and it started working, but now two days later it is not working again. I'm sure restarting explorer.exe will fix the issue but the real issue is that there was an update that caused this issue and Microsoft are the only people who can fix it.