This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 52%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJJ%3C/text%3E%3C/svg%3E)
Hello everybody,
we have some problems with displaying printers on Windows 10 Enterprise 2004 (Build 19041.508).
The printers are not displayed with the host name in the control panel. Instead, there is the model name of the respective printer. These display problems are also present in the Windows settings. If you choose one of the printers as default, the hostname appears in the control panel. If it is no longer a standard, it loses the host name again.
In addition, it takes more than 10 minutes to install a printer. Additional printers pending for installation will extend this time.
If you use a program such as Microsoft Word, all printers are correctly displayed with their hostnames in the printing area, even though the installation / setup of the printer in the control panel has not been fully completed yet.
Is there a known problem with the current Windows version? Is it related to drivers or driver versions?
I hope someone can help / support us with the problem.
Best regards
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 43%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
So far I've seen this issue on several test machines that I've upgraded from Win 10 Enterprise 1909 to Win 10 Enterprise 20H2, even clean installs of 20H2. Also, if I set a printer as default, the name changes to the correct share name, but if you set another printer as the default, then the previous default printer name reverts back to the driver name. This is happening with the HP and RICOH drivers, which are the only manufacturers we are using. I'm also using the latest drivers from these two manufactures. Looking at the printers in an Office application such Word they display normally.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 93%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAA%3C/text%3E%3C/svg%3E)
Seeing same exact issue... if you look at the printers inside the office application in word it shows correct display name.. hope there is a "solution" to this.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 96%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERG%3C/text%3E%3C/svg%3E)
I have been chasing this issue off and on for several YEARS. I recently returned to my current position after an absence of 3 years and started chasing it again.
This is the only relevant article I found discussing the issue.
Environment
Windows 2008R2 Standard
Virtual Machine installed some time in 2009 for the sole purpose of being a print server.
Printing was previously handled by our main file server.
Currently sharing 39 physical printers.
As IT support I setup and configure new workstations and assist users in problems.
The #$%^ naming of printers under Windows 10 creates endless frustration as the Windows Printer name label provides NO identifying information as to which printer is which.
Reviewing a few of my problem printers this morning I noticed an apparent correlation between the label Windows displays when searching for printers and the Bonjour Printer Service name displayed in the printer web interface.
For the HP M725, it appears under the Networking tab, TCP/IP Settings, Network Identification page.
For the HP M501dn, it appears under Networking tab, Network Identification.
It appears the default label here is set to HP Family Model Number Language (HOSTAME) by the printer itself. (We never set the Bonjour Service Name, we just ignore it.)
The string that was in this field matched the Name label displayed by Windows 10 search results minus the (HOSTNAME).
When I changed the field to match the printer sharename/HOSTNAME (we make them the same) the the Search results changed to display the entered Bonjour Service name with the Printer Model appended in brackets.
When I added the printer back in to Windows 10 it is now displayed as PRINTER SHARENAME (Printer Model label)
If this information is relevant to your situation and you experience the same results please leave a message confirming this behavior.
Funny how Microsoft Windows is using the APPLE print service name to label
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(32, 88%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAR%3C/text%3E%3C/svg%3E)
Not the same issue for me Rob - the driver name always replaces the share name.
Share name: Main Reception Ricoh - B&W
Driver name: Ricoh PCL6 UniversalDriver V4.30
Bonjour name: RICOH MP C6004 [002673C47EA3]
I'm going to log a MS case as I can't find a resolution.
That worked for me. So now we wait for MS to get their shite together...
Thanks for following up on this thread Jannik, great to get some useful info at last (why Microsoft can't publish this sort of thing is beyond me, but we are mere customers and it's not ours to question why).
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 6%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EF%3C/text%3E%3C/svg%3E)
Hi everybody.
I ran some tests on some windows 10 ver. 2004
We have Ricoh printers in production and are distributed via GPO.
If the server-based printers are using a v4 driver, they display correctly within 1/2 seconds.
If the printers use the specific printer driver, the printer model name is displayed.
At the moment, therefore, the solution for us is:
Do you have any news from Microsoft?
Do you use user code accounting, either in the printer directly or externally with Papercut etc? Type 4 drivers typically haven't worked for us in that respect.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 23%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEF%3C/text%3E%3C/svg%3E)
Any luck with MS?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 32%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH%3C/text%3E%3C/svg%3E)
OMG I have this same exact issue. For a week now I have been trying everything I can think of, even called our Printer Vendor who was confused. I started a discussion on this within Spiceworks too. Since I don't think it's a cut/dry solution.
I upgraded our NAS to Windows 2019 and it's exhibiting the same dang issue as our 2012 R2.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 73%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBH%3C/text%3E%3C/svg%3E)
As we had this same issue with 2008R2, before migrating everything to 2019 server, so it isn't the server OS causing the issue.
Makes sense, maybe in the call for the driver? I'm really surprised this isn't fixed yet. I was dealing with this issue two years ago around this same time on our 2012 R2. Once I tried to update the drivers, everything broke. So I placed all the printers back on the old drivers and didn't deal with it until this month updating to 2019.
I have had Ricoh Japan collect videos and logs, but they say they are unable to reproduce the issue, or they tell me to remove all my Ricoh drivers from the server/PC's, install all the newest, and see if that works - they want all old driver info completely nuked from the equation. As you know, that would be pretty disruptive to test across an organization... If I could test just one copier, I would, but to remove all of them and deploy all new ones? I can already hear my phone ringing off the hook from 150 end users complaining about their printers being all messed up...
What I am finding is that Ricoh is way too eager to point the finger at Microsoft, which doesn't make sense, as it is only Ricoh's printers that are installing with that 400 entry in the registry, no other printers (at least in my environment and I have HP's that work perfectly fine).
This should be between Ricoh and Microsoft to figure out, not us.
Same here. HP and Samsung load correctly. It is only our RICOHS, all same model numbers. I've tried updating their latest May PCL6 Universal Driver and it's still an issue. I did just try a GPO regedit but would need to somehow wildcard the last folder in order for this to work in environments. Since using * doesn't work on the folder nor the key itself for SYSTEM\CurrentControlSet\Enum\SWD\PRINTENUM*\
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 50%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Guys, any updates?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 11%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMC%3C/text%3E%3C/svg%3E)
Windows 11 fixed the V3 driver issue not displaying the name. We were also able to move some printers to the V4 driver that was newly released and fixed the extra error page after each print job.
Hello,
Please run Printer troubleshooter from Control Panel > Troubleshooting > View all. Let us know what it reports back.
Regards.
Hi @Kapil Arya ,
thanks for your answer.
When I run that the printers will show with their hostnames while troubleshooting runs. But after a short time, I think when they get initialized again they loose the hostnames and change back to the model name.
Best regards
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 56.00000000000001%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJW%3C/text%3E%3C/svg%3E)
Having the exact same issue here, on a Dell laptop with a newly reinstalled Windows 10 Pro, build 19041.058, fully patched. Network printer installation takes 5-10 minutes. On 1909 PCs, it's taking seconds.
If I open the "manage" console on a printer just installed (showing model name and not the directory name) and try to open Printer Properties, I get the error "Printer properties cannot be displayed. The system call level is not correct." I'm logged in as the domain admin.
Running a test print errors out with "You do not have permissions to modify the settings for this printer. If you need to change the settings, contact your system administrator."
I ran the troubleshooter, which found no problems/couldn't identify it. So, MS broke printing again with 2004. Yay.
I wanted to follow up on this issue. This seems to be the one and only hit on the Internet for this problem. I had hoped that the October 2020 cumulative update would fix the problem, but no. Nothing in event viewer, no clues or signs as to what the issue could be anywhere I checked. DISM and SFC had no effect. This stupid thing is a complete ghost.
Reinstalling from within Windows recovery did nothing, as it would just reload the existing OS build and updates, even when opting to wipe everything out. This was a direct install from a 2004 installation, so no rolling back to 1909. System restore was no help either.
So, I had the installation media for 1903 still laying around and blew the installed OS away. Updated to 1909 and no more printer installation issue.
If you're one of the unlucky souls who have washed up here, vainly looking for a solution to your stupid, stupid printer install problem, save your energy and don't bother troubleshooting for a week like I did.
Dust off and nuke it from orbit, just to be sure. It's 2020. Don't hope that dumb luck may eventually smile on you with an answer. It won't. It already left town with Jack.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 5%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENE%3C/text%3E%3C/svg%3E)
Same problem also to me. On windows 10 2004 updated computers and windows server 2016 updated servers.
I tried many workaround without success.