Windows 10: how do I update print que driver DriverVer=06/21/2006, 10.0.10586.0

This is the driver version installed in windows 10.


PrintQueue.INF - Microsoft Windows Print Queue & Printer Connection Driver Package
;
[Version]
Signature="$Windows NT$"
Provider="Microsoft"
ClassGUID={1ED2BBF9-11F0-4084-B21F-AD83A8E6DCDC}
Class=PrintQueue
DriverVer=06/21/2006,10.0.10586.0


If I try to update tells me the latest version / best driver is already installed


I bought a new HP pagewide printer and print spool keeps crashing etc.


Surely windows has updated its PrintQueue.INF driver since 2006


Cheers


Andy

:)

 

Can't get rid of Printer-6/21/2006 12:00:00 AM 10.0.15063.0 update


I deploy machines in bulk via MDT with a Windows Update step in the task sequence. This update appeared some time between Thursday evening and Friday morning here (UTC+8). It fails to install 8 times then craters the deployment. I had to disable the Windows Update task sequence step and run a manual update at the end of the deployments. Interestingly, this update doesn't appear when Windows Update is run manually.




These are brand new Surface Pros being imaged with a clean 1709 build, with no printers or other devices besides the type cover.

Pretty sure this update release is a cockup from Microsoft: 10.0.15063.0 is the build version of the March creators' update (1703), but we're deploying 1709 (10.0.16299.19). And why would XPS and print to PDF driver versions from 2006 be applicable to any version of Windows post-XP? Hopefully they'll realise and pull it sooner rather than later.

 

Can't get rid of Printer-6/21/2006 12:00:00 AM 10.0.15063.0 update


Ste84,

I'm with you. I have noted the same thing on my MDT setup with Creators Update and Fall Creators Update. Suddenly, late last week, this strange action started occurring. I allow the continuation on error for the updates, so it was not a show stopper, but with the default of 7 tries, that many reboots lengthened the time of deployment unacceptably for no decent reason.

Microsoft - Printer - 6/21/2006 12:00:00 AM - 10.0.15063.0
Error: 0x80240017

Things to note:

1. This is a NEW thing. Just started, late last week.
2. The update attempts do not appear in the update history.
3. Manually scanning for updates does not locate/attempt to install said update.
4. It affects, at least, Windows 10 Creators Update and Windows 10 Fall Creators Update (otherwise already fully patched.)

I have seen this on my virtual machine testing environment - I have NOT tested it on a physical machine yet (sounds like you are using physical machines.)

 

Can't get rid of Printer-6/21/2006 12:00:00 AM 10.0.15063.0 update

I am having exactly the same issue. I tried to do as you suggest with no joy. This is what I added:




Do you know the KB by chance that are related to these drivers? Maybe we can use the KB##### format to exclude the updates on the deployment. *sarc