Solution for: Epson scanner no longer works after Windows 11 update

Anonymous
2024-07-03T20:40:15+00:00

Resolved for me, want to share with the Community:

Forget about the Epson interface and instead download and use the "Windows Scan" app here:

https://apps.microsoft.com/detail/9wzdncrfj3pv?amp%3Bgl=US&hl=en-u.s&gl=US

Once I did that my Epson DS-510 started working again. You select what device you want to use, either printers or scanners. Your scanner should appear in the dropdown list if is connected.

Some history: I had updated to Windows 11 in November 2023, and for about half a year I was able to use the DS-510 like previously. My Epson DS-510 mysteriously stopped working in May-June of 2024. In that timespan I had installed some Windows 11 updates.

Today I spent over 1 1/2 hours on the phone with Epson support and they tried to help but couldn't figure it out. Also in the course of that call we came across an option to use a Microsoft scanning app "Windows Scan," but the Epson tech said to ignore that and kept looking for other solutions.

Finally one of them said why don't you call Microsoft? It seemed to make sense to me that the problems was related to the Windows 11 update in May-Jun, since that coincided with the Epson no longer working. Then suddenly I said to myself why not at least try the Windows Scan app, and that turned out to solve the problem!

**** Moderator note: Converted to discussion

Windows for home | Windows 11 | Devices and drivers

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

71 answers

Sort by: Oldest
  1. Anonymous
    2025-03-22T09:43:12+00:00

    Thanks for comments.

    Microsoft is always eager to ruin somebody's work. It seems like Microsoft doesn't care about people.

    None of any recent local advice (installing as admin, addon c++, reboot WMI service) didn't help me.

    Nice OS shell doesn't see the scanner and therefore Epson app cannot work.

    After bunch of scanning by clikking the virtual device in windows explorer with its poor options I was honoroed by oppotunity of successful lanching of Epson app (by physical buttons).

    And yet.

    God, UNbless Microsoft. They've taken hours from my life with impunity.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-03-22T14:10:42+00:00

    I understand that Microsoft's changes are at the root of this, BUT THIS HAS NOT WORKED FOR A LONG TIME NOW, AND MAYBE IT'S TIME FOR EPSON TO BE PROACTIVE instead of doing nothing and leaving its users in the lurch.

    At this point, I will blame Epson for having done ABSOLUTELY NOTHING to address the problem other than saying "It's Microsoft's fault -- you'll just have to wait."

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-03-22T19:11:52+00:00

    While still having problems with scanning 120-sized negatives, I ALSO had the scanner shoot craps in another way, and I am now getting the "Cannot connect" message. I tried this solution. I STILL get the "Cannot connect" message. It suggests that I look up the User's Guide, which tells me exactly zip how to fix the problem.

    Is Epson self-destructing, or do its people just not give a damn about their customer base anymore?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-04-01T20:34:08+00:00

    Why they would hide the box like that is beyond me, but this solution works!!!

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2025-04-17T23:33:32+00:00

    Some users were having issues with ScanSmart not installing on Windows 11 no matter how many times I ran the installer. What I ended up having to do was extracting the ScanSmart exe file using 7-zip, and opening the MSI folder within. Then manually install each MSI file. ScanSmart would then install and become available as a program. Hope this helps!

    Was this answer helpful?

    0 comments No comments