David Polanco San Antonio Technology Blog

anonymous Says:
August 15th, 2009

Brilliant- worked a treat- many thanks.

anonymous Says:
August 24th, 2009

thank you... solved my problem as well

anonymous Says:
September 07th, 2009

i have spent the past 3 hours trying to get the printer working, then I came across your article (and having previously used the existing driver) took yr suggestion and sit went straight up & running

many thanks

Dave - Sydney, Australia

anonymous Says:
September 28th, 2009

I followed the advise and had no luck... my printer is not printing even though it's not giving me any error messages, lights are not flashing etc

anonymous Says:
November 03rd, 2009

Saved me a lot of time. Thanks a million!! Worked like a charm!

anonymous Says:
November 29th, 2009

THANKS! I have spent 2 hours on this - I download a hotfix from microsoft trying to resolve it. I used another machine and copied the dll's.... and all I needed to do is not use the existing driver! UGH! It's the obvious stuff! THANK YOU!

anonymous Says:
December 08th, 2009

This was simple and helpful. It worked perfectly. Thanks for sharing this solution.

anonymous Says:
December 14th, 2009

Thanks for sharing this solution. I have replaced the drivers Worked perfectly.

Anil-India

anonymous Says:
January 25th, 2010

Thank you, it worked perfectly!

anonymous Says:
January 26th, 2010

This is no better than any of the dozens of other solutions that have FAILED! Windows 7 sucks.

anonymous Says:
January 30th, 2010

After many hours of web surfing, trying, and failing ... your suggestion WORKED!!! Many thanks for having taken your time to share this with the world. I, for one, am most appreciative!!!

anonymous Says:
February 08th, 2010

Your suggestion worked for me after numerous attempts of trying different things.

anonymous Says:
February 22nd, 2010

Excellent advise, indebted to you indeed!

anonymous Says:
March 06th, 2010

Sadly to say but this advise didn't work for me :-(

anonymous Says:
March 30th, 2010

Thanks.... worked....

anonymous Says:
April 28th, 2010

Sadly, this did not work for me either. Win7 is giving me fits. I've tried bazillion pdf convertor, have always used novapdf, worked fine. Have tried at least 9 others, they all seems to install fine, then don't show up in my devices/printers list. The one exception is Universal Document Convertor printer trial. It installed as expected. My only other need is converting djvu files from a German digital library to pdf. Completes that task fine too. If the others worked, they would create a pdf from a djvu viewer of choice. So, guess I'm stuck shelling out $69 for an app with limited use to me. Can't justify buying a full featured Adobe Acrobat. This does seem a Win7 issue. I am not happy!...and a bit poorer.

anonymous Says:
May 11th, 2010

Many thanks! It worked like smooth....

anonymous Says:
June 30th, 2010

Thanks. It worked!
Grampsny

anonymous Says:
July 07th, 2010

BRAVO

anonymous Says:
August 16th, 2010

have you been able to figure out a root cause? is this related to missing updates on the windows server?

anonymous Says:
August 28th, 2010

Unfortunately, I get the same error message when I attempt this solution!

anonymous Says:
October 20th, 2010

Saved me a world of work and pain@

anonymous Says:
November 15th, 2010

this error coming while installing printer only...after clicking fish..its appeariing..

anonymous Says:
January 30th, 2011

Worked for me just fine. Thanks!

anonymous Says:
February 17th, 2011

Thanks you made my day.

anonymous Says:
March 02nd, 2011

no help

david Says:
March 02nd, 2011

Try again, if this does not help than assign the printer another IP. Also make sure that the printer is connected to the same domain that you are.

anonymous Says:
March 15th, 2011

Hi
I did all of which you advise, yet went through process and still gave same message.
I looked at your suggestion about asigning another IP address, but can't, 4 other users use it with that IP address.

anonymous Says:
March 16th, 2011

simply wonderful!!!

anonymous Says:
March 17th, 2011

This was very helpful.

Gratitude

anonymous Says:
March 22nd, 2011

