You will notice that once an application is running, there are a few ways you can tell if an application is running virtualized or not. Of course, it will always be the 32-bit DLL if working exclusively on X86 platforms.

Now, I previously blogged about this part of the process last year and gave a convoluted diagram ( ) which was met with entertaining emails.Īssuming the application is going to be virtualized, after that workflow has completed, then either the AppVEntSubsystems32.dll or the AppVEntSubsystems64.dll is injected into the virtual process depending on the bitness of the application. The executable’s process is created but there will be a process notify callback by the App-V Virtual Environment Manager (AppVVemgr.sys) to determine if the process should be virtualized or not. The Junction point is parsed to the right version location in the package cache. But what happens when an application is double-clicked? App-V needs to determine if the application needs to be virtualized, and if so, which virtual environment. In previous blog posts, I discussed what happens when a package is added/configured, published, and when streamed.

Process explorer technet