We have been busy in work updating our AVE product to be App-V 5.0 compatible, and as you can probably guess, this has not been a trivial task. In anticipation of launching “next generation” version of AVE that supports App-V 5 packages, I would like to open up a call for those interested in beta-testing the upcoming product.

Hello, We have just released update to Application Virtualization Explorer, version 2.4.5. This update adds explicit support for three new (OSD) policy elements that were introduced in hotfix 8 for 4.6 SP1 and in 4.6 SP2. These policy elements are mainly meant to fix issue with Adobe Reader protected mode and now you can set them directly from AVE’s […]

For a long time already, Application Virtualization Explorer (AVE) has had the ability to set and edit virtualized environment variables per application basis (like you could do in the Sequencer by using that cumbersome OSD -tab), but in the recently released 2.4.0 version we decided to add support for editing variables at the package level too.

We have just released a new version of AVE, version 2.4, which adds some new features and enhances the existing functionality in the product.

We have had the 32-bit fixup tool available for a while (to correct issues in App-V 4.6 packages saved out from AVE prior to version 2.2.6), but since the recent events there appeared to be a need to do the opposite as well.

Oh man, I cannot believe that the old issue kind of came back to haunt us. Back in the last year we fixed an issue in our App-V -related products that caused all App-V 4.6 packages to be flagged as 64-bit packages, now it was the reverse.

Windows Team blog has just announced, for the first time publicly, development and the details of App-V 5.0. Along with the new App-V version. Along with the next App-V version, the blog post also announced Microsoft’s User Environment Virtualization (UE-V) product (which was previously known with codename “Park City”).

In this new series, we’re going to highlight some of the new features that we introduced in Application Virtualization Explorer (AVE), version 2.3, released in December last year (gosh, sounds like a long time ago when said like that!).

When we announced possibility to test upcoming (and now released) AVE 2.3 version back in the few months ago, I promised that we will give out two complimentary licenses for two of the feedback submitters, drawn randomly.

After looking at the basics of Virtual File System (VFS) and how the data behaves in the client for VFS virtualized directories in the previous articles in the series, let’s finish up the discussion of VFS folders by looking at one specific – rather interesting – bug (because that’s what it must be) when it comes to fully virtualized folders and the whole concept of isolation.