Unable to install hp printer driver. How I put the "firewood" of the HP printer on Windows XP

Greetings to you friends! " Printer driver not installed error 0x00000002 "  - this is a problem about which I want to tell you today, or rather, to show how I managed to cope with it. In general, it was like this, I received the task to connect from a virtual machine over the network to a printer that was locally connected to a completely different computer. Something I have done with articles about printers, this is the third in a row on this topic, well, who has subscribed to the newsletter articles I understand what I, well, okay, we will continue.

So, going to the virtual machine, I, as usual, tried to connect the printer by writing the name of the computer in the "Run" line, but to my surprise, instead of connecting to a computer, I received a notice before my eyes that such a computer was not on the network, or I was wrong entered his network name. Well, since I am persistent, I typed the name again, only this time looking at each letter I entered, the result did not make me happy, because a window appeared again about the wrong network connection.

Having finished with connection attempts using a simple method, I turned to alternatives, namely, I decided to connect the printer using the connection via “ Local port". Without even thinking about the error “Printer driver not installing driver 0x00000002” may appear, I downloaded the latest version of printer software from the manufacturer’s website ( By the way, the connected printer was the HP LaserJet 1020), and started installing it by running Local Port and writing the path to the network printer there.

How did I manage to connect the network printer and overcome the error 0 × 00000002

At first, everything seemed to be normal, after registering the address, my virtual machine saw the network printer I needed, and began the process of connecting to it. Immediately after the end of the connection, a driver installation window appeared before me, or rather, the system asked me to specify the driver that will use the printer when printing.


Since I prepared the driver in advance, for me this stage did not become a problem. By clicking on the " Install from disk“I indicated the path to the folder where my downloaded driver is located and began to wait for the installation to complete. But, it was not there, unexpectedly, the error “Printer driver is not installed 0x00000002” appears on the screen. I immediately had a few questions in my head. What's wrong? Why failed? Did I put the driver on the installation?

As it turned out the driver is the one that is needed and with the most recent version, the system is also all right, it is completely clean and that's it. Unable to find a logical reason for everything that happened, I started searching on the Internet, how can I fix the error “The printer driver is not installed 0x00000002”. As usual, a lot of different answers were found, which I will definitely consider, but a little later, but unfortunately from the fact that they advised me nothing helped.

I punched to connect again through the local port, only this time, instead of the network name, I indicated the IP address of the computer I wanted to connect to (   by running it in cmd). But unfortunately, the window with the error 0 × 00000002 did not take long to appear and reappeared before my eyes.

Then I tried to restart the print service using the buttons " Turn off"And" Launch", But a negative result followed as before.

Further, I was advised to clear the spool folder and all entries associated with it in the registry. Although my Windows was absolutely new and only one printer (HP LaserJet 6L) was connected to it for all the time, I decided to check this option, but as it turned out in vain, because I wasted my time. The error "Printer driver is not installed 0x00000002" as it appeared, and continued to do so.

But, having tried several options, I took the IP address, and decided to try my fate again, and try to connect to the computer in a simple way through “ Win + R". And what do you think happened to the miracle, I was still allowed to the remote computer and the HP LaserJet 1020 printer I needed appeared in front of me. Clicking on “Connect”, he surprisingly did it without any problems, while downloading the driver from his computer and was physically connected. When checking the printing from the printer, a flawlessly printed page came out, which made me very happy.


Perhaps by this I did not solve the problem itself with the error "Printer driver does not set error 0x00000002", but at least in my case, I found an alternative way out of the situation that will allow you to connect the printer over the network without any problems.

Tips for resolving error 0 × 00000002 when connecting a network printer

So now I will write the promised list of tips that can help in correcting the error that appears when you connect the printer

  • We try and the IP address of the connected computer;
  • Restart the Print Manager service by going " Control Panel» – « Administration» – « Services» – « Print manager". Going into it click first " Stop", and then " Launch"- this method is very often, it helps a lot;
  • Clean the Spool folder from unnecessary drivers - you can see how it is done;
  • Upgrade your system completely.  using the update center. Perform this item or not, those who have, you know better. This option is not a 100% solution, so see for yourself;
  • Alternatively, you can still try to install on the computer " Universal Print Driver"And then try installing the printer again;
  • Finally, try the option that helped me by connecting to the printer via “Win ​​+ R” and the IP address;

I would be very happy if you leave

Good day friends.

In general, the situation is as follows. The other day I brought this miracle along with my nubuck laptop on which for 7 years already !!! XP-scale works (since 2008) and says: “Diman, what do you want to do, but put me firewood on XP. 7-ka is not particularly productive. RAM 3 GB, so help out, I did not succeed, some kind of network asks the framework. ” All threw and left.

Well, I think, garbage question, let's do it now. .Net Framework 4 got it, installed it. All OK. It came to establish and then it began ...

As he asked the pot for a request to connect the cable, I completed this step and waited ... waited ... waited until I got an error from me.

