Event 513 PrintService Error

In the Event Viewer, I get this error every time any user logs onto this PC:"Group Policy was unable to add per computer connection \\COOLERMASTER-PC\HP Deskjet 2520 Series. Error code 0x7b. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server."
I reinstalled the driver to no avail. I checked the printer name and it is consistent. This is a PC with the printer attached via USB. Although connected to a modem/router, it is not a print server for a network. The best I can tell is that Windows now treats all printers via a print server interface. I've searched the net and tried a few things. I still get this error. The printer prints fine though. I've been wondering if it has to do with the order of loading services.


Here's the full error data:

Event 513 PrintService 4/4/17 07:29:58
- UserData
- RouterError
Name \\COOLERMASTER-PC\HP Deskjet 2520 Series
Error 0x7b

Log Name: Microsoft-Windows-PrintService/Admin
Source: Microsoft-Windows-PrintService
Date: 4/4/17 08:29:58
Event ID: 513
Task Category: Routing print spooler command(s)
Level: Error
Keywords: Router,Classic Spooler Event
User: CoolerMaster-PC\Geoffrey
Computer: CoolerMaster-PC
Description:
Group Policy was unable to add per computer connection \\COOLERMASTER-PC\HP Deskjet 2520 Series. Error code 0x7b. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-PrintService" Guid="{747EF6FD-E535-4D16-B510-42C90F6873A1}" />
<EventID>513</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>39</Task>
<Opcode>12</Opcode>
<Keywords>0x8000000000002800</Keywords>
<TimeCreated SystemTime="2017-04-04T01:29:58.425426700Z" />
<EventRecordID>3111</EventRecordID>
<Correlation />
<Execution ProcessID="1372" ThreadID="1400" />
<Channel>Microsoft-Windows-PrintService/Admin</Channel>
<Computer>CoolerMaster-PC</Computer>
<Security UserID="S-1-5-21-3009858439-3883855071-2290318543-1000" />
</System>
<UserData>
<RouterError xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2...er/core/events">
<Name>\\COOLERMASTER-PC\HP Deskjet 2520 Series</Name>
<Error>0x7b</Error>
</RouterError>
</UserData>
</Event>

Hi HH,
The error keyword is pointing at the router first.
and as you can print in my opinion that takes printer/usb drivers out of the equation.
Have a look at your router logs and GPO rules for it.

Roy

Thanks Roy, I popped 192.168.100.1 into my web browser and looked at my router log - nothing about this error (it was pretty bare bones, just device id and a failed login).
I opened the Local Group Policy Editor and searched for an entry for the router. I didn't find anything. I wouldn't really expect to as the router is not installed on the computer like a printer. I suspect, being a bit of a novice to this deep of administration, that I've misinterpreted your direction. Respectfully yours, Geoffrey

Well, just for kicks, I tried uninstalling the printer driver. Probably unsurprising to you, the Event is still there, albeit with a different error code (0x709 instead of 0x7b). I'd love a little more direction on this.

These are the contents of my HuaWei HG8245 router log file:
I'm wondering if something else is meant by "router logs" in the above post.
Manufacturer:Huawei Technologies Co., Ltd;
ProductClass:HG8245;
SerialNumber:48575443DD331A21;
IP:192.168.100.1;
HWVer:130D4600;
SWVer:V1R003C00S108;

1970-01-01 00:00:46 [Critical ] Reset reason: power off!
2017-03-20 13:26:41 [Error ] [WEB](++++++++++,**********) from ip:192.168.100.4 login faild!

I stopped and started the print spooler service. The error did not repeat. This error happens only when a user logs in. Uninstalling the printer driver doesn't make the event go away; it does change the error code. I've ardently tried to completely uninstall the driver. I don't know how windows can still refer to a driver that is completely uninstalled.

It appears to me that the real culprit in this problem was that the printer was deployed per user and per computer. Removing the deployments allows the printer to be accessed by all users on this one computer with no errors. One note - I have 4 workstations running off of 1 PC using SoftXpand MiniFrame software.