Windows 10 includes a new Print to PDF feature that can can be used to replace PDFCreator functionality with a native solution provided by the OS. This is a welcome change by most developers, however there are some differences between the two products and as such, limitations may exist in one that do not exist in the other.

One difference between these two products is that the Microsoft Print to PDF feature does not appear to allow the use of a comma in the file name or in the path to where the file is generated at while PDFCreator appears to allow it. When using the Print to PDF feature the file is generated as a 0 kb file.

This may seem trivial but it can be hard to troubleshoot if you are unaware of this behavior.

If it is a requirement to use a comma in the file name, and also a requirement to use the Microsoft Print to PDF feature, then this limitation can be worked around by printing to a temporary directory that does not include a comma while using a file name that also does not include a comma. Then move the file using MOVE DOCUMENT after it has been generated. In this way, the file can be renamed to include the comma and it can be placed in a folder that includes a comma.