Well, I think, okay, I'll wait, maybe it will still start ... but no, having reached 100% of the detection of the device, he spat out the next, no less beautiful mistake. And what is most interesting, the driver for the scanner is installed ...

Emotions overwhelmed ... And how else said Ivan Vasilyevich from the film “Ivan Vasilyevich Changes Profession”: “What more do you need a dog. Yes, nothing. Well, marry the bury, the king releases her "... But I did not let the printer ...

Well, I think, okay, since you didn’t follow the instructions, maybe I’ll think I’ll indicate the driver with pens and you will earn from me ...

And after some manipulations in the last step, when you need to click Finish, I click and ...

Well, I think either the skis do not go or I already have that ...

Spat on him and left until the next day. I began to look for answers on the network, and besides the fact that the drivers say curves and all that and HP in general, the team doesn’t sculpt the best drivers, well, I won’t argue with that ... Anything can happen. But how can I deliver. It felt like the printer was saying to you: “Break, break me completely. Completely break it "😆 😆 😆 Yes, yes, it was 😆

I also turned off the antivirus, I think maybe he ... no ... It's the same. Maybe the truth is firewood, went to offsite and downloaded the most recent ones ... the same thing ... 👿 👿 👿

There simply were no words ... Let me think, I’ll run through the antivirals, look for a virus cell, maybe it’s something, it happens that a virus hole has made some kind of hole ... I found about 200 viruses, cleaned, installed the driver again and everything was under the tail ...

I think, well, I call my friend, I say: "Listen, maybe I will take down the Windows and put it on the net." "What if it does not go?". I say: "Well, now I will try to install on 7-ku" ... iiii ... established.

As a result, in general, I came to another kid, he also had a pig, I say let me try to install it, it was installed the same way, everything is fine ... I think I feel somewhere I screwed it up.

I go again to the laptop, install. NetFramework 3.5 SP1 and what do you think, everything was installed until the last driver, nothing was missed.

That's because of the version of this framework itself, a lot depends on whether the drivers are installed or not, whether you will break your head or not 🙂

For some time, absolutely all printers suddenly stopped working in Windows Server 2008 R2 x64. Both installed locally and connected over the network, as well as printers of users of remote desktops (terminal servers). They also disappeared from the Start - Devices and Printers folder, only the computer and other input / output devices are displayed there. There are no printers.

When trying to install a printer driver, it does not matter whether it is networked or local, in any way, at the end, after installing the driver, the system displays the following messages:

“Failed to install printer. There is no print handler. ”

“Windows cannot connect to the printer. There is no print handler »

And in the section "Details" can be the text   "Error 0x00000002"  (this code means "ERROR_FILE_NOT_FOUND") .

Decision

The print processor is a component of the Windows printing system file "Winprint.dll". This file is used by default, but some printer drivers may use their own print handler, for example “hpcpp115.dll”.

These files should be located in the same location as the printer drivers:

In the system folder "c: \\ Windows \\ System32 \\ spool \\"

In this folder at least there should be such folders:

drivers \\  - driver files are stored here
PRINTERS \\  - print spool files are stored here
  prtprocs \\
- print handlers are stored here
SERVERS \\- here is stored information about computers on the network with available printers
  tools \\
- utilities are stored here

Accordingly, we are interested in the folder "Prtprocs"where the print handler files should be.

In my folder "Spool"  there was no folder at all "Prtprocs"i.e. the system quite reasonably swore that the print handler did not exist (it’s a pity that she didn’t even hint where and what files were missing).

To restore the folder "Prtprocs"  and its contents just copy it from another computer with the same operating system. If you need someone, you can download an archive with a folder "Prtprocs"  for Windows server 2008 R2 64-bit system.

So in the folder "C: \\ Windows \\ System32 \\ spool \\prtprocs"For a 64-bit operating system, at least two folders must be located:

W32X86 \\- for 32-bit drivers,
x64 \\- for 64-bit drivers.

Each of them must have a file. "Winprint.dll"(in principle, it is enough that it be at least x64). Also in the x64 folder there should be one or several folders (depending on the number of languages ​​in the system, I had two), for example:

en-us \\
ru-RU \\

Each file must contain a file. "LXKPTPRC.DLL.mui"(or LMPRTPRC.DLL.mui).

After restoring the print handler folder "Prtprocs"  and all its contents, you must restart the server (unfortunately, without this in any way). After the reboot, the previously installed printers appeared and when the driver is installed everything goes correctly and the printer starts working.

The reasons

The only reason for this situation that I can identify is the role setting. "Print and Document Service", it was after this that the printers disappeared and an error occurred about the print processor. The service, though useful, is still the main suspect in the appearance of this problem (maybe it has nothing to do with it). Removing the service and rebooting the server did not solve the problem. As well as installing it again.

It is also likely that the problem could be partially solved if a driver is installed that uses its own print handler.