Hotfix Package 2 for Microsoft App-V 5.1 and Hotfix Package 3 for Microsoft App-V 5.0 SP3 now available


Hi everyone, just a quick note to let you know that Hotfix Package 2 for Microsoft Application Virtualization (APP-V) 5.1 and Hotfix Package 3 for Microsoft Application Virtualization 5.0 Service Pack 3 (SP3) are now available.

For Microsoft Application Virtualization 5.1 RTM, this hotfix package fixes the following issues:

  • Issue 1: The lock on the VFS folder was not getting released when the user logs off from the client service
  • Issue 2: Microsoft Office Click-to-Run apps can't be opened from SharePoint in Internet Explorer. Embedded Office Click-to-Run apps may crash
  • Issue 3: Press and hold (or right-click) app on taskbar, the app icon becomes blank.
  • Issue 4: Provide mitigation for apps which don't handle long paths correctly.
  • Issue 5: Enable users to create multiple instances of Office 2016 Click-to-Run apps.
  • Issue 6: Re-enable APP-V 5.1 Management server address "http://localhost:<port>/packages" and "http://localhost:<port>/packagesummary"
  • Issue 7: The Confirmparameter is ignored when the Groupsparameter is null for Grant-AppvServerPackage command. Use the newly added Forceparameter to avoid the "Confirm Action" dialog.

For Microsoft Application Virtualization 5.0 SP3, this hotfix package fixes the following issue:

  • Issue 1: Microsoft Office Click-to-Run apps can't be opened from SharePoint in Internet Explorer. Embedded Office Click-to-Run apps may crash.

For complete details as well as a download link, please see the following:

3139245Hotfix Package 2 for Microsoft Application Virtualization 5.1 and Hotfix Package 3 for Microsoft Application Virtualization 5.0 SP3 (https://support.microsoft.com/en-us/kb/3139245)

J.C. Hornbeck, Senior Solution Asset PM
Microsoft Enterprise Cloud Group


Comments (11)

  1. Joe says:

    Hi, when mandatory profile used, profile sometimes still not being unloaded during logoff. Tested with 5.1.

  2. Jozef Jonas says:

    Hi, if mandatory profile used, profile is not unloaded properly during logoff. Tested with 5.1 and even with this new hotfix. Profile is hanged in ProfileList registry key. When the key is deleted, profile will finish unloading and cached profile is removed.

  3. Sizzl says:

    I can also confirm the same behaviour that Jozef has mentioned; however AppVClient.exe is correctly (eventually) releasing the lock on the VFS folder – just likely that it’s not doing it quick enough for the profile service to clean up the folder structure
    / ProfileList registry.

    This isn’t the end of the world for our setup, as users can successfully log back in without it creating a temporary profile (as was the behaviour before 5.1 HF2). So for us, it’s "good enough".

  4. tom says:

    Hi All, We've been experiencing issues on multiple devices running Win 8.1 and 10 with the explorer.exe process preventing from running. This results in a black screen after logon, only salvageable by firing up task manager and killing the appvclient service.
    On further investigation: removing C:windowsexplorer.exe from the HKLMSoftwareMicrosoftAppVClientVirtualizationEnableDynamicVirtualization key prevents the issue from reoccurring. Has anyone experienced this and what affect does removing the explorer.exe
    from that reg key have on appv functionality?

  5. Amayacitta says:

    Still having issues with the profile being locked on log off, it is much better but it still causes us issues. Will log a call with Microsoft now. Definitely App-V as if I disable the App-V service then the profiles load and unload perfectly. 🙁

    1. Amayacitta says:

      If it helps anyone our profile unload issues was resolved with hot fix https://support.microsoft.com/en-us/kb/3146751

      Microsoft refunded our case after finding this for us.

  6. Vamshi710 says:

    Hi,

    we are planning on rolling out Appv 5.1 Client in our company, and based on the technet article “https://technet.microsoft.com/en-us/library/mt346482(v=vs.85).aspx” , “KB 2533623” update is one of the pre-reqs for Appv 5.1 Client on Windows 7 SP1 machines. Is this still the latest pre-req or is “KB 2533623” Superseded by any latest KB? please let us know.

    thanks,
    vamshi.

  7. Ju says:

    Hi,
    Hotfix downloads seems to not be operational at this moment, someone could have a look pls ? :/
    Thx

  8. Lazaro Ravelo says:

    I too still have the issue with the %USERPROFILE%\AppData\Local\Microsoft\Appv\Client\VFS folder being locked by the App-V client on logoff after applying this hotfix.

  9. Jack Fetter says:

    Having an issue, just downloaded 5.1 HF2 today to troubleshoot an issue but it won’t install, says base product is not installed and log shows;

    [12BC:116C][2016-07-18T10:21:13]i105: Detected package: CoreX86Patch target: {B2A6CCDE-5E94-43D8-B47E-A455CEF33C4B}, state: Absent

    But 5.1.86.0 IS installed, both installed and functioning (here’s the registered MSI info);

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{B2A6CCDE-5E94-43D8-B47E-A455CEF33C4B}
    DisplayVersion=5.1.86.0

    5.1 was installed on Windows 7 via WDS deployment, it’s not an upgrade and works fine, been in our environment for many years. Tried to extract MSI from EXE to be sure it’s not an MSI-over-EXE problem and exe launches endless processes but never does anything, seems to be stuck in a loop when run via;

    AppV5.1RTM_Client_KB3139245.exe /Layout /LayoutDir=”C:\Sequences”

    Error log indicates;

    [2230:2234][2016-07-18T10:17:25]e000: Error 0x800700ce: Failed to launch parent process with unelevate disabled: C:\Sequences\App-V 5.1 HF2\AppV5.1RTM_Client_KB3139245.exe
    [2230:2234][2016-07-18T10:17:25]e000: Error 0x800700ce: Failed to launch unelevated process.
    [2230:2234][2016-07-18T10:17:25]e000: Error 0x800700ce: Failed to run per-machine mode.

    I am logged on as an Admin (member of Local Administrators Group).

    1. Jack Fetter says:

      Never mind, exe (patch) can be extracted on Windows 10 machines and resultant MSO installed just fine…

Skip to main content