As you know, DLL files in the Windows environment contain all the code needed by programs in order to properly function. And like with most other software, the functions in the DLL file have to be compatible with Windows especially if they are using any built-in service. So if you encounter an error that says, “DLL is either not designed to run on Windows or it contains an error”, when you try to launch a program, then this could be due to a compatibility issue. To fix this error, read on as this post will walk you through doing that.
Based on the reports of users who encountered this error, the error pointed to a DLL file that was either designed to run on a different version of Windows. It is also possible that the DLL file itself is the problem. Here’s the complete error message:
“Bad Image – DLL file is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.”
According to security experts, the DLL files that are known to trigger this kind of error message are msvcr100.dll, msvcr110.dll, msvcp140.dll, lmirfsclientnp.dll, and so on. To fix this problem, you can try to update or reinstall the program that’s throwing the error to its latest version. You could also ask the vendor for the latest version of the DLL as well as run a System File Checker scan.
Option 1 – Try to update or reinstall the program to its latest version
The first thing you can do to fix the problem is to update or reinstall the program that’s throwing the error. It is possible that the version of DLL might be using a system call that is deprecated. So if you had updated your Windows 10 computer recently, you might want to check for an update of the software or you could also try to reinstall its latest version.
Option 2 – Try asking the vendor for the latest version of the DLL
The next thing you can do to fix the error is to ask for the latest version of DLL from the vendor. There are times when the software uses an open-source version of DLL so it is better if you ask the vendor if there is a DLL file that has to be updated. If there is, then you need to make sure to register the DLL once you have it.
Option 3 – Try to re-register the problematic DLL file
You can also try to re-register the DLL to resolve the problem. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) controls in the Windows operating system. Follow the steps below to use it.
- Open Command Prompt as admin from the WinX menu.
- Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
- exe /[DLL file]
- exe [DLL file]
Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.
- After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.
Option 4 – Try to replace the DLL file from a trusted source
- First, you need to get the new DLL file from another computer with preferably the same file version number.
- After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
- x86: This PC > C:/Windows/System32
- x64: This PC > C:/Windows/SysWOW64
- Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
- Now type the “regsvr32 ntdll.dll” command and hit Enter.
- Restart your PC and check if the error is now fixed.
Option 5 – Run System File Checker scan
If reinstalling the program didn’t work, you can also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:
- Hit the Win + R keys to launch Run.
- Type in cmd in the field and tap Enter.
- After opening Command Prompt, type in sfc /scannow
The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:
- Windows Resource Protection did not find any integrity violations.
- Windows Resource Protection found corrupt files and successfully repaired them.
- Windows Resource Protection found corrupt files but was unable to fix some of them.
Reboot your computer.
Option 6 – Troubleshoot the isDone.dll error in a Clean Boot State
You can also troubleshoot the “DLL is either not designed to run on Windows or it contains an error” in a Clean Boot state. It could be that there are some third-party applications in your computer that are preventing the application from getting installed and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try installing the program again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.
- Log onto your PC as an administrator.
- Type in MSConfig in the Start Search to open the System Configuration utility.
- From there, go to the General tab and click “Selective startup”.
- Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
- Next, click the Services tab and select the “Hide All Microsoft Services” check box.
- Click Disable all.
- Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
- After you’ve set your computer into a Clean Boot State, make sure that you’re signed in as administrator and then try to install the application again.
Option 7 – Try scanning your computer using Windows Defender
The DLL file might also be infected with malware or virus and to eliminate it which could explain why you’re getting the “DLL is either not designed to run on Windows or it contains an error”. Thus, you have to scan your computer using security programs like Windows Defender.
- Tap the Win + I keys to open Update & Security.
- Then click on the Windows Security option and open Windows Defender Security Center.
- Next, click on Virus & threat protection > Run a new advanced scan.
- Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.
California's Department of Fair Employment & Housing has widened its anti-discrimination lawsuit against Activision Blizzard and claims the publisher has been shredding vital documents relevant to the ongoing investigation.
A recent report from Kotaku described the department as offering poorly paid, highly insecure positions, with a culture of hostility towards LGBTQ+ testers. The DFEH's rewording of "employees" to "workers" now hopes to take these contractors' experiences into account.
"As a contract employee, I feel there's a lot of pressure to excel, impress, and move through the ranks as fast as you can before your contract ends and you're forced to go 3 months without income or find another job," Axios reports one worker saying. "I take pride in what I do, but it feels like it's never enough."
Activision's contentious hiring of union-busting third-party law firm WilmerHale "directly interferes" with its own investigation, it says. By going to WilmerHale, Activision appears to be claiming that all work related to the investigation is privileged and can't be shared with DFEH.
The suit also claims that Activision HR shredded documents related to "investigations and complaints", against its legal obligation to retain them during the investigation. The relevant parts of the updated lawsuit were shared by Axios reporters Stephen Totilo and Megan Farokhmanesh, the former also noting that the DFEH "fixed their misspelling of Bill Cosby's name".
"DFEH is also informed and aware that documents and records have not been maintained as required by law or by the DFEH's Document Retention Notice," the complaint reads, "including but not limited to documents related to investigations and complaints were shredded by human resource personnel and emails are deleted thirty days after an employees separation."
