I'm using a Lenovo Ideapad Gaming 3i (i5-10300H, HM470, ME v.14).
Through UEFI advanced settings, I could find the “ME State” toggle, which puts the ME into the “temporarily disabled” mode.
While the laptop boots and I think everything is working, there's a single flaw: the laptop does not turn off. I can shutdown the OS and the screen turns off, but the fans keep going, the keyboard backlight does not turn off. I have to long-press the power button to manually turn it off.
So, I have some questions for you:
What's the practical difference between using me_cleaner to set the AltMeDisable bit vs. using the ME State toggle?
Perhaps there's an ACPI or other UEFI setup thing to fix the issue with the machine not turning off?
If I used me_cleaner, would I have the same issue I described?
Thanks in advance!
EDIT: It seems this has been somewhat discussed here. The consensus seems to be that “Temporarily Disabled” is not a definite solution, causing issues like the one I experienced.
That being said, I am not sure if me_cleaner has been successfully used in Comet Lake. My UEFI/BIOS is already unlocked and can be flashed through FPTW64.
Hi everyone!
I'm using a Lenovo Ideapad Gaming 3i (i5-10300H, HM470, ME v.14).
Through UEFI advanced settings, I could find the “ME State” toggle, which puts the ME into the “temporarily disabled” mode.
While the laptop boots and I think everything is working, there's a single flaw: the laptop does not turn off. I can shutdown the OS and the screen turns off, but the fans keep going, the keyboard backlight does not turn off. I have to long-press the power button to manually turn it off.
So, I have some questions for you:
Thanks in advance!
EDIT: It seems this has been somewhat discussed here. The consensus seems to be that “Temporarily Disabled” is not a definite solution, causing issues like the one I experienced.
That being said, I am not sure if me_cleaner has been successfully used in Comet Lake. My UEFI/BIOS is already unlocked and can be flashed through FPTW64.