No. The details are supposed to be there. What I actually get is...
PS C:\Windows\system32> compare-vm -Name GuestVM -DestinationHost DestHost -IncludeStorage -DestinationStoragePath \\NASShare\hyper_v
VM : Microsoft.HyperV.PowerShell.VirtualMachine
OperationType : MoveVirtualMachineAndStorage
Destination : DestHost
Path :
SnapshotPath :
VhdDestinationPath :
VhdSourcePath :
Incompatibilities : {21024}
PS C:\Windows\system32> move-vm -Name GuestVM -DestinationHost DestHost -IncludeStorage -DestinationStoragePath \\NASShare\hyper_v
move-vm : Virtual machine migration operation for 'ust00eovscsm11' failed at migration destination 'DestHost'.
(Virtual machine ID 78DBC993-F4C8-4CBB-B098-15730BEA00D5)
The virtual machine 'GuestVM' is not compatible with physical computer 'DestHost'. (Virtual machine ID
78DBC993-F4C8-4CBB-B098-15730BEA00D5)
Could not find Ethernet switch 'Virtual Switch 106'.
Memory reservation below minimum.
The operation cannot be performed because the object is not in a valid state.
At line:1 char:1
+ move-vm -Name GuestVM-DestinationHost DestHost -IncludeStorage -Dest ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (Microsoft.Hyper...VMMigrationTask:VMMigrationTask) [Move-VM], Virtual
izationOperationFailedException
+ FullyQualifiedErrorId : InvalidObjectState,Microsoft.HyperV.PowerShell.Commands.MoveVMCommand
As I'm sure you can see, I have one generic incompatibility when I run the compare. When I do the move, it shows that the minimum memory is too low and that the switch doesn't exist on the destination. Why aren't these in the compatibility report?