Winspool.drv – Pre Service Pack 2 Revision History for Windows 7 SP1, Windows Server 2008 R2 SP1 and Windows Small Business Server 2011 (SBS 2011)
30-Jul-2013 – 6.1.7601.22406 – Winspool.drv – x64 – http://support.microsoft.com/kb/2871131 – The size of the “HKEY_USERS\.DEFAULT” registry hive continuously increases on a Windows Server-based server
09-Oct-2012 – 6.1.7601.22130 – Winspool.drv – x86/x64 – http://support.microsoft.com/kb/2769359 – Print job fails when the printer driver isolation feature is set to isolated or shared mode in Windows 7 or Windows Server 2008 R2
13-May-2011 – 6.1.7601.21727 – Winspool.drv – x86/x64 – http://support.microsoft.com/kb/2542200 – A Win32 application that calls the EndDoc function crashes if you have 255 printing jobs in the queue in Windows 7 or in Windows Server 2008 R2
17-Mar-2011 – 6.1.7601.21685 – Winspool.drv – x86/x64 – http://support.microsoft.com/kb/981070 – “Windows can’t open Add Printer” error in a 64-bit version of Win7 or of Windows Server 2008 R2
18-Dec-2010 – 6.1.7601.21624 – Winspool.drv – x64 – http://support.microsoft.com/kb/2443101 – Print queue restore operations through the “printui.exe” command fail, error code 0x000000C in Windows Server 2008 R2 or in Windows 7
Spoolsv.exe – Pre Service Pack 2 Revision History for Windows Server 2008 R2 SP1, Windows 7 SP1 and Windows Small Business Server 2011 SP1 (SBS 2011)
09-Nov-2013 – 6.1.7601.22506 – Spoolsv.exe – x86/x64 – https://support.microsoft.com/en-gb/kb/2906850 – Print job status remains as “Sent to printer” when Isolated mode is set in Windows 7 or Windows Server 2008 R2
01-Nov-2012 – 6.1.7601.22149 – Spoolsv.exe – x86/x64 – http://support.microsoft.com/kb/2775511 – An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1
11-Feb-2012 – 6.1.7601.21921 – Spoolsv.exe – x86/x64 – http://support.microsoft.com/kb/2647753 – Description of an update rollup for the printing core components in Windows 7 and in Windows Server 2008 R2
11-Feb-2012 – 6.1.7601.17777 – Spoolsv.exe – x86/x64 – http://support.microsoft.com/kb/2647753 – Description of an update rollup for the printing core components in Windows 7 and in Windows Server 2008 R2
01-Oct-2011 – 6.1.7601.21830 – Spoolsv.exe – x86/x64 – http://support.microsoft.com/kb/2532459 – Print queue does not work if the queue is not one of the first 100 queues installed in a Windows Server 2008 or Windows Server 2008 R2 Terminal Services session
15-Jan-2011 – 6.1.7601.21642 – Spoolsv.exe – x86/x64 – http://support.microsoft.com/kb/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
15-Jan-2011 – 6.1.7601.21642 – Spoolsv.exe – x86/x64 – http://support.microsoft.com/kb/2466040 – Post-install customization does not start after you use Group Policy to configure a deployed printer in Windows Vista, in Windows 7, in Windows Server 2008, or in Windows Server 2008 R2
You may experience slow printing performance in Windows 7, Windows Server 2008 R2 or SBS 2011. This is when compared to previous versions of Windows such as Windows Vista or Windows Server 2008.
A hotfix KB 2526028 is available to improve the overall printing performance of these current desktop and server operating systems can be obtained from Microsoft.
Printers are probably the biggest source of problems for most IT Admins. Paper jams, low ink, leaky toner and streeky printing are just some of the joys you will often face. Another common issue is slow or incomplete printing, what’s the answer to this equally common user woe?
Well your in luck because this is one thing you may be able to ensure is not an ongoing issue for your users. Most printer manufacturers (i.e. Xerox, Canon and HP) offer Universal Print Drivers (UPDs) to tackle these very issues.
As a rule of thumb PostScript Drivers are best for printing from Adobe applications such as Acrobat (PDF) and/or other complex documents. PCL Drivers are usually best for priting basic documents, Microsoft Word Documents (doc, docx) and Excel Spreadsheets (xls) to name a few.
You may find it best to install and share your network printer twice, one instance using the PCL Driver and the other using a Postscript (PS) driver. You then just need to educate your users which printer instance to select from the printer list according to the document type they are dealing with.
Please feel free to comment on your own experiences