Multiplicity Winlogon dll is NOT running

I am running Windows 7 64 bit pro and I have random issues with the Multiplicity software, like being stuck on the secondary monitor.

 

  It's very frustrating and every time I troubleshoot it says:

 

  Multiplicity Winlogon dll is NOT running

 

  There is a big red X and I have no ability to do anything about it. I found a .bat file online and it did not work. Also the path to the registry is wrong. There is a reference to a thinkdesk folder, but that doesn't exist, There is also no Path registry entry in the Multiplicity folder in HKLM. I put on there and made a string value that sets the path to the program folder, but I am still getting the same error.

 

  Most of the time it still works, but I don't see why given the fact that it says it's failing to use winlogon.

 

  I'd really like to depend on this software. I paid fifty dollars for a piece of equivalent software I used to use for free back in the unix days, so hopefully someone can help me fix this problem.

3,377 views 3 replies
Reply #1 Top

Please submit a ticket to support@stardock.com, and provide as much information as possible about the issue and your system configuration.

 

Reply #2 Top

I have a similar but worst problem running Multiplicity Pro on an XP primary and attempting to connect to an additional Win 7 Home Premium new secondary.  Runs fine with an old Win XP secondary.  Am using Norton Security Suite on all three mechines and as near as I can tell the NSS program settings are identical.  I posted a ticket last week and so far it is unassigned.

A Google search suggests this is a long standing problem.

Stardock should be ashamed of this poor service.

Reply #3 Top

You submitted a ticket on the 3rd, then added another reply on the 4th, then again today.  The reason you haven't gotten a response yet is because, as the auto-reply email stated, each reply resets your position to the end of the queue.  Also, you created it on Friday, and our offices are closed on the weekend, so keep that in mind.

I understand being frustrated when something isn't working.  But saying we should be ashamed for not responding, when you haven't even given us the two business days we said it might take, let alone not following instructions to not send multiple replies, is a bit much.

I will make sure your ticket is addressed by the end of today.