Engineers have determined what is happening here. A program called Reflectant (Mfg. Edgesight), has a dll called rsl.dll that we use for injection loading. It lives in the SYSTEM32 directory, and it is necessary for it to be in that directory so that Winlogon can load it as a notification DLL. It also needs to be there because it makes it much easier for the driver to initiate the loading of rsl.dll. It doesn't need to know or care where the Agent was installed because it knows that rsl.dll will always be in the path.

However, Roxio also has a dll named rsl.dll. It resides in a directory under Program Files\Common Files\Roxio Shared that they append to the PATH environment variable as part of their installation. When loading this library, they forgo a fully-qualified path because they know that it's in the path. Unfortunately, SYSTEM32 is in the path first, which means that all they succeed in doing is loading our rsl.dll, causing the issue to occur.

I think you need to talk to Roxio on this one - those of us who answer are simply fellow-users of the product.

http://www.roxio.com/enu/support/default.html

If it won't take your login (which should be the same one you used here), come back and let us know, it give us more documentation. <grumble> ("improvement" in action - or is that "improvement inaction"?)

Lynn