I want to migrate app-v packages to MSIX packages

Question

Currently, we are using app-v packages to distribute virtual applications to each user.

We would like to migrate to MSIX as app-v will no longer be supported in 2026.

We can convert app-v to MSIX using the MSIX Packaging Tool, but since the reference points such as the registry are different, information set by users within the application will not be migrated.

Is there a way to migrate from app-v to MSIX so that the user settings information of the currently configured application remains?

Answer 1

Hi takashi-7890,

In addition to Alex Burlachenko, I have provided more information for your query.

Yes, you can convert your MSIX package into a VHDX file for use with MSIX app attach in Azure Virtual Desktop. This process allows applications to be dynamically attached to user sessions without traditional installation, optimizing resource usage and management.

Ensure you have a signed MSIX package of your application. Download the MSIXMGR Tool and create the VHDX Image then Add the VHDX to Azure Virtual Desktop.

Please visit this document for your reference: Create an MSIX image to use with app attach in Azure Virtual Desktop Add and manage app attach and MSIX app attach applications in Azure Virtual Desktop

If you have any further queries, do let us know. If the answer is helpful, please click "Accept Answer" and "Upvote it."

Answer 2

Hi takashi-7890,

yes, Microsoft will end support for App-V in 2026, making it essential to migrate to MSIX for continued application virtualization and management.

to migrate App-V packages to MSIX while preserving settings

App-V stores user settings in %APPDATA% and HKCU\Software\Microsoft\AppV, while MSIX uses containerized storage (C:\Users\<User>\AppData\Local\Packages\).

Export registry settings (reg export), copy user data files to the new MSIX container, and deploy via Intune or GPO.

Use FileRedirectionFixup to remap legacy paths.

Run App-V and MSIX in parallel while migrating settings gradually.

validate & test, deploy to a test group, use ProcMon to track missing settings, and adjust scripts as needed.

Just in cases https://ctrlaltdel.team/?p=289 here is link to my blog where included PowerShell Script for Migration.

rgds,

Alex

p.s. Please click Accept Answer and upvote if the above was helpful.