Printer Installed, but not visible

[drockwood94]

First and foremost, this thread is very similar to one below, but I figured it was probably better to post a new topic rather than reviving a thread from 2010. (Which I already posted to without realizing the date on it)

Okay, so I've got a problem where we installed an HP LaserJet 6P on our HP dx2450 that is running 32-bit Windows 7 Professional. When I connected the printer, it did not appear in devices and printers, but it showed up in device manager under other devices. I went ahead and installed the driver that is available to me (Through catalog.update.microsoft.com).

The printer installed successfully, according to the window, but it did not show up in Devices and Printers.
The printer shows up in the print context menus, as well as in the print management program.

The printer disappears occasionally upon reboot, and reinstalling it appears to work, but we get the same results as before.

Any help with this issue would be appreciated. While the printer showing up in devices and printers isn't necessary, it would be nice.

 

[fireberd]

The proper way to install a device, such as a printer, for most is to First Install the software and ONLY connect the device to the PC when the install program tells you. Connecting the device first can result in either no install or a corrupt install.

I recently installed a new HP All in One printer. The HP install instructions listed installing the software first.

 

[drockwood94]

Unfortunately, since HP doesn't offer windows 7 drivers for the 6P, only the drivers from Microsoft are available. You are unable to install these drivers without having the printer plugged in, as it needs to see that you have something compatible to use them with before it will allow the install. (There is no exe, you have to go through device manager to install these drivers and select the inf file)

 

[fireberd]

I've seen some of the older HP's that have the built in drivers. I didn't realize this was one of them.

The printer should be listed in the Device Manager. If it is, Right click on the entry to highlight it and then LEFT click "Uninstall". DO NOT uninstall the drivers. Disconnect the printer and restart the PC. Connect the printer and it should go through a new installation. This may fix the apparent Windows status corruptions.

 

[drockwood94]

Unfortunately, the printer does not appear under device manger after the initial installation. I did uninstall the printer through print management, though, and reinstalled. This did not work.


By built into the printer do you mean like the 1102 that pops up with a "Smart Install" when you connect it and it doesn't have the drivers? The HP LaserJet 6P doesn't have that. The only things available are the files available from Windows Update. (See attached image from HP's website in regards to obtaining drivers for this printer)

The next attachment is the website that HP refers you to (after jumping through a few hoops).
This is where I obtained my driver. It works flawlessly for all of our other printers. Just not this one.

By all our other printers, I mean printers of different models. The driver set includes information on multiple printers.

I'm not sure if the issue is with the printer, the driver, or the parallel interface card between the two. If it was the card, you'd think there'd be a problem with its drivers. But there isn't. The computer can communicate with the printer, so it shouldn't be the parallel card.

 

[fireberd]

What I was referring to was with many HP PC's, they have included the drivers for many of their products and the users do not have to download and install drivers. Just connect the unit and it is detected and the drivers installed.

This is a different case. I'm sorry I responded as this is out of my area.

 

[drockwood94]

Don't apologize for trying to help. That's just silly. We now have a good explanation of the problem rather than the half-explained piece of crap that was my original post.

You were definitely helpful in helping me puzzle out and troubleshoot my sound issue last week, so thanks for chiming in!