Как удалить драйвер принтера в Windows 8

Приветствую вас, мои дорогие читатели. Как удалить драйвер принтера в Windows 8? Таким вопросом задались пользователи системы Windows 8. На блоге я уже рассказывал про удаление драйвера от принтера, но по сравнению с Windows 7, процесс удаления несколько отличается, однако первый шаг одинаковый – нам необходимо попасть в «Панель управления».

Я не буду здесь расписывать разные способы, как это можно осуществить, приведу лишь один пример: на клавиатуре зажимаем клавиши «Win» + «X».

В появившемся меню снизу экрана слева, выбираем «Панель управления», которая может также называться «Control Panel». Когда она открылась, напротив надписи «Просмотр» нужно установить параметр «Категории», далее кликнуть левой кнопкой мыши по пункту: «Удаление программы».

В появившемся списке ищите название модели своего принтера, выделяем его и нажимаем кнопку «Удалить».

Но это только первый шаг. Далее снова заходим в «Панель управления», затем под «Оборудование и звук» нажмите «Просмотр устройств и принтеров».

Правой кнопкой мыши нажимаем по интересующему нас принтеру (их может быть несколько) и выбираем пункт «Удалить устройство».

Появится сообщение, в котором нажимаем «Да». Тем самым соглашаемся удалить это устройство.

Как только удаление завершилось, снова пользуемся теперь уже знакомой комбинацией клавиш «Win» + «X», и в выпадающем меню кликаем по пункту «Выполнить».

Теперь введите команду: «Services.msc» (без кавычек).

Перед вами откроется длинный список всех служб. Ищем среди них ту, которая называется «Диспетчер печати» и щелкаем по ней правой кнопкой мыши. В появившемся меню кликаем на «Перезапустить».

Теперь пришло время, наконец, узнать, как удалить драйвер принтера в Windows 8 окончательно. Нам снова предстоит воспользоваться сочетанием клавиш «Win» + «X» и зайти в «Выполнить». Только в этот раз нам нужно будет скопировать в поле ввода уже другую команду: «printui /s /t2» (разумеется, снова без кавычек). Окно, которое откроется на вашем экране, называется: «Свойства: Сервер печати». Необходимо зайти во вкладку «Драйверы» и там вновь щелкнуть по названию модели своего принтера. Нажимаем кнопку «Удалить…» в нижней части окошка. Когда появится подтверждающее диалоговое сообщение, устанавливаем в нем галочку напротив: «Удалить драйвер и пакет драйвера» и кликаем «ОК».

Все! Я вас поздравляю, драйвер принтера успешно удален с персонального компьютера и теперь можно смело ставить новый. Однако для перестраховки следует провести проверку. Выполняем уже знакомые нам команды: «Win» + «X», затем «Выполнить». Вводим команду «printmanagement.msc». Откроется окно, где находим в левой его части «Настраиваемые фильтры» — нажимаете, а в ней – «Все драйверы». Справа появится список, в котором находите модель своего принтера, нажимаете по нему правой кнопкой мыши и выбираете: «Удалить пакет драйвера».

Если будете устанавливать драйвер на принтер, то сделайте перезагрузку компьютера. После чего можете устанавливать новый драйвер принтера.

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.

Microsoft enhanced Point and Print compatibility driver printer driver is not installed on this computer

We are running Windows 7 Enterprise 64 Bit virtual desktops (using VMware View 6.1) and connecting users to a Type 4 Xerox printer driver/queue being hosted off of a Windows 2012 R2 Server. The driver on the server is listed as «Xerox WorkCentre 7970 V4 PCL6» and when the Windows 7 user connects to it the driver appears as «Microsoft enhanced Point and Print compatibility driver». Within the Win7 client’s «Print Management» it appears as version 6.3.9600.17415

The Printer works fine during their Windows session, they log out and when they log back in the print queue is still there but when you right click and go to «printer properties» it throws the following error

«The ‘Microsoft enhanced Point and Print compatibility driver’ printer driver is not installed on this computer. Some printer properties will not be accessible unless you install the printer driver. Do you want to install the driver now?»

Removing the queue then re-adding it fixes the issue for the Windows session you are in.

Side note: We are using VMware’s Persona Management to save user’s profile data across logoffs since the virtual desktops are non-persistent. I’ve only been able to reproduce this in Windows 7 using a virtual desktop, I can’t reproduce it on my physical Windows 7 box.

We are getting around this by using group policy and a vbs script to remove the queue on logoff then another script to re-add it on logon but that’s just a band-aid.

Also, a Type 3 driver works fine across logoffs but we need the Type 4 driver in this instance.

Installing printer driver Microsoft enhanced Point and Print compatibility driver failed

