@hlo58 Unfortunately I don't remember which version caused this particular behavior nor to which version the customer updated their ESXi's to solve the issue. The latest 6.7 U3 release however should be fine. (Which might be recommended due to security fixes anyway)