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

I keep getting Microsoft – “Printer-6/21/2006 12:00:00 AM 10.0.15063.0” updates coming up in wushowhide. Originally two of them, both were selected to be hidden. But every time one keeps coming up and there is only one listed under hidden updates.
I have an old Canon printer and use the old drivers with no problem, but MS keeps trying to install there drivers that don’t work well. I tried updating the printer in device manager and it did start to down load a new driver so it looks as if this update is related to the Canon printer and MSs desire to stop it working. How do I actually stop it being available as an update and is it actually for something else?

:)

 

Windows Update Catalog driver update package corrupted

I have the same problem. ESET is telling me that 2 updates are available:

Microsoft – Printer – 6/21/2006 12:00 AM – 10.0.15063.0 and

Microsoft – Printer – 6/21/2006 12:00 AM – 10.0.15063.0

These are very old drivers (2006) - they might even pre-date Windows Vista and I am running the latest version (re-downloaded today as an in-place upgrade) of Windows 10 Fall Creators. Are we meant to go back in time that far? I always thought that
drivers used for "update" purposes should be more recent than existing ones. Let's hope nothing comes up from Windows 3.1 next ;-).

 

Windows Update Error

Hi

i have tried to update my laptop but im getting these error's i dont know what to do or how to clear these error and update my laptop.

1: Intel - net - 7/2/2017 12:00:00 AM - 19.51.4.2 - Error 0x80070002

2: Intel - Other hardware - Intel(R) Dynamic Platform and Thermal Framework Manager - Error 0x80070002

3: Intel - Other hardware - Intel(R) Dynamic Platform and Thermal Framework Processor Participant - Error 0x80070002

4: Intel Corporation - Bluetooth - 4/7/2017 12:00:00 AM - 19.60.0.3 - Error 0x80070002

5: Intel Corporation - Display - 7/24/2017 12:00:00 AM - 22.20.16.4749 - Error 0x80070002

6: Intel Corporation - Display - 7/24/2017 12:00:00 AM - 22.20.16.4749 - Error 0x80070002

7: Intel(R) Corporation - MEDIA - 4/16/2016 12:00:00 AM - 8.20.0.922 - Error 0x80070002

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

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

10: NVIDIA - Display - 9/16/2017 12:00:00 AM - 22.21.13.8569 - Error 0x80070002

11: Realtek - Net - 7/14/2016 12:00:00 AM - 10.10.714.2016 - Error 0x80070002

12: Realtek Semiconductor Corp. - MEDIA - 11/29/2016 12:00:00 AM - 6.0.1.8004 - Error 0x80070002

13: Realtek Semiconductor Corp. - MTD - 12/22/2016 12:00:00 AM - 10.0.14393.21292 - Error 0x80070002

 

That driver repeatedly fails to install here with a digital signature error and appears to be a bug unrelated to your printer. You can just ignore it or it can be hidden through Powershell.

 

Thanks will have to hope it goes away as I don't know how to hide it via Powershell.

 

Update and Upgrade Windows 10 using PowerShell Installation Upgrade Tutorials

 

John,

This update is for the MS print-to-pdf printer not your real printer. [I discovered this by finding the update in the MS update catalog then comparing its hardware ID property to that given in Device manager, Print queues, MS print to pdf.]

Denis

 

You can turn off this printer Turn On or Off Microsoft Print to PDF in Windows 10 Apps Features Tutorials

 

Appears to be for the XPS Document Writer as well.

 

This update is for the MS print-to-pdf printer not your real printer. [I discovered this by finding the update in the MS update catalog then comparing its hardware ID property to that given in Device manager, Print queues, MS print to pdf.]



Thanks tried that and it and XPS said unto date?
Both are listed again!

 

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.

 

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:

• This is a NEW thing. Just started, late last week.
• The update attempts do not appear in the update history.
• Manually scanning for updates does not locate/attempt to install said update.
• 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.)

 

I set the update step to continue on error originally but it looked like it was still failing the deployment, but I had another post applications Windows Update step at the end I forgot about - d'oh. I disabled one and set the other to continue on error and it does now complete with the same warning you show.

To speed up the 8 reboots thing, edit this file: %DeployRoot%\Scripts\ZTIWindowsUpdate.wsf

On line 30 change:

Const MSIT_WU_REBOOT_MAX = 7

to a lower value. I used 2, maybe even 1 would be fine (max 2 passes).

 

Yep - I changed that to two (see the image), but I don't like that low of a number in particular.

I have also have changed my task sequences as the other answer given here earlier (missing now) suggested -- where the XPS service and Print to PDF role/feature is removed early in the task sequence and put back late in the task sequence - just to see if that would 'work around' the issue - but I have not actually tried it.

About to. Will update.

 

Very interested to see what your results are. Just started seeing this driver fail all our deployments and thought I was going crazy. Glad I'm not the only one. This has happened for me with both 1703 and 1709 deployments.