Table of Content
- Microsoft App-V integration in Windows 10
- Support lifecycle Microsoft App-V
- The rise of MSIX and MSIX App Attach
- Microsoft App-V is dead
Microsoft App-V has been around for a long time, and is used in many organizations. But ever since the native App-V integration in Windows 10, there is a lack of update information. Should you still invest in Microsoft App-V with the rise of MSIX? Is App-V really dead? In this blog post, I will share some facts and thoughts about App-V.
Microsoft App-V integration in Windows 10
Microsoft has integrated the App-V client in Windows 10 since the 1607 release. That is over 3 years ago, and since then there been minimal communication regarding any updates. As the client is integrated with the operating system, all the updates and fixes are release using Windows Updates. This makes it very hard to keep track on the fixes and the potential issues. The Microsoft App-V documentation website does not have any information regarding updates or fixes. The latest “Whats new in App-V for Windows 10” is regarding Windows 10 1703, which is released over 2 years ago. Luckily, we can always count on the App-V guru Tim Mangan. On Tim’s website you can find KB patches that address issues in the App-V client. Please note, this is not official Microsoft documentation and created on best effort by Tim.
The following table shows some recent updates of Microsoft App-V client.
| Issue | 1909 | 1903 | 1809 | 1803 | 1709 | Notes |
| ‘Addresses an issue that prevents a Microsoft App-V application from opening and displays a network failure error. This issue occurs under certain circumstances, such as when a system’s battery is low or there is an unexpected power failure.’ | none | Sept 26, 2019
(OS Build 18362.387) |
Sept 24, 2019
(OS Build 17763.774) |
Sept 24, 2019
(OS Build 17134.1039) |
Sept 24, 2019
(OS Build 16299.1420) |
The described issue is listed as resolved in both the Sept patches AND the July patches for 1903 and August for 1809/1803. Use the September one to be sure. |
| ‘Addresses an issue that prevents Microsoft App-V from handling a parameter of the CreateProcess API properly, which prevents the virtual process from opening.’ | none | Sept 26, 2019
(OS Build 18362.387) |
none | none | none | |
| “Addresses an issue that prevents Microsoft Application Virtualization (App-V) scripting from working if you run it when you’re not connected to a domain controller (DC). App-V scripting also fails when you run it in an environment that only contains Microsoft Azure Active Directory. ”
“Addresses an issue that prevents an App-V application from opening if the client is offline and a startup script is defined for the App-V application.” |
none | July 26, 2019
(OS Build 18362.267) |
July 22, 2019
(OS Build 17763.652) |
July 16, 2019
(OS Build 17134.915) |
July 16, 2019
(OS Build 16299.1296) |
These two items appear independently in the same KB for 1903, but only the first text appears in the 1809/1803/1709 KBs. They appear to be slightly different situations of the same problem, likely fixed with the same code change in all cases.
Wow! This has been a long time feature request (well, we documented it as a bug but were told that it was per-design). Presumably this was addressed for the Azure Active Directory scenarios that are not co-managed. But it should mean that App-V scripts now work on non-domain joined machines. |
| “Addresses an issue that causes Office 365 applications to stop working after opening when they are deployed as App-V packages. “ | none | June 27, 2019
(OS Build 18362.207) |
June 18, 2019
(OS Build 17763.592) |
June 18, 2019
(OS Build 17134.858) |
June 18, 2019
(OS Build 16299.1237) |
|
| “Addresses an issue that fails to update a user hive when you publish an optional package in a Connection Group after the Connection Group was previously published.” | none | none | June 18, 2019
(OS Build 17763.592) |
June 18, 2019
(OS Build 17134.858) |
June 18, 2019
(OS Build 16299.1237 |
Source: https://www.tmurgent.com/AppV/en/resources/app-v-5-versions/509-5-2-appvmonthlies
Support lifecycle Microsoft App-V
It is important to understand the support lifecycle has changed with the integration of App-V in Windows 10. The support lifecycle of the native integrated App-V client is based on the Windows 10 build. As the support ends for the Windows 10 build, it also applies to the App-V client.
The lifecycle of the various Windows 10 builds are specified in the table below.
| Windows 10 version history | Date of availability | End of service for Home, Pro, Pro Education, and Pro for Workstations editions | End of service for Enterprise and Education editions |
|---|---|---|---|
| Windows 10, version 1909 | November 12, 2019 | May 11, 2021 | May 10, 2022** |
| Windows 10, version 1903 | May 21, 2019 | December 8, 2020 | December 8, 2020 |
| Windows 10, version 1809 | November 13, 2018 | May 12, 2020 | May 11, 2021** |
| Windows 10, version 1803 | April 30, 2018 | November 12, 2019 | November 10, 2020 |
| Windows 10, version 1709 | October 17, 2017 | April 9, 2019 | April 14, 2020 |
| Windows 10, version 1703 | April 5, 2017* | October 9, 2018 | October 8, 2019 |
| Windows 10, version 1607 | August 2, 2016 | April 10, 2018 | April 9, 2019 |
| Windows 10, version 1511 | November 10, 2015 | October 10, 2017 | October 10, 2017 |
| Windows 10, released July 2015 (version 1507) | July 29, 2015 | May 9, 2017 | May 9, 2017 |
Source: support.microsoft.com
When using an older operating system the following support dates apply to App-V version 5.1.
| Products Released | Lifecycle Start Date | Mainstream Support End Date | Extended Support End Date |
|---|---|---|---|
| Microsoft Application Virtualization 5.1 for Remote Desktop Services | 11/1/2015 | 1/9/2018 | 4/14/2026 |
| Microsoft Application Virtualization 5.1 for Windows Desktops | 11/1/2015 | 1/9/2018 | 4/14/2026 |
| Microsoft Application Virtualization Hosting 5.1 for Windows Desktops | 11/1/2015 | 1/9/2018 | 4/14/2026 |
Source: support.microsoft.com
The rise of MSIX and MSIX App Attach
In 2018 Microsoft has introduced a new packaging format called MSIX. I have even written a hands-on blog post about it, right here. MSIX is going to be the new format which can replace both the traditional MSI and setups as well as AppX which is the current Microsoft Store format. MSIX will inherit all the features of UWP and it also introduces more container security options and allows application customization’s. Existing App-V packages can be converted to the new MSIX format. This allows organizations to convert App-V packages to the MSIX format and make them available from the Microsoft Store for Business.
This year Microsoft also introduced MSIX App Attach, allowing administrators to separate the applications from operating system in a dedicated layer. This layering technique provides better management while keeping the native application user experience. Using MSIX App Attach still provides the isolation using MSIX technology but also provides the ability to bundle multiple MSIX applications. The following video contains an excellent explanation.
Microsoft App-V is dead
Yes, besides Microsoft App-V is still supported and maintained, it is dead. It is clear since the integration of the App-V client in Windows 10, Microsoft has put minimal effort in this technology. There is minimal, to no information available on the various changes and fixes in the App-V client. Nevertheless, Microsoft App-V will be around for many years. Many organizations invested a lot of time and resources to convert applications to App-V packages. The transition to a new packaging format, like MSIX, is not done over night. But looking at the investment in MSIX and App Attach using the traction of Windows Virtual Desktop, the new strategy is clearly not App-V. Therefore Microsoft App-V is dead.
I think Microsoft is going to continue to invest in MSIX in 2020, making Microsoft App-V obsolete. Therefore, I would not recommend to organizations to invest in Microsoft App-V anymore. In 2020 it will be the time to prepare for adoption and transition to MSIX as the new standard for application virtualization, isolation and deployment. What do you think will happen with Microsoft App-V? Leave your thoughts in the comments below.
Photo by Eliott Van Buggenhout on Unsplash
