I have PDF Creator Plus. I recently upgraded to windows 10. The next time I tried to create a pdf, I foolishly accepted the PDF Creator offer to upgrade to 2.1.2. Ever since then, I have been getting the Internal Ghostscript error message. I uninstalled 2.1.2 and went back to 2.1.1, but I still keep getting the error.
It says I can find additional information in the log file. Where is that?
If it makes any difference, I also get a “Setup Helper Has stopped working” error. I can bypass it and get the 2.1.1 installed, but it doesn’t work.
you can view the log file by going to the debug section of the PDFCreator application settings and it also gets stored as a text file in your %USERPROFILE\appdata\local\PDFCreator path.
There have been reports by other users about issues with windows 10 (setup not installng the printer) wich we are currently still investigating.
perhaps there was a problem with the ghostscript installation, please try if installing http://downloads.ghostscript.com/public/gs914w32.exe directly to your PDFCreator folder solves the problem, if not please set the logging level to “trace” in the PDFCreator application settings and print anything, then send the resulting log to support@pdfforge.org.
I tried the ghostscript download link from Robin above (two times), but I keep getting the error message
“Installer integrity check has failed. Common causes include incomplete download and damaged media. Contact the installer’s author to obtain a new copy.”
Another thing: I can look in the print queue for PDF Creator and there are jobs sitting there. They will never print, but I can clear the queue. Likewise for PDF Architect 2.0 and 3.0 - both get jobs stuck in the queue. I can delete them, but I can’t get them to print.
I am afraid it is a bit hard to troubleshoot without being able to look at your system, but you will need a working copy of ghostscript, please try redownloading it, if it permanently failes there is probably an issue with your connection, Since Ghostscript does the actual .ps to PDF conversion, it makes sence that the jobs are now stuck in the queue. Jobs getting stuck in the PDF Architect queue has never been reported before, do you get any error messages when trying to convert with PDF Architect?