Being able to roll back a change is an important safety item. I don’t have multiple identical Framework laptops, so I can’t test on one laptop first. If I update the BIOS and I discover a new problem, then what do I do? I won’t even know for sure if the problem is due to the BIOS update without being able to test the rollback.
From what I read here, blocking rollback is intended to increase security. Ironically, this is having the opposite effect for me: I am seeing that there is a BIOS update which supposedly fixes a security problem, but I hesitate to install the update for fear of causing a problem I will be unable to remedy.
I don’t see why we can’t have the best of both worlds. What about two update packages, one that locks and one that doesn’t? Then users can choose the one that is most suitable.