It's really only the printer that changed, nothing else related our app, Sumatra, the OS or whatever and I can reproduce that error with the same printer on my own laptop using different verison of Windows, as long as my settings as well use SumatraPDF. One of my customers recently changed its printer from some small business HP device to a Konica Minolta bizhub C658 and starting with that we recognized printing errors in the special case a PDF is printed using the PDF Viewer SumatraPDF on the command line. This approach worked quite well for some years now. Sometimes this simply includes executing ShellExecute with the 'print' verb and let Windows handle everythign else, sometimes we directly execute apps using a specially configured command line etc. Because we need to support various formats, the currently implemented approach is to set default printer settings for the current user in Windows to the settings we need and afterwards use whatever native application is able to print some format. Thos different settings contain the paper bin to use and the duplex mode, if any at all.

I'm the developer of an application which supports automatic printing of files of various formats with different settings in some very special context.

Sumatra pdf printer