One of the support cases that we have had, since the release of Application Virtualization Explorer version 3.0 that started supporting App-V 5.0 packages, is how to run AVE itself inside 5.0 package. Sounds simple enough, doesn’t it: just add the files into .APPV file and go, right? Well, not so in this case…

As some of you may remember, we used to have a product called Virtualization Encoder available a few years back. The idea of that product was running scripted – or template-based – automated operations against App-V packages, without user intervention. Now, that feature is sort of back in AVE!

We have just released a new version of Application Virtualization Explorer (AVE) which adds couple of oft-requested features, as well as improves the experience overall!

Like mentioned in the Lib-V release announcement a week ago, it has taken us time to come with 5.0 SP2 support in our products. But now we are happy to tell you that also our premier App-V package editor/viewer, Application Virtualization Explorer, has reached a new major 4.0 release that includes the long-awaited SP2 support.

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.

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!).