No, I don’t think so. We’ve received a couple reports of this and we’re not completely sure why.
One user was using an earlier release of the 3.0 beta and using 18.104.22.168 fixed it for him
Another ended up reformatting his machine for other reasons and then 22.214.171.124 worked fine.
You and another user are having this issue and I can’t seem to figure out why.
So we’ve had about 4 cases of this. How did you do the install? Did you install over an existing SGP2 or did you install in a different folder? Do you have default profiles in place?