Comment 4 for bug 194798

Just wanted to update everyone here. This issue is a result of a setuid issue whereby in a previous build one executable had been setuid root and in this build a different executable had been setuid root and it wasn't handled properly. We are working with Parallels to resolve this issue (as well as another general error reported by their user base) and removing ALL setuid executables.

-Brian