Can't install printer (0x000006be error)

[jch]

I've got two new laptops with Vista Home Premier installed. They're
wirelessly networked and seem to function just fine with the exception that
I can't install my networked HP 2600n Laserjet printer. When attempting to
do so on either machine, I receive an error message that the print spooler
has stopped. I also receive an error 0x000006be. I can restart the print
spooler and try again but the same thing keeps happening.
I've seen this is a common problem with Vista with an assortment of printers
but I haven't read a viable solution. Can someone here help? I've
downloaded the latest driver and firmware from HP. The printer is connected
to the network router/switch and has its own IP. I have 2 other PCs which
run XP and can use the printer w/o issue.

Another issue is that with all the attempts to install the printer on the
new Vista machines, there is apparently multiple copies of the printer
somewhere in the works. I've deleted the printers from the printer wizard
but they still exist, in name at least, somewhere. Further attempts to
install the printer show various copies (eg Copy_5). I don't know how to
get rid of these. Is there a registry entry somewhere? Still, even removing
these instances of previous installation attempts will not solve the
problem. There is something wrong in the installation procedure which
caused this to occur in the first place.

[MICHAEL]

Have a look at these threads;
http://forum.soft32.com/windows/Vist...ict374805.html
http://www.winforumz.com/vista/Netwo...derasc-15.html

Then this excellent information from Microsoft;
http://technet.microsoft.com/en-us/l.../bb727037.aspx
File and Printer Sharing in Windows Vista

I did not find this encouraging;

http://forums.microsoft.com/TechNet/...2642&SiteID=17

[Romeo Props MICHALE the A$$]

MICHAEL wrote:

<snipped>

<Romeo, where are you boy? You can run Romeo Props MICHALE, but you
can't hide boy come out here you little *clown* come out.>

[jch]

I finally got it. The fix was to use the HP updated drivers (duh), but the
problem was that the downloaded drivers by themselves didn't fix the
problem. Downloading the entire HP CD with the installation files was
required.