Since the beginning of May, we have seen an increasing number of one error type (called TaskCanceledException) across all versions of PDFCreator since the 2.x versions. As these versions have worked for years without this error, it seems that this is caused by a bug in the .Net framework that was introduced with a Windows update.
The GDPR comes into force and we made adaptions to our terms and conditions.
Shortly after the latest PDFCreator release we are also releasing a new PDFCreator Server version.
With PDFCreator 3.2.0 we are the releasing another feature update for our last years redesigned PDFCreator.
We're looking back to a succesfull product development and want to complete the year with another highlight. Our last release was a complete enhanced redesign of our world famous PDFCreator. Now we have added some brand new features to inspire your workflows.
We proudly present the major release 3.0. It's a milestone in the history of PDFCreator. Being the very first accessible application for PDF conversion, PDFCreator is assisting you for more than 15 years now.
For the last few months, we have worked hard on PDFCreator 3.0 to make the user interface more intuitive and easier to use while keeping the extensive functionality of PDFCreator as you know it. Now we would like to hear your opinion on the work to see if you agree or we have forgot or misjudged something you are using intesively. We would like to have any many testers as possible, so feel free to install the beta version and give us your feedback. You can download the beta version here: http://go.pdfforge.org/pdfcreator3-beta
Like a lot of users already noticed, we have published the maintenance release PDFCreator 2.5.3 last week.
We would like to encourage PDFCreator Server users to install the update as soon at conveniently possible
The whole pdfforge team has to apologize for a sensitive bug in PDFCreator 2.5.0.
When using the e-mail client action with Microsoft Outlook, the e-mail address of one of our developers was always set as recipient.
We fixed that bug in PDFCreator 2.5.1 and would like to ask you to update as soon as possible!