08-27-2018 01:49 AM - edited 08-27-2018 01:51 AM
My organization have been facing this issue when System Update throws "FwUpdateCmd has stopped working". Luckily for us, we can just click "Close" and the Windows 10 is still operational without crashing. Why is this happening? What is the probable cause of this issue? I may not be able to go around collecting system logs of every affected user due to confidentiality and risk of disrupting their work. I will try to replicate this issue with one of the unpatched spare ThinkPads. We see X1 Carbon 5th Gen getting this.
Solved! Go to Solution.
08-29-2018 07:34 AM
Forget Lenovo. Their complacency will cause them to lose bulk tender PO in the future. I will see to it from my side.
Back to the error message. Now, my team have tested that it happens on almost all the new models with USB-C port. Some cases, the error goes away if System Update managed to download and patch up the hardware BIOS or some kind of firmware. Otherwise, the patching will fail and this error will keep coming out whenever System Update runs.
FwUpdateCmd seems to be failing when trying to scan for the motherboard for BIOS and firmware version.
The workaround? Reboot into system BIOS and take note of the BIOS and Intel ME Firmware version number. Go to your notebook model's driver download page. Find the BIOS updates and then Firmware ones. If the version number is higher on the web page, download them manually and apply the patch. Restart machine and run System Update again. The error should not appear again.
08-29-2018 09:57 AM
I'm looking into this problem, but so far, I haven't been able to reproduce it here. FwUpdateCmd is part of the Thunderbolt Firmware Update package. You mentioned this problem went away after updating BIOS and ME Firmware, but can you tell me what previous versions of BIOS and ME Firmware caused this problem to happen?
08-29-2018 01:40 PM - edited 08-29-2018 01:43 PM
I am not saying this is your problem; yours may be different. Mine was generating faulting errors for FWUpdateCmd in reliability monitor when I ran system update through vantage. BUT for me I had disabled Thunderbolt in BIOS under I/O port access. Once I enabled it my error went away.
If a post answers your question, please mark it as an”Accepted Solution“!
If a post helps you, please click the star to give it a "Kudo"!
I do not work for, nor do I speak for Lenovo. I will not respond to unsolicited private messages. Questions belong in the forum so it may help other forum members as well.
T490, TP 25 Retro, X1 Yoga 3rd Gen, W510 850 EVO, A30p
Retired 385D, A20p, A21p
08-29-2018 09:41 PM
09-03-2018 12:06 AM
I found the fix. At least for my organization's cases.
Check this Local Group Policy @ Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > "User Account Control: Detect application installations and prompt for elevation"
It should be set to "Enabled". It was previously "Disabled" for our deployed image.