Dan Gough rambles on about application packaging and virtualisation

Fix For Office 365 / App-V Interaction

In my previous post on this subject, I came to the conclusion that Office 365 apps just wouldn’t run in an App-V virtual environment. However there is a fix for this that can be applied to the client registry:

Even a Google search for ‘AllowJitvInAppvVirtualizedProcess’ turns up this article, however all reference to it has now been removed. What this means in terms of support I have no idea, so this setting should be added at your own risk; however I have found it to fix multiple issues including:

Creating shortcuts to Excel as a way to sequence Excel add-ins

Pasting Visio objects from virtualised Visio into Office 365 Word

I have so far not seen any negative effects from using this setting and am recommending that people use it, with the disclaimer that anybody should contact Microsoft support before doing so!

Post navigation

5 responses on “Fix For Office 365 / App-V Interaction”

Had several times contact with MS support, every time they let me verify the key was set ;-), I think that say enough.
If I recall correctly the key is now created on win10 1703 with appv enabled and recent O365 version as soon as it starts within an appv bubble!

Thank you for this fix! Our Oracle Client ODBC-drivers are now visible and work stable within Access C2R.

When I read this post first time, I tested this setting but it didn’t seem to do anything. But now, a few months later, I discovered my test-machine had only App-V Client 5.1 installed. While this fix requires at least HF2 to work.