"Not Implemented" when clicking on photos in Windows Explorer

Anonymous
2024-10-30T20:20:13+00:00

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.

0 comments No comments

147 answers

Sort by: Most helpful
  1. Anonymous
    2024-11-09T04:51:54+00:00

    The more people who request a phone call at https://support.microsoft.com/en-us/home/contact, the faster Microsoft will fix the problem.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-11-08T15:47:13+00:00

    Shaarmen There is no permanent fix for Photos as best we have determined. A temporary fix is to restart explorer. Most people have given up and moved to a different product like "Photos Legacy" as described by DamonB23 or "ImageGlass"](https://imageglass.org/release/imageglass-9-1-8-723-55 "imageglass.org") as I have done or they are using a product called Explorer++ as [LookinAround mentions.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-11-08T03:16:55+00:00

    Did the default get reset again? I reset and rebooted my Windows 10 PC two days ago but the problem hasn't returned. Yet. (I assume you meant to say you're running windows 10?)

    I agree all those MS instructions are too much work but footnote: a Windows restore point only saves/restores Windows system files and settings. It shouldn't affect your personal files. Still, i think it's still too much work.

    Another user posted they use Explorer++, a Windows Explorer alternative and it works. Try an Explorer alternative till MS gets this fixed?

    Just checked. I'm showing last update was 10/24/2024 though the problem didn't start till 11/5/2024. I'm also showing 3 updates that date: KB504554, KB5045933 and Servicing Stack 10.0.19041.5071 installed that date. I'm running Windows 10 Pro x64. So now am wondering what the heck is going on

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. 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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-11-07T04:40:56+00:00

    did this BUT it happened again!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments