Update:
The corrupt Windows user was the culprit in my instance. Since I created a new windows user and have accessed QB from that user I have not seen a single encryption error.
