locked
Issue installing Hotfix 1 for 5.0 RTM client RRS feed

  • Question

  • I cannot apply the App-V 5.0 Hotfix 1 (KB2799153) to a 5.0 RTM client (5.0.285.0) installed via MSI.

    However, applying the hotfix to a manual installed client installed via the EXE installer does work.

    Error message:

    • Full GUI install: "Setup failed while scanning the system for prerequisites. This update only applies to App-V client version 5.0.285.0. The App-V client is not present on this computer."
    • Silent install (logfile):
    [0D34:04AC][2013-04-05T17:01:56]: Burn v3.6.2803.0, Windows v6.1 (Build 7601: Service Pack 1), path: Z:\App-V Client 5.x (Microsoft)\Source\HF1\AppV5.0-Client-KB2799153-x86-and-x64.exe, cmdline: '/q /log "C:\Logfiles\Install\Tmpinst\appv_client_5_HF1.log" -burn.unelevated BurnPipe.{0B7A32DA-605A-4B0F-83A1-C441A5A74F90} {95DC714C-F6F4-4EF0-9AA1-91336B84A610} 5060'
    [0D34:04AC][2013-04-05T17:01:56]: Initializing string variable 'IsBundlePatch' to value 'patch'
    [0D34:04AC][2013-04-05T17:01:56]: Initializing string variable 'AppvInstallType' to value 'client'
    [0D34:04AC][2013-04-05T17:01:56]: Initializing version variable 'TargetBaselineVersion' to value '5.0.285.0'
    [0D34:04AC][2013-04-05T17:01:56]: Setting string variable 'WixBundleLog' to value 'C:\Logfiles\Install\Tmpinst\appv_client_5_HF1.log'
    Setting string variable 'WixBundleOriginalSource' to value 'Z:\App-V Client 5.x (Microsoft)\Source\HF1\AppV5.0-Client-KB2799153-x86-and-x64.exe'
    Setting string variable 'WixBundleName' to value 'Hotfix for Microsoft Application Virtualization (App-V) Client 5.0 (KB2799153)'
    AppvUX: Received install request: Going to install mode
    AppvUX: Detected install type: client
    AppvUX: Did not detect install type: client_rds
    AppvUX: Detected install type: client
    AppvUX: Detected install type: client
    Setting string variable 'MIGRATIONMODE' to value '1'
    Detect 12 packages
    Detected package: CoreX86Patch, state: Absent, cached: None
    Detected package: EnLangpackX86Patch, state: Absent, cached: None
    Detected package: DeLangpackX86Patch, state: Absent, cached: None
    Detected package: JaLangpackX86Patch, state: Absent, cached: None
    Detected package: ZhCnLangpackX86Patch, state: Absent, cached: None
    Detected package: ZhTwLangpackX86Patch, state: Absent, cached: None
    Detected package: CoreX64Patch, state: Absent, cached: None
    Detected package: CoreX64Patch target: {7DAB7C80-5E5A-4924-8F9F-B9C2BE53DFF7}, state: Absent
    Detected package: EnLangpackX64Patch, state: Absent, cached: None
    Detected package: DeLangpackX64Patch, state: Absent, cached: None
    Detected package: JaLangpackX64Patch, state: Absent, cached: None
    Detected package: ZhCnLangpackX64Patch, state: Absent, cached: None
    Detected package: ZhTwLangpackX64Patch, state: Absent, cached: None
    AppvUX: Detected install type: patch
    AppvUX: This update does not apply to this system.
    AppvUX: Detection has indicated this product cannot be installed. Exiting installer.
    Detect complete, result: 0x0
    Shutting down, exit code: 0x643
    AppvUX: Shutting down setup UI
    Variable: AppvInstallType = client
    Variable: IsBundlePatch = patch
    Variable: MIGRATIONMODE = 1
    Variable: TargetBaselineVersion = 5.0.285.0
    Variable: TerminalServer = 0
    Variable: WixBundleAction = 4
    Variable: WixBundleElevated = 1
    Variable: WixBundleLog = C:\Logfiles\Install\Tmpinst\appv_client_5_HF1.log
    Variable: WixBundleName = Hotfix for Microsoft Application Virtualization (App-V) Client 5.0 (KB2799153)
    Variable: WixBundleOriginalSource = Z:\App-V Client 5.x (Microsoft)\Source\HF1\AppV5.0-Client-KB2799153-x86-and-x64.exe
    Variable: WixBundleProviderKey = {7fe600e2-334e-4dcd-8bb5-85378a4a3686}
    Variable: WixBundleTag = 3E4877E3-6A75-4605-8C8A-914B2EFBFF42
    Exit code: 0x643, restarting: No

    Environment info:

    Win7 x64 SP1 as client OS with App-V 5.0 x64 installed (appv_client_MSI_x64.msi).

    App-V 5.0 language pack installed: appv_client_LP_enus_x64.msi

    Merged this registry file to apply all required settings to the client;

    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Publishing\Servers\1]
    "Name"="ServerName"
    "URL"="http://ServerName:83
    "GlobalEnabled"=dword:00000000
    "GlobalLogonRefresh"=dword:00000000
    "GlobalPeriodicRefreshInterval"=dword:00000000
    "GlobalPeriodicRefreshIntervalUnit"=dword:00000001
    "UserEnabled"=dword:00000001
    "UserLogonRefresh"=dword:00000001
    "UserPeriodicRefreshInterval"=dword:00000006
    "UserPeriodicRefreshIntervalUnit"=dword:00000001
    
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Coexistence]
    "MigrationMode"=dword:00000001
    

    Is there a workaround to install hotfix 1 to a 5.0 client installed with the MSI installer?


    Friday, April 5, 2013 3:05 PM

Answers

  • Thanks for the answer, but with the release of SP1 this hotfix has become more or less obsolete.
    • Proposed as answer by znack Tuesday, May 14, 2013 11:40 AM
    • Marked as answer by David WoltersModerator Wednesday, June 12, 2013 3:00 PM
    Tuesday, May 14, 2013 9:43 AM

All replies

  • How did you deploy the MSI? Did you make any changes? Did you apply a transform? Did you install the pre-reqs before the installation of the client?

    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

    Friday, April 5, 2013 7:55 PM
  • Prereqs are installed before the RTM client was installed (PoSh3.0, VC++2010).

    The RTM client is installed with some parameters (can post them tomorrow) and a regfile-import for other settings. No transformfile is used.

    But I get the same behaviour when I install the RTM MSI without extra parameters. In short; install RTM client without extra switches, reboot the machine, apply HF1 == fail! 

    I tried with and without AppV 4.6 SP2 present on the client machine, same result.

    Sunday, April 7, 2013 7:50 PM
  • Hi there,

    I had this problem also when trying to install this patch on any device where I had deployed the App-V client through Config Manager 2012 SP1.

    I was able to work around this by running "AppV5.0-Client-KB2799153-x86-and-x64.exe /REPAIR"

    Although it doesn't make much sense for it to not be able to install, but be able to repair despite not being installed, this did indeed update the version of the client to 5.0.515.0 and shows the hotfix correctly in the installed updates on the system.

    Monday, May 13, 2013 8:58 PM
  • Thanks for the answer, but with the release of SP1 this hotfix has become more or less obsolete.
    • Proposed as answer by znack Tuesday, May 14, 2013 11:40 AM
    • Marked as answer by David WoltersModerator Wednesday, June 12, 2013 3:00 PM
    Tuesday, May 14, 2013 9:43 AM