OT: KB3000850(Nov’2014), KB3013769(Dec’2014), prnms003.inf and oem.inf

Windows 8.1 update x64 (unitl Nov’2014 Update)

install Dec’2014 Update

>>> [Uninstall Driver Updates]
>>> Section start 2014/12/10 11:42:16.425
cmd: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17477_none_fa2b7d3b9b36c7b4\TiWorker.exe -Embedding
sto: Image State = Specialized
sto: Image Architecture = amd64
sto: Driver Updates = 1
sto: 11:42:16.440
sto: Driver Package = prnms003.inf_amd64_864418199e8fa69d
idb: 11:42:16.440
idb: Driver package ‘prnms003.inf_amd64_2438fbe64075076f’ is already active.
idb: 11:42:16.440
sto: 11:42:16.440
sto: Higher version of ‘prnms003.inf’ is currently reflected.
sto: Filename = C:\WINDOWS\System32\DriverStore\FileRepository\prnms003.inf_amd64_2438fbe64075076f\prnms003.inf
>> [Unstage Driver Updates]
>>> Section start 2014/12/10 11:42:16.440
cmd: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17477_none_fa2b7d3b9b36c7b4\TiWorker.exe -Embedding
sto: Image State = Specialized
sto: Image Architecture = amd64
sto: Driver Updates = 1
sto: 11:42:16.456
sto: 11:42:16.456
sto: 11:42:16.456
idb: 11:42:16.456
idb: Unregistered driver package ‘prnms003.inf_amd64_864418199e8fa69d’ from ‘prnms003.inf’.
idb: Deleted driver package object ‘prnms003.inf_amd64_864418199e8fa69d’ from DRIVERS database node.
idb: Driver packages registered to ‘prnms003.inf’:
idb: prnms003.inf_x86_2612b38ce6fb0ccb
idb: prnms003.inf_x86_48858e330b88a3d7
idb: prnms003.inf_amd64_2438fbe64075076f
idb: 11:42:16.456
cpy: 11:42:16.456
cpy: 11:42:16.456
cpy: 11:42:16.488
cpy: 11:42:16.503
sto: 11:42:16.503
sto: 11:42:16.503
sto: 11:42:16.503
>> [Uninstall Driver Updates]
>>> Section start 2014/12/10 11:42:16.628
cmd: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17477_none_fa2b7d3b9b36c7b4\TiWorker.exe -Embedding
sto: Image State = Specialized
sto: Image Architecture = amd64
sto: Driver Updates = 1
sto: 11:42:16.644
sto: Driver Package = prnms003.inf_x86_48858e330b88a3d7
idb: 11:42:16.644
idb: Driver package ‘prnms003.inf_amd64_2438fbe64075076f’ is already active.
idb: 11:42:16.644
sto: 11:42:16.644
sto: Skipping non-native x86 driver package ‘prnms003.inf’ on amd64.
>> [Unstage Driver Updates]
>>> Section start 2014/12/10 11:42:16.644
cmd: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17477_none_fa2b7d3b9b36c7b4\TiWorker.exe -Embedding
sto: Image State = Specialized
sto: Image Architecture = amd64
sto: Driver Updates = 1
sto: 11:42:16.660
sto: 11:42:16.660
sto: 11:42:16.660
idb: 11:42:16.660
idb: Unregistered driver package ‘prnms003.inf_x86_48858e330b88a3d7’ from ‘prnms003.inf’.
idb: Deleted driver package object ‘prnms003.inf_x86_48858e330b88a3d7’ from DRIVERS database node.
idb: Driver packages registered to ‘prnms003.inf’:
idb: prnms003.inf_x86_2612b38ce6fb0ccb
idb: prnms003.inf_amd64_2438fbe64075076f
idb: 11:42:16.660
cpy: 11:42:16.660
cpy: 11:42:16.660
cpy: 11:42:16.691
cpy: 11:42:16.691
sto: 11:42:16.706
sto: 11:42:16.706
sto: 11:42:16.706
>> [Setup Import Driver Package — C:\WINDOWS\system32\spool\DRIVERS\W32X86\<5112a0bc-c78d-45a1-92e5-1895a9747c63>\prnms003.inf]
>>> Section start 2014/12/10 12:41:51.583
cmd: C:\WINDOWS\System32\spoolsv.exe
inf: Provider: Microsoft
inf: Class GUID: <4d36e979-e325-11ce-bfc1-08002be10318>
inf: Driver Version: 06/21/2006,6.3.9600.17415
inf: Catalog File: prnms003.cat
pol: 12:41:51.973
pol: 12:41:51.973
sto: \prnms003.inf> 12:41:51.973
inf: \prnms003.inf> 12:41:52.004
inf: Driver package is fully isolated.
inf: Driver package ‘prnms003.inf’ is configurable.
inf: 12:41:52.020
flq: Copying ‘C:\WINDOWS\system32\spool\DRIVERS\W32X86\<5112a0bc-c78d-45a1-92e5-1895a9747c63>\prnms003.cat’ to ‘C:\WINDOWS\System32\DriverStore\Temp\<4b6285d8-5f78-2043-b214-1c7767e72553>\prnms003.cat’.
flq: Copying ‘C:\WINDOWS\system32\spool\DRIVERS\W32X86\<5112a0bc-c78d-45a1-92e5-1895a9747c63>\prnms003.inf’ to ‘C:\WINDOWS\System32\DriverStore\Temp\<4b6285d8-5f78-2043-b214-1c7767e72553>\prnms003.inf’.
flq: Copying ‘C:\WINDOWS\system32\spool\DRIVERS\W32X86\<5112a0bc-c78d-45a1-92e5-1895a9747c63>\I386\unishare.gpd’ to ‘C:\WINDOWS\System32\DriverStore\Temp\<4b6285d8-5f78-2043-b214-1c7767e72553>\I386\unishare.gpd’.
flq: Copying ‘C:\WINDOWS\system32\spool\DRIVERS\W32X86\<5112a0bc-c78d-45a1-92e5-1895a9747c63>\I386\unishare-pipelineconfig.xml’ to ‘C:\WINDOWS\System32\DriverStore\Temp\<4b6285d8-5f78-2043-b214-1c7767e72553>\I386\unishare-pipelineconfig.xml’.
flq: Copying ‘C:\WINDOWS\system32\spool\DRIVERS\W32X86\<5112a0bc-c78d-45a1-92e5-1895a9747c63>\I386\PrintConfig.dll’ to ‘C:\WINDOWS\System32\DriverStore\Temp\<4b6285d8-5f78-2043-b214-1c7767e72553>\I386\PrintConfig.dll’.
sto: 12:41:52.379
sig: <_verify_file_signature>12:41:52.473
sig: Key = prnms003.inf
sig: FilePath = C:\WINDOWS\System32\DriverStore\Temp\<4b6285d8-5f78-2043-b214-1c7767e72553>\prnms003.inf
sig: Catalog = C:\WINDOWS\System32\DriverStore\Temp\<4b6285d8-5f78-2043-b214-1c7767e72553>\prnms003.cat
sig: Success: File is signed in catalog.
sig: <_verify_file_signature exit(0x00000000)>12:41:52.676
sto: 12:41:52.708
sig: Signer Score = 0x0D000003
sig: Signer Name = Microsoft Windows
sto: 12:41:52.708
sto: 12:41:52.708
cpy: > 12:41:52.708
cpy: Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\prnms003.inf_x86_48858e330b88a3d7
cpy: \I386> 12:41:52.739
cpy: Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\prnms003.inf_x86_48858e330b88a3d7\I386
cpy: 12:41:52.754
cpy: 12:41:52.754
idb: 12:41:52.786
idb: Created driver package object ‘prnms003.inf_x86_48858e330b88a3d7’ in DRIVERS database node.
idb: Created driver INF file object ‘oem.inf’ in DRIVERS database node.
idb: Registered driver package ‘prnms003.inf_x86_48858e330b88a3d7’ with ‘oem .inf’.
idb: 12:41:52.786
idb: 12:41:52.786
idb: Activating driver package ‘prnms003.inf_x86_48858e330b88a3d7’.
cpy: Published ‘prnms003.inf_x86_48858e330b88a3d7\prnms003.inf’ to ‘oem .inf’.
idb: Indexed 1 device ID for ‘prnms003.inf_x86_48858e330b88a3d7’.
idb: 12:41:52.817
sto: 12:41:52.817
sig: Installed catalog ‘prnms003.cat’ as ‘oem .cat’.
sto: 12:41:53.083
sto: 12:41:53.098
>> [Setup Import Driver Package — C:\WINDOWS\system32\spool\DRIVERS\x64\<044db861-920c-4c3c-9a6b-e4ac41d36d7d>\prnms003.inf]
>>> Section start 2014/12/10 12:41:56.817
cmd: C:\WINDOWS\System32\spoolsv.exe
inf: Provider: Microsoft
inf: Class GUID: <4d36e979-e325-11ce-bfc1-08002be10318>
inf: Driver Version: 06/21/2006,6.3.9600.17415
inf: Catalog File: prnms003.cat
pol: 12:41:56.848
pol: 12:41:56.848
sto: \prnms003.inf> 12:41:56.848
inf: \prnms003.inf> 12:41:56.864
inf: Driver package ‘prnms003.inf’ is configurable.
inf: 12:41:56.864
flq: Copying ‘C:\WINDOWS\system32\spool\DRIVERS\x64\<044db861-920c-4c3c-9a6b-e4ac41d36d7d>\Amd64\PrintConfig.dll’ to ‘C:\WINDOWS\System32\DriverStore\Temp\<142fdd7f-7ea5-2e4a-a244-df2c9722cb66>\Amd64\PrintConfig.dll’.
flq: Copying ‘C:\WINDOWS\system32\spool\DRIVERS\x64\<044db861-920c-4c3c-9a6b-e4ac41d36d7d>\Amd64\unishare.gpd’ to ‘C:\WINDOWS\System32\DriverStore\Temp\<142fdd7f-7ea5-2e4a-a244-df2c9722cb66>\Amd64\unishare.gpd’.
flq: Copying ‘C:\WINDOWS\system32\spool\DRIVERS\x64\<044db861-920c-4c3c-9a6b-e4ac41d36d7d>\Amd64\unishare-pipelineconfig.xml’ to ‘C:\WINDOWS\System32\DriverStore\Temp\<142fdd7f-7ea5-2e4a-a244-df2c9722cb66>\Amd64\unishare-pipelineconfig.xml’.
flq: Copying ‘C:\WINDOWS\system32\spool\DRIVERS\x64\<044db861-920c-4c3c-9a6b-e4ac41d36d7d>\prnms003.cat’ to ‘C:\WINDOWS\System32\DriverStore\Temp\<142fdd7f-7ea5-2e4a-a244-df2c9722cb66>\prnms003.cat’.
flq: Copying ‘C:\WINDOWS\system32\spool\DRIVERS\x64\<044db861-920c-4c3c-9a6b-e4ac41d36d7d>\prnms003.inf’ to ‘C:\WINDOWS\System32\DriverStore\Temp\<142fdd7f-7ea5-2e4a-a244-df2c9722cb66>\prnms003.inf’.
sto: 12:41:57.067
sig: <_verify_file_signature>12:41:57.098
sig: Key = prnms003.inf
sig: FilePath = C:\WINDOWS\System32\DriverStore\Temp\<142fdd7f-7ea5-2e4a-a244-df2c9722cb66>\prnms003.inf
sig: Catalog = C:\WINDOWS\System32\DriverStore\Temp\<142fdd7f-7ea5-2e4a-a244-df2c9722cb66>\prnms003.cat
sig: Success: File is signed in catalog.
sig: <_verify_file_signature exit(0x00000000)>12:41:57.254
sto: 12:41:57.286
sig: Signer Score = 0x0D000003
sig: Signer Name = Microsoft Windows
sto: 12:41:57.286
sto: 12:41:57.286
cpy: > 12:41:57.286
cpy: Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\prnms003.inf_amd64_864418199e8fa69d
cpy: \Amd64> 12:41:57.286
cpy: Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\prnms003.inf_amd64_864418199e8fa69d\Amd64
cpy: 12:41:57.301
cpy: 12:41:57.301
idb: 12:41:57.301
idb: Created driver package object ‘prnms003.inf_amd64_864418199e8fa69d’ in DRIVERS database node.
idb: Created driver INF file object ‘oem .inf’ in DRIVERS database node.
idb: Registered driver package ‘prnms003.inf_amd64_864418199e8fa69d’ with ‘oem .inf’.
idb: 12:41:57.317
idb: 12:41:57.317
idb: Activating driver package ‘prnms003.inf_amd64_864418199e8fa69d’.
cpy: Published ‘prnms003.inf_amd64_864418199e8fa69d\prnms003.inf’ to ‘oem .inf’.
idb: Indexed 2 device IDs for ‘prnms003.inf_amd64_864418199e8fa69d’.
idb: 12:41:57.333
sto: 12:41:57.333
sig: Installed catalog ‘prnms003.cat’ as ‘oem .cat’.
sto: 12:41:57.395
sto: 12:41:57.395
Additional content from duplicate thread.

Читайте также:  Windows 10 как сделать нижнюю панель темной

Hotfix for KB3013769 & KB3000850

KB3000850(Nov’2014), KB3013769(Dec’2014), prnms003.inf and oem.inf

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.inf will removed

3.Re-install KB3000850 and KB3014442, restart PC

4.Open Command Prompt (cmd.exe) (Admin mode)

net stop Spooler

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

net start Spooler

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)

net stop Spooler

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

net start Spooler

9.Thanks my Registry Hotfix, Windows will create «Microsoft enhanced Point and Print compatibility driver» New versions CAB