Hm, the odd is, the pages are rendered, and then send to the printer. As far as I understand, the picture is rendered before preview and later send or shown. At least the GDI+ render events / methods of the listener are not called after the Preview is visible under normal use.
I do not know if the GDI+ sort of remembers the commands used to plot the drawing and rerun those commands on new output device or just have a picture stored and copy that to output.

>In my case, the GDI resources are exhausted regardless of the selected printer. I replicated the issue using multiple printers, including Microsoft Print to PDF.
>I've read before the docs you suggested. It says that the issue originated with KB5000809 and it was fixed in KB5001565, but in my case I had to actually uninstall KB5000808 (after uninstalling KB5001567 that was supposed to fix it).
>My suspicion is that there may be multiple bugs introduced with the KB updates attempting to fix the printer driver conflicts. The GDI problem could be one of these collateral bugs.
>
>>Then we know it's while talking to the printer. Any difference using other printer? PDF, Windows WPS, something?
>>
>>Check the printer driver type https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-1803
>>Search type in the doc to see how to identify.
>>
>>>I tried that several times. PREVIEW does not create the problem.
>>>
>>>>Does it make a difference if you
>>>>

>>>>REPORT FORM (m.lcRpt) TO PRINTER PROMPT PREVIEW 
>>>>

>>>>
>>>>and not print? Just multiple times preview?
>>>>
>>>>off topic:
>>>>On my machine the thing would have produced instant BSOD. Showing Printer dialog with the right printer in focus was enough ...