I think it goes beyond the printer.

In locking with the user, Winprint2 had been used.

In my case I had not triggered any printing, although contained instructions in the program.

I did searches and changes in records, I switched several times between local and remote access until the program crashed this time during CTRL + F5 and there it was as a child.

It was this, that caught my attention and I wondered if regardless of printer use the runtime, it calls this process child.