Orphaned Printers on Windows 7 64-bit

[71SoCal]

I'm getting orphaned printers on Windows 7 64-bit OS. I'm using the RemoveOrphanPrinters call, which works for 32-bit operating systems, but it seems to be ignored on 64-bit systems.

Has anyone seen this, or have a suggestion on how to deal with it?

Thanks...

[Tracker Supp-Stefan]

Hello 71SoCal,

I have asked the guys responsible for the Drivers SDKs to have a look at this and they will advise shortly.

Regards,
Stefan

[71SoCal]

Just wanted to check back to see if you've been able to determine if this is an issue with the PDF driver. Again, we're only seeing this on 64-bit systems. I'll look for your response.

Thanks...

[Paul - Tracker Supp]

HI 71SoCal,

the project manager who usually handles this forum and topic is not available this week. I've asked for someone else on the dev team to jump in on this one. You should have an answer soon.

Sorry for the inconvenience.

[Paul - Tracker Supp]

Hi again 71SoCal

I'm sorry for the delay here. It seems we do need our project manager on this. He will be available next week. Your patience in this is appreciated.

[71SoCal]

Just wanted to check back to see if anything has been discussed on this issue...

[John - Tracker Supp]

Hi,

we have tested again here and I am afraid despite our best efforts we cannot reproduce this - if we are going to take any further we are going to need some help in reproducing - perhaps a sample app ready to run and any further info you can provide.

Thanks

[71SoCal]

I have written a simple console test application that first attempts to clear any orphaned printers, then it will create a new printer. When prompted, use Task Manager to kill the application. Verify that an orphaned printer named MyPDFPrinter has been left behind.

Now if you run the application again, it will clean up that orphaned printer (on NON-Windows 7 machines), but it does NOT clean up the orphaned printer on Windows 7 64-bit machines.

Please test this and confirm whether the orphaned printer was cleaned up, or not on a Windows 7 64-bit environment.

Thanks...

[Ivan - Tracker Software]

Even using your example, I cannot reproduce the problem: when your application has been launched second time, orphaned printer, left after killing first instance via Task Manager goes away.

I will try to reproduce problem and hope I'll be able to do this.

[71SoCal]

Just to confirm, you're running this on a Windows 7 64-bit machine?

[John - Tracker Supp]

Yes