Well, gee isn't that spiffy? There are two things I don't like about this picture. One, what is "Windows Mobile 2003-based device connectivity" exactly? Two, why can't I just end pid 2812 directly from this screen? Are Exit, Ignore, Retry really the only options a person has?

Once more I'm thrust upon the hours of dilemma, should I just use the Windows Task Manager to find out about this process or should I bring out the big guns from the get go and use Sysinternals' PsKill?

"PsKill is a kill utility that not only does what the Resource Kit's version does, but can also kill processes on remote systems."

Ah, makes you nervous doesn't it? I bet someone is checking their firewall status right now. ;)

Let's see how Windows Task Manager fairs. Well I browse through my running processes and I don't see anything that could be 2812. Hmm, I'm running on Windows Vista and I do have a services tab on my Windows Task Manager. Let's check here next...

There it is! A quick internet search and we find out what WcesComm and RapiMgr is.

wcescomm.exe is not a Windows system file. The process listens for or sends data on open ports to LAN or Internet. The process starts when Windows starts (see Registry key: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run). The program is not visible. Therefore the technical security rating is 44% dangerous.

The program is not visible. File rapimgr.exe is not a Windows system file. The application listens for or sends data on open ports to LAN or Internet. The program can be removed using the control panel Add\Remove programs applet. Therefore the technical security rating is 43% dangerous.

ActiveSync reincarnated! Vista! Say it ain't so! See combined ActiveSync is at least 87% dangerous. I bet when it is all said and done, ActiveSync is 17437% dangerous.

Oh well, we stop the services and try again.

Success!