<Cross-posted to Automation channel> Has anyone noticed any problems using Chocolatey with App Layered images? When I uninstall or upgrade any Chocolatey packages, the original folder simply stays put on the C: drive. So if I upgrade Paint dotNet from 5.1.4 to 5.1.6, whether through removal/reinstall or simple upgrade, it stays on version 5.1.4. Is this simply because Chocolatey and App Layering can't work together? The original install goes fine - it is the subsequent change or removal that fails.

Are you changing it in a new layer, a layer version, the os layer? Im assuming the os layer since it sounds like a universal app. I think that should work fine as long as you arent using user layets and didnt get those apps installed in the user layer.

It's when the user updates their app versions, so in general use. There's no user layer in play. The users here are responsible for updating the apps themselves they've installed via the package managers (so they have to go and run the choco update themselves). Just when it finishes, the package manager thinks everything is updated but when the user runs the app it still shows the same version. Also, during the update process, the folder in c:\Program Files never gets deleted (which it should, it should be deleted and recreated). I think I'm coming to the conclusion that using App Layering along with a solution that allows the users to update the applications on their device isn't a good idea

Are the persistent desktops? Or do users upgrade every logon?

Persistent. Checking on the App Layering setup

Then your vdas should just be normal vms

Something odd going off then. Upgrade works fine on the image not using App Layering but fails on the one that does. Unless there's some other delta I've missed....hmmmm

Good to know. Computing always makes sense in the end.

It's always much easier when it actually gives you an error to work with, but you can't have everything 🙂