- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Agree with wila there are multiple problems here. The best thing is to re-create the VMDK descriptor. So if an old backup that is the unencrypted VMDK descriptor of the virtual disk, you can use that; otherwise will need manual recreation. Then go back to the state of before the vTPM (can re-create the vmx from the test.zip).
Additional problems I see aside from what already mentioned, the test.zip shows log using version 16.1.2 and virtual HW version 12 while the other log shows version1 16.2. There are no vTPM entries (vtpm.present, the vTPM endorsement keys) and no firmware = "efi" in the test.zip file.
2021-10-23T03:16:28.949+09:00| vmx| I005: Log for VMware Player pid=6276 version=16.1.2 build=build-17966106 option=Release
2021-10-23T03:16:29.284+09:00| vmx| I005: DICT virtualHW.version = "12"
2021-10-23T03:16:29.926+09:00| vmx| I005: DISKLIB-DSCPTR: Opened [0]: "Windows 10 x64.vmdk" (0xa)
2021-10-23T03:16:29.927+09:00| vmx| I005: DISKLIB-LINK : Opened 'R:\Virtual Machine\Windows 10 x64\Windows 10 x64.vmdk' (0xa): monolithicSparse, 125829120 sectors / 60 GB.
2021-10-23T03:16:29.927+09:00| vmx| I005: DISKLIB-LIB : Opened "R:\Virtual Machine\Windows 10 x64\Windows 10 x64.vmdk" (flags 0xa, type monolithicSparse).
2021-10-23T03:16:29.927+09:00| vmx| I005: DISKLIB-LIB_MISC : DiskLib_GetStorageBlockSizes: Failed to get storage block sizes, The virtual disk requires a feature not supported by this program.
2021-10-23T03:16:29.927+09:00| vmx| I005: DiskGetGeometry: Reading of disk partition table
2021-10-23T03:16:29.934+09:00| vmx| I005: DISK: Disk 'R:\Virtual Machine\Windows 10 x64\Windows 10 x64.vmdk' has UUID '60 00 c2 95 93 b4 9c 6e-d4 6e 9c 28 00 1f 84 1a'
2021-10-23T03:16:29.934+09:00| vmx| I005: DISK: OPEN 'R:\Virtual Machine\Windows 10 x64\Windows 10 x64.vmdk' Geo (7832/255/63) BIOS Geo (7832/255/63)
2021-10-23T03:16:29.940+09:00| vmx| I005: DISKUTILWIN32: DiskUtilW32IsATASSDDevice: Failed to send ATA IDENTIFY command to the target device.
2021-10-23T03:16:29.941+09:00| vmx| I005: DISKUTILWIN32: DiskUtilW32IsScsiSSDDevice: Reported rotation rate = 1
For vTPM to work, the firmware needs to be UEFI (firmware="efi" needs to be there). But before adding that line the guest OS will need to convert from MBR to GPT first. That should be done using the MBR2GPT tool.
https://docs.microsoft.com/en-us/windows/deployment/mbr-to-gpt
To enable secure boot for Windows 11,
uefi.secureBoot.enabled = "TRUE"
also needs to be in the vmx file.
Anyway, get the VMDK descriptor back to its original state.