App-v 5.1 SP3 application during supersedence handling, if ccmcache cleared downloads only User & Deployment Config XML files and does not download.appv file


Hi All,

We are currently deploying App-v 5.1 SP3 applications using SCCM 1910 BUILD.

I have observed that on a device where if old application let’s say Inhouse_TestApp_1.0 app is installed and later if we delete ccmcache from the device. Later in the day if we uninstall Inhouse_TestApp_1.0 on the same device then it fails to uninstall since when we recheck ccmcsche content of same 1.0 application it has only downloaded Deploymentsconfiguration.xml and UserConfiguration.xml file and doesn’t download .appv file leading App-v package failing to uninstall.


CAN YOU PLEASE HELP HOW THIS SITUATION CAN BE AVOIDED? and enable complete content is copied if it is ccmcache is deleted.



Naushad Ali T D


Answers ( 4 )


    Hi Anoop, thanks for your quick response.
    My query is more regarding appv application content downloads under ccmcache on Client devices.
    Basically, app-v applications in SCCM are packaged with output files like DeploymentConfiguration.xml, UserConfiguration.xml & .app-v file.
    But when we clear down ccmache and when we try uninstalling installed app-v app SCCM Only downloads two .XML file and doesn’t download .appv file.

    This is leading to app-v application failing to uninstall since SCCM Deployment type uninstall parameters set with remove-appvpackage pointing to .app-v file on the machine.
    This is currently a wide spread issues since our client is running script to clear ccmcache to gain space which is causing app-v upgrades & supersedence for older installed app-v app failing since no ccmcache content on them.
    Hope that’s enough description 🙂

    Naushad Ali


      As I mentioned above. I don’t think any active investment from Microsoft side in this part (AppV).

      In my experience I have many known issues like this. And these issues are overcome by organisations using powershell scripts.

      It seems to me you need to continue using the same scripts to manage these.

      Other option is to raise a ticket with Microsoft to raise an official known issue for this.

      Best answer

    Any Update on this please? Otherwise pls close the thread


    I don’t have an answer to this question.

    But I can provide some hints – I heard many issues with app-v versions and SCCM.

    Most of these issues are handled using custom PowerShell scripts.

    One of the examples is

Leave an answer

Sorry, you do not have permission to answer to this question .