UMC Report: Full Technical Investigation on LLT
Published on UMC Blogger Official
Overview
During an active testing session, our team conducted a deep investigation into unexpected behavior observed in Lenovo's WMI GameZone interface and the custom boot logo functionality within the Lenovo Legion Toolkit (LLT). This report summarizes the findings, root causes, and pending action items identified throughout the session.
Background
Testing began with the deployment of test1.ps1 a diagnostic script targeting the root\WMI namespace — specifically the LENOVO_GAMEZONE_DATA class. The script operates in safe mode, meaning it only invokes Get/Is methods that require no [In] parameters, to protect system integrity during automated testing.
Initial output from the script returned minimal results, causing confusion among the team. At this stage, the root cause was not yet identified.
Finding 1 — WMI Method Parameter Requirement
After testing on a 2025 Legion 5 15AKP10 running Windows PowerShell ISE as administrator, it was confirmed that two WMI methods had changed behavior on newer Lenovo hardware:
GetIfSupportOrVersionGet_Lighting_Current_Status
Both methods now require input parameters ([In]) to execute. Because the diagnostic script is designed to skip any method requiring [In] parameters for safety reasons, these methods were silently bypassed — producing output that appeared empty or broken.
This was subsequently confirmed across multiple devices by independent testers, ruling out any device-specific or OS-related cause.
Root Cause: Lenovo quietly changed the WMI GameZone interface on newer hardware models. The script's safe mode design, while intentional, cannot reach these methods without modification.
Required Fix: LLT must be updated to correctly pass the required input parameters when invoking these WMI methods on 2025+ hardware.
Finding 2 — Custom Boot Logo Silently Reverted
A separate issue was discovered during boot logo testing. When a custom boot logo is applied via LLT, the firmware silently reverts to the original Lenovo boot logo upon restart. Testing with a 3200×2000 black image confirmed the custom logo is not applied. Additionally, applying a logo through LLT causes the boot logo option within Lenovo Vantage to disappear entirely, even after reverting to the default image in LLT.
Suspected Cause: Secure Boot enforcement at the firmware level is likely blocking the custom logo from being applied. Third-party tools known to handle boot logo modification typically require Secure Boot to be disabled.
Status: Pending — A controlled test comparing behavior with Secure Boot ON vs OFF has been proposed but not yet completed. The conclusion cannot be confirmed until this test is conducted.
Summary Table
| Finding | Status | Fix Target |
|---|---|---|
WMI methods require [In] parameters | Confirmed | LLT update required |
| Custom boot logo silently reverts | Partially confirmed | Pending Secure Boot ON/OFF test |
Credits
Investigation conducted by the active testing team. Special recognition to BlazeGaming Triage for identifying the WMI root cause, conducting structured hardware testing, and delivering the final report. Additional confirmation provided by Brick and Aretzera.
This report was compiled from the #active-testing session log and reflects findings as of the final report timestamp (20:29).
Note: This is based on AI-generated writing assistance from the Claude Sonnet 4.6 used for writing.
Comments
Post a Comment