A business like Keysight doesn't get to live long and prosper by accident. They certainly would have a good handle on crisis management - but I wouldn't put this issue quite at that level. Not yet, at least.
As for them taking the correct action, there are still some stages to go before that call can be made - but, certainly, their initial response is what would be expected.
I might go so far as to say that Keysight might actually be happy with the disclosure - especially here - as it provides an objective and open discussion from a relevant cross section of their end-users. Clarity of the issue through informed reports and discussion means the topic is less likely to spiral off into journalistic sensationalism.
From what has been posted already, I see there are at least three other benefits for having members here report on their experiences....
1. The issue is consistent across many units
2. Different models have been identified as having the problem, so a common design element between them is a likely candidate for review.
3. Other models from Keysight have been shown to NOT have the problem - which means that Keysight's multimeter range has been demonstrably shown to have the problem in a limited number of models. So, if you're using one of their meters that is not on the naughty list, you can continue using it with confidence.