Laserjet 3015 Not Detected as Scanner in Windows 11

[etr3]

In a nutshell, I have a LaserJet 3015 All-in-One that works as a scanner in Windows 10, but I have not been able to scan with it in Windows 11. Printing has been working in both versions of Windows, but the pickup roller has developed an issue that prevents me from re-verifying at the moment. 

Comparing the two machines (Windows 10 vs Windows 11), the most pronounced difference I see is in the list of drivers installed.  Specifically, looking at:

Devices and Printers => (Entry for LaserJet 3015) => Right Click => Properties => Hardware Tab

I see the following list for Windows 11(Name :: Type)

HP LaserJet 3015 :: Universal Serial Bus controllers

hp LaserJet 3015 UPD PCL6 :: Print queues

HP PNP Scan Null :: System Devices

HP Printer :: IEEE 1284.4 compatible printers

HP Universal Printing PCL 6 :: Printers

For comparison, I see the following in Windows 10 (Name :: Type)

HP LaserJet 3015 :: Universal Serial Bus controllers

HP LaserJet 3015 Scanner :: Imaging Devices

HP Print Device UPD PCL 6 :: Print queues

HP Printer :: IEEE 1284.4 compatible printers

HP Universal Printing PCL 6 :: Printers

To highlight the interesting difference, Windows 10 has an "HP LaserJet 3015 Scanner" device where Windows 11 has a "HP PNP Scan Null" device.  The device name in Windows 11 almost sounds like a functionless placeholder. 

The only other notable difference is that I was using the 7.0.1.24923 version of the UPD in Windows 10, versus the 7.0.1.25570.  (I almost certainly started with the same version with Windows 10, but tried the latest driver when I re-installed). 

Beyond that, it's worth highlighting what I've tried so far. 

* Re-installed the HP Universal Print Driver (Removed Prior Drivers, Installed USB/Dot4 driver first, then installed the USB version of the HP UPD)

* Run the HP Print and Scan Doctor 5.7.4 => This gets to Step 2 and then shows a green check next to "Recommended Updates" and a red "X" next to "Device Manager".  The remaining progress boxes ("Device Status", "Windows (WIA) Scan", "HP Twain Scan", "HP Scan", and "Test Scan") have empty circles.  I have let the application restart the PC, and gotten the same results afterwards.  At that point, the application refers me to HP support. 

* I have made sure that all of the following services are running (and set for Automatic start): Windows Image Acquisition (WIA), Remote Procedure Call (RPC), DCOM Server Process Launcher, RPC Endpoint Manager, Shell Hardware Detection

* I have changed the logon for the Windows Image Acquisition (WIA) service to Local System Account and enabled the "Allow service to interact with desktop" option.  (I found this necessary to get scanning working in Windows 10 recently.) 

To test, my go-to is Windows Fax and Scan.  When I click the "New Scan" button, I get the following message: 

"No scanners were detected.  If a scanner is installed, make sure that it is powered on and connected to the computer, and then try again." 

I am using the same USB cable when I connect the printer to the two machines (Windows 10 and Windows 11). 

Thank you! 

[Valsimot]

The UPD drivers in WIN11 supports print only. Universal print driver is for print only, you will hardy get it to scan.

[etr3 · Accepted solution]

First of all, many thanks for the reply!!  Knowing that the Universal Printer Driver does not provide the scanner driver is very helpful! 

I now have the scanner in the LaserJet 3015 working with Windows 11. 

Ultimately, I had to use a Microsoft-supplied driver (obtainable for Windows update).  Underlining your point, I found out that I had been using a Microsoft-supplied driver in Windows 10, as well. 

I obtained the driver as follows: 

Windows Update => Advanced Options => Optional Updates (under Additional Options) => Driver Updates

I found the driver I needed in that list, marked the check box next to it, and clicked the "Download & Install" button.  Please note that you likely need the printer connected and powered up for Windows to off the option to download a driver for it. 

Thanks again for the advice, and I've tried to capture enough to be helpful should anyone else run into this. 

PS: Apologies to you, Valsimot, but I will go ahead and mark this post as the solution, so that if anyone else searches this they can quickly see there is a path forward for this printer.  I'd mark both posts as solutions if I could.  However, I still want to offer my hearty thanks!