@AlexC84,
Sorry I didn't respond sooner but I wanted to test out the new update (2301) before responding. I've only tested it on one computer so far but I was able to test a bunch of files that were throwing the error on 2212. They loaded and ran without any errors after the 2301 update was installed so it appears to have fixed the problem. If you find out otherwise, please post back here.