Specified Module could not be found (LogiLDA.dll)

Anonymous
2011-02-17T19:28:37+00:00
I made the mistake of running a registry cleaner and now get a computer startup error that states that the following ddl cannot run. As far as I can tell it is a Ligitech<br> Download Manager file. Do you know what I can do to fix this? <br><br> <br><br>C:\Windows\System32\LogiLDA.dll
Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2012-02-03T23:36:49+00:00

I had it too. This is what I did to fix it.

I went to Control Panel>System>Device Manager>Human Interface Devices>USB input Device (Logitech Download Assistant). Doube click. Uninstall driver.

Then Action>Scan for hardware changes and the driver updates itself from MS with Logitech ware. 

"logiLDA.dll" error is GONE.

I personally like a clean registry, although I know tech fundamentalists don't. So I will stick with it, but will keep an open mind.

If it comes back I will repost, as the idea of a "restore" is a good suggestion.

Jonathan AU

Was this answer helpful?

70+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2011-02-17T21:26:24+00:00

On Thu, 17 Feb 2011 19:28:37 +0000, DBC 7500 wrote:

I made the mistake of running a registry cleaner and now get a computer startup error that states that the following ddl cannot run. As far as I can tell it is a Ligitech Download Manager file. Do you know what I can do to fix this?

C:\Windows\System32\LogiLDA.dll

Do a system restore to a date before you used the registry cleaner.

And in the future, avoid using registry cleaners. Registry cleaning

programs are all snake oil. Cleaning of the registry isn't needed

and is dangerous. Leave the registry alone and don't use any registry

cleaner. Despite what many people think, and what vendors of registry

cleaning software try to convince you of, having unused registry

entries doesn't really hurt you.

The risk of a serious problem caused by a registry cleaner erroneously

removing an entry you need is far greater than any potential benefit

it may have.

Read http://www.edbott.com/weblog/archives/000643.html

and http://aumha.net/viewtopic.php?t=28099

and also

http://blogs.technet.com/markrussinovich/archive/2005/10/02/registry-junk-a-windows-fact-of-life.aspx

Let me point out that neither I nor anyone else who warns against the

use of registry cleaners has ever said that they always cause

problems. If they always caused problems, they would disappear from

the market almost immediately. Many people have used a registry

cleaner and never had a problem with it.

Rather, the problem with a registry cleaner is that it carries with it

the substantial risk of having a problem. And since there is no

benefit to using a registry cleaner, running that risk is a very bad

bargain.


Ken Blake (MS MVP)

Was this answer helpful?

30+ people found this answer helpful.
0 comments No comments

89 additional answers

Sort by: Oldest
  1. Anonymous
    2012-03-15T21:07:07+00:00

    This fixed it for me, nice one.  Dunno why Windows Update would install an update to a Logitech updater and do it wrongly :(

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2012-11-17T05:36:00+00:00

    This fixed it for me, nice one.  Dunno why Windows Update would install an update to a Logitech updater and do it wrongly :(

    " [...] Dunno why /Windows/ Update [...]"

    You just answered your own question.

    ANYWAY: I was also able to fix this issue by "Control Panel>System>Device Manager>Human Interface Devices>USB input Device (Logitech Download Assistant). Doube click. Uninstall driver."

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2013-04-19T12:20:08+00:00

    Thanks, that worked for me too.

    Was this answer helpful?

    0 comments No comments