Thank you for reporting the problem. It turned out that we have a bug, which blocks this from working correctly. The bug will be fixed in the next release.
As a workaround, you can mark globalzpo.exe as safe in Executables View. This should silence this rule.