130+ Instances of HPBOID.EXE on 2003 Terminal Server (236 Views)
Reply
Occasional Visitor
Fred Macondray Jr.
Posts: 1
Registered: ‎05-10-2006
Message 1 of 6 (236 Views)

130+ Instances of HPBOID.EXE on 2003 Terminal Server

We've got a 2003 Windows Terminal Server we all use frequently.

It appears that one of our users has an HP LaserJet1200 installed so they can print from home, however, somthing is causing the process to be re-launched over and over w/o ever killing itself.

Each one of these processes is using over 4MB of RAM!!!

Please help. How can I disable this app?

Thanks,
Fred

Please use plain text.
Occasional Visitor
Jon Aherne
Posts: 3
Registered: ‎06-07-2007
Message 2 of 6 (236 Views)

Re: 130+ Instances of HPBOID.EXE on 2003 Terminal Server

I have the same issue with a terminal server.
the remote office and remote users all have HP printers.

The HPBOID.EXE is not terminating on the TS.
I am planning on shutting down the HPBOID.EXE service in SERVICES and the remooving all instances of this file in Task Manager. Reboot the server and get the remote users to print again.

I would like more info on this before I go this route.
Please use plain text.
Occasional Visitor
Jon Aherne
Posts: 3
Registered: ‎06-07-2007
Message 3 of 6 (236 Views)

Re: 130+ Instances of HPBOID.EXE on 2003 Terminal Server

Another thread had a responce of:
"I've had this problem many times, on variuos servers. what I do is: Download the latest driver for you printer.

Uninstall all versions of the installed driver.

Stop the spooler service, and search your harddrive for any hpboid.exe/dll and hpbpro.exe/dll files and delete them.

Restart the spooler service.

Unzip the new printer drivers, and edit the .inf file, removing ALL lines referring to the above files.

Install the new drivers.

(will complained about not being a microsoft signed driver, just ignore).

Should be fine."

But does it work on a terminal server related issue
Please use plain text.
Advisor
Vikas Rattan
Posts: 20
Registered: ‎03-11-2007
Message 4 of 6 (236 Views)

Re: 130+ Instances of HPBOID.EXE on 2003 Terminal Server

Hi Fred

Search for the file and rename it, add 1 in the begining or in the end. It will never pop up again in the task manager.

Let me know if that resolves the issue..

Vikas
Help On The Move
Please use plain text.
Advisor
Patrick J. Burwell
Posts: 17
Registered: ‎01-04-2007
Message 5 of 6 (236 Views)

Re: 130+ Instances of HPBOID.EXE on 2003 Terminal Server

pskill \\hostname -u hostname\Administrator -p password HPBPRO

pskill \\hostname -u hostname\Administrator -p password HPBOID

psinfo \\hostname -u hostname\Administrator -p password HPBPRO

Get this pskill from PSTool on Technet or go directly to http://www.sysinternals.com and you will be redirected - Microsoft bought it.

Then go find the driver in msconfig and remove it, removing all instanced of the driver from the drive as well (say no to the reboot). Open Regedit to the HKLM/software/Microsoft/Windows/Current_Version/Run key and remove the msconfig entry to prevent MSConfig from returning. While there confirm the entries for the HP Monitoring software have been removed.

Patrick Burwell
VP, Technology
iQor.com
The key to success is persistence
Please use plain text.
Frequent Advisor
Jeff Smith
Posts: 85
Registered: ‎09-13-2004
Message 6 of 6 (236 Views)

Re: 130+ Instances of HPBOID.EXE on 2003 Terminal Server

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation