locked
Windows 10 and App-V 5.1 RRS feed

  • Question

  • I'm testing App-V 5.1 and Windows 10, so far just with Office 2013/2016 using the C2R tool to generate the app-v packages.

    I've been able to use the packages on windows 8.1 successfully however trying to add the client packages with Windows 10 has resulted in errors.

    I have enablepackagescripts set to 1 (with group policy) and powershell execution policy set to remotesigned.

    I started testing with SCCM and then moved into powershell to get a better error description and this is what I get when I try to run the add-appvclientpackage command:

    Add-AppvClientPackage : Embedded Script process exited with an error code indicating failure (return code other than
    0). Please ensure that Embedded Script process can complete successfully and exits with 0.
    Operation attempted: Configure AppV Package.
    AppV Error Code: 100000000C.
    Please consult AppV Client Event Log for more details.
    At line:1 char:1
    + Add-AppvClientPackage -path \\perkinswill.net\pwit\software\applicati ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidResult: (:) [Add-AppvClientPackage], ClientException
        + FullyQualifiedErrorId : ConfigurePackageError,Microsoft.AppV.AppvClientPowerShell.AddAppvPackage

    the event log shows this:

    machine script for event AddPackage with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\441720FC-1500-4EFA-9184-EC61A1610F97\Root\..\Scripts\Integrator.exe"' exited with failure error code: Unknown Win32 Error code: 0x7597. Because Rollback is set to true in the script definition, the current AppV Client operation was rolled back.

    and this:

    Package {d24c3bdd-8fad-44d3-998c-933f8f053682} version {441720fc-1500-4efa-9184-ec61a1610f97} failed configuration in folder 'C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\441720FC-1500-4EFA-9184-EC61A1610F97' with error 0x79100E10-0xC.

    Anyone run into this yet or successfully deployed windows 10 with office in appv?

    Thursday, October 15, 2015 12:50 AM

Answers

All replies

  • I haven't tried it yet because typically, I advise against running Office as a virtual application but in relation to the error.

    What version of the ODT did you try?


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

    Thursday, October 15, 2015 3:04 AM
  • I've tried it in my testlab, office2016 also created with ODT (ProPlusVolumex86)... no issues so far on win10. Are you deploying globally? Are you 100% sure packagescripts is enabled? Check with powershell on you client.
    Thursday, October 15, 2015 7:46 AM
  • I've been able to use the packages on windows 8.1 successfully however trying to add the client packages with Windows 10 has resulted in errors.

    All my App-V packages worked great on Windows 7 until I upgraded to Windows 10, then could not use the App-V client anymore. Lots of errors.

    After removing the SID from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Virtualization\LocalVFSSecuredUsers it was solved.

    Maybe this also works for you. Make sure to make a backup of that key first.



    Twitter | Blog | App-V Deployment Whitepaper | My AppX section
    If you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Thursday, October 15, 2015 8:49 AM
  • I've tried it in my testlab, office2016 also created with ODT (ProPlusVolumex86)... no issues so far on win10. Are you deploying globally? Are you 100% sure packagescripts is enabled? Check with powershell on you client.

    ya package scripts is for sure enabled, get-appvclientconfiguration shows it as 1, I'm deploying globally.

    You created the package with the click to run tool correct?  Are you using windows 10 enterprise?  I have office 2013 volume and 2016 O365 (we have both license methods).

    I might try on my home computer running windows 10 pro.

    Thursday, October 15, 2015 4:22 PM
  • ran some Microsoft updates on the test host.  Works now, thanks for your suggestions!
    Thursday, October 15, 2015 10:11 PM