Lesson Learned.  Today I expanded a vhd file for a image that had snapshots.  When I tried to start the image I received the error noted in the title of this post.  Fortunately I found information that recommended downloading and running the vhdtool in repair mode.  referenced from Technet.

http://downloads.integent-com-staging.xbjfxmg0-liquidwebsites.com/vhdtool.zip

I ran the tool on the VHD and AVHD pair and here was the output:

C:Virtual Machines 2Test Machines>vhdtool /repair FOO.vhd FOO_1CE6964B-29B6-4D37-97AA-E847195217F3.avhd
Status: Resizing base VHD "FOO.vhd" to match the size indicated in child VHD "FOO_1CE6964B-29B6-4D37-97AA-E847195217F3.avhd".
Status: Attempting to open file "FOO.vhd"
Status: File opened, current size is 6144
Status: Attempting to open file "FOO_1CE6964B-29B6-4D37-97AA-E847195217F3.avhd"
Status: File opened, current size is 70144
Status: Opened "FOO.vhd" as base VHD file, type is dynamic-sized.
Status: Base VHD’s identifier is "d3300579-5c82-4422-8697-5bf970b3534c"
Status: Opened "FOO_1CE6964B-29B6-4D37-97AA-E847195217F3.avhd" as child VHD file.
Status: Child VHD’s parent identifier is "d3300579-5c82-4422-8697-5bf970b3534c"
Status: Resizing base VHD to match child size of 1073741824 bytes
Status: VHD footer generated
Status: VHD footer written to file.
Status: VHD footer written to file.
Status: Operation complete.
Status: Complete

 

technet reference