Thank you Solved my problem in just a second, while I have searched for hours...thanks...

anonymous Says:
April 05th, 2011

1. Simply rename the files in <root dir>:\WINDOWS\system32\spool\prtprocs\w32x86 and copy the files from another machine using the same printer from its <root dir>:\WINDOWS\system32\spool\prtprocs\w32x86.

2. Now try to reinstall the printer, it will work.

anonymous Says:
April 17th, 2011

Awesome... Thanks dear... That worked great....

anonymous Says:
April 18th, 2011

i have tryed all of these pointers and i still have Printer driver was not installed Operation could not be completed (Eror 0xe00000100)

PLZ HELP ASAP

anonymous Says:
April 18th, 2011

^^ i have also replaced all the files in
<root dir>:\WINDOWS\system32\spool\
with a different Windows 7 Computer

anonymous Says:
May 03rd, 2011

Pure Genius. Worked like a champ

anonymous Says:
May 05th, 2011

Thanks so much!

anonymous Says:
May 25th, 2011

Thank you!

anonymous Says:
July 07th, 2011

Still worked even after all these years!

Thanks again!

anonymous Says:
July 08th, 2011

In Win 7 64bit this worked and seemed to install.
Thanks from the BC Okanagan

Now I have problem with TS with 32 bit driver trying to print on 64 bit remote. Another puzzle to unravel.

ogopogogo

anonymous Says:
October 20th, 2011

Awesome David.. it works. Thanks
-
Printer: HP LeaserJet 2600n
OS: Windows XP SP3

anonymous Says:
February 20th, 2012

The printer is connected to the xp operating system but it is giving same error while connecting that printer from windows7 still giving the same error.

anonymous Says:
June 09th, 2012

i need forget it

anonymous Says:
July 27th, 2012

Holy. F*&^@%. $#1t.

I've been stewing over this for DAYS, and it was that simple. A thousand thanks man!

anonymous Says:
August 17th, 2012

A solution that worked for me:

Searched my "Windows" folder for "winprint.dll" and copied it to the "Windows\System32\spool\prtprocs\x64" and restarted. All my printers magically re-appeared and I could print to them without any further set-up, driver download, or tinkering...

anonymous Says:
November 01st, 2012

Yesterday, i was facing the same problem and could not be able to resolve because using the existing driver.
Now the error is resolve when i reinstall the printer driver. Thanks for helpful information.

www.iyogireviews.com/

anonymous Says:
November 02nd, 2012

Same issue, but I have worked on this for four hours now, have done exactly what you stated plus, uninstalled the HP software completely and deleted all the files from my hard drive, (three times now), and still that pesky error message comes up during installation "print processor does not exist." I am gonig to bed now and totally frustrated.

anonymous Says:
December 18th, 2012

Been trying to install a printer for many days and getting the bloody message about the processor. Tried installing remotly via vnc,rts, and via the machine itself proved futile. UNTIL I did the rplace printer dirver instead of use the current one.

All I can say is thanks.

anonymous Says:
December 24th, 2012

Thank you! What a struggle trying to get a Vista laptop to print from my printer connected to a Windows 7 workstation. Made some progress then ran into this issue! This worked, had to do some more tinkering in addition to get it to fully work, but finally got it! Thanks again!

anonymous Says:
January 14th, 2013

This had worked. I have tried a lot of things even checked the MS website which of course didn't help.

Thanks for the help.

anonymous Says:
March 15th, 2013

No luck with your fix.
windows server 2008 R2 does not have a winprint.dll in the ...\spool\prtprocs\w32x86 folder, only in the x64 folder. I replaced that from a print server that I have successfully installed and printer to the printers I am having issues with. Even built a print server and installed several of the problematic printers and exported them and imported them into the problematic server with overwriting the drivers, no luck. Blasted the entries out of the registry for the problematic printers and still no luck when recreating and saying to use the freshly downloaded drivers. This is killing me. I know it is something related to this winprint.dll, but the instructions to place it in the \spool\prtprocs\w32x86 folder are not applicable to server 2008 R2