Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works

status code 128

  • Please log in to reply



    New Member

  • Member
  • Pip
  • 3 posts
Lucky, I just went through this with a client. He had about 10 server systems all thoroughly infected. I was surprised to be able to clean them all but it worked. Here's what I did:

1) Make sure you have some Anti-Virus software--preferably something well known like Norton or MacAfee--installed and updated with the latest virus definitions.

2) Start up your system in Safe Mode.

3) Turn off all Services you don't absolutely need or don't recognize.

4) Remove any program startup selections you don't absolutely feel safe with.

5) Run a full virus scan on your system.

I did this and found that a number of the services that had been installed were infected. I then removed those services using Add/Remove Programs and found they were not removed--surprise, surprise. So I removed them from the disk, manually, and then removed all references to them in the registry.

This is a hassle, true, and if you have backups of your data and know its virus free, might be easier to reinstall windows. I found this to be an easier solution, though, and it worked.

Good luck.
  • 0




    New Member

  • Member
  • Pip
  • 1 posts

This is mainly happening as the RPC server keeps on failing. You would need to patch your system with the patches given for Blaster and Sasser worm in Microsoft. If you had already patched you system, then the second method would be

2. Go to services -- RPC -- Remote Procedure Call not RPC locator

Recovery tab-- First Failure--- Choose either restart service or take no action. Do the same for Second failure and Subsequent failures.

After following this procedure please check your system. This should definitely work.

  • 0

Similar Topics

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP