Hello,
If I'm not mistaken, you asked the same question a few months ago, I only told you that this type of behavior has already happened to me on several occasions, and it's a topic that has been discussed several times in this forum and elsewhere often without finding a precise answer to explain the circumstance.
There are those who have solved the problem by making sure they have the most recent firmware versions and/or have used the "custom" images released by the manufacturer at the time of installation because they include the correct set of drivers for the systems in use. But then we also turn to the manufacturer of both the systems and the software because the problem may already be known and/or there may be a solution to it.
Then perhaps it would also be the case to know whether before this very recent update the problem persisted or not.
Regards,
Ferdinando