Canon Postscript Printer Driver Windows 7 Install Update
All of our printers are actually "printer connections" to print queues shared from a Windows Server R2 server. The server has the necessary v3 drivers and the configuration of each printer, and downloads them to the client computer when the printer connection is added.
This works fine for and bit Windows 7 clients for all 3 of our major drivers: All our drivers are Windows 7-style "v3" drivers; we don't yet have the server support for Windows style v4 drivers. Now that we're starting to deploy bit Windows 10 Enterprise, we're seeing a new problem with this PrintUI approach. However, the same PrintUI command for a Canon fails, if it is the first Canon printer on the client computer.
In other words, the driver installation is failing. If a technician manually runs the "Add Printer" wizard and provides elevated credentials to install the signed driver, then subsequent PrintUI commands for Canons work fine on the computer. That workaround does not help with the new Windows 10 problem; though the computer shows the Canon driver successfully installed in printmanagement.
We didn't have enough Windows 8 or 8. All our Windows 10 computers are currently version ; we didn't have the original version long enough to know if it had the problem. I cannot find any documentation on the Microsoft Web site that describes how Windows 10 clients might handle scripted printer additions differently than earlier versions of Windows.
I cannot find any comments anywhere to suggest that PrintUI works any differently under Windows 10 than it did with Windows 7. None of the printer drivers are the very latest versions, but none is older than a year either.
Has anyone out there seen anything like this in their move to Windows 10? Can anyone give me a starting point for research? Any help will be greatly appreciated. The PrintUI command printui. The Event Log shows a misleading error: This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.
These are misleading because: I cannot try a newer driver. I have only the one print server, and if I add a test queue with a newer driver, the print server starts upgrading all the existing print queues to the newer driver, which disrupts our labs. I have to wait for a maintenance window to do anything with the driver.
I cannot run the PrintUI commands as an administrator. We have no global administrator account to use for this. And we do not use Group Policy in our environment. Can you see my hands tied behind my back? Despite all this bad news, I think I have some good news, or at least a workaround. It talks about "package-aware" drivers.
By the time I found this Microsoft article, I had found a workaround, and it matches the advice given in the article: Fortunately, the PrintUI command set can help with this; unfortunately, it's not as simple as they suggest.
I sure hope they fix their drivers soon. And I posted all this information here because one of you out there is going to encounter the same PrintUI problem with a different printer manufacturer or driver, and I wanted to share this workaround I found. As this issue is specific to Windows 10, I have moved this thread into Windows 10 forum so that you would get more efficient support.
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff microsoft.
If it is possible, please try to download the latest printer driver from the Canon website. Since manually adding the printer with elevated credentials will work. We could try to run the script manually with administrator permissions to have a test.
As a workaround, we could try the following gpo to deploy the printer. Setting up Printers via Group Policy https: Please mark the reply as an answer if you find it is helpful. PrintUI commands to add a printer connection only work if there is no existing printer with that name installed on this computer. I tried just about every solution out there with no avail.
I even tried to uninstall the update but I can't find it since it was included in the anniversary update. Another workaround that I found is to change a registry setting for the printer driver to make the server think it is package aware. This is not the best solution but it works until Canon produces a better driver for us to use. Basically you need to go to. Make sure the hex value ends in an ODD number most of mine were showing 4 so I changed them to 5.
Best Regards, Amy Please remember to mark the replies as answers if they help and un-mark them if they provide no help. Wednesday, July 27, 6: If you have feedback for TechNet Support, contact tnmff microsoft. Thursday, July 28, 3: Any help would be greatly appreciated.
Tuesday, August 2, 5: Thursday, August 4, 3: Sande Does this solution work for you? Because I get errors while trying to run it. I'm trying to add a shared Xerox WorkCentre network printer I tried just about every solution out there with no avail. Monday, September 5, 4: This is not the best solution but it works until Canon produces a better driver for us to use http: Thursday, September 29, 9: Thank you, thank you, Bernard!
I had searched all the Canon resources I could find online, but never found this answer. This is such a simple fix, compared to what I have been doing. Thursday, September 29, Edited by Sande Thursday, September 29,
Welcome to Canon Support
I am trying to convert Pagemaker 7. Please repost your question in the Windows7 Forum at: Did this solve your problem? Sorry this didn't help. So if someone wants to get an answer to this problem, those links will do you no good at all.
Canon PIXMA iP8750 Driver & Software Download