Tip: To Disable Virtualization

Embedding Manifest to Disable Virtualization in Windows Vista

This will disable the virtualization for your application.

On a Vista machine, this manifest can be used for security requirements for an application. For example, on Vista, applications are not allowed to write into "Program Files" or Windows directories.

If requestedExecutionLevel is not set to true, the Registry and file virtualization will be turned on. The program will be writing to "Program Files," but it's really writing to C:\Users\<username>\AppData\Local\VirtualStore\Program Files. The Registry redirects HKEY_LOCAL_MACHINE\Software to HKEY_CURRENT_USER\Software\Classes\VirtualStore\MACHINE\SOFTWARE\<Application Registry Keys>.

To disable the virtualization, you need to create a Manifest file and add the manifest file in the application build events. The Manifest file disables the virtualization in Vista for your application.

Right-click the project--> click the properties-->. On the left-side menu, you need to click the compile menu-->. In the Compile menu, you have this Build Events. When you click the build events, you will have a Post-build event command line; below that, you have a test box.

Here is the link for the manifest file: http://msdn.microsoft.com/en-us/library/bb545961.aspx.

uiAccess needs to be set to false and the level should be asinvoker.

<security>
   <requestedPrivileges>
      <requestedExecutionLevel level="AsInvoker" uiAccess="false"/>
   </requestedPrivileges>
</security>

Virtualization

Before adding the following line of code in that post build command line text box, you need to find the path of the MT.exe file. Usually, it will be in "C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\MT.exe". Otherwise, please search and find the its path.

To build and embed the manifest file to connect to the application automatically, you need to add the following code in the post-build event of the application and keep this manifest file in the application path.

"Path of the MT.exe"
   -manifest "$(ProjectDir)[application name].exe.manifest"
   -outputresource:"$(TargetDir)$(TargetFileName)";#1


About the Author

Jeya Kumar

I am working as s Seniour software Engg. in L & T infotech.I am having 4+ years experience in windows and web development.

Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Relying on outside companies to manage your network and server environments for your business and applications to meet the needs and demands of your users can be stressful. This is especially true as many Managed Hosting organizations fail to meet their service level agreements. Read this Forrester total economic impact report and learn what makes INetU different and how they exceed their customers' managed hosting expectations.

  • Data integrity and ultra-high performance dictate the success and growth of many companies. One of these companies is BridgePay Network Solutions, a recently launched and rapidly growing financial services organization that allows merchants around the world to process millions of daily credit card transactions. Due to the nature of their business, their IT team needed to strike the perfect balance between meeting regulatory-mandated data security measures with the lowest possible levels of latency and …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date