The application was not detected after installation completed successfully (0x87D1041C) - Zoom

[Rugved_Vaidya]

Hello,
I am trying to Deploy Zoom Meetings using the mentioned Requirement and Detection Rule, 

Problem is the App deployment is able to update the outdated Zoom app present in the target machines but returning with the failed output and also able to identify if the Requirement rule is met or not (Not applicable where Zoom is not present),

Is there anything need to update in Rules ?

[#2]

Hi @Rugved_Vaidya,

The image you provided shows a file-based requirement rule with the path set to "C:\Users%username%\AppData\Roaming" and the file/folder set to “Zoom,” with the property set to “File or folder exists.”

If Zoom is not detected after installation, it's possible that the specified file path or folder doesn't exist post-installation. Verify the Zoom application's installation path on target machines and adjust the detection rule accordingly.

Please click Mark as Best Response & Like if my post helped you to solve your issue.
This will help others to find the correct solution easily. It also closes the item.

If the post was useful in other ways, please consider giving it Like.

Kindest regards,

Leon Pavesic
(LinkedIn)

[#3]

Have you tried using registry and display version as the detection logic instead?

[#4]

Just to be 100% sure as I couldnt find it in your screenshots.... i assume the install behavior is configured to install as user.

[#5]

Yes, Install behavior is set to User

[#6]

I checked the path on Target machine and its correct as set for Requirement / Detection rule

[#7]

No, can you please suggest any reference or article ?

[#8]

Here is the official link - https://learn.microsoft.com/en-us/mem/intune/apps/apps-win32-add#step-4-detection-rules

[#9 · Accepted solution]

Thanks for the article, i have tried Registry method got same result but using MSI method at detection rule was success, used the following detection rule

 

[#10]

The registry under the HKLM uninstall key will use the same MSI product code. It should have worked, but if MSI based detection is working for you then that should be good enough.