Kb.vmware/s/article/78708 Link

If a VM ran for 337 days continuously without a reboot or vMotion migration to a fresh host, the internal counter would overflow. The VM would instantly fail.

The issue stems from a compatibility problem between the ESXi UEFI boot loader and certain UEFI firmware implementations. When ESXi attempts to "shut down" runtime firmware services (a normal step before taking full control of hardware), the firmware does not respond correctly or enters an invalid state. This is often triggered by: kb.vmware/s/article/78708

This KB highlights a classic computer science problem: If a VM ran for 337 days continuously

If you have "Set it and forget it" appliances (domain controllers, backup servers, legacy Linux boxes) that pride themselves on years of uptime, check them against this KB. That high uptime counter might actually be a ticking time bomb. When ESXi attempts to "shut down" runtime firmware