As I recall it, it did not. Would be unusual for security software anyway. After switching to another account, it tried to start, failed and spawned the said error message. It made no difference whether it was an administrator or an user-account: the first one that was addressed always worked fine, while the second failed. There was actually a work around: after getting the error message I switched file-guard off and fired it up manually, then it got working fine again.