Download Drive Ricoh Aficio Mp 171
Osoulo Lejeune
Visit FAQ section for questions regarding user code, printing lots of blank pages, error code SC738, printing protocol, multiple copies, duplex on Mac, etc. Download the PPD directly is easier and faster since it has no dependency requirement and the file size is much smaller. Visit FAQ section for installing a PPD file. Download the driver package if you want to install all drivers (100+). Throughput 37.
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.
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:
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...
In registry there is the path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\SWD\PRINTENUM under that key there are subkeys with the IDs of all installed printers. Every single ID has the property named "ConfigFlags". When changing its value to "0" (hexadecimal) it should use the hostname for displaying. In this bug the value is "400" (hexadecimal) and it uses the name of the driver.
Not only this, it also fixes printer installation problem, when it takes about 15-20 minutes to install driver!
I've tryed to install network shared printer directly from print server, printer appears in Control Panel as unidentified device. After that i changed "ConfigFlags" key to "0" , restarted Print Spooler service and printer finished installation with a few seconds!
But the problem still in, that printer should be already registered with GUID in the system registry to fix it.
We running on Win10 20H2.
Like you, when changing that 400 to 0 in the registry, everything works just fine for all my Ricoh's, but why are those 400's being entered in the first place? I sure hope someone fixes this soon, I can't take this bug any longer. To me, this would seem like a Ricoh issue because the drivers are what write those entries in the registry, which is why I am surprised that you said Microsoft indeed admitted there was a bug.
We have had the same issue on computers running Windows 10 2004, with a couple of different ricoh printers. We tried to use the Ricoh PS Universal Driver, instead of the PCL version, and it seems to solve the issue.
The PowerShell script is only useful once the registry keys exist, which only happens after the deployment/driver install is initiated (which is slow), so essentially you can either wait for multiple group policy check intervals to occur, or if you are on a new system (or are in a hurry) just simply keep launching gpupdate /force from a command prompt on the target system until all the printers show up as desired.
With this workaround I was able to drop the deployment time of 5 network printers from a WS2016 print server on W10 20H2 clean load from 20+ minutes to under 5 min, and have all the printer name show up correctly. (All HP LJ printers and MFPs, all Type-3 drivers)
Students of Jefferson 2 posing with their teacher, Alice Riedesel, on their float at the Waverly, Iowa, Fair of 1910. The float is a farm wagon drawn by four horses. The male driver stands on the float holding the reins. Three other men pose beside the horses.<br><br>Message on back from T.L.H. to unidentified receipient.
aa06259810