HP Printer Issue vs XP

  • Thread starter Thread starter Poprivet
  • Start date Start date
P

Poprivet

I think this is likely an HP issue, but since HP wants nothing to do with
supporting its customers has become so painfully obvious to me, I thought
I'd ask here.

There is a program that starts at boot called statusclient.exe. It seems to
go into a state where it occupies either 50% or > 90% of the processor time.
I've googled quite a bit on it, and I do seem to have identified the right
culprit, but ... I can't figure out how to keep it from loading; it comes up
with my HP Colorjet 2550n printer load. From what I can gather, it's the
program that sends printer alerts to the screen and monitors ink levels,
etc., so it's useful to have around.
But, I can't even figure out how to stop it from loading!

Anyone here have any experience with it, and a way to either get around it,
or at least stop it from loading?

I've tried the Java fixes; I did have both revs 9 and 10 and deleting 9
dropped the % by ten for a short time, then it popped right back to 50% and
stayed there. I thought MSConfig, but no help there I can find.

TIA,

Pop`
 
Check the RUN or RUN ONCE keys in the registry.
Can you find that file? Change it to statusclient.exeold & reboot & see if
any complications result.
 
Try Autoruns from the new Windows SysInternals (formerly Sysinternals) site:
http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/Autoruns.mspx
This will show all apps/etc. that load/run when you first boot and
selectively allow you to stop any that you don't want.
If this utility (statusclient) is listed you then can use AutoRuns to stop
it from loading.

Note: To get additional details on an item in the list you may need to
highlight the item (right click) and use the Google option to get the
details, especially useful for the more obscure items in the list.

JS
 
Thanks, Bruce, I thought that was good advice. Unfortunately, it seems to
matter because things went unstable and the Norton Windoctor monitors failed
to load. I put it back and voila, they worked again.
AND, my original assessment apparently is in error; statusclient at
first isn't loaded, but then loads later on as I discovered today, and went
right to the 50% cpu mark again.
Then I closed Windoctor and it the cpu time dropped to normal levels, and
statuscilent.exe is showing 0% cpu usage now. Strange. It's too soon to
say it's gone for good with Windoctor closed, but ... so far so good. If I
make it thru the day I'll run Windoctor's monitors again and see if it comes
back.
I don't -think- it's malware of any kind but those are famous last words.
It definitely seems to be HP related, but why it starts using all that cpu
time is beyond me, esp in view of Windoctor letting it settle down. Oh,
using the printer doesn't seem to have anything to do with it going to 50%
either. I don't think <g>.

Thanks,

Pop`
 
I probably shouldn't say it but "Norton"? Oh no!!!
I fix, help & advise many computers & people & I reckon over 50% of the
problems I encounter involve Norton products. How much memory do you have in
that computer?
 
lol, yeah, you're talking to the devil's brigade here! Memory is 512 but if
you're thinking paging, no it's not involved; no disk drive traffic when
it's at the 50% mark, all visible apps closed and buffers cleared.
Windoctor however is an interruptive process, I know, and when it
interrupts, some processes have trouble getting restarted for several cycles
but it's not the cause either, although -something- is!
What I can't figure out is why/when statusclient.exe is called - yet.
Mainly due to a shortage of time on my part. I'll find it; soomer or later,
if it'll just happen again! No sign of the 50% issue since my post, dang
it!

Think we can agree to disagree on Norton? <g>

Pop`
 
Back
Top