Windows enterprise app updateSolved

I’ve seen apps update automatically when they’re deployed through the required apps policy. That usually keeps devices aligned with the latest version. Did you try assigning it that way?

Hi @ethan_,

What you have done can work. When you replace the installer within the same app entry, devices typically pick up the update during their next scan cycle. The catch is that this depends on when each device checks in and how the app is detected, which is why the behavior can feel inconsistent.

For a more controlled rollout, the better approach is to treat the update as a new version altogether. Upload it as a separate app entry, deploy it alongside the existing one, and once you are confident the upgrade is complete, remove the older version. This way, you avoid any confusion around versions and get much clearer visibility into how the rollout is progressing.

Regards,
Sienna Carter
Hexnode UEM

Also worth keeping in mind, if the app has its own auto-update feature, it’s better to turn that off in managed environments. Otherwise, you’ve got the app updating itself while Hexnode is trying to enforce a version, and that overlap can get messy.

I’ve tried both approaches, and honestly, updating within the same app entry works, but it’s not something I’d rely on at scale. Some devices pick it up right after a scan, others take their time depending on check-in frequency. Using a new app entry gives you way more control. It’s especially useful if you’re rolling things out gradually.