Now this seems to be a nice solution, but I was wondering whether permanently opening a file path constitutes a security risk.Curt@invincea wrote:Yes, just add OpenFilePath=%Local AppData%\Temp\PDFCreator\Spool. And everything will just work from then on.APMichael wrote:Yes, that works! Thank you very much for the hint.Curt@invincea wrote:Ok, when Sbie first blocks PDF Creator, a failed print job gets stuck in the PDF Creator print queue. From then on, PDF Creator will no longer work. After you dbl-click on SBIE1319 to allow the process to print to file, you must manually clear the print from the print queue. Then PDF Creator will function properly.
Do you see if there is a solution with the OpenFilePath setting possible?
Or is the "real world security impact" of permanently allowing an app such as PDF creator more or less negligible ?
If it is risky, the I would rather allow per session access for PDF creator (which is a slight pain in the ... as you can see above)
Thanks in advance!