Scanning directories on a VHD return different results when mounting the VHD file and using the OS filesystem

I created a virtual HD using Windows 7 Pro, SP1. I then applied a Windows 7 Pro (Gold) image from a WIM file to this VHD. Mounting both the WIM and VHD files and then scanning the directory structures results in identical results.
Examining the directory structure of the WIM file using DiscUtils also results in similar results (there is a dir which the OS file system returns an access denied exception and the DiscUtils virtual WIM doesn't). Examining the directory structure of
the VHD file using DiscUtils results in a radically different result. There are multiple directories which the DiscUtils.Vhd does not see which the OS filesystem as well as the DiscUtils.Wim do.

Please let me know what other information I can provide to help demonstrate this.

I've tried to reproduce this, but don't see any real problems, comparing the output of DIR with the output of enumerating the folders using DiscUtils. The folder '\Users\All Users' doesn't enumerate in DiscUtils, but this is because there's no support
for SYMLINK / SYMLINKD reparse points in DiscUtils. Can you provide more details on which folders are missing?

1) the .VHD was created by Windows 7 and originally mounted via the management snap-in.
2) the .VHD was "populated" by applying a .WIM image to it.
3) the dir and file counts from the mounted .VHD agree with the dir and file counts from the .WIM file
4) information gathered using DiscUtils WIM file support agrees with informatio gathered from a mounted .WIM file.