Our new official repo is on github
LCD Smartie version 5.6 is released!
Download it now: https://github.com/LCD-Smartie/LCDSmartie/releases

No plugin working on win 7 64bit, get loadlibrary failed 193

Discuss anything to do with plugins

Moderators: _X7JAY7X_, caesar, IFR, mattcro, limbo

Post Reply
gsm_dealer08
Posts: 2
Joined: June 28th, 2015, 2:40 pm

No plugin working on win 7 64bit, get loadlibrary failed 193

Post by gsm_dealer08 »

Just got my LCD and downloaded LCD smartie. All works fine but when I try to load any plugin I get "load of plugin failed. loadlibrary failed with 193". The only one that works is NVplugin dll, all the rest give the same error.
I am running Windows 7 64 bit, have NET framework 4 installed, I have put the .config file in the folder,I have put the updated DLbridge dll file in the folder,I have run as administrator,I have tried everything.
I have spend about 10 hours so far trying to get a plugin to show CPU temp on the screen. At this point I am exhausted. I want Sensor Bridge in particular. Please help!

gsm_dealer08
Posts: 2
Joined: June 28th, 2015, 2:40 pm

Re: No plugin working on win 7 64bit, get loadlibrary failed

Post by gsm_dealer08 »

If anyone has the same error,here is the fix:
Repairing NET Framework 2.0/3.0 files on Windows Vista

You can use the following steps to repair the files that are a part of the NET Framework 2.0 and 3.0 on Windows Vista and Windows Server 2008:

Click on the Start menu, choose All Programs, then Accessories, then right-click on the Command Prompt item and select Run as administrator
Click Continue to authorize opening a command prompt with administrative privileges
Run this command in the cmd prompt: sfc /scannow
The cmd prompt should list text stating "Beginning system scan. This process will take some time."
Wait for the scan to complete (this can take several minutes so be patient). This command will scan all protected system files and replace incorrect versions with correct Microsoft versions
When the scan completes, the SFC tool will indicate whether or not it found any problems and whether or not it was able to fix them
If any errors are reported that SFC was unable to fix, there are steps in this knowledge base article and this how-to guide that explain how to locate and attempt to fix the errors

Turns out the built-in NET 3.5 was damaged and running that command fixed it.

Post Reply