What work is being done by pdfordge to determine root cause of the issue described in the hyperlink you referenced?
The words "it seems that this is caused by a bug in the .NET framework" sounds to me like pdforge is guessing it's a .NET bug - they don't really know what is causing the issue, but only guessing it's .NET because "these versions have worked for years without this error".
Please keep in mind, .NET security updates are not the only updates being installed on workstations around the world. There are numerous updates being installed (JRE, .NET, OS, ect.) . Has pdforge reached out to Microsoft for any assistance/direction on this issue?
I understand there is a workaround available by installing a newer version of PDFCreator, but that is not an easy task for my company to do, since there are requirements and processes that must be followed to do a simple upgrade. It would be helpful if pdforge could provide a better level of support by giving more details on what specially they believe is the root cause: which Microsoft KB is causing the issue.