Is this the only policy that doesn't apply? Have you tried creating a new policy that does something else? Preferably something that doesn't require access to a file, such as disabling the Run command. Or do you have others in place that already work?
I'd certainly start with Group Policy Modelling to see what's going wrong.
Maybe this link will help:
Using Group Policy Modeling and Group Policy Results to Evaluate Group Policy Settings