If you are using App-V and moving to Windows 10 1703 or 1709 , you need to be aware of an issue, temporary workaround, and “permanent fix” that we are waiting for.
The short of it is that last summer Microsoft decided to change the implementation of the App-V virtual registry to use containers. We don’t know a lot about …

Sebasitan, the German Microsoft Escalation Engineer we often get new news from about App-V, recently blogged about the dates for the lifecycles for App-V 5.1. Before people get upset, let’s make sure you understand what this means.
NOTE: This post is part of a series. You might want to start at the beginning: