App-V Server Deprecation Creates a New Decision Point
For organisations still relying on Microsoft Application Virtualization (App-V), the deprecation of App-V Server represents an important turning point in their application delivery strategy. Microsoft announced the deprecation of App-V Server components in 2024, affecting the central infrastructure used to publish, manage and distribute virtualised applications.
The App-V client remains a supported component of Windows, while the App-V Sequencer can still be used to create and maintain virtual application packages. Organisations can therefore continue operating established App-V estates without immediately replacing every application.
However, App-V is no longer being actively developed. Although existing functionality remains supported, Microsoft has moved the technology into extended support, with development primarily limited to security updates and bug fixes.
For IT teams, this introduces an important strategic decision. The priority is not necessarily to replace every App-V package immediately, particularly where existing applications remain stable and business-critical. Instead, organisations should evaluate how applications will be packaged, managed and delivered in the future, reducing their dependency on ageing infrastructure while preserving their investment in existing application packages.
App-V Extended Support Through 2029
In October 2026, Microsoft announced a three-year extension to App-V Server support. Microsoft KB5131438 confirms that App-V Server will remain in extended support through October 9, 2029, reversing its previous end-of-support position in April 2026.
This provides welcome breathing room for organisations managing large App-V estates, particularly those with hundreds or thousands of virtualised applications that cannot realistically be migrated overnight.
However, this is an extension of the existing product lifecycle, not a return to active development. Organisations should not expect significant new features, improved administration, broader cloud integration or a long-term product roadmap.
The additional three years should therefore be viewed as an opportunity to plan and modernise rather than a reason to postpone migration indefinitely. IT leaders can use this period to evaluate alternative delivery platforms, assess application compatibility and establish a phased migration strategy that minimises disruption to users.
Why App-V Client and Sequencer May Be Next
Unlike the App-V Server components, Microsoft has retained the App-V client and App-V Sequencer within the Windows support lifecycle. Both have moved into fixed extended support and remain available, although neither is receiving significant new feature development.
The App-V client continues to run virtualised applications, while the Sequencer enables IT teams to create and maintain packages. These components can also operate without the traditional App-V Server infrastructure when alternative publishing and management mechanisms are used.
Nevertheless, the retirement of the original server infrastructure sends a clear strategic signal. Although Microsoft has not announced the removal of the App-V client or Sequencer from future Windows releases, organisations should recognise the risk of building their long-term application delivery strategy around technology that is no longer being developed.
MSIX Is Not a Complete App-V Replacement
Microsoft positions MSIX as its modern Windows application packaging format and recommends it as a migration option for organisations moving away from App-V.
However, there is an important distinction between the two technologies.
Unlike App-V, which included dedicated management and delivery infrastructure through its Management, Publishing and Streaming Server components, MSIX does not provide its own centralised application delivery platform. MSIX is primarily a packaging and installation technology, leaving organisations to decide how applications are distributed, assigned, updated and managed across endpoints.
Similarly to App-V, MSIX packages can be deployed using existing endpoint management solutions such as Microsoft Configuration Manager (SCCM) or Microsoft Intune. These platforms provide centralised deployment, assignments, monitoring and reporting, allowing MSIX packages to be managed alongside traditional MSI and EXE applications.
For non-persistent environments, such as pooled virtual desktops that are frequently rebuilt or reset, traditional application installation may be less desirable. Microsoft App Attach provides an alternative approach, allowing applications to be dynamically attached and made available to users without permanently installing them into the underlying operating system image.
In Azure Virtual Desktop (AVD), App Attach enables applications to be delivered from centrally stored disk images, reducing the requirement to maintain multiple golden images and simplifying application lifecycle management. This is particularly beneficial in non-persistent environments, where applications can be provisioned dynamically according to user assignments.
However, one of the biggest challenges with MSIX remains application compatibility, particularly with large, complex applications. Microsoft’s Package Support Framework (PSF) was developed to help address compatibility issues by applying runtime fixes and redirections to applications that would otherwise fail within the MSIX container. However, its latest published GitHub release dates from February 2024, more than two years ago at the time of writing.
Tim Mangan’s alternative Package Support Framework implementation offers additional fixes and capabilities, helping extend compatibility with applications that would otherwise be difficult to package using MSIX.
Even with these frameworks, success is not guaranteed. Large engineering and construction applications, specialised line-of-business software and applications with complex services, drivers or licensing components can be difficult to package or support reliably.
Recast Application Workspace Package Delivery
A viable App-V replacement strategy should not require every application to be converted to a new packaging technology immediately. Instead, organisations should adopt a phased migration approach in which existing App-V packages continue to serve users while applications are assessed, remediated and modernised at an appropriate pace.
This requires an application delivery platform capable of supporting multiple packaging technologies rather than enforcing a single standard.
In addition to App-V and MSIX, organisations may need to deliver traditional MSI and EXE applications, VMware ThinApp packages, PowerShell scripts and other installation or application delivery methods.
Recast Application Workspace, formerly Liquit Workspace, provides a centralised approach to managing and delivering applications across physical PCs, virtual desktops, persistent virtual machines and non-persistent environments.
Its flexible package and action-based architecture enables organisations to manage different application technologies through a consistent delivery platform, including existing App-V packages where the required client components remain available.
Applications can be presented and provisioned based on user, device and environmental requirements, reducing the need to maintain multiple application delivery mechanisms and simplifying administration across diverse endpoint estates.
Application Layering and Isolation with Liquidware FlexApp
Liquidware FlexApp’s layering approach offers greater compatibility with complex engineering and specialist applications that prove difficult to package using containerised technologies such as MSIX. It enables applications to be packaged into dynamically attached application layers, typically using VHDX-based storage, and attached when required, allowing applications to appear locally installed without being permanently incorporated into the underlying operating system image.
This approach offers several advantages, particularly in shared virtual desktop environments, non-persistent desktops and endpoint estates where maintaining multiple golden images creates significant administrative overhead.
Applications can be packaged independently of the operating system, reducing the need to rebuild or update desktop images whenever application requirements change.
Historically, application layering and application isolation have been separate concepts. However, Liquidware introduced FlexApp Sandbox Isolation in version 6.9.5, released in June 2026.
This extends FlexApp’s capabilities by allowing selected applications to execute within isolated Windows Sandbox environments, supporting scenarios where different versions of the same application need to operate side by side or where additional separation from the underlying operating system is desirable.
This brings FlexApp closer to some of the application isolation capabilities traditionally associated with App-V, while retaining its broader application layering and delivery functionality.
For organisations transitioning away from App-V, a combination of Recast Application Workspace and Liquidware FlexApp offers a potentially attractive approach.
Existing App-V packages can continue to operate during the transition, while applications requiring alternative delivery methods can be introduced progressively. Recast Application Workspace can provide centralised application management and delivery, while FlexApp can address suitable applications where dynamic layering or isolation offers advantages over traditional installation or MSIX packaging.
