Why is my Epson Scanner freezing after upgrading to Windows 10 Spring 2018

Nice Analysis.   I tried accessing Epson Support for the Epson L355 printer and not sure if it is still supported.   I was trying to determine if there was a recent firmware update.  Could not find any.  What concerns me is that any Epson device that scans older than about one year may not be supported.   I am also questioning whether the EXE being 32bit software is a problem.  Don't know.  With all this problem with scanning is an interesting coincidence that Epson released a June firmware update for my printer.   Lastly,  I tested my old V700/V750 photo scanner.  It does not work after the first scan without going to the task manager and shutting down the 32bit exe, and then recycling the power button on the scanner.  Oh well.  I also tried downloading software for a later model but similar.  No doing.  Did not work.  In conclusion I will keep my old V700 scanner for any slides left to scan.  You know I may try to connect my V700 scanner to my old Macbook Pro and see if there is a problem.  This assume Epson release a Mac version of the EXE.  

Again great work.

I've the same issue with my EPSON L355 network printer as well since the latest updates to Windows 10. Basically what happens is:

Using network scan via wifi:

• After opening "EPSON scan", the scan window appears. But what happens after a while of inactivity is that several smaller popup windows from EPSON scan also appeared and disappeared (i.e. the "flickering" behaviour) at one corner of the desktop screen. The entire scan application thereafter hangs, and the only way to close this would be to either click on the window to trigger the "application isn't responding" window, or use Task Manager to force close it. Sometimes, I may be lucky to scan one image, before EPSON scan freezes.
• After force closing EPSON scan, reopening it results in a error window popping up which states "Network scanner is not available: currently being used by user. User: [...] [...] Epson Scan will close.". But the user name and IP address is actually myself, so in some sense the scanner got "locked out" itself.
• The only workaround would be to turn off the scanner, close EPSON scan fully, and then turn it back on. But the same problems will appear again after scanning the first image (if lucky).

Using USB connection:

• EPSON scan likewise freezes
• After force closing EPSON scan, reopening it results in a different error message: "Cannot communicate with the scanner. Make sure the scanner is on, correctly setup and connected with no errors indicated. For detailed information, see Solving Problems in the User's Guide."
• The only workaround would be to turn off the scanner, close EPSON scan fully, disconnect then reconnect the USB cable and then turn it back on. But the same problems will appear again.

What I've done:

• Reinstalled EPSON Scan to no success
• Reinstalled the printer driver to no success
• Tried using all the different dated versions of the printer driver and scan software to no success
• Tried using all combinations of Windows Compatibility mode to no success
• Installed the latest Windows updates to no success
• Running EPSON scan as administrator to no success
• Using system restore to no success

Searching for the logs on Event Viewer (Windows logs > Application) gives the Error-level event:

So basically I've no idea what else I could do to fix this.

Hello,

Yes the compatibility mode worked for me as well, however with my Windows 10 I did not find the "compatible" feature in the properties window, I found it as described on this post-https://www.laptopmag.com/articles/set-compatibility-mode-windows-10.

I applied a June Epson firmware update to my Epson XP-830 Expression Premium printer/scanner.  So far no more problems.   I am able to Scan, Save and rescan new documents without any problems.   However, my 6-7 year old Epson V700 photo scanner is still not working quite right. I am going to see if setting compatibility to SP3 will work provide in doing so does not interfere with my newer printer.  Both devices use a different EXE file.  Thanks for the post.

I have had this exact same problem for a couple of weeks.

"Fixed" for now by setting compatibility mode to XP SP3 and running as admin.