Windows 10: Application of KB446933 or KB4462930 causes boot up message LogiLDA.dll not found.

After application of Windows 10 updates KB4462933 or KB4462919 I started receiving the following error message each time after a starting up Windows 10:


RunDLL


There was a problem starting C:\Windows\System32\LogiLDA.dll


The specified module could not be found.



However, if I do a directory display of C:\Windows\System32 I find the following:


LogiLDA.DLL 10/13/2016 9:55 PM Application extension 3,851 KB


Obviously the error message shows the suffix as lower case dll and the directory display shows DLL as upper case but if I try to make an exact copy using lower case dll Windows 10 says that the DLL entry and the dll entry are exactly the same.


So I have 2 questions


1) Is the Windows error message in error since the dll does actually exist?


2) Why did this error show up after application of 2 Windows 10 updates if this error supposedly has nothing to do with Windows 10 since it is part of the Logitech software and as far as I know has not changed since 2016?


I understand that an internet search brings up many solutions on how to get rid of this error message but what is troubling to me is what caused this error to show initially and why does each person encountering this error have to solve it manually for themselves?

:)

 

Logilda DLL and NVSPCAP64 DLL errors

See the following:

Fix: nvspcap64.dll missing or not found errors on startup - Appuals.com

https://appuals.com/fix-nvspcap64-dll-missing-o...

Logilda.DLL refers to the Logitech Download Assistant.

Open Start > Settings > Apps > Apps & features

Look through the list and uninstall it.

 

dll file not found after Creator's Update, Code Execution Cannot Proceed

Hi Aberfoyle,

It is possible that the
.dll file was corrupted during the update causing the error to occur.
To better assist you, kindly find the
.dll file
in
c:\Windows\System32. If you can find the
.dll file, it means that we need to
register
your
.dll file
to your
Operating System
for it to
work. To do this, we need to
unregister
the
.dll file
first and
re-register
it. Here are the steps on how to do so:

To unregister the .dll file:

• 
  Press
  Windows key + R, type
  Regsvr32 /u c:\Windows\System32\VCRUNTIME140.dll
  and hit
  Enter/OK.
  

To re-register the .dll file:

• 
  Press
  Windows key + R, type
  Regsvr32 c:\Windows\System32\VCRUNTIME140.dll
  and hit
  Enter/OK.
  

If you cannot find the
.dll
file in
c:\Windows\System32,
kindly run these methods of troubleshooting
so that we will know if the issue is within/not within the
Operating System:

Method 1:
Run SFC Scan.  

SFC
will
scan
and
run
an
automatic repair
to any
corrupted system files
that it will detect. We suggest that you perform it twice. To run an
SFC scan, follow these steps:  

• 
  Run
  Command Prompt as Administrator.  
  
• 
  Type
  sfc /scannow
  and hit
  Enter.   
  

Note:
Kindly run
SFC twice or thrice
and check for results before you proceed to the next method.

Method 2: Clean Boot.

Clean Boot
will
stop or disable
the
applications
that are running in your
computer's background.
To perform a
Clean Boot, click
here.

Note:
Reset the computer back to
Normal Mode
once you are done with the troubleshooting by following the section
"How to reset the computer to start normally after clean boot troubleshooting"
from the same article.

After performing these
methods of troubleshooting
and still the issue persists, we suggest that you contact your
computer/laptop manufacturer
for further assistance.

Update us on how it goes.

Regards.

 

Missing .dll files after upgrade

Hi Arletta,

I would suggest that you do a Clean boot and check if some service or application is causing the missing DLL message to appear. Follow the steps from the article :

How to perform a clean boot to troubleshoot a problem in Windows 8, Windows 7, or Windows Vista

http://support.microsoft.com/kb/929135



Note: Refer "How to reset the computer to start as usual after troubleshooting with clean boot" under more information to reset the computer to start as normal after troubleshooting.