Hello, I can confirm this same issue. My machine is also the Thinkbook 13s G3 ITL (20V9004EUS) which is about 6 months old. Prior to the failed firmware update, the system was very stable with no unexpected issues. The attempted firmware update was about 1 week ago. Ever since, the secondary (right side) fan will frequently spin up to full speed. Meanwhile the primary (left side) fan will completely deactivate. Observing the system temperatures, nothing looks out of the ordinary with CPU Core/Package temperatures all in the 45-60C range. This behavior did not exhibit prior to the failed update. Previously, both fans would always run in tandem.
Unfortunately, I do not have version information from before the update. Here's what has been done so far:
- Checking BIOS following the failed update: BIOS Version F9CN42WW
- Checking for updates through Lenovo Vantage: No updates available, system up to date.
- Checking Lenovo Support Website for available updates: BIOS Version F9CN46WW, Intel ME 15.0.35.1898 available
I manually updated to the latest versions for both firmware files, and both installations were successful; however, the fans will still intermittently go into the "lopsided" state. I can't seem to find a way to reliably trigger the issue, but the only way it will occasionally resolve is if I either re-run the bios update utility for F9CN46WW, or do a hard shutdown by holding the power button for 10-15 seconds.
The only correlation time the computer seems to consistently enter the "lopsided fan" state is when I walk away long enough for the laptop to turn off the screen or enter sleep mode. I can typically hear the single fan turn on to full speed from the other room, and it will stay that way until I take one of the above actions.
The failed update must have also triggered a TPM clear, because I was required to enter the Bitlocker drive recovery key prior to booting after the failed update.
Any details for trying to resolve this would be much appreciated. Let me know if you need more information.
Edit: I do also see the following in my windows update history, which may correspond to the problematic firmware:
