02-19-2020 01:39 AM
02-19-2020 04:42 AM
thx,so we know that some windows or redist update breaks touchdr.exe, doing a clean install however is not an option for me, it takes days to configure all the other software, so why not fix the issue with touchdr.exe?
I might seem annoyed, but I have several canon scanners that has become unusable due to this issue, and I believe it is time for canon to provide a workable solution?
best regards Thue.
02-19-2020 03:57 PM
Well, I bought an extra new SSD, to try if a clean install works, and identify the issue.
I also kept the old SSD with the otherwise working setup.
I still did not finish completely migrating the old system to the new SSD.
This whole thing sucks, I would not buy a Canon scanner ever again, for sure.
04-06-2020 01:57 AM
during the past weeks, I was in close touch to Canon Switzerland. They did a very nice job and looked seriously to find the error.
The last step would have been, reproducing the failure while a log-software is running. However, to reset all log files in my ->Temp-Folder I decided to delete ALL my temporary data on my Computer. I used the Windows10 settings app for that (System->Storage->TemporaryFiles). All of a sudden, the scanner worked afterwards nicely with the CaputureOneTouch. It still doesn't work with the Windows10 scanner app, but that doesn't bother me.
Please try that out and provide feedback, we came among several other issues, which could have an impact as well.
06-20-2020 03:49 AM - edited 06-20-2020 03:50 AM
I cleaned the Temp files as you described (Windows 10, latest download of CaptureOneTouch).
Unfortunately, with the Canon DR-C225W, the same errors appear for using CaptureOneTouch.
10-08-2020 07:37 AM
CaptureOnTouch V4 Problem:
TouchDR.exe runtime error - visual c ++
ok, the solution in my case was:
reset the language settings in Windows. Set all options Language&Region to the same e.g. English/United States:
- Windows display
- Apps & websites
- Regional format
In my case I had setup Windows to have Engish/United states as display language and as Regional format, while the Country or region was set to Germany.
CaptureOnTouch stopped working after an Windows update or whatever.
The TouchDR.exe is picking up the wrong language/locale setting once the driver of the scanner is activated and exits with the runtime error message.
You can verify the timing by leaving the scanner disconnected until CaptureOnTouch V4 is running. Once you plug in the scanner, the app will crash. However, it is NOT a driver error. The scanner is working well all the time with other Twain-compatible apps. It is still the TouchDR.exe, which is causing the problems.
10-08-2020 07:43 AM
Thank you for sharing your experience. This is actually an interesting assumption because I had an untypical language setting on my laptop as well, probably the same as you.
10-18-2020 03:51 AM
I've ran into this issue multiple times now. It works when starting with a clean installation of windows but you must not forget to install the scanner drivers and software at first because there seems to be an order issue? It is really annoying if you forget to install and test the scanner is working and find out after a week the same issue is back and you can start all over again because it seems unfixable. Also tried other scansoftware (Vuescan), which does work, but I personally find the captureontouch better/easier.
For now I have found a workarround by using vmware player. I've created a clean Windows installation on which I only installed the drivers and the software and everything is working now. I also disabled the networkcard to prevent any windows update from spoiling it. Just to be sure So if i want to scan I just power on the image and when done, hibernate it so it ready to go when needed. The scanned files i then can move to my own windows.
It is not ideal, but easier then re-instalation my entire computer. I'm really happy that it is "working" now but still sad that there is no real solution to this...
02-16-2021 11:07 AM
I had the same problem. I changed all settings to German, now it works.
(Win 10, CaptureOn version: CaptureOnTouchPro_V.4.5.1620.1118)