Windows 7 microsoft enhanced point and print compatibility driver
Installing printer driver Microsoft enhanced Point and Print compatibility driver failed
OT: KB3000850(Nov’2014), KB3013769(Dec’2014), prnms003.inf and oem
Windows 8.1 update x64 (unitl Nov’2014 Update)
install Dec’2014 Update
Hotfix for KB3013769 & KB3000850
KB3000850(Nov’2014), KB3013769(Dec’2014), prnms003.inf and oem
Installing printer driver Microsoft enhanced Point and Print compatibility driver failed
Hotfix for KB3013769 & KB3000850
Step by step (for x64)
1.Uninstall KB3013769, restart PC
2.Uninstall KB3014442 and KB3000850, restart PC
oem
3.Re-install KB3000850 and KB3014442, restart PC
4.Open Command Prompt (cmd.exe) (Admin mode)
copy %windir%\WinSxS\amd64_ntprint.inf_31bf3856ad364e35_6.3.9600.17415_none_2c0b97e88e705434\Amd64\PS5UI.DLL %windir%\System32\spool\drivers\x64\3\PS5UI.DLL
copy %windir%\WinSxS\amd64_ntprint.inf_31bf3856ad364e35_6.3.9600.17415_none_2c0b97e88e705434\Amd64\PSCRIPT5.DLL %windir%\System32\spool\drivers\x64\3\PSCRIPT5.DLL
copy %windir%\WinSxS\amd64_ntprint.inf_31bf3856ad364e35_6.3.9600.17415_none_2c0b97e88e705434\Amd64\UNIDRV.DLL %windir%\System32\spool\drivers\x64\3\UNIDRV.DLL
copy %windir%\WinSxS\amd64_ntprint.inf_31bf3856ad364e35_6.3.9600.17415_none_2c0b97e88e705434\Amd64\UNIDRVUI.DLL %windir%\System32\spool\drivers\x64\3\UNIDRVUI.DLL
copy %windir%\WinSxS\amd64_ntprint.inf_31bf3856ad364e35_6.3.9600.17415_none_2c0b97e88e705434\Amd64\UNIRES.DLL %windir%\System32\spool\drivers\x64\3\UNIRES.DLL
KB3000850 have bug don’t update this 5 files.
5.Re-install KB3013769
6.Copy all text & save to XXXX.reg file, after double-click install it.
↓━━━━━━━━━━━━━━Copy all━━━━━━━━━━━━━━━━↓
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\PackageInstallation\Windows NT x86\DriverPackages\prnms003.inf_x86_2612b38ce6fb0ccb]
«DriverStorePath»=»C:\\WINDOWS\\System32\\DriverStore\\FileRepository\\prnms003.inf_x86_2612b38ce6fb0ccb\\prnms003.inf»
«CabPath»=»C:\\WINDOWS\\system32\\spool\\DRIVERS\\W32X86\\PCC\\prnms003.inf_x86_2612b38ce6fb0ccb.cab»
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\PackageInstallation\Windows x64\DriverPackages\prnms003.inf_amd64_2438fbe64075076f]
«DriverStorePath»=»C:\\WINDOWS\\System32\\DriverStore\\FileRepository\\prnms003.inf_amd64_2438fbe64075076f\\prnms003.inf»
«CabPath»=»C:\\WINDOWS\\system32\\spool\\DRIVERS\\x64\\PCC\\prnms003.inf_amd64_2438fbe64075076f.cab»
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\PackageInstallation\Windows NT x86\DriverPackages\prnms003.inf_x86_48858e330b88a3d7]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\PackageInstallation\Windows x64\DriverPackages\prnms003.inf_amd64_864418199e8fa69d]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-3\Microsoft enhanced Point and Print compatibility driver]
«InfPath»=»C:\\WINDOWS\\System32\\DriverStore\\FileRepository\\prnms003.inf_x86_2612b38ce6fb0ccb\\prnms003.inf»
«DriverVersion»=»6.3.9600.17480»
«MinInboxDriverVerVersion»=»6.3.9600.17480»
KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3\Microsoft enhanced Point and Print compatibility driver]
«InfPath»=»C:\\WINDOWS\\System32\\DriverStore\\FileRepository\\prnms003.inf_amd64_2438fbe64075076f\\prnms003.inf»
«DriverVersion»=»6.3.9600.17480»
«MinInboxDriverVerVersion»=»6.3.9600.17480»
KB3013769 have bug don’t update [KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\. \Microsoft enhanced Point and Print compatibility driver]
7.Open Command Prompt (cmd.exe) (Admin mode)
copy %windir%\WinSxS\amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.17480_none_4389c29fa7dabd7c\Amd64\PrintConfig.dll %windir%\System32\spool\drivers\x64\3\PrintConfig.dll
copy %windir%\WinSxS\amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.17480_none_4389c29fa7dabd7c\Amd64\unishare.gpd %windir%\System32\spool\drivers\x64\3\unishare.gpd
copy %windir%\WinSxS\amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.17480_none_4389c29fa7dabd7c\Amd64\unishare-pipelineconfig.xml %windir%\System32\spool\drivers\x64\3\unishare-pipelineconfig.xml
copy %windir%\WinSxS\x86_prnms003.inf_31bf3856ad364e35_6.3.9600.17480_none_e76b271bef7d4c46\I386\PrintConfig.dll %windir%\System32\spool\drivers\W32X86\3\PrintConfig.dll
copy %windir%\WinSxS\x86_prnms003.inf_31bf3856ad364e35_6.3.9600.17480_none_e76b271bef7d4c46\I386\nishare.gpd %windir%\System32\spool\drivers\W32X86\3\unishare.gpd
copy %windir%\WinSxS\x86_prnms003.inf_31bf3856ad364e35_6.3.9600.17480_none_e76b271bef7d4c46\I386\unishare-pipelineconfig.xml %windir%\System32\spool\drivers\W32X86\3\unishare-pipelineconfig.xml
9.Thanks my Registry Hotfix, Windows will create «Microsoft enhanced Point and Print compatibility driver» New versions CAB
Working well with enhanced Point and Print
The updated printer sharing mechanism is referred to as enhanced Point and Print, and it allows print clients to print to v4 shares without downloading the manufacturer-provided device driver from the print server.
Because client machines do not download the entire driver package when they connect with a print server that has enhanced Point and Print and v4 printer drivers, it is important to be aware of the following architectures. This information should help you to develop and package your v4 printer driver appropriately.
Windows 8 Client Connection Behavior
When a Windows 8 client connects to a shared print queue that is using a v4 printer driver, the client will try to obtain a driver that supports client side rendering. The client searches the local DriverStore for a driver with a HardwareID that matches the server driver’s PrinterDriverID. If one is found, that driver will be installed locally. Otherwise, the client will connect using the enhanced Point and Print driver.
In both cases, the client downloads configuration data from the server using GetPrinterDataEx calls. The configuration data includes data files like generic printer description (GPD) files, PostScript printer description (PPD) files, the driver property bag, JavaScript constraints and a resource DLL. The client also downloads the CAT file that was associated with the server’s driver.
The print system then examines the client and validates that the resource DLL contains no executable code. The print system also verifies that the downloaded files are valid and signed by the CAT file downloaded from the server. Any files that are untrusted will be deleted. The following diagram illustrates this configuration-related communication between a WindowsВ 8 client and shared print servers that use the v4 printer driver.
Windows 7 and Windows Vista Client Connection Behavior
WindowsВ 7 and WindowsВ Vista clients may also connect to shared print queues that use a v4 printer driver. In this case, however, the client will always download the enhanced Point and Print driver from the server. This driver uses server side rendering to ensure that the proper printer description language (PDL) is generated for the printer.
Configuration data is downloaded from the server in the same way for Windows 7 and Windows Vista client connections, using GetPrinterDataEx calls. If any downloaded files fail validation against the server’s CAT file, they are deleted. The following diagram illustrates this configuration-related communication between a Windows 7 or a Windows Vista client and shared print servers that use the v4 printer driver.
Shared printers that are backed by a v3 printer driver will continue to work using the existing Point and Print system.
Windows 7 microsoft enhanced point and print compatibility driver
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
Hello, here in the past week or so I’m starting to see a trend where a few Windows 7 x64 clients are running into printing issues, getting this error in their PrintService event log:
«Installing printer driver Microsoft enhanced Point and Print compatibility driver failed, error code 0xbc8, HRESULT 0x80070bc8. See the event user data for context information.»
Our setup is a Windows 2012 R2 print server with several type 3 and type 4 driver shared print queues using the «computer» directed «deploy with group policy» feature. Our current setup has been running smoothly for months. As you can imagine from the error the problem queues in question are the type 4 using the client side Microsoft enhanced Point and Print compatibility driver. The symptoms that the user sees are when they go to print to the printer they are presented with dialog boxes that indicate that the driver is not installed, such as, do you trust this printer or they are prompted to install a driver.
The only real issue I’ve had with our setup since it was first built was when I ran Windows updates on the print server back in July and I installed KB2962409 (June 2014 update rollup). Immediately after installing this update (other updates were installed as well but I suspected this one as causing the issue since this was the only update that was ran where printing was mentioned in the description) pretty much all v4 print driver users stated calling about having issue printing to v4 queues and they were being prompted to update their Microsoft enhanced Point and Print compatibility driver. Fortunately removing KB2962409 immediately resolved the issue.
Fast forward to a couple of weeks ago I ran Windows updates and installed KB2975719 & KB2984006 (Aug & Sept update rollup) among the other standard Windows updates. While no issues were noticed right away, we have had a small handful of computers show these symptoms since. Not sure if those updates are related at all, but wanted to throw that out there. Has anyone seen these issues before? Anyone know what’s causing this? Or even know how to fix it once the client computer is in this state? I don’t see anyway of repairing or reinstalling or updating the built in Microsoft enhanced Point and Print compatibility driver. The only fix I’ve found for this is reimaging the computer, which works perfect, but not the most ideal solution considering we don’t know what’s causing it, and if this issue will start to grow larger.
Windows 7 microsoft enhanced point and print compatibility driver
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I’ve recently installed some printers on Windows Server 2012 R2 to be shared on Windows 7 machines. I had no problems installing or sharing them, or installing them on the client machines. That was until a user discovered that when they’d change their preferences on one printer (to A5 sheets), those settings would be carried across to another of their installed printers (a different model).
I checked the drivers to discover that a number of the printers are using the Microsoft Enhanced Point and Print Compatibility Drivers instead of their native drivers.
I did a bit of reading on the subject and understand what this driver is, it doesn’t seem right that it should be carrying settings between different print devices that use this driver?
Has anyone else experienced this? Does anyone know how to rectify it? We can’t require users to change their settings each time they want to print to a different networked printer.
Answers
If you have Server 2003 TS boxes there is no way the Enhanced Point and Print compatibility driver will run there.
There is nothing wrong with switching to the Version 3 drivers. Once again you will need the 32bit and 64bit versions installed on the print server for software distribution.
Any share you created with the Type 4 drivers has some settings that will be totally nuked when changing from Type 4 to Type 3. You can only change the driver if the printer is not share.
Alan Morris Windows Printing Team
All replies
Thank you for posting your issue in the forum.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Andy Qi
TechNet Community Support
Here are some articles related to this issue. Hope they are helpful.
Configure Print and Document Services
Point and Print with Driver Packages
Working well with enhanced Point and Print
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Thanks for your reply. Unfortunately, I’ve read through all of those articles, plus others, and none of them seem to address the issue that we’re experiencing.
We have v4 drivers installed on our server which results in the Microsoft enhanced Point and Print compatibility driver being used on our Windows 7 clients. That’s as expected.
The problem is, for example, that our users have a HP and a Brother printer. They want to print A4 documents on the HP printer and A5 documents on the Brother. When they change the paper size to A5 on the brother printer and then go to print something on the HP printer, the paper size is A5 on that printer also so they have to change it back to A4. Every time they want to switch printers, they have to change the paper size. It shouldn’t happen this way. It seems to be because they’re sharing the Microsoft enhanced Point and Print compatibility driver.
Should I remove the v4 drivers from the server and manually install the v3 drivers? This seems like a backwards step. Surely others have managed to avoid this issue? I’m interested in knowing how.
Is this within the same application? Information from a co worker
The observed behaviour is due to application-specific design. Office apps ‘save’ the ‘active’ Paper size (ie: the devmode) with the document, so if a doc was saved with Letter active, then it’ll continue print as Letter unless the user explicitly changes it. The line length and location of page breaks often matter in Office apps, so they don’t switch the Page size arbitrarily.
Notepad is different in that it will use the default Paper size (technically, the entire devmode) of the ‘default’ printer at application startup. So, if the default is Letter, and the user selects a different printer, the page size will continue to be Letter unless the user explicitly changes it.
In most scenarios, all of a user’s printers will have the same default Paper size and so they don’t notice this behaviour. We typically only hear about the issue when Office documents are provided to users who have different defaults.
The issue isn’t limited to Paper size, but it’s usually the most noticed.
To reiterate, the behaviour is application specific, and different applications behave differently. Many are not impacted at all.
Windows 7 microsoft enhanced point and print compatibility driver
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
Hello, here in the past week or so I’m starting to see a trend where a few Windows 7 x64 clients are running into printing issues, getting this error in their PrintService event log:
«Installing printer driver Microsoft enhanced Point and Print compatibility driver failed, error code 0xbc8, HRESULT 0x80070bc8. See the event user data for context information.»
Our setup is a Windows 2012 R2 print server with several type 3 and type 4 driver shared print queues using the «computer» directed «deploy with group policy» feature. Our current setup has been running smoothly for months. As you can imagine from the error the problem queues in question are the type 4 using the client side Microsoft enhanced Point and Print compatibility driver. The symptoms that the user sees are when they go to print to the printer they are presented with dialog boxes that indicate that the driver is not installed, such as, do you trust this printer or they are prompted to install a driver.
The only real issue I’ve had with our setup since it was first built was when I ran Windows updates on the print server back in July and I installed KB2962409 (June 2014 update rollup). Immediately after installing this update (other updates were installed as well but I suspected this one as causing the issue since this was the only update that was ran where printing was mentioned in the description) pretty much all v4 print driver users stated calling about having issue printing to v4 queues and they were being prompted to update their Microsoft enhanced Point and Print compatibility driver. Fortunately removing KB2962409 immediately resolved the issue.
Fast forward to a couple of weeks ago I ran Windows updates and installed KB2975719 & KB2984006 (Aug & Sept update rollup) among the other standard Windows updates. While no issues were noticed right away, we have had a small handful of computers show these symptoms since. Not sure if those updates are related at all, but wanted to throw that out there. Has anyone seen these issues before? Anyone know what’s causing this? Or even know how to fix it once the client computer is in this state? I don’t see anyway of repairing or reinstalling or updating the built in Microsoft enhanced Point and Print compatibility driver. The only fix I’ve found for this is reimaging the computer, which works perfect, but not the most ideal solution considering we don’t know what’s causing it, and if this issue will start to grow larger.