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...

When launching sequenced Adobe illustrator shortcut we see the below issue in the App-V client machine. Reason: This is due to UAC and the application requires to be run as administrator. Solution: To test manually Click Start > All Programs. Right click on the Adobe Illustrator shortcut  and click Run As Administrator. The shortcut will launch without any error. So how to resolve this in the App-V 5.x package? We need to suppress the UAC prompt when run as administrator using RunAsInvoker or other shims. Check my another blog for more information to solve this issue  here

Many packages that completely worked in inbox App-V in windows 10 1607 failed after upgrading to windows 10 1703. The reason for failure is due to Microsoft changed the way to load registries in containers CREG instead of usual virtual registry VREG. 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 This issue is fixed in windows 10 1703 with the new hotfix released. https://support.microsoft.com/en-us/help/4077528 We can clearly see that they have made use of the temporary fix to change the registry virtualization to use the VREG instead of the modern CREG that was mentioned earlier to permanently fix this issue. Apart from the registry fix, this update also fixes many other App-V issues which can bee seen below. This update will be downloaded ...

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...

Earlier when we unpublish App-V packages it used to stay in the App-V cache location  and used to occupy unwanted storage space on the client machines. If we want to remove them to free up space we need to  do manual removal or using powershell command Remove-AppVClientpackage I had blogged earlier a simple powershell script to remove all unpublished packages that are either published globally or to a user.   With the release of the new windows 10 creators update v1703 App-V client provides options to automatically cleanup the unpublished packages.It requires restart. This option can be enabled either by PowerShell or group policy or Registry. PowerShell: Open PowerShell as administrator and run the below code. Set-AppvClientConfiguration -AutoCleanupEnabled 1   Run the below code to get the status. Get-AppvClientConfiguration Group Policy: Go to Administrative Templates-System-App-V-PackageManagement-Enable automatic cleanup of unused appv packages and select ena...

As all would have heard about the inbuilt App-V and Ue-V available with Windows 10 Anniversary update 1607 which has been released on August 2nd 2016.It is available only with the Windows Enterprise and Education editions. They will also be included in-box in Windows Server 2016 Standard and Datacenter. If you are using Windows 10 Professional or earlier and plan to upgrade to the Windows 10 Anniversary release, you will need to deploy the Enterprise edition to use App-V and UE-V on those devices. I have already blogged about this in my previous post when I tested App-V and Ue-V in windows 10 build 14316 and some common issues found. You can have a look here in the below link. http://app2pack.blogspot.com/2016/04/app-v-ue-v-available-by-default-in-new.html http://app2pack.blogspot.com/2016/04/windows-10-build-14327-enabling-or.html By default App-V and Ue-V are disabled in the OS. You need to enable it to use them. It can be done by enabling in services,GPO or using Powershell comm...

Even though App-V client is installed and been enabled, running the App-V generated msi shows the below error. Resolution: Create a transforms for the generated MSI and remove the highlighted Installed OR APPV_CLIENT_INSTALLED launch condition.This should fix the issue temporarily. For a permanent fix we need to wait for Microsoft to release its updated OS.

As everyone would have already known the earlier news that Microsoft has planned to incorporate App-V in its new windows 10 release Redstone 1. Recently Microsoft has released its insider preview release for Windows 10 Build 14316. I had an opportunity to test it. Below are some interesting findings. 1. We can see the App-V files present in the C:\windows\System32 folder. One can think why Microsoft has kept the files like this instead of keeping them in a separate folder?  (Ex: C:\windows\System32\App-V). Though we were not able to get answers, we have to wait for Microsoft to give its reason.   2. The same applies to Ue-V files. They are also present inside the same C:\windows\System32 folder and not in a separate folder (Ex: C:\windows\System32\Ue-V). . 3. Next we tested publishing some sample apps. it wasn't successful. The reason was that the App-V Client service was disabled by default. Turning the App-V client services manually ON worked for us. We can start the se...