Hewlett Packard Laserjet 6p Printer Driver Rating: 3,8/5 2671reviews

Ian1806 wrote: so what was the process that worked for you? It is already on page 1 of this forum thread but here I paste it again for your convenience: • Update your printer's driver (let Windows and Device Manager search for updates). • Go to Device Manager, open your parallel port's properties, choose port properties and check 'Do not try to use interrupt' (it is the first option) and tick 'Enable legacy Plug and Play detection'. • Get DevCon.EXE from - make sure you choose the right version for your system.

• Write a small script (let's name it printer.cmd) with the following contents: @echo off cd /d%~dp0 devcon disable *PNP0401 timeout /t 1 >nul devcon enable *PNP0401 • Put that script together with DevCon.Exe in one folder (example: C: scripts) • Create a scheduled task which executes this script on user logon. Let the script be executed under the SYSTEM account there (run this command as administrator): schtasks /create /tn 'Fix Printer' /tr c: scripts printer.cmd /sc ONLOGON /ru SYSTEM (If your WIndows 10 is not in English language, you will have to replace the ONLOGON parameter to fit your language.

Hewlett-packard Laserjet 6p Printer Driver Free Download

NOTICE: Hewlett Packard's current LaserJet 6P driver release resolves driver conflicts, improves your computer's stability and restores communication with all.

In German, it is, for example, BEIANMELDUNG. Please see the output of schtasks /create /? For details.) • That's it! I had the same issue (getting Windows 10 version 1511 build 10586 to allow printing to my 'trusty' HP Laserjet 6P). Not being real savvy with programming, I wasn't able to follow your advice/instructions about creating the printer.cmd. What I did find out, though, did solve my problem.

The HP Laserjet 6P was connected to my computer via a parallel cable from the printer to the LPT1 printer port on the back of the computer. Windows 10 build 1511 recognized the printer (saying all was fine) but when I tried to print to the printer, it gave me an error saying no drivers available. Before I updated to Windows 10 from Windows 7, all worked fine. I thought maybe the build of Windows 10 (build 10586 version 1511) was the problem, but could only go back to Windows 7, not to build 10240 (as stated by some in this forum). Having another computer in the house that had Windows 10 (build 10240) on it that had NOT been upgraded to build 10586, I experimented by moving the HP Laserjet 6P to that computer.

To make a long story short, the HP Laserjet is NOW working on all of the Window 10 computers, no matter what the version/build. For me, the PRINTER CABLE was the culprit. If I tried connecting the 2 with a parallel printer cable to the LPT1 printer port, I would get an error.

But when I connected the 2 with a different parallel printer cable via a usb port connection, all was good. Even the dreaded Windows 10 version 1511. Just thought I would pass this on.and hoping all keeps working no matter what build Windows 10 throws our way.

Would be nice, though, if HP would produce a driver for a standard parallel printer cable. DuaneTN wrote: I had the same issue (getting Windows 10 version 1511 build 10586 to allow printing to my 'trusty' HP Laserjet 6P). Not being real savvy with programming, I wasn't able to follow your advice/instructions about creating the printer.cmd. What I did find out, though, did solve my problem. For me, the PRINTER CABLE was the culprit. If I tried connecting the 2 with a parallel printer cable to the LPT1 printer port, I would get an error.

But when I connected the 2 with a different parallel printer cable via a usb port connection, all was good. Even the dreaded Windows 10 version 1511. Just thought I would pass this on. Rubygems No Such File To Load Rbconfig more. and hoping all keeps working no matter what build Windows 10 throws our way. Would be nice, though, if HP would produce a driver for a standard parallel printer cable. It is not the cable itself but the parallel port and its driver. This driver was destroyed by Microsoft in order to entirely remove parallel port support in the next Windows versions.