Intelr management and security application local management service

Success! Subscription added.

Success! Subscription removed.

Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your profile.

2910 Discussions

Intel Local Management service high CPU usage windows 2012 r2

‎06-27-2017 06:21 AM 38,187 Views

High CPU usage on the process Intel Local Management service on start-up. If we stop it. the server is fine. Checked for Threats with Malwarebytes and ESET, but none. AMT is uninstalled. on the properties of the process it refers to windows\Vss\writers\ but i cant find any files in there.

Strangely nothing is on the startup as well, so i'm really concerned where is it coming from. My guess for now is a left over app. service.

Preview file ‎06-29-2017 04:05 PM 30,860 Views

Please look in services and find. Stop the service and set it to "disabled" Intel Management and Security Application Local Management Service. Open an Admin command prompt and type the following:

This should remove from your system.

‎08-09-2017 11:04 AM 30,860 Views

I had the same problem on a new Dell XPS 13 (9360 Kaby Lake) laptop: the fan would run for extended periods and the chassis would get very warm, for no apparent reason.

I'm very angry over the hours I spent trying to find the cause. First off, Dell knows nothing - they just rely on installing "the latest Intel BIOS and drivers". Which I did, repeatedly, through 7 Aug 2017. And from web reports it seems that this LMS junkware has been causing the same problem for about ten years.

How is it possible for a company the size of Intel to still be sending this out? After a discovery period while I was realizing that a problem even existed, I found HWInfo showing both CPU cores at 90 degC . How many users are simply living with this absurd condition in their new high-end "Intel Inside" laptop? 90 deg C!! Ten years! Again - just incredible. You guys are the experts! You made all these chips!

In fact in my case the machine was about to go off as a gift. So if I hadn't realized and fixed the problem - late on the last possible night - the user would certainly have assumed it was normal, and I wouldn't have seen it again. Very, very angry.

As for the fix: I got into the Services list (with Admin privilege) and located "Intel Management and Security Application - Local Management Service". Opening its properties I stopped it and set its startup type to "Disabled". I should have, but did not, also delete LMS.exe.

I'll see if the problem reoccurs, as it has for some other folks. That means have the machine brought back and check it out myself, with apologies to the new owner. Terrible piece of work, Intel driver team.