Community
I recall seeing some very similar posts within the last few months (maybe years). I don't recall seeing that any of them were ever resolved. If you are a Subscription customer, this is definitely one you should create a technical support case for. (I just realized that being "non-current", this is probably not an option for you.)
If repair or re-install had no effect, you might try repairing and/or unistalling/re-installing .Net framework stuff. (I'll leave the details for that to others who are more qualified than me.)