Ihave run into this as well. It is very frustrating that the ScanSnap software loses communication with the device. I have had a little success with getting it to communicate by pressing the scan button on the device, but like you mentioned reboot always works. Hopefully someone has figured this out
does the device lose com, when the windows device it is connected to goes into sleep mode? or does the scanner have a sleep / low power mode? I think I might be inclined to check on those things as well.
I was hopeful with the upnphost service, but was finally able to test it out yesterday, no luck. I first tried just starting the upnphost service, no luck. Then I tried restarting that, then restarting the epson scan service, and the WIA service, still getting the same error message.
Hi , did you find out a solution yet? I have the same EXACT problem as yours for almost 2 years. My scanner is Epson V550. I have tried restarting all the suggested system services. I could not get the scanner work until I reboot the system. Could you please advice if there is anything we can give it a try?
I hope that by telling my very bad experience with the Adobe Photoshop product and the customer support, I will avoid others to suffer from the same fate (and maybe, possibly make Adobe a better company).
We pay Adobe because we need a premium product and a decent customer support (otherwise free open-source alternatives like GIMP would do). Scanning and editing images is one of the main use of Adobe Photoshop. Epson is one of the main international manufacturer of scanning equipment. Epson did their share of the work:
I followed the procedure to the letter. Despite having asked 8 times to continue the conversation via e-mails, the second human (Him*****) kept on answering me on the chat. On top of that, he didn't solve the problem and tried to shift the reponsability onto Epson despite the problem being entirely within the Adobe Photoshop software. Why (and how) on earth would (and could) Epson modify and Adobe software source code ? Completely ridiculous.
I am sorry to remind Adobe of something very basic it seems to have forgotten: we are the customers, we are paying and we deserve minimal standards regarding software quality and customer support level.
Read my post again, directly above this one. This was TWAIN, and TWAIN no longer exists. It is not developed, not supported, not 64 bit native (which is an absolute requirement in MacOS). TWAIN is dead.
There are some basic standards in the IT hardware and software industry. One of them is to (at least) allow backward compatibility, especially when it comes wih inter-hardware or inter-software technology and protocols.
Most IT users are not tech enthusiasts or geeks who live only to see the next innovation for the sake of innovation itself. Most users are regular people or SME (small and medium-sized entreprises) who need IT tools to execute a task in a stable and long-term IT environment. This is why innovation must always come hand in hand with backward compatibility.
Epson Scan 3.925 (07-2018) is a 2 years old software with standard communication protocols built-in. With all the money we pay Adobe (monthly subscription), I think we can ask them to allow that kind of minimal backward compatibility in Adobe Photoshop.
It is up to Adobe (monthly subscription) to program the last mile within Adobe Photoshop and maintain it, with backward compatibility if necessary. Wether it is inside the core program source code or in a plugin doesn't change that fact.
Your examples are more universally accepted standards - not an isolated plugin from a single vendor. The issue you are having is Epson has decided not to invest anymore time into keeping the plugins current for this scanner.
It's not up to Adobe to fix all the possible equipment compatibilities, its the vendor who should be updating the plugins to meet current standards. Epson has chosen to discontinue this product and no longer support the software.
Scanning from within Photoshop hasn't been an option for at least ten years. It was possible through the TWAIN plugin, which hasn't been maintained or developed for a long time. It was very buggy and unreliable, causing crashes and other problems, and for that reason Photoshop dropped all support for it around CS4 in 2009.
Since a few days ago I used the last EPSON drivers for my scanner, an Epson Perfection v550 Photo, and was able to scan within Photoshop using the Epson Scan interface, which is very precious as it saves a lot of time as opposed to scan with Epson Scan from the desktop.
Now, having updated all the drivers to the last versions (the V550 is a relatively recent model, still on sale) there is no way I can make the Epson Scan driver appear in the "Import" menu in Photoshop: it just uses Apple's own "Image Capture" plugin which is basically useless for me.
When the problem occurs, you'll see a small Epson window flicker in the bottom corner of the screen and sometimes bounce around sporadically. The app locks up and your only recourse is to terminate the software through the Task Manager and then power your device off and on again. This happens most commonly after switching to a different application and then back.
Epson has acknowledged that this problem affects most of their products and they've reportedly escalated the matter. Until a fix becomes available through Epson or Microsoft, the quick fix is to simply run it in administrative mode. Here are the complete steps:
You should now be able to launch Epson Scan Utility again and use it without issue. Depending on your user account settings, you may have to click "Yes" if prompted with a security alert.
The first time you launch the application after making these changes, you may also receive a "compatibility alert." Select "Yes, this program worked correctly" to close it.
If you have User Account Control enabled, you'll receive a confirmation box each time you launch the app in administrative mode. Although a minor nuisance, there are a couple solutions.
When the alert appears, you can click on "Show More Details" and then "Change when these notifications appear." From there, you can lower the level to the second notch to still receive the alert but without dimming the entire desktop. You can alternatively set the option to "Never Notify" to remove the alert entirely. Be aware that this is a global setting and unless you are an advanced user I don't recommend disabling it, since the alerts can help prevent malware installation.
A more intelligent solution is to use a third party utility or the task scheduler to disable the alert on this application exclusively. Since this can be a somewhat more involved process, I will refer you to an excellent tutorial from Raymond.cc, which thoroughly covers numerous methods of doing so. You'll find the tutorial link below.
Thank you sooo much! I am not a tech person and didn't know why my scanner portion suddenly stopped after the pre-scan. Your link solved it, Jasia! Thank you, Matt for having this site!! Much appreciated
On second day, the earlier problem has recurred again: after one scan, flickering is seen in the windows icon at the bottom left corner of the screen and then the scanner software crashes. I have to reboot the scanner before the Scanner software runs and keeps crashing after one scan.
Hi Satish, first double check that under the icon's properties you have changed it via "Change Settings For All Users" and before checking "Run As Administrator" as otherwise there may be some oddities like this.
If that is set and still happens, you may want to navigate to the directory of the scan software manually and then set these same permissions on all of the EXEs directly. For most scanners the software is in "C:\windows\twain_32\escndv\" and there may be four or more EXEs that you can adjust (you may have to set "Show File Extensions" to see which is an EXE).
Finally, if the problem still persists then consider also setting the EXE to run in "Windows XP Service Pack 3" which should solve it but could break the "Browse for Folder" option so you'd want to configure where the scans are saved beforehand. You could try "Windows XP Service Pack 2" if that still gives you grief.
Other than that I don't have much advice I haven't heard of this happen before but also don't have that device or specific drivers to test directly. Good luck! Epson has slowly been rolling out some fixes for some of their newer products but older ones still have this issue and require the workaround.
Although you may have tried these steps, we believe the following will resolve your issue.
Launch Epson Scan (if applicable).
Under Home or Professional mode, please click on Configuration at the bottom part of Epson Scan.
On the Configuration window, click on the Other tab, and click on Reset All.
Confirm restoring of Epson Scan.
Launch the Epson Scan program again and try to use the Preview option.
Thank you sooo much for sharing your knowledge! Such a simple solution to what's been driving me mad for months re-starting my PC just to scan once at a time. Was on on the verge of packing it up and returning to the shop!! Fantastic!
Hi Matt, Thanks for posting this info. I have a Lenovo Yoga with Windows 10/64 bit, and a new Epson V600 just purchased. I followed the instructions when installing it, but it never hooked up with the computer. When I followed a link that I was directed to by Epson, the driver at that link covered Windows 10/32 bit, something I didn't notice until after I downloaded it. That download driver did not work with the Epson, but did shut down my Office 365. I took me quite a while to remove all the various components/drivers that I had installed while trying to set up the Epson. The link you suggest does not mention anything re Windows 10, also nothing re 32 vs 64 bit. Do you have any suggestions regarding options for Windows 10/64 bit? I'm going to try calling Epson, but am wondering if you have any thoughts about Epson compatibility with Windows 10/64 bit. Thanks for your help.
3a8082e126