"Hi everyone, I am currently using PDF24 Creator and it works great as my default printer. I’ve configured a custom profile (named 'CICCIO') that forces Black & White output and limits DPI to reduce file size.
However, I have a specific requirement: the print job is not triggered by a standard user via browser, but by a local Windows Service running under a different account (likely SYSTEM or a dedicated service user).
In this scenario, the printer no longer 'sees' my custom profile, resulting in high-resolution color prints instead of the desired B&W/low-DPI output.
Is there a way to enforce a global default profile via Registry (e.g., under HKLM or a specific flag like /fo/CICCIO) so that any user—including SYSTEM—is forced to use the 'CICCIO' settings?"
Copy the profile from the HKCU part of the registry to the corresponding HKLM area. This makes the profile visible to all users and even to services.
The profile (CICCIO) is applied correctly when printing from a web browser, but it is completely ignored when the source file is a PDF being printed to the PDF24 virtual printer.
It seems like when a PDF is the source, the driver/backend performs a sort of 'passthrough' that bypasses the B&W and DPI constraints set in the profile, even if the profile is set as default in HKLM. How can I disable this behavior and force the 'CICCIO' profile processing for PDF sources as well?
The profile is only in
ComputerHKEY_LOCAL_MACHINESOFTWAREWOW6432NodePDFPrint
(neverthenless che key installdir is C:Program Files (x86)PDF24)