Winlogon dll is NOT running

from Stardock Forums
According to my slave computer, it says that the winlogon dll is not running, no matter what i do i cant fix it.  these are the steps and results ive taken:

first off, only windows firewall is enabled, and i confirmed the entry
i used the http://sd.stardock.com/mike/apps/reinstall_mpp_service.bat on slave computer with no change
ive reinstalled multiplicity and redownloaded it
ive confirmed that both computers are using same version
primary computer says that it can connect but then doesnt
Everything else on troubleshooter on slave checks out except for winlogon
multisrv32.exe and winlogon.exe are both currently running in task manager on the slave computer
netstat -n -a shows that port 30564 is listening
telnetting from primary to slave was successful
still no connection, still no change in the error "Multiplicity Winlogon dll is NOT running" on slave computer

what else is there that i can do?
multiplicity
6,249 views 5 replies
Reply #2 from Stardock Forums Top
both vista 32 bit, it got fixed...and its wierd, this is what happened:

i had basically given up, then one night my MAIN computer rebooted cuz of windows updates, once it rebooted, it connected almost instantly to slave, and slave out of no where said winlogon.dll was running fine and passed testing....wtf? lol

but now, i have dual booted XP on laptop and now im trying to get it to work there too, and my main comp says that it connects fine in the troubleshooter, but really doesnt

i did practically same steps as my original post, minus the winlogon stuff since it works fine now with no go :(
TouchTasks - Access tasks with ease on Windows touchscreens.
Reply #3 from Stardock Forums Top

You can also try:

  1. Unload Multiplicity
  2. Stop the Stardock Multiplicity Service
  3. Start the Stardock Multiplicity Service
  4. Open Multiplicity

... it has personally worked for me each time ...

Reply #5 from Stardock Forums Top

I have had the same problems with winlogon.dll not running (on a laptop and tower with win7-32bit).

After rebooting both computers, the laptop came up in a temp profile and it worked! winlogon.dll was running.  I logged out of the temp and back into my main on the laptop and is continuing to run.

Is something being written to the user profile that when you get a clean one it clears up the problem? I'm not computer saavy, so I clueless, but putting out what fixed it (I am not rebooting again for as along as I can get away with it 'cause I need the connection right now to finish a project. I'll report back here if it fails after my next reboot).