HPBOID.EXE remove it permanently

Some HP Printer drivers install a service called HP Status Server based on an executable called hpboid.exe, on terminal service machine it start itself many times and it doesn't remove it whenever user disconnect itself consuming too much resources.

Since this service isn't required for printing using Terminal Server, I tried to avoid process creation in some ways:
1) Deleting services
2) Disabling services
3) Removing permission to HPBoid.exe for Local System Account

But nothing works....

I also read this post http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=370850&admit=-682735245+1190810782857+28353475 but the solution was still far away.

I thought I need to understand better when and how it start the process. After analyzing the behaviour on some server I notice the process was started for only some printer drivers and for all these drivers I found the following values into this registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-3\\Dependent Files


The solution was to manually remove this entries from Windows Registry for each drivers.

UPDATED: http://vittoriop77.blogspot.com/2007/10/hpboidexe-remove-it-permanently_22.html
Share on Google Plus

About Vittorio Pavesi

    Blogger Comment
    Facebook Comment

6 commenti:

Anonymous said...

Some drivers, such as the Business Inkjet 2300 PCL6 and the Color Laserjet 5500 PCL6 have HPBOID.EXE and HPBPRO.EXE rather than .dll

Anonymous said...

These are reinstalled when you add or update a new HP driver. At this time I monitor processes... when HPBPro or HPBoid show up I execute a script that kills them and strips them out of the registry. I am not interested in making a special process for every time I install a new driver - this one shot in the arm process has kept my servers from crashing for a while now.

Anonymous said...

You say that monitor processes? How I can monitor the hpbuid or hpbpro process to launch a script? Can yopu help me?

Anonymous said...


i had the same troubles on a win2k3 terminal-server. the only working solution was a little script:

net stop spooler
sleep 5
taskkill /F /IM HPBOID.exe
taskkill /F /IM HPBPRO.exe
sleep 5
net start spooler

save it as kill_hpprocess.cmd

now open a new task in the windows task-scheduler and let the schedule run daily.



Anonymous said...

I like HP's solution. Just delete it, deleting the file will not affect the printing functionality.

See this http://h10025.www1.hp.com/ewfrf/wc/genericDocument?docname=c00850968&cc=us&dlc=en&lc=en&jumpid=reg_R1002_USEN

Lon Vetula said...

If you delete them and have to install another driver, it puts it back.

Group Policy, Computer Conofiguration, Windows Settings, Software Restriction Policies, add a Hash rule that does not allow this program to run.