Hi Bruce,
I'm a d3/win app developer for 20+ years and have migrated my dev & released systems seamlessly across every d3 release from AP/OA!! The only time I had to do some 'work' [and it was a little] was in moving from R83 to AP. Now on d3v9; no new issues. Just better, and faster.
I currently have my dev system on W10/64 bit and deployed systems on W2018/64. All fine.
Now, in terms of your printer issue; a lot depends upon how you setup d3 to print. I always use NTPrint via coldstart and associate form queue[s]. The ONLY time I've had trouble printing is when the printer is a GDI printer. I've found that a generic HP Laserjet 4 PCI driver will work if the "better" or "more complex" manufacturers driver will not play nice. I also sometime had to alter the data type within the server's driver instance to RAW. But I never got blank pages.
What I did get was blank pages between jobs which I was never able to totally eradicate.
So now to Printwizard... My latest app is a true browser-based system built using designbais; and for certain sets of printed output going via the browser just was not on. I had to print 'centrally' and I did not want the hassles of setting up printers, NTprint etc. So I settled on Printwizard; which is fantastic. So, let me clear a few things up for you:
1. As Bob said Pritnwiz does not need a server of it's own. It happily co-exists on my W10/64 desktop dev system; as well as deployed W2018/64 systems
2. It is fast and does not consume much resource.
3. IMHO, it is true that the product is hard to get your head around [sorry Bob] as it is soo big and potentially complex. That said, Bob is great at support, and extremely patient and helpful. I probably use < 30% of it's abilities.
I hope that helps guide you onto the right path, no matter whether you wish to pursue direct d3 printing; or utilise Printwiz.
Cheers