Windows Print queue display unknown driver. Printer has been reinstall several times

[MTB1028]

HP 8720 is  failing with an unknown driver.  I have reinstalled the HP software several times with reboots.  The Scan Doctor does not show and error, but it will not print a test page either.  I can print a diagnostic page from the HP 123 app, bun not from any Windows applications that use the Windows print queue.  I have installed the latest firmware on the printer and have also downloaded the lastest HP driver.  

[Betty0610]

@MTB1028

Welcome to the HP Support Community.

Let's try to do a root uninstall and reinstall of the software:

Unplug any USB cable, if any, before doing this.

1.) In Windows, search for and open Programs and features

2.) Select your HP Printer

3.) Select Uninstall

4.) In Windows, search for and open Devices and printers

5.) In the Devices and Printers windows look for your HP printer. If you see it listed right-click on it and choose 'Delete' or 'Remove Device'

6.) Open up the run command with the "Windows key + R" key combo.

7.) Type printui.exe /s and click Ok. (Note: there is a space in between “printui.exe” and “/s”)

8.) Click on the "Drivers" tab

9.) Look for HP Printer driver. If you see it Click on it and click Remove at the bottom

10.) Select Ok

11.) Select Apply and Ok on the Print Server Properties windows

12.) Close Devices and Printers

13.) Open up the run command with the "Windows key + R" key combo

14.) Type c:/programdata and click Ok. Go to Hewlett Packard folder, remove any printer related folders & files.

15.) Restart the computer.

Once done, please download and install the software from here:

https://support.hp.com/in-en/drivers

Let me know if this helps.

If the information I've provided was helpful, give us some reinforcement by clicking the Accepted Solution and Kudos buttons, that'll help us and others see that we've got the answers!

Thanks!

Have a great day!

[MTB1028]

Hi,  I did reply, but the message did not post.

I followed your recommendations but it did not resolve it.  I get the following errors in the event log whenever I attempt to print.

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          5/25/2020 11:09:15 AM
Event ID:      10016
Task Category: None
Level:         Warning
Keywords:      Classic
User:          MTB-PC-0001\MTBennett1
Computer:      MTB-PC-0001
Description:
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
 and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
 to the user MTB-PC-0001\MTBennett1 SID (S-1-5-21-2386778706-1139788029-1226644935-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.

[Betty0610 · Accepted solution]

Let's create a TCP IP port:

1. Print a Configuration Page to get the printer's IPv4 address (you can also tap on the wireless icon on the front panel of your Printer to get the IP address)

2. On your PC, go to Control Panel, from Devices and Printers, right-click the printer and left-click Printer Properties, select the Ports tab.

3. Click Add Port, select Standard TCP/IP Port, then select New Port and follow the wizard.

4. Type in the proper IP address for the printer.

This video resource will show you how to do it:

Create & Use TCP IP port

Let me know if this helps.

If the information I've provided was helpful, give us some reinforcement by clicking the Accepted Solution and Kudos buttons, that'll help us and others see that we've got the answers!

Thanks!

Have a great day! 

[MTB1028]

Hi betty0610,

That worked!!  I am singing your praises all the way to the printer.  

I am courious, why would it resolve the address using the tcp/ip protocol instead of the WSD port? 

[Betty0610]

The WSD is not a port, but a port monitor. A port monitor looks at the information coming in from the TCP/IP port and makes changes or routing depending on what comes into the port.

When data comes into the TCP/IP port, a port monitor is there watching for that to occur. The WSD port monitor would take over that function from the regular TCP/IP port monitor.

Assigning a TCP/IP port can bypass the port monitoring.

Hope this helps 🙂