The customer had built a new UEFI based vdisk and deployed it to production. The customer subsequently observed that the PVS Servers were recording a clearly inaccurate boot time,  of millions of minutes, in Windows Event logs when target devices were booting.

Example inaccurate boot time logged in events:
PVS Server Event logs -> Application Event logs ->Source StreamPrcocess

Device <target device name> boot time: 28961418 minutes 16 seconds.

The customer recreated their BDM boot ISO files using their updated PVS servers.

Once PVS UEFI target devices booted using the recreated BDM media, the PVS Server event logs showed expected boot times for target devices in that customer environment.

Example accurate boot time logged in events:
PVS Server Event logs -> Application Event logs ->Source StreamPrcocess

Device <target device name> boot time: 0 minutes 41 seconds.

Problem Cause

This issue of recording inaccurate boot times of UEFI based PVS targets was identified and resolved by Citrix PVS engineering team, and included in PVS UEFI bootstraps for 1912 CU6 and all subsequent PVS releases.

If using PXE boot and PVS server tftp for booting, the PVS server upgrade would have already upgraded the bootstrap file, and so no action would have been required.

However if using BDM boot, additional action is required to recreate the BDM boot ISO, or to update the BDM boot disks.

The customer in this case had created their BDM boot media using a much earlier version of PVS several years beforehand. The relevant PVS component is the bootstrap, and so to avail of this fix required the customer to recreate their BDM boot media with the latest PVS server release.