I’ve tried your method, but I think this causes issues.
With the added Requirement rule, it prevents apps from being installed initially.
So if a user deletes the app or a new user is signing in for the first time, this Win32 app will never install.
It seems that because the requirement can’t find the app, so can’t see the version, it never installs.

How have you solved this?
For new users, I created a Power Automate Flow. When a new user is added, they get added to a group. This group has apps assigned to it, but these Win32 app deployments do not have the additional requirement for versioning.
After a few days, they are removed from the group and placed into a group with all other existing users. This other group has Win32 apps assigned with the requirement rule.

This is really only a partial solution. If a user signs into a different machine or accidentally deletes a required app, the apps will never install.

At least in MECM it works like this, I expect same in Intune. Why even there would be that ‘Associate with 32-bit app’ switch then, when you avoid it by using %ProgramFilesx(86)%?

I use a simple custom detection script for this
$version = (Get-Item ‘c:\Program Files\VideoLAN\VLC\vlc.exe’).VersionInfo
if ([version]::Parse($version.FileVersion) -lt [version]::Parse(‘3.0.16’))
{ Write-Host “true” }
else
{ Write-Host “false” }
Still searching for solution in the scenario:
1. a software is installed from Intune
2. software update with version detection is deployed from intune and software is updated
3. client reinstalls software with older version
4. detection script won’t check installed version – this is something I don’t know how to overcome. how to force intune to check periodically if software match version with detection script and if not take an action to update it.

Hi Ľuboš,

That really depends on your needs. The current Supersedence feature doesn’t fir our needs, so we’re still using above workaround.