If you look through posts here there is a lot said about it.
I have posted all my findings here in the past.

As others said:
>
There are still some situations, where printerSetCurrent() fails.
<

I have seen this on the last 3-4 versions of Windows and Paradox 9 and up.
Various combinations. The worst part is that I have had machines where it
was fine for years, no major Windows version change or Paradox version change
and it just starts to fail. And oddly when it starts, it seemed to work sometimes,
then fail more frequently to being unusable. I once waiting about 12 hours
for the spinning to come back, never did.

I had one instance where a PC reboot fixed it every time. Sometimes rolling
back Windows updates fixed it. Sometimes removing all printers and loading
them back one by one fixes it. Wipe drive and reload windows always fixed
it. Reinstalling Paradox never fixed it. 

The “nvidia graphics driver” comment is interesting, have not heard that,
but maybe changing that driver might shake it loose?

When this first started, I used sendkeys to change printers via the menu.
Horrible, but worked. The sendkeys slowly failed for various reasons.

My plan B was to (as others said) print to PDF or other static printer name,
then print that PDF to where ever need.

I use Adobe Acrobat, you must alter some on the fly registry setting to control
the output file name. Not the worst, I build a pdox library to handle it,
and have had to update it when Windows or Adobe version change.

Note: I think (after searching) the current printer is stored in memory,
not in registry and not anywhere in a file. 


FYI
This newsgroup is migrating to 
https://groups.google.com/g/thedbcommunity
feel free to post there

"Ivan" <ivan.moro@web.de> wrote:
>I've read a message about Pdox11:
>
>    https://www.tek-tips.com/viewthread.cfm?qid=3D1820341
>
>that a user has problems with pdox11 on win11 with the method
>
>    printerSetCurrent()
>
>This function call allways hanging. Can somebody confirm this?
>
>I'm using Pdox9 and use this function too (within each print, to set the

>desired printer). I myself don't use Win11 by now, but have customers, who
=
>
>use it. No one reports, that he can't print.
>
>Are there any experiences with it?
>
>Ivan 
>
>
>---
>Diese E-Mail wurde von AVG auf Viren gepr=C3=BCft.
>http://www.avg.com
>