I believe there is no room for improvement in Microsoft App-V since it is officially at the end of life. Microsoft does not negotiate extensions for their end-of-life solutions.

It has been a great tool over the years, but the company has managed to write most applications to bring them up to date, many written from scratch or as web-based applications. It's highly likely that we will decommission the Microsoft App-V solutions next year, keeping backups for a period until the new applications stabilize.

I'm confident that once they transition to newer versions, they will phase out Microsoft App-V just like they do with operating systems. When Microsoft decides to close a version, such as Windows 10-22H2 or 21-H2, it happens. Paying for extended support is costly and, in the end, not worth it. Organizations must think of alternatives, possibly leaning towards MSIX, although MSIX doesn't support very old software used on Windows XP or 2000, which raises doubts about what can truly be improved. It's clear they won't introduce anything new; they will only provide security patches as they approach the end-of-life timeline.

View full review »

Regarding improvements in Microsoft App-V, I would appreciate seeing the successor, MSIX, work better, as nothing is going to be implemented anymore since it is end of life by the end of the year. I want it to work as they've claimed for the last 10 years.

View full review »

The problem with Microsoft App-V is that there is no choice since Microsoft has decided to stop it, and we are searching for alternatives.

Microsoft App-V needs to evolve, possibly with better integration with other solutions, particularly since we use Citrix and want to integrate App-V packages more efficiently.

The management of packages should be easier, possibly through a web console for visibility in versioning, and options to convert packages when changing technologies.

Many companies avoid using tools like Admin Studio due to high costs. Additionally, Microsoft App-V has been slow, and users experience delays when launching applications, which presents significant challenges.

View full review »

I would like more server hardware in the cloud. Deploying more into the Azure architecture would be beneficial, and maintaining support for legacy applications would facilitate easier deployments onto new operating systems like Windows 11. View full review »

There is definitely room for improvement with Microsoft App-V, especially in terms of enhancing troubleshooting resources and user guidance.

View full review »

The process was streamlined but didn't make our work simple. We encountered an issue with the person responsible for designing the website. They installed a plugin that disrupted the services and made the website inaccessible. We resolved the problem using the automatic backup preconfigured on the platform. The website was restored quickly, making it easy to address the user-created issue.

View full review »

Microsoft has announced that it is going to discontinue the solution. I wish the vendor would not discontinue the tool. The reporting features could be improved. We use our in-house tools for reporting.

View full review »

The downside is that Microsoft bought this product and they are going to discontinue it in 2026. This is worrisome for us.

I would like to see them continue to maintain the product. From my point of view, it reached a maturity where we can consider it to be perfect.

If we wanted to be picky, Microsoft could improve the synchronization of the client. We were forced to put our own PowerShell script, which mimics the built-in functionality of the syncing. It would avoid errors.

Another feature that has not been implemented, but would be nice to have is the possibility to publish different shortcuts within the same package, to different groups. 

There is a solution in place, but it's not really working. If you have two different groups on two different shortcuts, everything works fine, as long as you don't have a common set of users in those groups. As soon as you have one user in both groups, then the client won't know which one to publish, and it is not able to do a merge between those two settings.

I would like the synchronization improved and to have the possibility to publish different shortcuts to different groups within the same package.

View full review »

If it were possible to integrate App-V with a cybersecurity solution then we could implement a documentation registry, which would be useful.

View full review »