- #LENOVO INTEL MANAGEMENT ENGINE DRIVER WINDOWS 10 INSTALL#
- #LENOVO INTEL MANAGEMENT ENGINE DRIVER WINDOWS 10 64 BIT#
- #LENOVO INTEL MANAGEMENT ENGINE DRIVER WINDOWS 10 DRIVERS#
- #LENOVO INTEL MANAGEMENT ENGINE DRIVER WINDOWS 10 WINDOWS 10#
#LENOVO INTEL MANAGEMENT ENGINE DRIVER WINDOWS 10 64 BIT#
First, the MEUpdate.cmd references a 64 Bit Executable. And since applying a bad “fix” to AMT might very, very well result in a completely unusable system… I hope you could clarify & detail a bit more. But I don’t dare applying your fix because there are so many unclear points.
#LENOVO INTEL MANAGEMENT ENGINE DRIVER WINDOWS 10 DRIVERS#
Is anything else from the directory DRIVERS needed? As I see it, you seem to be just tossing everything away from the two downloads and only use the extracted HECI_REL. This question is connected to the question if I need the directory DRIVERS with it’s two entries at all. Instead, it creates a directory WIN in which somewhere deeper HECI_REL is available. The overlay parameter you are using with mkwinpeimg does not generate a HECI_REL directory in the root of the booted windows. Especially, I findt it important to state that the files from the BIOS directory are required (not the efi* ones). My operation system is Ubuntu 16.04 and I think you should take more extensive note about this issue. Is Directory DRIVERS/ME needed? If not, why do I have to download the second driver (which generates ME)?Īs others pointed out, I, too, had to copy all files from /usr/lib/syslinux/modules/bios to /usr/lib/syslinux in order to not to run into that “missing chain.c32” error.
if only HECI_REL is needed (which is in DRIVERS/AMT). Then, I don’t understand why I should download both drivers from Lenovo and extract them etc. First, what do you mean with “Save off HECI_REL folder” (Step 6)? Save off – to where? And what does “Save off” mean anyway? Reboot, go back into BIOS and change your settings back to how you started.īut some things are unclear.In the command prompt of the booted WinPE environment, run the following to start the update:.Reboot, go into BIOS and turn Secure Boot OFF, Legacy BIOS ON, and AMT ON.Mkwinpeimg -W /path/to/mounted/windows10-32bit-installer/ -O winpe_overlay disk.img
#LENOVO INTEL MANAGEMENT ENGINE DRIVER WINDOWS 10 WINDOWS 10#
Use mkwinpeimg to create the boot disk, pointing it to the mounted Windows 10 installer and the “winpe_overlay”:.“winpe_overlay” (or copy from the Windows box you extracted things on) Copy ~/.wine/drive_c/DRIVERS to a new folder, e.g.
This probably isn’t needed if you’re installing from packages, but may be requried if you’re on, say, Fedora.
#LENOVO INTEL MANAGEMENT ENGINE DRIVER WINDOWS 10 INSTALL#
If you don’t have the path /usr/lib/syslinux/modules/bios on your system but you do have /usr/share/syslinux/modules/bios – you will need to change a bit of the file programs/mkwinpeimg.in to point to the /usr/share locations rather than /usr/lib before you install wimlib. Go and install – we’re going to use it to create the boot disk.Save off HECI_REL folder, it’s the only extracted thing you’ll need.You can do this in ~/.wine/drive_c/DRIVERS/WIN/AMT, with “cabextract SetupME.exe” or (as suggested in the comments) you can use the innoextract utility (from linux) to extract them (a quick check shows this to work) you now need to extract the management engine drivers.Run both exe files with WINE or on a windows box to extract the archives, you do not need to run the installers at the end.Go to Lenovo web site for Drivers & Software for your laptop, under Chipset, there’s ME Firmware and Software downloads You will need both.by right clicking and choosing to mount, or by doing ‘sudo mount -o loop,ro file.iso /mnt’ Mount the ISO as a loopback device (e.g.A shell prompt shouldn’t scare you too hard. WINE or a Windows box to run two executables (because self extracting archives are a thing on Windows apparently).These instructions are pretty strongly inspired by This is how I updated my Intel ME firmware on my Lenovo X1 Carbon Gen 4 (reports say this also has worked for Gen5 machines).
0 kommentar(er)
