HELP! Problem using HPSCAN.exe or TWAIN driver for HP Laserjet Pro cm1415fnw using Windows 7

Question

I have been using the HP Laserjet Pro cm1415fnw for over a year without a problem.  At the time when I first purchased the unit, I was using a Dell desktop with Windows XP and connected the printer via USB port.  I was able to print and scan from my computer, including from within applications that use TWAIN scanning driver such as Word, Acrobat, etc.
I have since upgraded to an HP slimline s5-1160 computer using Windows 7.  I installed the Laserjet software from my installation CD's without a problem.  The printer is connected to the computer by USB port.  I can continue to print without a problem.  However, I no longer am able to scan using the HP software (HPscan.exe) nor from within applications that use TWAIN scanning driver such as Word, Acrobat, etc.  When I attempt to do so, it takes a long time before it asks me what TWAIN scan driver to select.  When I select the HP cm1410 MFP series, the program either crashes or reverts to the state it was before I attempted to scan an image into a document from within the program.
I can however scan successfully using the Windows Scan and Fax wizard or if I choose "Devices and Printers" from the Start Menu and select "Start scan" from the menu after right-clicking the HP printer icon.  However this option limits my use of the scanner -- I cannot scan to a PDF nor can I scan multiple pages into an OCR application.  I'm forced to scan to either a JPG or TIF or PNG.
As for attempting to resolve this problem I have done the following with no success:
Uninstall and reinstall the full software and drivers (and using the most recent version on the HP website)
Change USB ports and/or cables
Run the HP scan diagnostic utility, which seems to show an error at the WIA scanning step and then recommends that I uuninstall and reinstall the full software.  When I skip that and allow it to check for TWAIN scanning, it gives me a similar error, suggesting that I use the most recent version of the drivers (the driver that I am using is v 3.0 dated 11/12/2009)  Therefore in this case the HP scan diagnostic utility does NOT provide a fix for this problem other than uninstall and reinstall, which I have done several times to no avail
Contact HP support both for the computer and the multifunction printer (which as I understand are different support staff).  The printer staff claims it's a software problem and that the computer staff should be able to resolve it (something about not having "launchpad" installed properly.  When I contact the computer staff, they claim it's a printer driver issue.  So I am at a standstill
I researched the HP support forums only to find from this link - http://h10025.www1.hp.com/ewfrf/wc/document?docnam​e=c02661093&cc=us&dlc=en&lc=en&product=4089468&tmp​... - that if you cannot scan from HP software that you can use the programs that rely on WIA drivers (Windows Fax and Scan) which I already know I can do but implies that HP does NOT have a solution for how to scan using their own software!
My gut tells me that this is one of those problems that many others may have but for which there is no workable solution.  It's possible that during the course of uninstalling and reinstalling the software, remnants may remain behind that prevent proper functioning of the drivers, but without knowing how to specifically "clean" those remnants before reinstalling the software, I am at a loss.  Oh and by the way, I've also tried using CCleaner and Norton Registry Cleaner in an attempt to clean those remnants, but that effort didn't help.  
My question is basically this... does anyone know of a fix around this problem or must I resign myself to using the Windows Fax and Scan wizard to scan in documents and images and forget about using TWAIN programs as HP seems to be suggesting?  I would think that given that I am using an HP printer/scanner along with an HP computer with Windows 7 that this problem should NOT be a problem!  
This question was solved.
View Solution.

Answer 1

Before attempting to install the printer on my computer (HP slimline s5-1160), I had been able to successfully install the printer previously on two other computers: a Lenovo T-410 laptop (work computer using Windows XP) and an HP Pavilion Elite HPE (wife's computer using Windows 7).
On those computers, I can use the TWAIN driver from within applications without a problem, and the HPSCAN.exe file works as well.  Both computers connect to the printer wirelessly.
It is while trying to install the printer on my home computer via USB that I am having all sorts of difficulty. I have also tried to connect my s5-1160 to the printer wirelessly from my computer. I also checked the Windows Services, and all seems fine there.  I also tried switching USB ports and cables.   Again, no luck with the scanning using TWAIN driver. 
One other point: when I use the original installation CD that came with the printer to install on the s5-1160, the installation seems to stop when it says "Checking requirements for installation"  That didn't happen with the two other computers.   However, that problem doesn't happen the s5-1160 when I used the more recent version of the full software from the HP website.
Let me reiterate.  I have never had any problems with printing from any computer.  The scanner works fine from my s5-1160 if I resort to using the scanner and fax wizard using the WIA drivers.  What I am unable to do is to get the scanner to work from within an application using the TWAIN driver or if I use the native HP application (hpscan.exe).  Nothing seems to happen.   Because of that I cannot scan directly into a PDF.
And the only fix that the HP scan diagnostic utility continues to recommend is that I uninstall and reinstall the software.  It shows errors in the WIA scanning step and TWAIN step.
Is it possible that because of behind-the-scenes Windows updates that my s5-1160 is receiving that a software conflict is created that prevents the TWAIN driver from functioning properly?  Other than that I am at a loss to figure out why this is happening.