My Windows 11 has some really weird behaviour recently.
Initially I didn't think about this is LLT issue, but after I identified how to workaround the issue, I believe it is LLT problem.
My environment:
Legion 7 connected to a docking station via TB4 port, all external devices are connected to the TB4 docking station, including monitors, keyboards etc.
If I unplug the TB4 cable when on Quiet mode, once plug back in, my Windows will become extremely slow, and sometimes LLT will crash.
During the extremely slow period, a simple workaround is to switch to other mode, like balance or performance, the computer will immediately back to normal.
How to reproduce the bug?
Set power mode to "Quiet"
Use the computer for a while
Unplug TB4 cable
Wait a few seconds or minutes
Plug TB4 port back
What is the behavior that you expected?
Windows start perform extremely slow: mouse is lagging, starting a program is slow, everything is so slow
Version
2.12 Beta3
OS
Windows 11 22H2 22621.1413
Device
Legion 7 16IAX7 - Type 82TD
BIOS version
Legion 7 16IAX7 - Type 82TD
What's wrong?
My Windows 11 has some really weird behaviour recently. Initially I didn't think about this is LLT issue, but after I identified how to workaround the issue, I believe it is LLT problem. My environment: Legion 7 connected to a docking station via TB4 port, all external devices are connected to the TB4 docking station, including monitors, keyboards etc.
If I unplug the TB4 cable when on Quiet mode, once plug back in, my Windows will become extremely slow, and sometimes LLT will crash. During the extremely slow period, a simple workaround is to switch to other mode, like balance or performance, the computer will immediately back to normal.
How to reproduce the bug?
What is the behavior that you expected?
Windows start perform extremely slow: mouse is lagging, starting a program is slow, everything is so slow
Logs
log_2023_03_28_02_44_50.txt
Do you have Lenovo software installed?
Did you disable any Lenovo software using Lenovo Legion Toolkit?
Additional information
The issue was not there back to 2.11