PDA

View Full Version : Registry Legacy entry


lws
January 24th, 2011, 03:41 PM
Would anyone know what this Legacy entry is related to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_MPKSL3194D331
In System,System Properties,Device Manager,hidden devices, "Mpksl" with different added numbers ie. "Mpkslb521fec5" and so on keeps replicating itself with different added numbers. I keep deleting them but they keep returning. Never had this problem before. I am in XP Pro SP3 and any information would be appreciated. P.S. I did a google search on the above and got no results.

Bubba
January 24th, 2011, 04:03 PM
A MS Security Essentials service :-\

Multiple files starting with MpKsl keep trying to run at startup - part of MSE?

-{ Quote: "The MpKsl... file is a "service" which changes with each definition update. This is something new which started with the engine update (1.97.xxx.0) last week. With each update from now on, the old MpKsl... service is deleted and a new MpKsl... service is started.

This probably is done to defeat new forms of malware. My current file is located here:

C:\Documents and Settings\All Users\Application Data\Microsoft\Microsoft Antimalware\Definition Updates\{C5946A27-1913-47D3-B5CF-C4EEE4C366AB}\MpKsl8497ee63.sys" }-

lws
January 24th, 2011, 04:30 PM
-{ Quote: "A MS Security Essentials service :-\

Multiple files starting with MpKsl keep trying to run at startup - part of MSE?" }-

Many thanks. Yep, I checked C:\Documents and Settings\All Users\Application Data\Microsoft\Microsoft Antimalware\Definition Updates\{F5007136-30E0-4ADC-BA1F-28BED0EED15E} and Mmksl file is there. As I said, I never seen it before and was wondering what the hell it was. Thanks again.

Gemini IDF
April 2nd, 2011, 06:59 AM
Thanks also from me for that Bubba. I had been getting piles of these 'Legacy' files mounting up in my Registry, flagged as 'Invalid Services' by my Registry Cleaner. Now I know they're undeleted MSE updates entries, I can rest easy.
I too, had done a Google search with no joy, except that I was worried by a suggestion that they were the result of a trojan! :argh:
Thanks again.