WSA uninstall unsuccessful

The only other thing that I notice is that one of the several svchost.exe has increased CPU usage, but settles eventually. I think it is an issue that started occurring after some recent Microsoft Update, that happen in their monthly cycle of updates.

 

I found a link about increased SVCHOST.exe high CPU - http://blogs.technet.com/b/asiasupp...matic-update-causes-svchost-exe-high-cpu.aspx

NB: It was written in 2007, but seems applicable still in 2013.

 

Confirmed by stopping the Automatic Updates in services on XP...

 

Musn't terminate this svchost...otherwise dire consequences.

 

@Tarnak can you please do as Joe suggested?

Thanks,

TH

 

I would, but between my recent PM's to Joe and certain answers I have received, and this thread.... you could say that, I am reluctant to proceed with an uninstall, until I get precise and unambiguous instructions to literally expunge this current install from my system. I want to ensure every last hidden remnant is gone, so I can do a fresh install.

So, Joe if you can reply to my last PM, and provide clear and concise instructions, I will go ahead and try a 3rd attempt to unistall.

 

Sorry I didn't know this went to PM's but you keep posting screen-shots? Now that makes it confusing as we can't follow the remedy.

TH

 

W

And you can see how I am confused when I don't seem to be able to pose the question/problem to Joe. Let alone the 'remedy'.

P.S. I always thought pictures were worth a thousand words.

 

Replied

 

Hi Tarnak

You can also find some more about the svchost.exe CPU usage issue here: https://www.wilderssecurity.com/showthread.php?t=353289

 

Thanks...I saw that thread, soon after I had posted my comment.

Edit: correction

 

After, uninstalling again, and reinstalling, I thought all was well...It ran for about 30 hours....no problems.

Then just about 20 minutes ago, one of the WSA.exe's spawned a child process, mofcomp.exe. - http://www.processlibrary.com/en/directory/files/mofcomp/28920/ I tried to get a screenshot, but my system went into freeze mode for several minutes.

After, the computer became responsive, I got the following screenshot showing 3 wsa.exe's running.

 

Ah good

 

Tarnak,

Just looking over your description of things, it's very obvious that you have too many things interfering with WSA's operation (and possibly other operations). I told you for example that when uninstalling, Windows itself cannot unload the kernel driver realtime. It seems like an innocent thing to you: A protection program blocks WRSA.exe from making changes to critical system registry locations (and may not even tell you it is blocking it). But what you see is WSA doesn't uninstall. Never occurs to you that thee uninstall failed because another security program blocked it.

The image you posted of the registry change would be WSA trying to do an upgrade. Block that and suddenly it's running one version of the executable and another of the DLL. Programmatically, it's liable to engage that change attempt multiple times, since normally it's just going to overwrite the same data with no ill effect. Block it or delay it each time and if the program checks back to make sure the data was written before continuing its operation, you've just broken everything it was trying to do.

And while getting your tech support directly from the vice president of the company may sound cool, quite honestly I'd go for normal tech support more of the time. The engineers there spend ALL of their time supporting the product, finding potential issues, and cooking it down for consideration of the coders. In every instance I've worked support, thee support from the coders themselves was not all that great until there was a solid idea of exactly what was going on, and that was what escalation engineers did.

Overall:
You need to tell your other security software to not mess around with each other or WSA. Temporarily block the actions of a kernel-level program that you want to be there and you'll end up with many potential messes. Chances are pretty high that most of the security packages you have are not even working properly. I wouldn't even begin to run that much stuff, and running multiple things really should come with an intimate understanding of what works on the Windows side and why and how. The program can say "Critical system area", but it takes a trained human mind to know what that "critical system area" actually means.

 

Techfox1976,

You obviously have more knowledge than me, but please don't deign to state what you seem to imply, that I am seeking Joe's attention.

For your information, it was Joe that contacted me by PM way back in 2008, when Prevx 2 was introduced to Wilders' members for their use and testing. So, I have been there for PrevX/Webroot, by using this software since the first time it was introduced to Wilders' members

Whenever, I post about my experience with a product it is with the intent to assist, and certainly not for it to "sound cool".

Be that as it may, I am sure Joe can let me know privately, by PM if he has any concerns about my approach to using/testing WSA.