application

Later have been seeing issues when removing earlier versions of Adobe Acrobat DC and installing newer version in windows 10 1703/1709 which has been explained very well in the below blog by Ryan Ververs-Bijkerk https://www.logitblog.com/app-v-application-was-unable-to-start-correctly-on-windows-10/ The solution was to restart the machine and try again earlier. Now this is fixed with the release of new updates for windows 10. 1703 fixed in 2018.10 - KB4462939 1709 fixed in 2018.10 - KB4462932 1803 fixed in 2018.10 - KB4462933 Thanks to Tim Mangan for sharing this update information.

After publishing the App-V sequenced TortoiseSVN, all the context menu shortcuts are visible and it works fine. Only the background context menu option is not visible. In this blog, I will demonstrate and provide a solution for it. First download the TortoiseSVN software from the below link. https://tortoisesvn.net/downloads.html Download the Latest windows ADK so that we can use the latest App-V Sequencer from the below link. https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install Sequence the TortoiseSVN application using default steps. Even if you use PVAD when sequencing, we can see the same issue that the background context menu is not visible after publishing. After Publishing the sequenced package, we can see that when we right click file\folder\drive the context menu option is visible as App-V will install those respective registry entries in the local machine and they will be used by the explorer due to dynamic virtualization concept. FILE: FOLD...

Many packages that completely worked in inbox App-V in windows 10 1607 failed after upgrading to windows 10 1703 and 1709 versions. The reason for failure is due to Microsoft changed the way to load registries in containers CREG instead of usual virtual registry VREG. To know about this change do have a look at the below articles from Tim Mangan. http://www.tmurgent.com/TmBlog/?p=2692 http://www.tmurgent.com/TmBlog/?p=2733 There was a temporary fix which was available and Roy Essers posted it in twitter a long back. It was adding the below registry entry manually in the 1703/1709 machines. [ HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\AppV\Client\Compatibility] "RegistryCompatibilityMode" = dword : 00000001 Microsoft has released an update earlier today which is supposed to fix this registry mapping issue. https://support.microsoft.com/en-us/help/4074588 We can clearly see that they have made use of the temporary fix to change the registry virtualization to use the VREG instead of...