I have discovered a bug, I do NOT consider as a feature, with Windows Vista and above issue for the H-Ext to detect the Halo installation is writable to the current user. With Virtualization enforced due to no manifest embedded in Halo application, it kept thinking the Halo installation within the Program Files directory, Program Files (x86) for 64 bit, is writable when it's not. I do not have a workaround this issue nor have ability to fix it without directly editing the Windows OS or the Halo application itself. I have post news about it.
>>> Windows Vista and Above Issue with Legacy App Virtualization <<<
Will Sawnose, aka Roger, fix this in future release? Please? I personally preferred to keep the Halo applications code signed to show the Halo users that it is valid executable and not modified version...
If you are concerned about corrupted maps, Halo will display a message of "___.map" is not compatible or is corrupted. You can remove specific map from the maps folder inside the Halo's directory. Besides, any of your game saves are saved in your document folder where it should be at anyway.
I have made the comparison of pros and cons about the AppData for "VirtualStore" directory being used, 87% of it are cons. So, I am completely against the Virtualization starting from Windows Vista and newer for the Program Files applications.
Since I have not heard from them, I already proceeded with the patch to fix the problem within the H-Ext. I have no idea when the next release date for H-Ext... It all depends on work.