![]() Printbrm -r -s printserver -f backup.printerexportĢ.There is a similar thread in QA forum that the user finally choose higher version of another PDF printer as workaround.ģ.What is the patched KB that has broken the PDF printer and you could post the details in user voice forum for the product team to check further. Hopefully this will help point someone else in the right direction.ġ.If the print driver does install on the server, use the print backup utility c:\windows\system32\spool\tools\printbrm.exe to backup the driver and then restore the driver to the machine with the issue adding the driver to the driverstore. Not sure if this fix will do the trick long term, but so far after scrubbing out old printers, drivers, and pretty much cleaning out all registry / driver on the server its the only thing that has looked promising. I used the values that existed in the DriverStore - C:\Windows\System32\DriverStore\FileRepository on my servers. Note- the exact values of ntprint.inf_x86 and _64 might be specific to build or updates installed, I'm not sure that they are universal to 2016. I did the following and so far printing is back to normal for Type-4 drivers-ġ- ran "pnputil /enum-drivers" from a command promptĢ- used psexec to elevate and run regedit as systemģ- investigated the - HKEY_LOCAL_MACHINE\DRIVERS\DriverDatabase\DriverInfFiles\ntprint.infĤ- updated the (Default) value to include - ntprint.inf_x86_6fbb4b09e9354bf2 and ntprint.inf_amd64_6fbb4b09e9354bf2ĥ- updated the Active value to - ntprint.inf_amd64_6fbb4b09e9354bf2 for the active driver reference on the problematic machine, ntprint.inf_圆4. One thing I noticed was that the ntprint.inf file was referencing ntprint.inf_x86. Quick update- making a bit of progress on this (I think). It almost seems like whatever is in this update is breaking any/all of the Type 4 printer drivers.ĭoes anyone know a fix for this issue? We would like to have the updates installed to stay up to date and safe, but the PDF printer is a must have. This works, until the Windows updates are installed, which breaks the printer again. Performed a full reset and fresh windows install on the server. When going through the wizard to install the driver, we get the same error listed above. When clicking on the properties of the PDF printer, it mentions that the driver is not installed (although we believe it is). We are always presented with "Unable to install, Element not found". Uninstalled the printer and tried to reinstall. At first we could not locate the issue, but some time later, after uninstalling the Windows updates, the feature started to work again. We have been having an issue for the past 2 months where on all 4 of our Windows Server 2019 RDSH, the Microsoft Print to PDF feature stopped working along with other built in printers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |