Host env WAS: Win10 Pro x64 current with Windows Update, vintage 2010 Intel Core i7 Lynnfield hardware, being retired
Host env NOW: Win10 Pro x64 current with Windows Update, Skull Canyon NUC, replacement machine
VMs: 3 VMs, 3 VHDs, two differenced from the third. Each VM was exported, from the powered off virtual state, about two months ago.
Problem: tried to import the VMs and get error "encountered an error while loading the virtual machine configuration... Import failed. Import task failed to copy file." Got error for each of the VMs when I tried to import it. Event viewer is not much more insightful:
"The description for Event ID 18440 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
%%2147943712
0x80070520
\\HOMESERV\Dick\DIY migration\XPSP3 Pro (diff from this)\Virtual Machines\AB33AB3E-0BC7-4D7B-A5B8-0B371F7A5DCF.VMRS
C:\ProgramData\Microsoft\Windows\Hyper-V\Planned Virtual Machines\AB33AB3E-0BC7-4D7B-A5B8-0B371F7A5DCF.VMRS
The locale specific resource for the desired message is not present"
I also saw some previous threads, via the Google, suggesting that I should create new VMs and "add the VHDs later" but there was no hint how one adds VHDs later or copies VHDs--with differencing chains involved--from one machine, or an exported VM, to another.
I must be missing something fundamental that I'm too ignorant to understand. Any helpful advice on how to migrate the VMs from the retiring machine to the new one would be greatly appreciated! Surely this is possible?