Quantcast
Channel: Intel Communities: Message List - Intel® vPro™ Platform
Viewing all articles
Browse latest Browse all 1770

Re: microLMS running after FW Patching to fix SA-00075

$
0
0

Michael,

 

Thank you so much! I have got it Patched now, thanks to your input. Just for reference, -if anyone ever manages to mess this thing up to the extent I did,

Here are the steps I had to take:

 

1: Started SoftPaq (HP drivers and updates suite) and ignored its claims regarding what was downloaded and what was installed.

I then Found the MEI drivers "Intel Management Engine Interface (MEI) Driver" (SoftPaq 57380) and installed them

- This Driver reinstalled and started LMS, UNS and ME services / drivers to my OS, and I let them all have full access to whatever Network connections they wanted

 

This is a screen capture of the SoftPaq window:

vuln_ME4.png

 

2: Tried to install the HP SoftPaq SP80195 again, but it failed like before. It just flashed a CMD-prompt and exited without any info given, other than the

OS.log file located in the SP80195 extraction directory is updated with current date.

 

3: Rebooted, and entered MEBx BIOS. MEBx page still said: "Intel (r) Management Engine BIOS Extension v8.0.0.0069 / Intel (r) ME v8.1.3.1350", so Patch not applied.

 

4: Exited MEBx BIOS page and booted to Windows

 

5: After Boot, I ran the Intel-SA-00075-GUI.exe, and it showed this:

vuln_ME.png

I found it strange LMS was not running, and went into Start > Control Panel > Administrative Tools > Services, and double checked the service was indeed running,

and ran the Discovery Tool again:

vuln_ME1.png

I guess the Service just needed a bit more time to start than I had given it...

 

6: Started HP SoftPaq and selected the sp80195 from the "This Computer > Downloaded SoftPaqs" window. I right-clicked it and selected

"Unpack to directory" and renamed the default directory (sp80195) to "sp80195a":

vuln_ME5.png

 

7: I then navigated to the new "sp80195a" directory, and double-clicked the "CallInst.exe", and that _finally_ seemed to unpack, install and Patch

my Firmware (The CMD-prompt did not just flash and fail, but ran a full install that took a minute or so...):

vuln_ME2.png

8: I rebooted, and ran the Discovery Tool again, and there it was:

vuln_ME3.png

 

Finishing off

I guess my last steps will be to decide If I am going to let all the ME-services and components keep running on my system or if I will disable

everything again. It is tempting to Provision my system and play around with this to see if I find it useful to be able to access my system remotely,

but my system is only managed by me and its use will be solely CAD / CAM and 2D design and I cant actually imagine a scenario where I would

benefit from having this running in the background.

 

- - - -

 

Just out of curiosity, I ran a fresh PassMark on my system to see if there was any noticeable effects of having the services running:

 

Before ME Patch:

passmark_hp8770wbeforeME.png

After ME Patch:

passmark_hp8770wAfterMEacti.png

I dont think those differences has anything to do with this Patch, and it will not be noticeable that the LMS, UNS, ME services are running...

 

And My HWINFO64-info now looks like this:

hwinfo001.png

hwinfo002.png

hwinfo003.png

 

And a new drop-down is present after Update and Patch showing "Intel ME" as a separate listing:

hwinfo004.png

 

So. Thank you again Michael!

All in all, it looks like what was needed was for me to understand that I had to install the MEI-drivers and let all services (LMS, UNS, ME)

be running before I could Patch. I know I could have just said "thank you Michael, -it worked" and left this post at that, but just in case anyone

else tries to solve similar problems, I do all those screendumps and flood this topic with info

 

- Guess this entire post should be renamed "How to unmess ME and apply SA00075-Patch after having followed too many Mitigation guides

online without understanding what one is doing"...

 

Claus


Viewing all articles
Browse latest Browse all 1770

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>