High process IDs

Re: WSA uninstall unsuccessful

Looking in the eventviewer logs, I found these, which maybe useful, or not.


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date: 14/10/2013
Time: 12:01:48 AM
User: N/A
Computer: ***Identifying information removed***
Description:
The WRSVC service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7035
Date: 14/10/2013
Time: 12:01:54 AM
User: ***Identifying information removed***\ ***MyName***
Computer: ***Identifying information removed***\ ***My Name***
Description:
The WRSVC service was successfully sent a start control.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 14/10/2013
Time: 12:01:55 AM
User: N/A
Computer: ***Identifying information removed***\ ***MyName***
Description:
The WRSVC service entered the running state.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7032
Date: 14/10/2013
Time: 12:01:58 AM
User: N/A
Computer: ***Identifying information removed***

Description:
The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the WRSVC service, but this action failed with the following error:
An instance of the service is already running.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date: 14/10/2013
Time: 12:02:21 AM
User: N/A
Computer: ***Identifying information removed***
Description:
The WRSVC service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

Re: WSA uninstall unsuccessful

Some of the actual listings around the time of the glitch with WSA....

 

Re: WSA uninstall unsuccessful

What I am not implying but stating directly is this:
You are using too many security products that can and will interfere with each other and with anything else on the system without a solid enough understanding of how the deep core guts of the computer's operating system and programming work to support such use. It's like throwing random food into a blender and calling it a meal, then trying to ask a chef why it's not tasting right.

For example, you posted a windows system event log entry of windows noticing that the service crashed, followed by windows saying it's trying to restart the service, followed by windows saying the service reported that it started successfully. Instead of saying "The service crashed and restarted successfully, then something caused Windows to try to restart it again for no apparent reason", which is what would lead a support engineer working with you to request the basic WSALogs set, which would lead them to notice that when you did an uninstall or it tried to do an upgrade, your other security software blocked the transfer of permission to the new version, thus causing two copies of the service to be installed, thus causing it to go into a service spawn loop.

What I am implying is that you are creating unrealistic situations and faults that are likely entirely unique to your configuration and unfortunately consuming a lot of everybody's time with these errors that are best resolved by not putting so much potentially-conflicting software on the system and trying to make it work. This is called trolling, whether you are doing it maliciously or not, it's a manner of looking for attention. It's similar along the lines of a WSA user saying "I got infected! You didn't protect me!" and having to be told "That's because you took the infection out of quarantine, allowed it, ran it, took the stuff it installed out of quarantine, allowed it and re-ran it, then shut down WSA when it told you to, despite WSA telling you this was a bad idea."

You can say you are well-protected. You can quantify this by saying you've never had an infection. I can counter by saying that I've got nothing but WSA and I've never had one either, so I'm just as well-protected as you. But my computer doesn't scream at me every time something happens, ask me about what I want to do, etc. So my computer is just as secure as yours and is also more usable and faster.

Either way, I will stick to the basics: Yes, you can run WSA with other working things as a general rule. You are running other things with other things that should not be used together. That means you no longer have other working things, you have other broken things. WSA will try its best to run on a broken system, but there is nothing in the world that will stop a user 100% of the time from causing failures. You successfully found a failure. You are likely the only person out of millions who will encounter a failure caused in the way you caused it. Thus, it is not to the benefit of anybody at all, not even you, to continue to diagnose or correct when you have multiple other things that should not be running together not configured properly to allow things to work.

 

Re: WSA uninstall unsuccessful

Amen....

 

Re: WSA uninstall unsuccessful

Well thanks! Looks like a case of shoot the messenger!

 

Re: WSA uninstall unsuccessful

No, it's not. In this case the messenger is also the person who generated the message. And we're not shooting.

"Doctor, it hurts when I go through this door because I gave it a microwave anti-intrusion system that makes all people hurt when they try to go through it!"

"Then either don't go through that door, or take down the system that is doing precisely what you wanted it to do by hurting you so you won't go through the door."

Locking a place up tight with an active-response security system is great as long as you have the keys, codes, and know how the system works so you can use it to your advantage and not be shot by it. In this case, it appears you lack the keys, codes, and know-how of the system. So we are simply recommending that you learn, or stop using a security system that will hurt you because you don't know how to use it.

 

Re: WSA uninstall unsuccessful

I have one more thing in response, and then I let it rest..."Doctor My Eyes", have seen the light.

 

Re: WSA uninstall unsuccessful

mofcomp.exe is used on Windows XP to have WSA integrate into the Security Center. I imagine that one of the other security products blocked WSA from executing it for whatever reason (this area has been unchanged since the 2012 release). A reboot should allow you to resolve it - the Security Center access only takes place shortly after installation.

 

Re: WSA uninstall unsuccessful

DrWatson just tried to start, but I don't know what initiated it...but I got some screenshots. Maybe unrelated to WSA.

 

Re: WSA uninstall unsuccessful

I found the log. Don't know if it is worthwhile.

 

Re: WSA uninstall unsuccessful

On the basis of this quote -

"As far as I am concerned, 1 byte is excessively large for a Dr. Watson
log file.

In my opinion it is the most useless component of Windows XP and one
which I routinely dispense with whenever I find it running on a
system.

I have never encountered a situation where Dr. Watson was of any value
whatever in identifying the cause or helping to fix a problem."

I have deleted the log, since it had grown to 36 MB.

 

Re: WSA uninstall unsuccessful

I wish I could find out what causes WSA 2014 to go into a continual restarting loop... This behaviour only started with this version. So, don't say I am nitpicking, or as someone recently, said here, a troll.

 

Re: WSA uninstall unsuccessful

A remote support session may be helpful for this - do you have any idea as to the regularity with which it occurs, so that we could perhaps plan the session (daily/etc.)?

Thanks!

 

Re: WSA uninstall unsuccessful

There was no problem since yesterday morning as can be seen from process explorer... It took ages to make this post, because system is sluggish. I am about to reboot, to get system back to normal. Be Back soon!

 

Re: WSA uninstall unsuccessful

Back up! ...systray just loading.

 

Re: WSA uninstall unsuccessful

Just idling...

 

Re: WSA uninstall unsuccessful

what are the other security products you're currently using in real time?

 

Re: WSA uninstall unsuccessful

This is one, that I am using...

 

Re: WSA uninstall unsuccessful

...and

MBAE, VS, Zemana, KPCDoctor and Vipre

 

Re: WSA uninstall unsuccessful

holy moly, all in real time? (i think you are, as far as i can see from your system tray).
isn't that a total overkill? no wonder why you have system anomalies.

 

Re: WSA uninstall unsuccessful

It all depends...every system is unique!

Here is some more info, since every bit helps.

 

Re: WSA uninstall unsuccessful

Some more info...

 

Re: WSA uninstall unsuccessful

i have never seen this much security software being used in real time at once, not even on wilders. right now i'm trying to figure out how your system managed to survive till now without constant bsod's.

 

Re: WSA uninstall unsuccessful

I like to think I am the conductor of an orchestra, that is in tune.

This system has been up and running since 2007, and the OS has never been reinstalled since then. I think I may have some clue, but I am sure some may disagree.

 

Re: WSA uninstall unsuccessful

well, all i can say is i'm glad for you.