This article may be weighted too heavily toward only one aspect of its subject. Please help by introducing more general information to this article. Feel free to discuss the issue on the talk page. (February 2019)

Application virtualization is a software technology that encapsulates computer programs from the underlying operating system on which they are executed. A fully virtualized application is not installed in the traditional sense,[1] although it is still executed as if it were. The application behaves at runtime like it is directly interfacing with the original operating system and all the resources managed by it, but can be isolated or sandboxed to varying degrees.

In this context, the term "virtualization" refers to the artifact being encapsulated (application), which is quite different from its meaning in hardware virtualization, where it refers to the artifact being abstracted (physical hardware).


Diagram of application virtualization
Illustration of an application running in a native environment and running in an application virtualization environment

Full application virtualization requires a virtualization layer.[2] Application virtualization layers replace part of the runtime environment normally provided by the operating system. The layer intercepts all disk operations of virtualized applications and transparently redirects them to a virtualized location, often a single file.[3] The application remains unaware that it accesses a virtual resource instead of a physical one. Since the application is now working with one file instead of many files spread throughout the system, it becomes easy to run the application on a different computer and previously incompatible applications can be run side by side. Examples of this technology for the Windows platform include:


Application virtualization allows applications to run in environments that do not suit the native application. For example, Wine allows some Microsoft Windows applications to run on Linux.

Application virtualization reduces system integration and administration costs by maintaining a common software baseline across multiple diverse computers in an organization. Lesser integration protects the operating system and other applications from poorly written or buggy code. In some cases, it provides memory protection, IDE-style debugging features and may even run applications that are not written correctly, for example applications that try to store user data in a read-only system-owned location. (This feature assists in the implementation of the principle of least privilege by removing the requirement for end-users to have administrative privileges in order to run poorly written applications.) It allows incompatible applications to run side by side, at the same time[4] and with minimal regression testing against one another.[5] Isolating applications from the operating system has security benefits as well, as the exposure of the virtualized application does not automatically entail the exposure of the entire OS.[4]

Application virtualization also enables simplified operating system migrations.[4] Applications can be transferred to removable media or between computers without the need of installing them, becoming portable software.

Application virtualization uses fewer resources than a separate virtual machine.


Not all computer programs can be virtualized. Some examples include applications that require a device driver (a form of integration with the OS) and 16-bit applications that need to run in shared memory space.[6] Anti-virus programs and applications that require heavy OS integration, such as WindowBlinds or StyleXP are difficult to virtualize.

Moreover, in software licensing, application virtualization bears great licensing pitfalls mainly because both the application virtualization software and the virtualized applications must be correctly licensed.[7]

While application virtualization can address file and Registry-level compatibility issues between legacy applications and newer operating systems, applications that don't manage the heap correctly will not execute on Windows Vista as they still allocate memory in the same way, regardless of whether they are virtualized.[8] For this reason, specialist application compatibility fixes (shims) may still be needed, even if the application is virtualized.[9]

Functional discrepancies within the multicompatibility model are an additional limitation, where utility-driven access points are shared within a public network. These limitations are overcome by designating a system level share point driver.[10]

Related technologies

Technology categories that fall under application virtualization include:

See also


  1. ^ "Microsoft Application Virtualization Technical Overview". Microsoft. Retrieved 1 July 2017.
  2. ^ Husain, Amir. "How to build an Application Virtualization Framework". VDIworks. Retrieved 1 July 2008.
  3. ^ Gurr, Coby (28 July 2008). "Facilitating Microsoft Windows Vista Migration Through Application Virtualization" (PDF). Dell.
  4. ^ a b c d Winslow, Philip; Semple, Robert; Maynard, Jason; Simson, Dennis; McGrath, Bryan (26 November 2007). "Desktop Virtualization Comes of Age" (PDF). Credit Suisse. Archived from the original (PDF) on 20 February 2009. Retrieved 3 March 2008.
  5. ^ "Overview Series: Windows Vista Application Compatibility". TechNet. Microsoft. 25 July 2008. Retrieved 1 July 2017.
  6. ^ Varhol, Peter (1 September 2007). "Application Virtualization Hits Its Stride". Redmond Magazine. 1105 Media. Archived from the original on 10 June 2008.
  7. ^ Sommer, Tim (June 2012). "Top 200 SAM Terms – A Glossary Of Software Asset Management Terms". OMTCO. Retrieved 20 May 2013.
  8. ^ Marinescu, Adrian (3 August 2006). "Windows Vista Heap Management Enhancements" (PDF). Microsoft.
  9. ^ Jackson, Chris (30 April 2008). "Can You Shim Applications Virtualized in SoftGrid?". Microsoft.
  10. ^ Enzler, R (2003). "Virtualizing Hardware with Multi-context Reconfigurable Arrays". Field Programmable Logic and Application. Lecture Notes in Computer Science. Vol. 2778. pp. 151–160. doi:10.1007/978-3-540-45234-8_16. ISBN 978-3-540-40822-2.