Question restoring a scanner to being viable

[Sebastian42]

Some months ago, I cloned my system to another hard drive and now run that clone in a different PC. My original PC needed its motherboard replaced, and after I replaced it with one that had the same technical description (the same coded name), the scanner would no longer work - Control Panel shows it as problematical in its 'Devices and Printers' and Device Manager shows its driver as problematical, even after I uninstalled it and re-installed the driver from the original driver software. The PC that runs the clone DOES allow the scanner to work. I'd like advice on how to get the scanner to work again in the PC from which I made the clone.

 

[Geven]

Tricky situation you've got there! Here are a few steps I can suggest taking to troubleshoot the issue:

1. Double-check your connections - unplug the scanner, restart your PC, and then plug the scanner back in. This might force the PC to re-recognize it.
2. Try using a different USB port, just to rule out any issues with the specific port you've been using.
3. If your motherboard has integrated USB ports, it might be worth checking if there are any driver updates available for the motherboard itself.
4. Try running the scanner software in compatibility mode. Right-click on the application, select 'Properties', go to 'Compatibility' tab, and then select an older version of Windows.

If none of these steps work, you might want to consider a system restore point (if you have one) from a time when the scanner was working.

 

[Sebastian42]

Tricky situation you've got there! Here are a few steps I can suggest taking to troubleshoot the issue:

1. Double-check your connections - unplug the scanner, restart your PC, and then plug the scanner back in. This might force the PC to re-recognize it.
2. Try using a different USB port, just to rule out any issues with the specific port you've been using.
3. If your motherboard has integrated USB ports, it might be worth checking if there are any driver updates available for the motherboard itself.
4. Try running the scanner software in compatibility mode. Right-click on the application, select 'Properties', go to 'Compatibility' tab, and then select an older version of Windows.

If none of these steps work, you might want to consider a system restore point (if you have one) from a time when the scanner was working.

I need to back-track and correct mis-information I posted.

The correct version is that I cloned a x64 system and am running that in another computer. The PC running the duplicate, allows the scanner to work, but the PC with the source of that duplicate does NOT. I have noticed that the power to the scanner is not secure. That puts the onus on ME to now test the scanner again in the SOURCE system while ensuring that the power is 'on'.

Irrespective of the result, that still leaves me with the problem that the scanner no longer works in a PC (running x32) since the mobo has been replaced with one that has the same code-name specification. It is in the x32 system where I need the scanner.

I can add that I have tried an altogether different BUT VIABLE/WORKING scanner on the x32 system and that would not work there.

I have run the troubleshooter and it offered a fix, but that does not seem to improve things.

 

[Geven]

Given that you've tried different scanners on the x32 system without success, it appears the issue might be more system-related. Since your x64 clone works with the scanner, it rules out issues with the scanner itself. Here are a few more ideas to try:

1. Have you checked if your x32 system supports the scanner model? Sometimes, hardware compatibility can be limited on older or different architectures.
2. If you haven't done so yet, try running the scanner installation as an administrator. Sometimes permissions can block proper installation.
3. Do you have any third-party security software installed? They can interfere with drivers and devices.
4. Have you tried running a system file check (sfc /scannow) in Command Prompt?

 

[Sebastian42]

1. I think I mentioned that the scanner had worked 'well' in the x32 system, until I changed the motherboard to one with the same code-name specification.
2. I can try that.
3. Yes I have Avast running - but am not afraid to disable it - especially if off-line.
4. I have run both scannow and DISM

 

[Sebastian42]

I think I have run the gamut of options; Compatibility mode - I chose Win7 - it proposed XP; As Administrator; different USB lead and socket, Avast disabled; all to no avail.

The latest check in Device Manager says 'no drivers needed or loaded'.
I'm running out of ideas.

I have tried two other scanners (that still worked last time they were used) - and they give the same result. I have a suspicion that my Registry has developed an antipathy to scanners.

 

[Steltek]

What is the manufacturer name and model of the scanner?

 

[Sebastian42]

HPscanjet2300 - it worked in this PC until I replaced the PC motherboard with an ostensibly identical one.

For what my opinion is worth, I really think that something has happened in the registry which is causing WORKING scanners to show in Control Panel and Device Manager as 'problematical' - that has now happened to three.

 

[Sebastian42]

I freshly installed x32Win10ProV22H2 in a NEW SSD, and booted it in this PC where the scanner wont work. Once I installed the driver from the original software, the scanner worked in the fresh system. So although the problem started when the motherboard was replaced, the 'new' motherboard does NOT prevent the scanner from working; AND the original driver is still able to make the scanner work. What to make of that ?

 

[Steltek]

You might try running a Windows repair install on the affected machine in the event something is corrupted, followed by a reinstall of the scanner software and driver.

And, if that doesn't work, it might be time to consider a rebuilding the system based upon a clean new Windows install since you know that will work. Unfortunately, that can be the cost of trying to deal with very old hardware (i.e. if that is the scanner I think it is, it works on Windows 98 so it ain't exactly spring chicken hardware).

 

[Sebastian42]

I had not previously noticed an error message in Device Manager which mentioned a probable error in Registry and gave Code19. A google search led me to the correct key for Upper Filters that had to be deleted. Now the scanner works again.