When you installed Poser, you had a choice about where to locate your main runtime. One of those choices was to put it in the tradiitonal place, inside the Poser folder within Program Files. If you did that, you may have issues of various kinds.

Newer versions of Windows (and some AV programs) are really anal about keeping an eye out for programs that try to write into the folders of other programs, especially in Program Files.

As a result, we have situations like Poser content installers that can't install content, because they are trying to write into the Program Files Poser folder and the security apps think that's a virus trying to install itself. If you stop and think about it, pretending you don't know what program is running, and just watch what it is doing, Poser content installation looks a lot like virus infestation. Python scripts are being installed, files are being overwritten, etc.

Now I don't actually know how the QMgr does its thing, but if you think about how a scene would be distributed, clearly it involves moving content from the main Poser app to the distributed renderers. The distributed renderers do not have a copy of the content files (or may not), and so they will receive stuff from Poser to use during the render. This is a lot like installing content, but more dynamic.

Of course, if you installed your main runtime in the newer approved places, then this type of thing should not be a problem.

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)