Windows Vista and Above Issue with Legacy App Virtualization

Hello everyone, we have discovered a problem with Windows 7 and legacy Halo applications causing the “UAC Virtualization”. It is forcing the Halo application to think they are writing to <drive>\Program Files**\<your halo installation> when it’s actually writing to¬†%localappdata%\VirtualStore\Progam Files**\<your halo installation>. So, how can we fix this permanently for generation to generation of Windows OS? A manifest is needed to be embedded inside Halo application in order to work properly and H-Ext will have better knowledge of what’s going on. This is affecting all versions of H-Ext and legacy brands. It is also¬†affecting on Windows Vista and above, possible Windows Server 2008 and above too, both 32 and 64 bit OS.

Why does H-Ext need an extension folder inside the halo installation?
To allow multi-installation of Halo applications run separately instead of using same user document’s directory.

Will we provide a patcher to append a manifest into Halo application?
We do not know, it’s a general issue with all other legacy applications before Windows Vista. One thing we hope for is Sawnose to provide Halo application with the embedded manifest in the next release.

What exactly is needed inside the manifest?
Below this is what’s needed to be inside the manifest in order to completely disable the UAC Virtualization.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
 <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">


** For Windows 64 bit, it will be “Program Files (x86)” without the quote.


About Admins

The sponsor of DZS's Halo website and development of DZS Halo Extension for both dedicated and client hoster.
This entry was posted in News. Bookmark the permalink.

Leave a Reply