This is a known issue when orphaned configuration files or broken symbolic links exist.
To get around this you can try deleting the broken symbolic links:
Locate to the path "C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines\" (you need to enable the Show hidden files and folders). Compare each symbolic link (these .xml files are actually symbolic links) with your existing virtual machine, find out which .xml file is orphaned and then delete it. After this, restart the VMMS service.
