Skip to content
Support
  • There are no suggestions because the search field is empty.

Why Assigning Updates to Existing Applications Might Not Work

This article explains why assigning an update to an existing application in Microsoft Intune might not work as expected and explores alternative solutions.

Limitations of App Update Detection

Devicie back catalog app updates use requirements and detections to determine if an application update is applicable to a device. However, these checks have limitations:

  • Context Mismatch: Requirements are only met for applications installed in the same context (user or system) as the update. If the existing application was installed with a different context (e.g., user-installed vs. system-wide deployment), the update won't be triggered.
  • Installer Differences: App detections are typically built for specific installers (e.g., MSI or EXE). If the existing application was installed using a different installer than the update, our detection might not recognise it.
  • Architecture Mismatch: Updates are designed for a specific architecture (32-bit or 64-bit). If the existing application has a different architecture than the update, it won't be compatible.

Common Scenario: VLC Player Update Challenges

Let's consider a real-world example: deploying a new version of VLC player as a required update. Here's why issues might arise:

  • Multiple VLC Versions: VLC doesn't automatically replace older versions if they are installed differently (e.g., installer vs. program file). This can lead to a situation where a user has up to four different VLC versions:
    • 32-bit MSI installer
    • 64-bit MSI installer
    • 32-bit exe
    • 64-bit exe
  • Limited Update Scope: The provided update (MSI 64-bit) can only replace existing installations if they are also 64-bit MSI versions. Here's a breakdown of the limitations:
    • If someone has a 32-bit exe version, installing our update will result in the update installing alongside it rather than replacing it. The same goes for having both 32-bit and 64-bit exe. This would result in up to four VLC versions on the device, which may be the same or different versions.
    • Installing the 64-bit exe won't remove the existing 32-bit exe. It can also coexist with both the 32-bit and 64-bit MSI installer versions.
    • The 32-bit MSI can replace the 32-bit exe, but it won't touch the 64-bit exe or the 32-bit MSI version.
    • Our 64-bit MSI can replace the 64-bit exe, but it won't affect the 32-bit exe or the 32-bit MSI version.

Why Reimaging Can Be Critical

Due to limitations like those encountered with VLC, Intune updates might not successfully patch applications that were not deployed by Intune itself. In such scenarios, reimaging devices becomes a critical step to ensure:

  • Clean Slate: Reimaging erases everything and installs a fresh operating system. This guarantees a clean installation of the application, allowing Intune updates to function as intended.

Alternative Solutions and Next Steps

While reimaging offers the most reliable solution, it might not be feasible in all cases. The customer can explore alternative methods like manual scripts to remove existing versions of applications. Additionally, consider including user prompts as an option for a small number of lingering outdated applications (applications with built-in update mechanisms).

Conclusion

By understanding the limitations of Devicie app update requirements and the importance of a clean installation environment, you can make informed decisions about deploying application updates. If you have further questions or require more specific guidance, consult the Devicie support team for assistance.