Well, it turns out that the drive was copied. In the 2019 Hyper-V server, the drive was offline. Set it to online and all was good.
That was unexpected.

I exported a Windows 2012R2 server from ESX 6.0 to Hyper-V (server 2019). The system boots and everything works but the export did not include the D: drive from the 2012R2 server. The D: drive in VMWare is a separate VMDK file but is stored on the same datastore. For now, I'm manually copying the da...