09-08-2016 10:12 PM
I ran into this problem today after trying to update bios. Downgrading to 1.82 fixed the problem.
Hope this helps someone else.
02-17-2017 06:37 PM
I have the same problem with my L440.
I can't seem to downgrade the BIOS to 1.82 though:
I get this message:
"BIOS image file does not match this system.
The utility process has not completed."
I know it's the right BIOS because with 1.87, I get this message:
"BIOS image file is same as BIOS ROM.
An update is not necessary at this time."
02-23-2017 10:45 PM
L540. I too have the problem with caddy and "configuration changed" after upgrading the firmware to 1.87 (and no problem before). It took me forever to isolate the problem and find this post.
I can't seem to downgrade the firmware; it says this firmware is not for your system. If someone has experience downgrading, please explain.
09-06-2017 12:48 AM
09-06-2017 12:58 AM
I have exactly the same problem, I am running a dual disk system, I am booting Windows off a 120GB M.2 2242 SSD and I have a 1TB 2.5 drive in the main bay for storage. I upgraded to BIOS 1.87 or the latest one and now the system refuses to boot past the "ThinkPad" startup logo if both disk are in the system. It just gets stuck in a rebooting loop that says "configuration change - restart the system". I need both drives in my unit and I can not understand why upgrading the BIOS has now stopped this from happening. I have tried to rollback and install an earlier BIOS version but It will not allow this... It says that the BIOS is not for my machine, even though it was working fine on the earlier version.
Did anyone find a fix to this? I am so frustrated here, I am never upgrading my BIOS again, it is just not worth the hassle and causes more problems than what it fixes, the way things are going I will be selling my L440 for parts soon.
03-05-2019 08:37 AM
Hello, so I bought an l440 and now I have the same problem, can´t downgrade less than 1.89 and pc is still restarting while the caddy with HGST HDD is inserted, is there any workaround to this issue? Obviously this happend after BIOS update..... and i do not know what version it was before.....