I have a Xerox One Touch 2400 scanner (from the year 2004), but my computer died and I now have a newcomputer with Windows 10 (W10). Windows cannot find any driver for my scanner so I cannot use it. The CDs that came with the scanner included Paperport and Textbridge OCR and the driver, but maybe I could make do with the Windows 10 scanning apps if I could just find a driver. The scanner has immense sentimental value for me, and I cannot really afford a new one. Surely there is some way I could get it working on W10. Can anybody help me, please?
The one on the CD and the one on the scanner website work fine on Win 10 as long as you disable driver signing first.
Last I did it , it went like this to disable it
a. Press the Win + C and click on PC settings.
b. Switch over to the “Update & recovery” section.
c. Then click on the Recovery option on the left hand side.
d. Once selected, you will see an advanced startup section appear on the right hand side. You will need to click on the “Restart now” button.
e. Once your Computer has rebooted you will need to choose the Troubleshoot option.
f. Then head into Advanced options.
g. Then Startup Settings.
h. Since we are modifying boot time configuration settings, you will need to restart your computer one last time.
I. Here you will be given a list of startup settings that you can change. The one we are looking for is “Disable driver signature enforcement”. To choose the setting, you will need to press the F7 key.
Thank you! I shall psyche myself up to trying my old XP CD. Having to disable driver signing on Windows 10 sounds a bit scary though.
If I need to try one of the drivers on the scanner website, I presume that the XP one would be a better bet then the Vista ones. Am I correct? Also, (if that doesn't work) I don't know whether, with a 64 bit computer and (what I presume is) a 32 bit scanner I would be better off trying the 64 bit Vista driver or the 32 bit one.
Sorry for the extra questons but I'm quite nervous about messing up this computer.
Newer is better, so Vista would be my choice, that said, they are probably identical and it won't make any difference.
32 and 64 bit isn't the scanner, it is your PC, which is likely x64 (64 bit)
On the PC look in your C: drive, if there is a Program Files and a Program Files (x86) then you need the 64 bit driver. If there is not a Program Files (x86) you need the 32 bit.
As for disabling driver signing, no worries, it's easy, its quick, and the worst case scenario is that you will end up no farther ahead and just have to turn it back on after failing. All you would have done is wasted 10 minutes of your life that would have been better spent looking at funny pictures on the Internet. Here is one to make up for those you missed.
Re your first reply, now I do need a 64 bit driver, so how could the one on the CD work since in 2004 XP was only 32 bit (as far as I know the 64 bit versions came out in 2005)? So it looks like I'll have to try the Vista one. But I'm wondering whether one of the later, Windows 10 compatible, drivers that claims to work for the Visioneer 2400 might work better? I have found some photos on-line where that model looks just like the Xerox one - but others where it doesn't! Any advice?
Maybe something for W7 or W8 would be safer than the Vista driver, but without going through all the drivers for all the models on the website to see if they are compatible with the Xerox One Touch 2400 (or that Visioneer 2400 - if it is the same thing) it's not easy to know what best to do.
I may sound a bit paranoid, but I really do not want to mess up this computer as I'm having other problems with it.
Anyway, thanks for the squirrel photo: I think it just realised its XP was gone and it was stuck with Windows 10.
You can try whatever you want, but if a scanner has a Windows 10 driver, it shares nothing in common with yours.
I must have mis-read whatever it was I could have sworn I saw on one of the Xerox/Visioneer websites. Sorry.
I guess my only option is to try the Vista 64 bit driver and just hope Windows 10 doesn't get upset by it. I probably won't try it for a while because I'm having some USB port problems and I'll have to get them fixed soon.
Anyway, thank you for your suggestions. If I ever do get the scanner going I'll come back and give your inital post a tick, but forgive me if I don't do that yet.