Garth Jones Admin on 3 September at am. You are a genius and a scholar! That worked! Thank you! Bernhard on 16 May at am. Scott on 20 April at pm. Georg on 29 June at am. I love you, the path setting fixed it for me. Iman on 1 August at am. Ron on 9 August at pm. You are the best! Thanks for this! TC on 11 November at pm. Thanks, worked for me Reply. Aaron Wong on 18 November at pm. Worked immediately for me! Thank you so much! Mark P on 17 December at pm. Thanks again Reply. Hans de Bruijn on 12 January at pm.
Andrei on 5 February at pm. Sherwin on 16 February at pm. DonaldTrap on 24 February at pm. Tnx a lot u saved me hours of swearing Reply. Robert T on 25 March at am. Canon Iri Reply. D on 4 August at am. Skrblik on 8 November at am. THX dude, works for me. James W Troy on 21 December at pm.
This was a very helpful article. This article brought my old CanoScan F back to life. Thank You! Peter on 2 November at am. Regards Mort1s1. Monday, December 26, AM. Does not work for me :- Ideas? Win8 64 bit, Lide Wednesday, January 16, AM. Tuesday, June 4, PM. Thursday, September 12, AM.
Sunday, January 5, PM. Ltd 0. Hi had this same error but nothing no fixes i found on line fixed the issue until i discovered i was being very stupid!!! Thursday, February 13, AM. Hi Marc from Russia write this solution and work for me.
Sunday, May 4, AM. Scanner Canon LiDE Tuesday, May 27, AM. Tuesday, October 14, PM. Saturday, August 1, PM. Tuesday, October 20, PM. Saturday, February 20, PM. Now, the question is why does Canon provide bit drivers for Russia but not for the US? Tuesday, February 23, AM. Friday, September 30, AM. Ist 0. EXE then appeared a dialogue box, where you can choose the external scanner source in my case Lide50 and I've enjoyed my 10 years old scanner! Thanks to all for help me!
Thursday, September 14, PM. I have CanoScan F scanner and currently using Windows 8. BMP images. Thanks a lot for the info. Jeff, you Sir, are a Gentleman and a Scholar, a million thanks, excellent walkthrough and worked an absolute treat, once again many thanks.
Thanks, it worked for me. Not sure how it worked over the previous years! I updated the drivers from the Canon site but that did not help. The Path addition was the needed fix.
Gary Davis Webguild. I have just had this problem. I just tried to edit the path, but only got as far as Control Panel and System and Security. I have no advanced settings tab in my system and security menu. Re-installing the programme does not help as I continue to get the same message. Man, you are a lifesaver. My F stopped working after upgrading to Win 7 SP1. I was on the verge of throwing out the scanner and buying a new one. Thanks so much! Running Vista Home Premium.
My CanoScan NU, about 10 years old now, is only used it a few times a year. Like everyone else has experienced, it just stopped working! Added the folder to the system path and it started working again. I can't imagine that something just took it out of the path. I doubt it was ever there to begin with. Must have been some system configuration change or other service pack that mucked up Twain, but what do I know.
Regardless I'm glad its working now, saved me a trip to Staples. Apologies if this is redundant, I didn't read through the entire thread. Win7x use Canoscan Toolbox v4. For some reason the newer one doesn't work, but the older one does 5. Install the driver first SetupSG. Once everything is done you will need to reboot before everything will work. A good tool for testing and troubleshooting is to download Irfanview, which has Twain and scanning tools under the File menu.
Geez, forgot to say that I'm using an f - procedure might work for other older models too. I just want to say thank you. My canoscan lide 70 works like charm. I tried this and it doesn't work. Hi Jeff. Thanks very much. I have spent hours with unistalling and reinstalling the Canon drivers and software to solve this problem which made no impact. I tried your solution on my XP system and it worked perfectly. Thank you so much!!! My Canoscan Lide 60 is working again and your instruction made it fast and simple.
Thanks a lot for the trick. Why can't the installer add the path itself. Or why is it necessary to have it in the PATH variable in the first place. But I gess we can be lucky Canon provides 64 bit drivers for such old products. Another satisfied customer. Thanks, Jeff! I have been doing this sort of stuff a long time, and when I come across someone who gives such a precise and effective answer, I find it truly awesome.
Thank you, this work fantastically! I can stop swearing at my scanner now Thank you, it worked for me. Only the puzzle is why the problem appeared. It worked for more than one year without any problem. Hi Jeff, Thank you very much for the clear and concise instructions, it helped to fix the error quickly.
Thanks, Joseph. Thank you so so much! Now I am enjoying the great performance of my scanner again! I'm so grateful to you! I used your info to fix my old Canon LiDe scanner. It was great to find this solution on the internet. It really works! Thanks for keeping this info out there for us to find. Thank you very much for the info. I was going to buy a new scanner. Imagine that. You just saved me some bucks.
Thanks Jeff for the information regarding the "path". Unfortunately it did not work but together with the comment from Elliphant on June use canoscan v4. Hey there, this didn't work for me unfortunately, I have a Canon NU and it suddenly stopped working about a month ago saying its unable to open TWAIN source, do you have any other ideas? Thanks, Jackie. Hi Jeff, Thank you so much. This helped me with CanoScan F. Thanks, Tibor. Big thanks Jeff! CanoScan F. Used to work fine for years. Suddenly stop working today.
Don't know how the environment variable got changed. Windows update maybe? I wish I had found this years ago. Thanks Jeff - it didn't fix my CanoScan DU2F problem but your instructions were really easy to follow and made me feel less frustrated nevertheless!
Hiya Jeff, I was wondering if you could post that entire pathway plz because I accidentally deleted the pathway instead of just adding to it. I went to press the arrow on my laptop and pressed wrong button grrrrrrrr, could you help plz thanks. Thanks Jeff! After installing a new Canon multi-function printer, my old Cannon F scanner stopped working with the error described.
It's got a long scanning bed, so I want to keep it. It now works again after following your instructions. Thanks again!! No luck for me, but awesome this has worked for so many people. Very annoyed at Canon for being so unenvironmental - imagine all the scanners that just go to landfill because people can't figure this stuff out.
Thanks so much, after reading so much different threads and spendings HOURS of other solutions including a complete Factory re-set , this worked liked nothing I also double checked and did a restart Cheers Rick. It would just give me a "Scan failed" every time. Hi Rick, It looks like the F is a European model only which possibly could be the problem with installed a US version of the software but that is just a guess.
Windows 7 64 bit and a Canon F. I had this problem, and went nack to the Canon 4. Thank you. Windows 7, 32 bit, Canoscan Lide I think it might have to do with the new 5. I tried inputting the path for one, then the other, but neither worked. Should I put in both? It worked!! Better than some of the other solutions that are out there. Thanks so much.
I was reinstalling my driver everytime i come across this problem. Now its fixed forever! Thank you so much for this wonderful article! Hi I need your help!!! I'm using canoScan F. Thanks for the info! Thanks for posting this! I've wasted a LOT of time trying to figure out why my scanner no longer wants to scan and this fixed it in less than 5 minutes. I wish I had found it sooner. Thanks for posting this. It was really a lot of help. At last I am able to successfully scan my document. Worked like a charm.
I still don't know how my path variable got erased, but who cares, it's fixed now. When you find it's folder name, then add that as described above - each scanner model has a different folder name. This solved the problem. Was dumbfounded as to why the error appeared on the newer computer. Let's hope this entry stays around as long as it's needed.
I have tried every one of the above fixes for a Win7 Home 64bit installation, even upgraded PhotoStudio 5. We have uninstalled everything and started from scratch, still in the wilderness with this scanner.
Thanks so much for making my day easier. Jeff - your trick is still working - thank you so much for such a clear post on this. Best wishes Inga. Just want to say thanks a lot for this! Google definitely put the most helpful answer at top of list! I used CanoScan Toolbox 5. Reinstalling the software didn't fix the problem, but your solution did. You saved me a major headache, Thank you so much!
I think this is still the definitive source on the internet for solving this problem. After much fiddling I finaly reached the goal. The problem was my newest toolbox program. Some time ago I downloaded CanoscanToolbox4. But this program was not able to find the driver, no matter what I did. Seems to have worked for me too Jeff. Running a F under Win7 32bit. Have been puzzling since then though still able to acquire scans through Photoshop so thought problem was Toolbox rather than driver.
Then found your posting - what a hero! I have changed many types of drivers, try compatibility modes etc. Now I am knocking my head against the wall ; Everything is ok now. It works. Thank You again. Thanking you so much for the advice I added the environment variable and it fixed it. Wow, you know how much time I wasted on this until i found your tip!!
Very long phonecalls with Canon helpdesk, emails with them, no one could help me. Thanks you very much! I suppose that Canon don't want to provide such an easy solution rather than providing new scanner hardware to increase their profit Thank YOU! It's amazing that in April this is still a problem that is so simply solved and is not listed on the Canon website as a solution.
You are my new hero and you don't even need to grab the nearest tablecloth to wear it all week as a cloak with your underwear outside of your trousers:. I've been using W7 bit operating system on my laptop for about 18 months. I couldn't find or do anything to get it to work until I found your very well explained fix.
Many thanks. Another success. I was going to toss this hand-me-down LiDE30 in the trash. No need now to buy a new one. Any one know why? Path fix did NOT work as others have reported for this version. It's working for me without doing anything with path. Jeff, Thanks for posting this article! I could tell that both my drivers and the application to drive my older Canon f were installed and functional Win 7 Home Premium. Many thanks for the solution it is rare that such precise advise is found on the web.
Hello Jeff, thank you very much for posting this solution, it worked out fine for me. Fantastic straight forward information! Now, it is working again! I wonder why the CanoScan toolbox isn't able to handle this issue or at least return a meaningful error message! Because, obviously this trivial problem is causing trouble and time loss to thousands of users. Thanks for the screen shots too! We technically challenged need all the help we can get.
Thank you very much. Lide 25 users with windows 7. Exactly same problem after setting this additional directory to my path environment variable. You, sir, are a life saver. Worked perfectly on Windows7 bit with a Canoscan F. Then I discovered your page, and after one minute my Canoscan lide 25 is back to life!
Thank you so much!! You are an absolute genius! Spent months researching this and saw something on another forum but not as clearly explained as this! Thank you very much, It worked for me: to install the Canoscan Lide 25 on Windows 7 x I had been trying the solution from the official Canon and windows websites, it was not working.
I had been trying various solution found on the internet: in vain. You solved the problem. Scanner worked like a charm for many years and then suddenly stopped working. I am computer programmer with lots of experience and it would have taken me a lot of time and so you saved me a lot of headache! Thanks, I was holding on fixing this for days before I googled this.. Today I didn't have my wife's laptop to use my scanner and didn't have a choice but to find a solution.
This tip worked for me Win 7 and many thanks.. Just bought a Win64 laptop, and I must have installed, uninstalled, and re-installed the software and drivers a dozen times. Rebooting like a madman didn't help, either. Just a simple addition to the path and all is well. Thank-you thank-you thank-you.
I was fighting with this bothersome problem for years. I installed and unistalled drivers and Toolbox I don't know how much times and sometimes it didn't work.. And now with this simple trick it's all ok! Really thanks so much. Thanks for posting a simple, but very effective fix! After a Windows update and some other installs, my scanner suddenly started presenting this error dialog.
Adding the twain path fixed it. No luck here. Modified the path variable, but still getting the error. Windows 7, 64 bit, Canon CanoScan F. CanoScan Toolbox. I modified Path and it seemed not to work, but I had to close and re-launch Photoshop, the destination application. Then all was well! Don't know if this has already been posted, but for Windows 7 bit users, CanoScan Toolbox 5.
Hi, thanks for a perfect hint. Got my scanner operating quickly. Such a simple fix, but so deep in the details. Worked great. Canon owes you a beer!
Thanks a bunch! This worked for me as well with a Canon f on Windows 7 x You save my day Jeff! Why Canon did not have this kind of information and let its customer setting in the dark?!
In all Canon support forums and portals, no word even mentioned about this particular disdainful problem. Wow - this is the first time I have had success with online help!! Many thanks!!!!!!!!!!! That did the trick. But what I don't understand is, why it suddenly got this point. Thanks for the help. Got it working now. Can't understand why it used to work but then decided not to. Good job there's young people like you who can find out how to sort it.
Many thanks, I spent 2 hours searching the internet in vain for a solution until I found this page. Now I got it working. Shame on Canon for ignoring this problem. It's people like you that actually help the world go round. Been trying to get a LiDe35 to work under W7 64Bit for 6 months and this was the missing bit, Thank you sooo much.
However, it is unacceptable that one needs to do manually what should be done automatically. Good directions, by the way. Pity they didn't work, though.
Absolutely no change to the twain error message. I'm amazed that people such as yourself go to so much effort to create step by step instructions like this for the rest of us.
Thank you for your time, effort and knowledge. Mil gracias por la solucion inimaginable desde mi experiencia pero dio con la solucion!! It really worked on my PC. Now I can use my scanner canoscan f. Thank you very much for solving this annoying thing! More than one year I was using older computer for scanning only This was extremely helpful, had no problems until today and have owned the scanner 6 months.
This helped me solve the issue quickly. Thank you for posting this fix. I finally got my Canon lide35 scanner to work in W7 bit after using the lide60 driver and your path instructions. Glad that I can still use this old scanner which was a really good model.
Tried the path thing to no avail. Scanner is a LiDe F. Tried uninstalling.. Reading back through all the comments I found one which said much the same but got it to work by running Canoscan as Administrator and voila! Clearly it has come about from a Windows update! Last year I read heaps of advice, mainly about deleting old drivers and installing the latest version from Canon, but all to no avail.
Today I had another bash at it, was just about to throw in the towel again, and then found your page. Why couldn't Canon get that right? Thank you VERY much indeed. Just changing the path worked!! Setting PATH didn't help me either. Running Toolbox as Administrator helped me. Thanks for this article.
0コメント