Win10 Relevance not working

Update: Simple syntax error with spacing, sorry about that. Working now

Hey guys, this seems like a weird one. If I do a simple file exists on a bunch of my win10 machines, it is not showing up as relevant. I know that it is relevant, so I cleared out the relevance, ran the job to move the file that exists, and it shows Failed; however, it did move the file. Any help would be appreciated, not sure if this is a WOW64 redirection thing or not.

Bes Version 10.0.3.66

My relevance:
exists file “c:\program files\vmware\vmwaretools\vmwareresolutionset.exe”

actionscript:
move “c:\program files\vmware\vmwaretools\vmwareresolutionset.exe” “c:\temp\vmwareresolutionset.exe”

That would be my guess as well (wow64). Disable the wow64 and test it again:
action uses wow64 redirection {not x64 of operating system}

also for the relevance try: exist x64 file “c:\program files\vmware\vmwaretools\vmwareresolutionset.exe”

1 Like