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 this change. I believe it was an attempt to modernize, and while I hope it was to improve performance, I have my doubts about those results.
| NOTE: See update https://www.tmurgent.com/TmBlog/?p=2736 |
What is clear is that the change caused a lot of issues, and a temporary workaround was given out (see: this TechNet Forum post). That workaround consists registry change that makes the registry system revert to the virtual registry. Microsoft has indicated that a permanent fix should be available at the end of this month (February 2018), and if you implement the temporary fix you will need to remove that workaround.
App-V fixes for Windows 10 are released as operating system changes, so I expect it to appear as a non-security fix of the OS. So that probably means it appears in the March rollup?
Whether the permanent fix is to give up on CReg and revert back to VReg or solve the issue is unknown, but I am guessing that we return to VReg.
Stay tuned.
