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 am having the EXACT same problem as described. Take the .jpg out of a folder and put it on the desktop, then photos opens it with no problem. BUT THIS SHOULDN'T BE NECESSARY! Microsoft fix it so Photos opens the file while in the folder (like it use to before the update)!!!!
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.
We will see how it shakes out in the long run, but THIS solution worked for ME. Everyone's computer is different, and I don't even know what was causing this issue in the first place, but it worked. I would encourage people to try this solution and see if it works for them.
The reason I have high confidence in this solution not being temporary is that it resolved the "not implemented" error during my current session of Explorer, ie not having to restart it from task manager. Nothing I have done prior accomplished this. Seriously, all I did was confirm I was still experiencing the issue in my current session, install the legacy Photos app, set it to default within settings, and ta da all my photos opened normally again.
I did try the default viewer trick with the current Photos app, and this did not work. It was after reading people saying that still didn't fix the problem even after reboot that I went with the above solution. It's a good thing I didn't reboot too; it wouldn't have given me the immediate gratification of the issue disappearing with the install of legacy Photos. I'm also not particularly keen on the redesign, problems aside. So I have no qualms with reverting. :)
If this solution does solve people's issues permanently, then it's clear the issue arose from the recent photos update. I don't know how I started experiencing it BEFORE installing the update, but maybe Windows implements some changes in an update before you actually restart to install it. I can't remember if the UI change had been implemented before or after I installed the update, and before or after the issue arose.
I'll keep posted if this solution sticks, but I'm optimistic.
I'm having the same problem now. What is the fix ?
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
I have also just started to get this error.
Obviously I have Windows Explorer, but I also have another file management program called Explorer ++. Jpegs open flawlessly from this platform, so this confirms the issue is generated by Windows Explorer.
