That to me is pretty strange, as normally it is because of the changed processes/components in a program update that might cause the blocking experienced. So when dropping back to the previous avast version, those processes/components would be as they were and appear to pass through OA without problem.

To me that tends to conform OA blocking the updated components, rather than there being a problem with the latest beta. Otherwise we would be seeing many more such problems in the forums by the avast beta and OA users and we aren’t seeing this.

I’m convinced if you installed the beta and then reinstalled OA it would detect the programs/component currently installed in its learning mode without problem. Unfortunately the OA users haven’t graced us with their presence.