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

Page 1 of 3 123 LastLast

  1. Posts : 87
    W10
       #1

    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?
      My Computer


  2. Posts : 486
    Windows 10x64 17713
       #2

    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.
      My Computer


  3. Posts : 87
    W10
    Thread Starter
       #3

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

  4.   My Computer

  5. Try3's Avatar
    Posts : 7,517
    Windows 10 Home x64 Version 20H2 Build 19042.928
       #5

    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
      My Computer

  6. spunk's Avatar
    Posts : 2,845
    Windows 10 Pro 64 Bit 20H2
       #6
      My Computer


  7. Posts : 486
    Windows 10x64 17713
       #7

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

    Appears to be for the XPS Document Writer as well.
      My Computer


  8. Posts : 87
    W10
    Thread Starter
       #8

    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!
      My Computer


  9. Posts : 2
    Various
       #9

    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.
    Can't get rid of Printer-6/21/2006 12:00:00 AM 10.0.15063.0 update-capture.jpg

    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.
      My Computer


  10. Posts : 4
    Windows 10
       #10

    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-.pngCan't get rid of Printer-6/21/2006 12:00:00 AM 10.0.15063.0 update-deploymenterror.png
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:29.
Find Us




Windows 10 Forums