Hi,
It seems the virtual disk is corrupted. Please click Inspect Disk in the Actions pane of the Hyper-V Manager and select the last avhdx file, then click Inspect Parent to identify the order of the differencing disks. Since the chain is already corrupted, you may have to guess the order based on file size, last modified time, etc. After that you can try merging the differencing disks manually and see if the VM can start with the merged disk. Refer to the below link for the detailed steps of merging the virtual disk files. Please remember to back up your virtual disk files before any operation.
Best Regards,
Ian Xue
-----------------------------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.