08-02-2015 01:12 PM
2 problems in 1 day
1^ Problem (al 09:00)
My problem is with printer HP Photosmart 6520
My hardware is PC Lenovo Z50-70 with initial Windows 8.1 Update at last update in this version,
and upgrade to Windows 10, with 18Gb ram and SSD 256Gb Disk CPU I7-4510U 2.0--2.60 Ghz
Upgrading from windows 8.1 to windows 10,
in windows updare, this error is displayed:
• Hewlett-Packard - Imaging - Null Print - HP Photosmart 6520 series - Errore 0x80070103
and in installation history the message is:
Hewlett-Packard - Imaging - Null Print - HP Photosmart 6520 series
Hewlett-Packard Imaging software update released in November, 2009
At 21:00, reloaded Windows 10 update and error is changed:
At this moment error is
• Hewlett-Packard - Imaging - Null Print - HP Photosmart 6520 series - Errore 0x8024200b
Solved! Go to Solution.
08-02-2015 01:25 PM
I got notification of similar topic and errors prior to Windows 10 install. They were related to a Windows update that failed to install on two devices. The update will still not install on either device...one with 10 and the other still operating with 7. Good news is that my HP printer is still connected to network and, as of a couple of hours ago, is still operational. I still would like to know how to dismiss the problems or, at least, the notifications.
08-02-2015 12:48 AM
Ok, Ok, even my printer and my scanner work well, but it 'stupid ALWAYS have this message every time you use Windows Update. and you can not even remove this update from Windows Update
08-03-2015 04:49 AM
I have just got rid of this update error message on Windows 10 by going into settings, devices, connected devices, then clicking on device manager link at bottom of screen. Then delete the 'Unknown Printer'.
It worked for me!
08-09-2015 11:44 AM
I tried this. It got rid of the failed updates but I lost use of my printer
Take a look at the following for a full fix. All OK now, Failed updates gone & latest Printer Drivers / Software installed.
Thanks for pointing Me in the right direction. Up to now, thought this was a Windows Update problem & I had been trying to fix it with DISM & SFC. Obviously it wasn't.