Run DLL error message/background container.dll

Anonymous
2013-10-18T12:34:39+00:00

I am getting the following message:

Run DLL

There was a problem starting

c:\users\ed\appData\local\conduit\backgroundco container\background container.dll

What can I do to repair this problem?

Thank you.

Ed

Windows for home | Previous Windows versions | Security and privacy

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
quietman7 MVP Alumni 19,830 Reputation points Volunteer Moderator
2013-10-18T23:02:36+00:00

RunDLL is a legitimate Windows file that executes/loads .dll (Dynamic Link Library) modules which too can be legitimate or sometimes malware related. A RunDLL "Error loading... message usually occurs when the .dll file that was set to run at startup in the registry or as a scheduled task has been deleted. Windows is trying to load this file(s) but cannot locate it since the file was mostly likely removed during an anti-virus or anti-malware scan. However, an associated orphaned registry entry still remains and is telling Windows to load the file when you boot up. Since the file no longer exists, Windows will display an error message. You need to remove this registry entry so Windows stops searching for the file when it loads.

To resolve this, download AutoRuns and save it to your Desktop.

  • Create a new folder on your hard drive called AutoRuns (C:\AutoRuns) and extract (unzip) the file there.
  • Open the folder and double-click on autoruns.exe to launch it.
  • Vista/Windows 7/8 users right-click and select Run As Administrator.
  • Please be patient as it scans and populates the entries.
  • When finished scanning, it will say Ready at the at the bottom and list all entries under the Everything tab.
  • In the top menu, click File > Find... and type the file name (backgroundcontainer.dll) related to the error message, then click Find Next.
  • Alternatively, you can scroll through the list and look for any entry related to backgroundcontainer.dll and conduit.
  • If found, right-click on the entry and choose delete.
  • Exit Autoruns and reboot your computer when done.

An alternate method to resolve this issue is as follows:

  1. Go to Start > Control Panel > Administrative Tools.
  2. Open Task Scheduler and click on Task Scheduler Library.
  3. Look through the list for an entry related to BackgroundContainer.
  4. If found, right-click on it and select Delete.
  5. Exit all programs and reboot the computer when done.

Afterwards, please download and scan with the following tools which will search for and remove many unwanted programs (PUPs), adware, toolbars, browser hijackers, extensions, add-ons and other junkware as well as related registry entries.

AdwCleaner

Junkware Removal Tool

Malwarebytes Anti-Malware

-- Note: The contents of the AdwCleaner log file (AdwCleaner[S0].txt) may be confusing. Unless you see a program name that you recognize and know should not be removed, don't worry about it. If you see an entry you want to keep, return to AdwCleaner before cleaning...all detected items will be listed (and checked) in each tab. Click on each one and uncheck any items you want to keep (except you cannot uncheck Chrome and Firefox preferences lines).

Was this answer helpful?

40+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2013-10-18T12:38:12+00:00

Hi,

"conduit" is related to Malware

Google has little information on that file, so it is probably a left over Startup Entry from Malware that has been removed by your Security Programs.

Download, install, update and scan your System with the free version of Malwarebytes AntiMalware:

http://www.malwarebytes.org/products/malwarebytes\_free

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

If problem remains after scanning, take those Entries out of Startup:

"How to use MSCONFIG in Windows 7"

http://netsquirrel.com/msconfig/msconfig\_win7.html

You can also use this free Program to do that, too:

"Autoruns for Windows v11.32"

http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx

Cheers.

Was this answer helpful?

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

156 additional answers

Sort by: Most helpful
  1. Anonymous
    2013-11-02T21:01:54+00:00

    THANKS!

    It worked, I sit here mystified it was so simple a child could do it. The malware programs got rid of conduit but left behind that error message upon start up. I went through my tech person but he could not get rid of it. He also said to not download the virus-ware removal stuff that I had tried  as some of it is worse then the virus. Sooooo with a shaky hand I did what you said and it worked.

    thanks for taking the time to educate and help us

    THANKS

    Earl

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-11-01T22:06:46+00:00

    It is not uncommon to receive such an error(s) when booting into Windows after using anti-virus and other security scanning tools to remove malware.

    Thank you very much folks. I had the same problem and this fixed it!

    Was this answer helpful?

    0 comments No comments
  3. quietman7 MVP Alumni 19,830 Reputation points Volunteer Moderator
    2013-11-01T17:52:40+00:00

    Community forums like this do not provide assistance via email or private message.

    I recommend further investigation. Many of the tools we recommend here are not capable of detecting (repairing/removing) all malware variants so more advanced tools are needed to investigate. To receive individual assistance with malware disinfection from an expert you would need to visit a site with a dedicated forum for posting comprehensive logs for review. In most cases they will have a Preparation Guide with instructions for you to read and follow. See the section Get Expert Analysis near the bottom of the Malware Removal Guide for a list of sites which offer such assistance.

    Was this answer helpful?

    0 comments No comments