Cannot Remove or Delete Network Printer in Windows

Remove Network Printers from Windows via Registry Editor

Step 1: Click on Start, Run and then type in regedit and press Enter. This will open the registry editor.

Step 2: Navigate to the following key in the registry:

HKEY_CURRENT_USER – Printers – Connections

Here you should now see a list of all network printers with the server name first, then a comma, and then the name of the actual printer.

Go ahead and click on the printer in the left menu and press the Delete button or right-click and choose Delete. Unfortunately, that’s not all! You also have to delete the printer from one more location in the registry:

HKEY_LOCAL_MACHINE – SYSTEM – CurrentControlSet – Control – Print – Providers – LanMan Print Services – Servers – Printers

Now under the servers key, you should be able to expand it and see the name of the print server that actually hosts the printer you want to delete. Go ahead and expand the print server key and delete the printer from the list.

Now close the registry editor and reboot your computer. The undeletable network printer should now be gone! Note that the method above is just for network printers. If you have a local printer and want to remove it the same way via the registry, you need to go to the following registry keys below:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\ Windows NT x86\ Drivers\Version-3\

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers\

Understanding Active Directory Domain Services (AD DS) Functional Levels

Applies To: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2

Functional levels determine the available Active Directory Domain Services (AD DS) domain or forest capabilities. They also determine which Windows Server operating systems you can run on domain controllers in the domain or forest. However, functional levels do not affect which operating systems you can run on workstations and member servers that are joined to the domain or forest.

When you deploy AD DS, set the domain and forest functional levels to the highest value that your environment can support. This way, you can use as many AD DS features as possible. For example, if you are sure that you will never add domain controllers that run Windows Server 2003 to the domain or forest, select the Windows Server 2008 functional level during the deployment process. However, if you might retain or add domain controllers that run Windows Server 2003, select the Windows Server 2003 functional level.

When you deploy a new forest, you are prompted to set the forest functional level and then set the domain functional level. You cannot set the domain functional level to a value that is lower than the forest functional level. For example, if you set the forest functional level to Windows Server 2008, you can set the domain functional level only to Windows Server 2008. In this case, the Windows 2000 native and Windows Server 2003 domain functional level values are not available. In addition, all domains that you subsequently add to that forest have the Windows Server 2008 domain functional level by default.

You can set the domain functional level to a value that is higher than the forest functional level. For example, if the forest functional level is Windows Server 2003, you can set the domain functional level to Windows Server 2003or higher.

The following sections describe the features that are available at the different functional levels.

Features that are available at domain functional levels

The following table shows the features that are available at each domain functional level.

 

