wscsvc32.exe was added to FreeFixer's database on 14th July 2009. The most recent search for this file was done on 14th July 2009. wscsvc32.exe is located in the 'C:\WINDOWS\system32\' folder and has a size of 739840 bytes.
So far there has been 1 search for wscsvc32.exe.
If you have additional information about the file, please share it with the FreeFixer users by posting a comment at the bottom of this page.
The following is the available information on wscsvc32.exe:
| Property | Value |
|---|---|
| Company name | Microsoft Corporation |
| File description | Windows Security Center |
| Internal name | Security Center |
| Original filename | wscsvc.exe |
| File version | 6.00.2900.5512 (xpsp.080413-2105) |
wscsvc32.exe is not signed.
| Property | Value |
|---|---|
| MD5 | eeb16761a01042626352e45f71****** |
| SHA256 | 690b675d9cd895f512ad028e87b4a50bb40bf2f3f56abb05358f8c58d0****** |
To help other users, please let us know what you will do with wscsvc32.exe:
The poll result listed below shows what other users chose to do with wscsvc32.exe:
NOTE: Please do not use this poll as the only source of input to determine what you will do with wscsvc32.exe.
The following graph shows how often wscsvc32.exe has been searched on Google over time:
If you feel that you need more information to determine if your should keep this file or remove it, please read this guide.
Hi, my name is Roger Karlsson. I've been running this website since 2006. I want to let you know about the FreeFixer program. FreeFixer is a freeware tool that analyzes your system and let you manually identify unwanted programs. Once you've identified some malware files, FreeFixer is pretty good at removing them. You can download FreeFixer here. It runs on Windows 2000/XP/2003/20008/Vista/7 RC1. (32-bit only).
If you have questions, feedback on FreeFixer or the freefixer.com website, need help analyzing FreeFixer's scan result or just want to say hello, please contact me. You can find my email address at the contact page.
Please share with the other users what you think about this file. What does this file do? Is it legitimate or something that your computer is better without? Do you know how it was installed on your system? Did you install it yourself or did it come bundled with some other software? Is it running smoothly or do you get some error message? Any information that will help to document this file is welcome. Thank you for your contributions.
I'm reading all new comments so don't hesitate to post a question about the file. If I don't have the answer perhaps another user can help you.
Im going to try to remove wscsvc32.exe with your freeware. I have been plagued lately with this file being infected over and over. Maybe it is a trojan/backdoor. Dont know for sure but I doubt if its abscence could match the problems associated with its prescence here lately. Try to remember to drop you a line when it looks like I have some good info. Thanks for the freebie.
# 9 Sep 2009, 16:40
I just removed it the hard way with the task manager and a lot of patients.... kept throwing pop ups and all sorts of stuff with it, there was also another file associated with it TA86ORTUTTS9.EXE not sure what all it was but its gone off my comp for now and hopefully doesn't come back anytime soon
# 2 Jan 2010, 21:17
sshnas21.dll,
monnid32,
wwwpos32.exe,
aqlb.hjo,
incognito.exe,
rarype32.exe,
netuza32.exe,
9fo3ar0j.exe,
kbdsock.dll,
freddy84.exe,
freddy82.exe,
freddy81.exe,
freddy80.exe,
extrac64_cab.exe,
wmpscfgs .exe,
cliconfg64.exe,
winhlp64.exe,
siszyd32.exe,
sshnas.dll,
IS2010.exe,
smss32.exe,
winlogon32.exe,
helper32.dll,
IS15.exe,
richtx64.exe,
settdebugx.exe,
sr882388.exe,
questservice111.exe,
ccdrive32.exe,
av_md.exe,
essledv.exe,
msa.exe,
algqeh32.exe,
ld16.exe,
freddy79.exe,
photo_id.exe,
winupdate86.exe,
kwanzy131.exe,
wind7upd.exe,
mstre26.exe,
winlogon86.exe,
AVR10.exe,
webserver.exe,
ihaupd32.exe,
wyeke.exe,
wyeke.dll,
AdobeARM.exe,
WLIDSVC.EXE,
ssscheduler.exe,
getPlus_Helper.dll,
wscsvc32.exe,
zavupd32.exe,
herss.exe,
ie3sh.exe,
pp14.exe,
zwangi.exe,
msb.exe
filterpipeline..,
Scott writes