I have the same issue described on this thread, with my networked HP
Photosmart 3210. OS is Vista Home Premium with all of both MS and HP updates
as well as the HP CIT223969 "Critical update to prevent unexpected printer
uninstall".

the HP support suggested me to disable both UAC and the Antivirus, you may
imagine how my reply was. I think HP produces high quality hardware, but
software should really improve: actually, I got the svchost.exe_HPSLPSVC
crash each time my notebook resumes or the assigned IP changes.

not to mention the scanner part of the HP 3210 is not present on Windows
Vista Scanner applet.

matro

"John H" ha scritto nel messaggio
...
I mentioned that I was having problems with my 6310 and that I would post
again if my problem was resolved. I am glad I didn't post too soon! I
also
am unable to accurately express my frustration with HP and with MS. It
was a
huge mistake to purchase Vista instead of XP for my new computer. The
fact
that I had a perfectly good HP PSC 750 which HP wouldn't support in Vista
should have been a clue for me, but nooooooo - I had to go out and
purchase a
new HP printer which doesn't work with Vista.

HP support were very polite and suggested numerous things, most of which
didn't work. The only thing that seemed to work was to turn off the "CUE"
service as I mentioned in my previous post. That resulted in a working
(networked) printer, but left me with regular error messages which were
bothersome, but the printer worked. Now, today, although my printer shows
"ready" as a network device nothing prints. I have been working on it for
about two hours, including rebooting the computer, which curiously didn't
clear the print cue. I have just tried shutting off the Windows Print
Spooler service and turning it back on and then rebooting. For some
reason,
I now have a working printer. Temporarily.

The joke is that this 2+ hour effort was merely to print address labels
for
Xmas cards. This kind of time savings I don't need.

Sadly, the only folks reading this will have likely already purchased an
HP
printer. If not, don't! If you can return yours, like I should have
done, I
recommend you do so. Both HP and MS have known about this problem for at
least 6 months. I don't accept that they can't fix it, they are likely
just
too embroiled in a ****ing match over who should be responsible.