What does this mean?
Microsoft announced a change of plans for the End-Of-Life for App-V and inclusion into AppAttach for AVD at a conference in Hamburg Germany. In this post I’ll outline what was said and offer my ideas on what it might mean for you.
At the MAD 2024 Conference in Hamburg Germany last week, Microsoft’s Jim Moyle and Sebastian Gernert discussed changes to the End Of Life state of Microsoft’s Application Virtualization product, Microsoft App-V, and changes to AppAttach on AVD.
Where we were
App-V, which I had a hand in creating at Softricity (the company that Microsoft bought for the technology), got its start in 2000 and development on the product stopped many years ago as Microsoft shifted to replace the technology with MSIX. After a series of dates, and delays in those dates, the End-Of-Life for App-V was established as April 2026.
The App-V Sequencer, a software package used to transform traditional applications into App-V application packages, has always lived as part of the Windows ADK. The ADK, which used to be released in conjunction with OS releases, hasn’t been updated in many years. It still works as well as it ever did and while there might not be an official EOL date it was clear that there is no support available on the component. As the software is only used to prepare applications offline, we found that most enterprises seemed to be OK (yet uncomfortable) with continuing to use this unsupported software.
The Server software, the key component of MDOP to deploy the packages, has been end of life for some time now. It still works fine, and many Enterprises are still using it, but those that cannot use unsupported software in critical roles have had to move on. Some use SCCM or Intune to deploy. But those needing time critical delivery now use Citrix to deploy App-V packages, some use AppVentiX, and still others use home-grown solutions.
The Client software, originally an add-on has been built into the OS starting with Windows 10. This is the critical piece that allows the packaged virtual applications to be installed and run. The end of life for this component is always tied to the end of life of the operating system build. So, while it wasn’t a real end-of-life date, many unofficial statements were made by Microsoft that App-V would (or could) be removed as early as 2022. But eventually the April 2026 date was documented as the official end-of-life date for the App-V client.
But then earlier this year it was announced that the App-V client would be included as part of the Server 2025 release (App-V is used both on the desktop operating systems and on the Server when Remote Desktop Protocol is used). Since the server has a 5+5 support policy this caused many to question if the App-V client is really EOL.
MSIX AppAttach, Microsoft’s name for the management of MSIX apps in AppAttach format for AVD, until now supported only MSIX packages or applications baked into the image.
What was said
The summary of the announcement is as follows:
- The End-Of-Life for the App-V Client is rescinded.
- The App-V Sequencer deprecation is rescinded.
- App-V Server is still EOL.
- MSIX AppAttach is rebranded as AppAttach, and will add support to deliver not only MSIX in AppAttach format, but also App-V (as App-V packages).
- The new AppAttach also will have integrations by third-party vendors to deliver packages their packages using additional software built by the third-party vendors that plug into the Azure Console for AVD.
What we think it means
At TMurgent, we have been at the forefront of helping customers make use of both Microsoft App-V and the replacement MSIX, through a combination of free community tools, commercial software, training, and consulting. We live and breathe this stuff and want to provide some ideas on how you to think about it.
The motivation for these changes come from several factors:
-
- These announcements provide Microsoft’s customers with an increase in choice. But it is mostly all about moves to ensure increased Azure revenue. AVD needs fast dynamic delivery of applications, and Intune won’t cut it. MSIX via AppAttach hasn’t produced enough application compatibility (well, until recently). So, bringing along App-V apps, and other third party formats, is a stop-gap measure. Supporting other formats for AVD is also about filling the app gap, which is just a temporary issue.
-
- Large Enterprise customers that use App-V, and there are a lot of them, have been quite vocal that they have been kicking the tires on all of the alternatives (MSIX, Citrix App Layering, Omnissa Cloud Volume, Liquidware FlexApps, and Numecent Cloud Volumes) and find them all currently lacking. Responding to those customers in this way gives them more time to consider their options and Migrate on their own schedules.
In deciding what this means for your organization, you should consider what was not said:
- While Security Fixes for the Client Components are guaranteed for now, we heard that there will be no new App-V feature work, but we didn’t hear any commitments about non-security fixes, such as the known bugs that have languished for years. While Microsoft would probably be forced by customers to fix the client if an OS change broke it, we didn’t hear a promise on that.
- The 5×5 support on Server 2025 establishes that we’ll have a client supported on the server for 10 years. But we did not hear that this means it will be supported on the desktop OS. We’d guess that it probably will be, but no guarantees on that. We will have to check the support against every desktop OS release to be sure.
- While the Server will exit support in April 2026, there is an outstanding question as to whether it will be updated before then. The server is built using components that themselves go EOL prior to the 2026 date. That’s a security issue, and as such could possibly be addressed by Microsoft with a rebuild of the software retargeting newer versions of the dependencies. Customers that are relying on the server until then should consider if they need to get off of the server sooner than that, or voice their concerns with Microsoft to address this need.
How to view the situation may depend on where you are with applications today:
- Using App-V and have not started migration away yet. You were behind on planning a migration and got lucky. Take a deep breath. Spend effort completing migrations off of Windows 10 and earlier Server OSs. But then don’t ignore that App-V will be going away eventually. We’ll discuss why later on.
- Using App-V and are currently in evaluation/planning stage for a migration away. You might also be lucky; migrations take time. There is nothing in the announcement that should cause you to abandon the evaluation/planning. But it doesn’t need to be top priority this year if there are more critical things to do.
- Using App-V and are currently Migrating to MSIX (and/or AppAttach MSIX). You have made your choice and should continue this migration. Again, you might reduce the priority on this (although we did not hear a date on when App-V packages will be supported via AppAttach on AVD).
- Using App-V and are currently Migrating to another technology. You have made your choice and should continue this migration. But we’ll just mention that MSIX is now more capable than you think. So if you have problems with your choice you can stay with App-V for a while and/or move some apps to MSIX.
- Not using App-V but Migrating for other purposes. It may take some time to figure out what the advice should be. We would be reluctant to suggest a customer start with App-V now if they have never used it. MSIX is probably a better choice. But maybe you’d like one of the other folks mentioned earlier too.
Where we are with MSIX
MSIX is still considered to be the Microsoft replacement for both the MSI and App-V, even if they are not going away tomorrow. It cannot handle all of the traditional Win32 and .Net Framework applications that exist, but then no packaging format can.
We measure App-V compatibility at 98% and (using our tooling to help) MSIX now at 90%. That’s up from 60% two years ago and 82% at the beginning of this year. Those are full compatibility numbers to your UAT, and other formats are no better.
But MSIX is not just about repackaged apps. New applications being built with .Net 5 and above are native MSIX packaged apps. Vendors are not replacing their older software installers from Exe/MSI to MSIX, but new software is.
More importantly, the operating system is slowly changing to expect apps to integrate the way that MSIX does, with complete separation in the OS.
- App-V and MSIX are good at application isolation at runtime, something important for security.
- MSIX is also excellent at also separation of how the app integrates into the OS at installation. App-V (as well as traditional installers and the other formats) still end up writing to the same places traditional apps did while installing. This means intermixing its files into the start menu folders and registry settings under the Classes keys for file type associations, Shell Verb commands, Shell Extensions, and (at least some of the) COM registrations, with all of the other traditional applications. So, shortcuts sometimes get messed up, filetype conflict occurs, and shell extensions are not as well isolated, leaving the possibility of security issues.
- MSIX is becoming THE native app format in the OS, and as the OS evolves we may find other methods of installation becoming more like second-class citizens.
This is why we caution that the announcement is great news, but not news that you should forget about getting off of App-V. Eventually.
Our opinion: MSIX should be your first choice
We made this statement last month. Nothing here changes that. The announcement just reduces the pressure to move on from App-V right away.
MSIX, for application packages that work well with the technology, offers better integration into the OS, with complete separation for the start menu, file type associations, shell extensions, and COM. App-V may be close in that support, but with MSIX your app can’t be broken by installation of another app. As the OS continues to evolve to be more secure, there will be more opportunities for App-V to fall further behind. Moving towards Microsoft’s new native model for these integrations will likely become more and more important over time.
We have made great progress in the MSIX application compatibility story, currently at 90% (measured by UAT tests, and that is up from 82% at the start of the year) and in the ease of packaging for the majority of apps to that level. As easy as for App-V or better.
Yes, you’ll need our TMEditX to achieve those numbers. And some of those apps require experience and probably packaging training, which we can provide. There is no single application format that can deliver 100% of Windows applications for every scenario the enterprise needs them. MSIX is ready to be your first choice, and for those apps that don’t work today, App-V or a native install can be the backup.
So, if you are using App-V and worried about the end of life, take a deep breath, but don’t forget the reasons to modernize your app infrastructure.