Domain functional level	Available features	Supported domain controller operating systems
Windows 2000 native	All of the default AD DS features and the following directory features are available: Universal groups for both distribution and security groups. Group nesting Group conversion, which allows conversion between security and distribution groups Security identifier (SID) history Note In Windows Server 2008 R2, the Personal Virtual Desktop feature was introduced. It requires the Windows 2000 native domain functional level. To deploy personal virtual desktops, your schema for the Active Directory forest must be at least Windows Server 2008. To use the added functionality provided by the Personal Virtual Desktop tab in the User Account Properties dialog box in Active Directory Users and Computers, you must run Active Directory Users and Computers from a computer running Windows Server 2008 R2 or a computer running Windows 7 that has Remote Server Administration Tools (RSAT) installed.	Windows Server 2008 R2 Windows Server 2008 Windows Server 2003 Windows 2000
Windows Server 2003	All the default AD DS features, all the features that are available at the Windows 2000 native domain functional level, and the following features are available: The domain management tool, Netdom.exe, which makes it possible for you to rename domain controllers Logon time stamp updates The lastLogonTimestamp attribute is updated with the last logon time of the user or computer. This attribute is replicated within the domain. The ability to set the userPassword attribute as the effective password on inetOrgPerson and user objects The ability to redirect Users and Computers containers By default, two well-known containers are provided for housing computer and user accounts, namely, cn=Computers, and cn=Users,. This feature allows the definition of a new, well-known location for these accounts. The ability for Authorization Manager to store its authorization policies in AD DS Constrained delegation Constrained delegation makes it possible for applications to take advantage of the secure delegation of user credentials by means of Kerberos-based authentication. You can restrict delegation to specific destination services only. Selective authentication Selective authentication makes it is possible for you to specify the users and groups from a trusted forest who are allowed to authenticate to resource servers in a trusting forest.	Windows Server 2012 R2 Windows Server 2012 Windows Server 2008 R2 Windows Server 2008 Windows Server 2003
Windows Server 2008	All of the default AD DS features, all of the features from the Windows Server 2003 domain functional level, and the following features are available: Distributed File System (DFS) replication support for the Windows Server 2003 System Volume (SYSVOL) DFS replication support provides more robust and detailed replication of SYSVOL contents. Note Beginning with Windows Server 2012 R2, File Replication Service (FRS) is deprecated. A new domain that is created on a domain controller that runs at least Windows Server 2012 R2 must be set to the Windows Server 2008 domain functional level or higher. Domain-based DFS namespaces running in Windows Server 2008 Mode, which includes support for access-based enumeration and increased scalability. Domain-based namespaces in Windows Server 2008 mode also require the forest to use the Windows Server 2003 forest functional level. For more information, see Choose a Namespace Type (http://go.microsoft.com/fwlink/?LinkId=180400). Advanced Encryption Standard (AES 128 and AES 256) support for the Kerberos protocol. In order for TGTs to be issued using AES, the domain functional level must be Windows Server 2008 or higher and the domain password needs to be changed. Note Authentication errors may occur on a domain controller after the domain functional level is raised to Windows Server 2008 or higher if the domain controller has already replicated the DFL change but has not yet refreshed the krbtgt password. In this case, a restart of the KDC service on the domain controller will trigger an in-memory refresh of the new krbtgt password and resolve related authentication errors. For more information, see Kerberos Enhancements. Last Interactive Logon Information Last Interactive Logon Information displays the following information: The total number of failed logon attempts at a domain-joined Windows Server 2008 server or a Windows Vista workstation The total number of failed logon attempts after a successful logon to a Windows Server 2008 server or a Windows Vista workstation The time of the last failed logon attempt at a Windows Server 2008 or a Windows Vista workstation The time of the last successful logon attempt at a Windows Server 2008 server or a Windows Vista workstation For more information, see Active Directory Domain Services: Last Interactive Logon(http://go.microsoft.com/fwlink/?LinkId=180387). Fine-grained password policies Fine-grained password policies make it possible for you to specify password and account lockout policies for users and global security groups in a domain. For more information, see Step-by-Step Guide for Fine-Grained Password and Account Lockout Policy Configuration (http://go.microsoft.com/fwlink/?LinkID=91477). Personal Virtual Desktops To use the added functionality provided by the Personal Virtual Desktop tab in the User Account Properties dialog box in Active Directory Users and Computers, your AD DS schema must be extended for Windows Server 2008 R2 (schema object version = 47). For more information, see Deploying Personal Virtual Desktops by Using RemoteApp and Desktop Connection Step-by-Step Guide(http://go.microsoft.com/fwlink/?LinkId=183552).	Windows Server 2012 R2 Windows Server 2012 Windows Server 2008 R2 Windows Server 2008
Windows Server 2008 R2	All default Active Directory features, all features from the Windows Server 2008 domain functional level, plus the following features: Authentication mechanism assurance, which packages information about the type of logon method (smart card or user name/password) that is used to authenticate domain users inside each user’s Kerberos token. When this feature is enabled in a network environment that has deployed a federated identity management infrastructure, such as Active Directory Federation Services (AD FS), the information in the token can then be extracted whenever a user attempts to access any claims-aware application that has been developed to determine authorization based on a user’s logon method. Automatic SPN management for services running on a particular computer under the context of a Managed Service Account when the name or DNS host name of the machine account changes. For more information about Managed Service Accounts, see Service Accounts Step-by-Step Guide(http://go.microsoft.com/fwlink/?LinkId=180401).	Windows Server 2012 R2 Windows Server 2012 Windows Server 2008 R2
Windows Server 2012	The KDC support for claims, compound authentication, and Kerberos armoring KDC administrative template policy has two settings (Always provide claims and Fail unarmored authentication requests) that require Windows Server 2012 domain functional level. For more information, see What's New in Kerberos Authentication.	Windows Server 2012 R2 Windows Server 2012
Windows Server 2012 R2	DC-side protections for Protected Users. Protected Users authenticating to a Windows Server 2012 R2 domain can no longer: Authenticate with NTLM authentication Use DES or RC4 cipher suites in Kerberos pre-authentication Be delegated with unconstrained or constrained delegation Renew user tickets (TGTs) beyond the initial 4 hour lifetime Authentication Policies New forest-based Active Directory policies which can be applied to accounts in Windows Server 2012 R2 domains to control which hosts an account can sign-on from and apply access control conditions for authentication to services running as an account. Authentication Policy Silos New forest-based Active Directory object, which can create a relationship between user, managed service and computer, accounts to be used to classify accounts for authentication policies or for authentication isolation.	Windows Server 2012 R2

Features that are available at forest functional levels

The following table shows the features that are available at each forest functional level.

 

Forest functional level	Available features	Supported domain controllers
Windows 2000	All of the default AD DS features are available.	Windows Server 2008 R2 Windows Server 2008 Windows Server 2003 Windows 2000
Windows Server 2003	All of the default AD DS features, and the following features, are available: Forest trust Domain rename Linked-value replication Linked-value replication makes it possible for you to change group membership to store and replicate values for individual members instead of replicating the entire membership as a single unit. Storing and replicating the values of individual members uses less network bandwidth and fewer processor cycles during replication, and prevents you from losing updates when you add or remove multiple members concurrently at different domain controllers. The ability to deploy a read-only domain controller (RODC) Improved Knowledge Consistency Checker (KCC) algorithms and scalability The intersite topology generator (ISTG) uses improved algorithms that scale to support forests with a greater number of sites than AD DS can support at the Windows 2000 forest functional level. The improved ISTG election algorithm is a less-intrusive mechanism for choosing the ISTG at the Windows 2000 forest functional level. The ability to create instances of the dynamic auxiliary class named dynamicObject in a domain directory partition The ability to convert an inetOrgPerson object instance into a User object instance, and to complete the conversion in the opposite direction The ability to create instances of new group types to support role-based authorization. These types are called application basic groups and LDAP query groups. Deactivation and redefinition of attributes and classes in the schema. The following attributes can be reused: ldapDisplayName, schemaIdGuid, OID, and mapiID. Domain-based DFS namespaces running in Windows Server 2008 Mode, which includes support for access-based enumeration and increased scalability. For more information, see Choose a Namespace Type (http://go.microsoft.com/fwlink/?LinkId=180400).	Windows Server 2012 R2 Windows Server 2012 Windows Server 2008 R2 Windows Server 2008 Windows Server 2003
Windows Server 2008	All of the features that are available at the Windows Server 2003 forest functional level, but no additional features are available. All domains that are subsequently added to the forest, however, operate at the Windows Server 2008 domain functional level by default.	Windows Server 2012 R2 Windows Server 2012 Windows Server 2008 R2 Windows Server 2008
Windows Server 2008 R2	All of the features that are available at the Windows Server 2003 forest functional level, plus the following features: Active Directory Recycle Bin, which provides the ability to restore deleted objects in their entirety while AD DS is running. All domains that are subsequently added to the forest will operate at the Windows Server 2008 R2 domain functional level by default. If you plan to include only domain controllers that run Windows Server 2008 R2 in the entire forest, you might choose this forest functional level for administrative convenience. If you do, you will never have to raise the domain functional level for each domain that you create in the forest.	Windows Server 2012 R2 Windows Server 2012 Windows Server 2008 R2
Windows Server 2012	All of the features that are available at the Windows Server 2008 R2 forest functional level, but no additional features. All domains that are subsequently added to the forest will operate at the Windows Server 2012 domain functional level by default.	Windows Server 2012 R2 Windows Server 2012
Windows Server 2012 R2	All of the features that are available at the Windows Server 2012 forest functional level, but no additional features. All domains that are subsequently added to the forest will operate at the Windows Server 2012 R2 domain functional level by default.	Windows Server 2012 R2

Guidelines for raising domain and forest functional levels

The following guidelines apply to raising the domain or forest functional levels:

• You must be a member of the Domain Admins group to raise the domain functional level.
  
• You must be a member of the Enterprise Admins group to raise the forest functional level.
  
• You can raise the domain functional level on the primary domain controller (PDC) emulator operations master only. The AD DS administrative tools that you use to raise the domain functional level (the Active Directory Domains and Trusts snap-in and the Active Directory Users and Computers snap-in) automatically target the PDC emulator when you raise the domain functional level.
  
• You can raise the forest functional level on the schema operations master only. Active Directory Domains and Trusts automatically targets the schema operations master when you raise the forest functional level.
  
• You can raise the functional level of a domain only if all domain controllers in the domain run the version or versions of Windows Server that the new functional level supports.
  
• You can raise the functional level of a forest only if all domain controllers in the forest run the version or versions of Windows Server that the new functional level supports.
  
• You cannot set the domain functional level to a value that is lower than the forest functional level, but you can set it to a value that is equal to or higher than the forest functional level.
  
• With versions of Windows Server that are earlier than Windows Server 2008 R2, you cannot roll back or lower a functional level under any circumstances. If you have to revert to a lower functional level with a version of Windows Server that is earlier than Windows Server 2008 R2, you must rebuild the domain or forest or restore it from a backup copy.
  
• After you set the domain functional level, you cannot roll back or lower the domain functional level except in the cases listed in the following table. The domain functional level can be lowered only by using Windows PowerShell. For more information, see Set-ADDomainMode.
  
  

   

  Current domain functional level	Current forest functional level	Rollback options
  Windows Server 2012 R2	Windows Server 2012 R2	None unless you first lower forest functional level
  Windows Server 2012 R2	Windows Server 2012	Windows Server 2012
  Windows Server 2012 R2	Windows Server 2008 R2	Windows Server 2012 or Windows Server 2008 R2
  Windows Server 2012 R2	Windows Server 2008	Windows Server 2012, Windows Server 2008 R2, or Windows Server 2008
  Windows Server 2012	Windows Server 2012	None unless you first lower forest functional level
  Windows Server 2012	Windows Server 2008 R2	Windows Server 2008 R2
  Windows Server 2012	Windows Server 2008	Windows Server 2008 R2 or Windows Server 2008
  Windows Server 2008 R2	Windows Server 2008 R2	None unless you first lower forest functional level
  Windows Server 2008 R2	Windows Server 2008	Windows Server 2008
  Windows Server 2008 or lower	Windows Server 2008 or lower	None

• After you set the forest functional level, you cannot roll back or lower the forest functional level except in the cases listed in the following table. The forest functional level can be lowered only by using Windows PowerShell. For more information, see Set-ADForestMode. For more information about the Active Directory Recycle Bin, see What's New in AD DS: Active Directory Recycle Bin (http://go.microsoft.com/fwlink/?LinkId=141392).
  
  

   

  Current forest functional level	Recycle Bin enabled?	Rollback options
  Windows Server 2012 R2	Yes	Windows Server 2012 or Windows Server 2008 R2
  Windows Server 2012 R2	No	Windows Server 2012, Windows Server 2008, or Windows Server 2008 R2
  Windows Server 2012	Yes	Windows Server 2008 R2
  Windows Server 2012	No	Windows Server 2008 R2 or Windows Server 2008
  Windows Server 2008 R2	Yes	None
  Windows Server 2008 R2	No	Windows Server 2008

List of print related hotfixes post Service Pack 2 for Windows Server 2003.

Applies to
Windows Server 2003 Service Pack 2
Windows Server 2003 SP2
W2K3 Service Pack 2
W2K3 SP2
Windows Server 2003 Service Pack 2 R2
Windows Server 2003 SP2 R2
W2K3 Service Pack 2 R2
W2K3 SP2 R2

List of print related hotfixes post Service Pack 2 for Windows Server 2003 as of Sep. 2012:

Originally published Sep. 2009.  Updated Mar. 2012.

Note: Regular support of Windows Server 2003 with Service Pack 2 ended in 2010. So there aren’t going to be any new hotfixes except for the Security hotfixes.

WARNING:  There should be a 3 hours scheduled change control.
The reason is for the hotfixes that contain unidrv.dll or ps5ui.dll, the print queues will have to go thru:
832219 Users cannot print after you install a service pack, update rollup, or printer hotfix on a server in Windows 2000 or in Windows Server 2003
http://support.microsoft.com?id=832219 
 

2712189 FIX: A custom .NET Framework 1.1 Service Pack 1 application that uses Windows Forms may not print or may not apply defined printer settings in Windows XP, Windows Server 2003 64-bit Edition or Itanium Edition, Windows Vista, or Windows Server 2008
http://support.microsoft.com/?id=2712189


Update(s):
System.Drawing.dll  1.1.4322.2497

2702328 FIX: A custom .NET Framework 4 application that uses Windows Forms may not print or may not apply defined printer settings in Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2
http://support.microsoft.com/?id=2702328


Update(s):
Setup.exe
SetupEngine.dll  10.0.30319.568
SetupUi.dll  10.0.30319.568
System.Drawing.dll  4.0.30319.568

2702327 FIX: A custom .NET Framework 2.0 Service Pack 2 application that uses Windows Forms may not print or may not apply defined printer settings in Windows XP or Windows Server 2003
http://support.microsoft.com/?id=2702327


Update(s):
System.Drawing.dll  2.0.50727.5729

2328677 Some text from an XPS file is printed incorrectly by a .NET Framework 4.0-based WPF applicati
http://support.microsoft.com/?id=2328677


Update(s):
Reachframework.dll  4.0.30319.352
SetupUi.dll  10.0.30319.352  295,248
Setupengine.dll  10.0.30319.352
Setup.exe  10.0.30319.352

2480118 You cannot print results to files by using web applications in Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2 after you install security update MS10-061
http://support.microsoft.com/?id=2480118


Update(s):
Spoolsv.exe 5.2.3790.4804

2279637 Some information is not printed when you print a large document on a computer that is running Windows Server 2003
http://support.microsoft.com/?id=2279637


Update(s):
Gdi32.dll 5.2.3790.4742
Supersede(s):
959482 Horizontal black stripes are displayed in the print output when you print an image to a PCL printer from a computer that is running Windows Vista, Windows Server 2008, Windows XP, or Windows Server 2003
http://support.microsoft.com/?id=
941973 A GDI object handle is leaked on a Windows Server 2003 Service Pack 2-based computer when you print a rotated picture by using Internet Explorer
936780 You may experience performance issues when you print documents from a 32-bit program in a 64-bit version of Windows Server 2003
930627 The private data of the DEVMODE data structure may be corrupted when you use raw mode to print a document in a 32-bit application on a computer that is running a 64-bit version of Windows

2279561 "0x00000050" Stop error occurs on a terminal server that is running Windows Server 2003 if a user mode printer driver is used in a terminal server session
http://support.microsoft.com/?id=2279561


Update(s):
Win32k.sys 5.2.3790.4743
Supersede(s):
2028925 "0x00000050" Stop error code in Windows Server 2003 Service Pack 2
http://support.microsoft.com/?id=2028925
960266 Error message when you call the CreateProcess function to start a process of a console application by using an account other than the current logon account in Windows Server 2003: "The application failed to initialize properly (0xc0000142)"
959828 Stop error on a Windows Server 2003 SP2-based terminal server or a Windows Server 2008 SP2-based terminal server when users print documents in terminal sessions: "0x0000008E" or "0x00000050"
959482 Horizontal black stripes are displayed in the print output when you print an image to a PCL printer from a computer that is running Windows Vista, Windows Server 2008, Windows XP, or Windows Server 2003
959338 You receive a PAGE_FAULT_IN_NONPAGED_AREA Stop error when you print a document from a Windows Server 2003 server that is running as a terminal server
939884

981650 You cannot print text in a terminal server session in Windows Server 2003, in Windows Server 2008, or in Windows Vista if the printer uses the "Generic / Text Only" driver
http://support.microsoft.com/?id=981650


Update(s):
Gdiplus.dll 5.2.6001.22729
Gdiplus.man
Supersede(s):
956807 The Unicode hyphen character (U+2010) is not drawn when you use an application that uses GDI+ API functions in Windows Server 2008, in Windows Vista, in Windows Server 2003, and in Windows XP
951759 When an application uses GDI+ to print to a color printer on a Windows Server 2003-based, Windows Vista-based, or Windows Server 2008-based computer, ICM color matching is not performed

981429 Some XPS file text is printed incorrectly by a .NET Framework 3.0-based WPF application
http://support.microsoft.com/?id=981429


Update(s):
Presentationcore.dll 3.0.6920.4031
Presentationframework.dll 3.0.6920.4031
Presentationhost.exe 4.0.40305.0
Presentationhostdll.dll 3.0.6920.4031
Presentationhostproxy.dll 4.0.31106.0
Reachframework.dll 3.0.6920.4031
System.printing.dll 3.0.6920.4031
Windowsbase.dll 3.0.6920.4031
Supersede(s):
980294 Characters in the Barcode font are printed in the Wingdings font in an XPS document that is created by using the .NET Framework 3.0

980276 The Print Spooler service crashes when you try to remove a printer on a computer that is running Windows Server 2003 SP2
http://support.microsoft.com/?id=980276


Update(s):
Localspl.dll 5.2.3790.4677
Supersede(s):
968585 A handle leak occurs in the print spooler service after you resubmit a print job to a shared printer on which the "Keep printed documents" option is enabled
962910 After security update MS08-062 is installed on a print client, the client cannot print documents to a Windows Server 2003-based IPP print server if the related printer driver is not installed
955455 The print process crashes under heavy stress on a computer that is running Windows Server 2003 or Windows XP Professional x64 Edition if the computer uses hyper-threading technology
952206 A printer-driver upgrade operation fails on printer clients that are running Windows Server 2003 or Windows XP when multiple printer queues are upgraded at the same time
934885 The Print Spooler service may stop sending print jobs to a printer that uses the standard port monitor on a Windows Server 2003-based computer
932699 A printer driver upgrade operation may fail in Windows Server 2003

979405 FIX: Error message when you run a script that uses the PrnAdmin utility to install the HP Universal Print Driver PCL6: "-2147024894: The system cannot find the file specified"
http://support.microsoft.com/?id=979405


Update(s):
Ntprint.dll 5.2.3790.4649
Wntprint.dll 5.2.3790.4649

977585 Text strings that are not in a clipping region are printed unexpectedly when you use Microsoft XPS Document Writer to print a file in Windows Server 2008, Windows Server 2003, or Windows Vista
http://support.microsoft.com/?id=977585


Update(s):
Msxpsinc.amd64.gpd
Msxpsinc.amd64.ppd
Msxpsinc.gpd
Msxpsinc.ppd
Mxdwdrv.amd64.dll 0.3.6002.22298
Mxdwdrv.dll 0.3.6002.22298
Mxdwdui.dll 0.3.6002.22298
Mxdwdui.gpd
Mxdwdui.ini
Stddtype.gdl
Stdnames.gpd
Stdschem.gdl
Stdschmx.gdl
Unidrv.dll 0.3.6002.22298
Unidrv.hlp
Unidrvui.dll 0.3.6002.22298
Unires.dll 0.3.6002.22298
Xpssvcs.amd64.dll 6.0.6002.22298
Xpssvcs.dll 6.0.6002.22298
Supersede(s):
944203 You may be unable to print a job after you install the .NET Framework 3.0 or the XML Paper Specification Essentials Pack on a Windows XP SP2-based computer or on a Windows Server 2003-based computer

977225 Incorrect lines are printed when a Word document is printed on a computer that is running Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/?id=977225


Update(s):
Stddtype.gdl
Stdnames.gpd
Stdschem.gdl
Stdschmx.gdl
Unidrv.dll 0.3.7601.21760
Unidrv.hlp
Unidrvui.dll 0.3.7601.21760
Unires.dll 0.3.7601.17514
Supersede(s):
969744 Underlines are missing when you print a document

975126 Some custom-sized pages are printed incorrectly if they have different dimensions and are printed consecutively from a computer running Windows Server 2003, Windows Vista or Windows Server 2008
http://support.microsoft.com/?id=975126


Update(s):
Locale.gpd
P6disp.gpd
P6font.gpd
Pcl4res.dll 0.3.5479.0
Pcl5eres.dll 0.3.5479.0
Pcl5ures.dll 0.3.5479.0
Pclxl.dll 0.3.5479.0
Pclxl.gpd
Pjl.gpd
Ps5ui.dll 0.3.6002.22223
Pscript.hlp
Pscript.ntf
Pscript5.dll 0.3.6002.22223
Pscrptfe.ntf
Ps_schm.gdl
Ttfsub.gpd

974266 Group Policy Preferences Client-Side Extension Hotfix Rollup
http://support.microsoft.com/?id=974266 
 
971276 You receive incorrect print output if the IPrintPipelineProgressReport interface is used in your printing application on a Windows XP SP3 or Windows Server 2003 SP2-based computer
http://support.microsoft.com/?id=971276


Update(s):
Filterpipelineprintproc.amd64.dll 6.1.3790.4316 147,456 14-Aug-2009 12:49 x64 SP3
Filterpipelineprintproc.dll 6.1.2600.5863 89,088 14-Aug-2009 12:49 x86 SP3
Msxpsinc.amd64.gpd Not Applicable 73 19-Jun-2008 03:03 Not Applicable SP3
Msxpsinc.amd64.ppd Not Applicable 72 19-Jun-2008 03:03 Not Applicable SP3
Msxpsinc.gpd Not Applicable 73 19-Jun-2008 03:04 Not Applicable SP3
Msxpsinc.ppd Not Applicable 72 19-Jun-2008 03:04 Not Applicable SP3
Mxdwdrv.amd64.dll 0.3.6002.22136 760,320 14-Aug-2009 12:49 x64 SP3
Mxdwdrv.dll 0.3.6002.22136 779,776 14-Aug-2009 12:49 x86 SP3
Mxdwdui.dll 0.3.6002.22136 198,656 14-Aug-2009 12:49 x86 SP3
Mxdwdui.gpd Not Applicable 67,628 19-Jun-2008 03:04 Not Applicable SP3
Mxdwdui.ini Not Applicable 42 19-Jun-2008 03:04 Not Applicable SP3
Printfilterpipelinesvc.exe 6.1.2600.5863 594,432 14-Aug-2009 09:02 x86 SP3
Prntvpt.dll 6.1.2600.5863 117,760 14-Aug-2009 12:49 x86 SP3
Stddtype.gdl Not Applicable 23,812 30-Nov-2007 12:56 Not Applicable SP3
Stdnames.gpd Not Applicable 14,362 30-Nov-2007 13:03 Not Applicable SP3
Stdschem.gdl Not Applicable 59,116 30-Nov-2007 12:56 Not Applicable SP3
Stdschmx.gdl Not Applicable 2,278 30-Nov-2007 12:56 Not Applicable SP3
Unidrv.dll 0.3.6002.22136 372,736 14-Aug-2009 12:49 x86 SP3
Unidrv.hlp Not Applicable 21,225 30-Nov-2007 11:46 Not Applicable SP3
Unidrvui.dll 0.3.6002.22136 744,448 14-Aug-2009 12:49 x86 SP3
Unires.dll 0.3.6002.22136 761,344 15-May-2009 05:21 x86 SP3
Xpsshhdr.dll 6.0.6002.22136 575,488 14-Aug-2009 12:49 x86 SP3
Xpssvcs.amd64.dll 6.0.6002.22136 2,936,832 14-Aug-2009 12:49 x64 SP3
Xpssvcs.dll 6.0.6002.22136
Supersede(s):
954550 Some Microsoft XPS features are not available in Windows Server 2003 and in Windows XP

971314 All PCL inbox printer drivers become unsigned after you install the Microsoft .NET Framework 3.5 SP1 or the XPS Essentials Pack in Windows XP or in Windows Server 2003
http://support.microsoft.com/?id=971314


Update(s):
Ntprint.cat
Supersede(s):

961118

967663 Only one 32-bit service can print on a computer that is running a 64-bit version of Windows Server 2003 when multiple services are configured to run under one non-SYSTEM account
http://support.microsoft.com?id=967663


Update(s):
Splwow64.exe  5.2.3790.4457

967499 You encounter printing issues after a new OEM print driver, a printer hotfix, or a service pack is installed on a Windows Server 2003-based clustered printer server
http://support.microsoft.com?id=967499
 
960677 When you print a document to a redirected printer in a Windows Server 2003-based terminal server session, the document is printed to a redirected printer of a different client
http://support.microsoft.com/?id=960677


Update(s):
Rdpdr.sys 5.2.3790.4424
Note:  Only for Terminal Servers.
Supersede(s):
938645 You cannot communicate with the local device by using a redirected COM port in a Windows Server 2003-based terminal-server session

958910 When you send a print job to an Internet Printer Protocol (IPP) print server from a Windows-based computer, the print job fails and never restarts
http://support.microsoft.com/?id=958910


Update(s):
Inetpp.dll 5.2.3790.4417
Winetpp.dll 5.2.3790.4417

957389 When you run an SUA application that prints log messages from the system logger daemon, ISO 8859 characters are printed incorrectly on Windows Server 2003 R2-based, Windows Vista-based, and Windows Server 2008-based computers
http://support.microsoft.com/?id=957389


Update(s):
Syslogd 9.0.3790.4368

957187 Stop error if you use some OpenType fonts on a computer that is running Windows Server 2003, Windows Vista, or Windows Server 2008: "Stop 0x00000050"
http://support.microsoft.com/?id=957187


Note:  This replaces KB 948046 V1 which is known to cause the .bud file to keep on getting regenerated and slows printing (customers have reported slow down in printing up to 3X).
 
Update(s):
Locale.gpd
P6disp.gpd
P6font.gpd
Pcl4res.dll 0.3.5479.0
Pcl5eres.dll 0.3.5479.0
Pcl5ures.dll 0.3.5479.0
Pclxl.dll 0.3.5479.0
Pclxl.gpd
Pjl.gpd
Stddtype.gdl
Stdnames.gpd
Stdschem.gdl
Stdschmx.gdl
Ttfsub.gpd
Unidrv.dll 0.3.6001.22252
Unidrv.hlp
Unidrvui.dll 0.3.6001.22252
Unires.dll 0.3.6001.22252

Supersede(s):
948696 Text that is formatted in printer device fonts may not print correctly in x64 versions of Windows Server 2008, of Windows Vista, and of Windows Server 2003
948046 A Word document is not printed as expected after you install the Windows European Union Expansion Font pack in Windows Server 2003 or in Windows XP

956048 An application that calls the Image Color Management (ICM) functions in the Icm32.dll module may crash on a Windows Server 2003-based computer
http://support.microsoft.com/?id=956048


Update(s):
Icm32.dll 5.2.3790.4343
Wicm32.dll 5.2.3790.4343

955549 When you open an .rtf file that contains a MergeField field in a paragraph, indents that are added to the paragraph are not displayed in Windows Server 2003 and in Windows XP Professional x64 edition
http://support.microsoft.com/?id=955549


Update(s):
Msftedit.dll 5.41.21.2509
Riched20.dll 5.31.23.1229

954744 FIX: Some pages are printed in the incorrect orientation when you use Terminal Services Easy Print to print a document that contains both portrait-oriented pages and landscape-oriented pages
http://support.microsoft.com/?id=954744


Update(s):
.net framework 3.0 SP1:
Servicemodelreg.exe 3.0.4506.725 61,440 25-Sep-2008 17:17 x86 SP1
Tswpfwrp.exe 3.0.6920.1201
 
.net framework 3.0 SP2:
Tswpfwrp.exe 3.0.6920.1201
 
Note:  Only for Terminal Servers

953546 The Print Spooler process (Spoolsv.exe) crashes while it is copying print driver files on a computer that is running Windows Server 2003 or Windows XP
http://support.microsoft.com/?id=953546


Update(s):
Updates Win32spl.dll 5.2.3790.4301
Supersede(s):
931318

952909 When you try to print a document to a PostScript printer in an application, the application exits unexpectedly, or you find that an invalid PDF file is created from the incorrect data in the PostScript file
http://support.microsoft.com/?id=952909


Update(s):
Atmfd.dll 5.1.2.227

946198  The print queue status is displayed as "Offline" on a Windows Server 2003-based print server if SNMP is enabled and if the printer devices do not respond to SNMP commands
http://support.microsoft.com/?id=946198


Update(s):
Tcpmib.dll 5.2.3790.4211

937932 Error message when you run a 16-bit program in Windows Server 2003: "NTVDM has encountered a hard error"
http://support.microsoft.com/?id=937932


Update(s):
Wwow32.dll 5.2.3790.4087

937193  The complete name of a network printer cannot be displayed on a computer that is running Windows Server 2003 or Windows XP
http://support.microsoft.com/?id=937193


Update(s):
Printui.dll 5.2.3790.4077
Wprintui.dll 5.2.3790.4077

Printer Driver Isolation

Printer driver isolation improves the reliability of the Windows print service, by enabling printer drivers to run in processes that are separate from the process in which the print spooler runs.

Support for printer driver isolation is implemented in Windows 7, Windows Server 2008 R2 and later operating systems.

For Windows 7 and Windows Server 2008 R2, an inbox printer driver must support printer driver isolation and be able to run in an isolated process.

Previous Versions of Windows

In previous versions of Windows, including Windows Server 2008, printer drivers always ran in the same process as the spooler. Printer driver components that ran in the spooler process included the following:

• Print driver configuration modules
• Print processors
• Rendering modules

The failure of a single print driver component could cause the print subsystem to fail, halting print operations for all users and for all print components.

New Versions of Windows

With Windows 7 and Windows Server 2008 R2, an administrator can, as an option, configure a printer driver to run in an isolated process--a process that is separate from the spooler process. By isolating the driver, the administrator can prevent a fault in a driver component from halting the print service.

For more information about the spooler functions, see Spooler Component Functions and Structures.

Driver Isolation Support in INF Files

By default, if the INF file that installs a printer driver does not indicate that the driver supports driver isolation, the printer class installer configures the driver to run in the spooler process. However, if the INF file indicates that the driver supports driver isolation, the installer configures the driver to run in an isolated process. An administrator can override these configuration settings and specify, for each driver, whether to run the driver in the spooler process or in an isolated process.

To support driver isolation, the INF file that installs a printer driver can use the DriverIsolationkeyword to indicate whether the driver supports printer driver isolation. Setting DriverIsolation=2 indicates that the driver supports driver isolation. Setting DriverIsolation=0 indicates that the driver does not support driver isolation. Omitting the DriverIsolation keyword from the INF file has the same effect as setting DriverIsolation=0.

Spooler Functions for Driver Isolation Settings

The following table shows the spooler functions that an administrator can use to configure the driver-isolation settings.

Function name	Operation
GetPrinterDataEx	Get the driver-isolation settings for a printer.
SetPrinterDataEx	Set the driver-isolation settings for a printer.
EnumPrinterDataEx	Enumerate driver-isolation settings for a printer.
FindFirstPrinterChangeNotification FindNextPrinterChangeNotification	Request notifications of changes to the driver-isolation settings for a printer.

The format for the data is as follows:

• Driver in each group is separated by '\'
• Each driver group is separated by '\\'

The first group loads the driver into the spooler processes. Each subsequent group loads the drivers in isolated processes per group. The second group is considered the 'shared' group in which other isolation-capable drivers are loaded by default.

Configuring Driver Isolation Mode through Administration

A computer administrator can use the Windows Print Management console or call the Windows spooler functions to configure the driver-isolation settings for each printer driver installed on a computer. The administrator configures the driver to use one of the settings listed in the following table.

Driver-isolation mode	Meaning
Shared	Run the driver in a process that is shared with other printer drivers but is separate from the spooler process.
Isolated	Run the driver in a process that is separate from the spooler process and is not shared with other printer drivers.
None	Run the driver in the spooler process.

Ideally, a printer driver is able to run in shared mode. That is, it runs in an isolated process shared with other printer drivers but separate from the spooler process. A driver might need to run in isolated mode if it can run in a process separate from the spooler process, but has difficulty sharing the process with other drivers. For example, a poorly designed driver might have file names that conflict with those of related drivers or of different versions of the same driver, or the driver might fault frequently or have a memory leak that interferes with the operation of other drivers that run in the same process.

To support troubleshooting, the domain administrator can disable the driver-isolation feature on a computer in the domain, or the administrator can force all of the printer drivers on the computer to run in isolated mode. In isolated mode, each driver must run in a process separate from the spooler and from the other printer drivers.

If driver isolation is disabled by group policy, the isolation is off for all printer drivers. If isolation is enabled, then the individual drivers are mode-checked. If a driver has isolation mode set, it runs in shared, isolated, or none mode, based on the registry entry. However, if the driver does not have isolation mode set and it is compatible with isolation, it runs in shared mode. If the driver is not compatible with the mode, the group policy override determines whether the driver runs in shared mode or none mode.

The following chart shows a decision map for choosing the driver isolation mode:

Spooler Functions Allowed under Driver Isolation

Only specific functions are allowed under driver isolation.

Spoolss.dll Functions

The following functions are exported by spoolss.dll and are available to spooler plugins by linking to spoolss.lib.

AddMonitorW

AppendPrinterNotifyInfoData

ClosePrinter

DeletePortW

DeletePrintProcessorW

EndDocPrinter

EndPagePrinter

EnumFormsW

EnumJobsW

FlushPrinter

GetJobAttributes

GetJobAttributesEx

GetJobW

GetPrinterDataExW

GetPrinterDataW

GetPrinterDriverDirectoryW

GetPrinterDriverW

GetPrinterW

ImpersonatePrinterClient

OpenPrinterW

ReadPrinter

RouterCreatePrintAsyncNotificationChannel

RouterGetPrintClassObject

SetJobW

SetPrinterDataExW

SetPrinterDataW

StartDocPrinterW

StartPagePrinter

WritePrinter

WinSpool.drv Functions

The following functions are exported by winspool.drv and are available to spooler plugins by linking to Winspool.h.

AppendPrinterNotifyInfoData

ExtDeviceMode

ImpersonatePrinterClient

IsValidDevmode

PartialReplyPrinterChangeNotification

ReplyPrinterChangeNotification

RevertToPrinterSelf

RouterAllocBidiMem

RouterAllocBidiResponseContainer

RouterAllocPrinterNotifyInfo

RouterCreatePrintAsyncNotificationChannel

RouterFreeBidiMem

RouterFreeBidiResponseContainer

RouterFreePrinterNotifyInfo

RouterGetPrintClassObject

RouterRegisterForPrintAsyncNotifications+

RouterUnregisterForPrintAsyncNotifications