locked
AppV 5 Package deployed with SCCM on W10 1709 Client don’t work RRS feed

  • Question

  • When we deploy an AppV 5 Package with SCCM 1706 to Windows 10 1709, the Application is not working properly. It seem’s, only if something is Sequenced in [{Common AppData}]

    When we remove and then add the Package with the Command prompt, it’s working.

    The KB4074588 is alredy installed, also the Regkey ‘RegistryCompatibilityMode’.

    Any Idee??

    Friday, February 23, 2018 12:59 PM

All replies

  • If you have the KB installed, then no need to set the registry. The update itself will take care.

    Not Working properly means? Could you provide more information. Eventvwr log error?


    (Please click on Vote as Helpful and/or Mark as Answer, if it has helped you.)

    MVP - Windows and Devices for IT

    app2pack.blogspot.com: app2pack.blogspot.com

    Monday, February 26, 2018 9:25 AM
  • There are/where two different issues on 1703 and onwards… the creg issue, which has been resolved on 1709 after installing KB4074588. This CU basically puts appv back to vreg by default. Application affected would not start or throw errors, mostly appv4 converted packages, issues with connection groups and hooking with separate appv packages. The update for 1703 is KB4077528
    The second issue which is afaik only on 1709 is when you deploy with Config Manager. It's related to the fact that config manager deploys under system account. If you manually add with powershell, you use your admin account with elevated rights. The issue is related to the registry.dat file which needs to be copied down to programdata.... the file would disappear as soon as you publish the package, which would break it. Are facing this issue? I'm not sure but this sounds like it is/was also related to the vreg -> creg switch (can anyone confirm). As Vig points out setting RegistryCompatibilityMode got obsolete with KB4074588. You can put cReg back on by setting ContainerRegistryEnabled (which I do not recommend)……. So which issue are you facing :)?

    Also keep in mind, although Config Manager 1706 is backwards compatible with 1709... Conif Manager 1710 fully supports 1709!


    Roy Essers


    • Edited by Roy Essers Saturday, March 3, 2018 7:39 PM
    Saturday, March 3, 2018 7:07 PM