VM time ahead by 5 hours

[acebmxer]

As title says VM time is ahead by 5 hours. I checked the host time via idrac (dell server) time is correct their. Via idrac I access the virtual console and verify xcp-ng host is using default ntp server info.

Other host at same location is esxi host and the vms on that host have the correct including the Windows Domain controller.

On the vm with incorrect time I see " Last successful time synchronization is 2/1/26 8:15:34 am( was correct 15 min ago) Time server local CMOS Clock. Time zone is set correctly.

Edit also note - VM was migrated from ESXI Windows 10 bios boot. Formigration i choose Windows 11 template.

When booting the vm I get this error:
Manually deleting the VTPM does not help. VM still boots but gives error.

vm.start
{
  "id": "146c5089-1e37-d3b4-83a3-8ba53a0ee2e6",
  "bypassMacAddressesCheck": false,
  "force": false
}
{
  "code": "NOT_IMPLEMENTED",
  "params": [
    "Booting BIOS VM with VTPMs attached"
  ],
  "call": {
    "duration": 3868,
    "method": "VM.start",
    "params": [
      "* session id *",
      "OpaqueRef:6373a25c-a4f8-9c57-f487-23d851a3a35e",
      false,
      false
    ]
  },
  "message": "NOT_IMPLEMENTED(Booting BIOS VM with VTPMs attached)",
  "name": "XapiError",
  "stack": "XapiError: NOT_IMPLEMENTED(Booting BIOS VM with VTPMs attached)
    at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202601291557/packages/xen-api/_XapiError.mjs:16:12)
    at file:///opt/xo/xo-builds/xen-orchestra-202601291557/packages/xen-api/transports/json-rpc.mjs:38:21
    at runNextTicks (node:internal/process/task_queues:64:5)
    at processImmediate (node:internal/timers:472:9)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}

While shutding down the vm to add this note about VTPM, when vm booted back up time is now correct. Noted VM was rebooted and shutdown a few times from initial boot and for vm tools install.
Time is now synced with the domain controller.
Thoughts?