![Microsoft App-V vs. VMware ThinApp [EOL] report](https://www.peerspot.com/assets/media/images/icons/pdf-80836ec5.svg){kind=icon}
![VMware ThinApp [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,f_auto,q_auto,w_64/i8676a39lscwk1j2bgjuyjwm9p92.png)
![VMware ThinApp [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,f_auto,q_auto,w_30/i8676a39lscwk1j2bgjuyjwm9p92.png){kind=small}
![VMware ThinApp [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,f_auto,q_auto,w_40/i8676a39lscwk1j2bgjuyjwm9p92.png){kind=small}
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.
![Inuvika vs VMware ThinApp [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,f_auto,q_auto,w_30/89d7ciyDq3LQ6zBiXyvnWu1F.png){kind=small}
