windows - How to resolve BackgroundContainer.dll error on startup?

  • V. G.

    When I start my desktop it gives me an error about BackgroundContainer.dll.

    enter image description here

    How to get rid of it?

    I found nothing when i started regedit.exe and searched (F3 or CTRL+F) for BackgroundContainer.dll

  • Answers
  • Community

    This was a malware. It was removed by your AntiVirus Scanner, but the registry entries are still present to start the malware at startup.

    Start regedit.exe and search (F3 or CTRL+F) for BackgroundContainer.dll and delete all entries you find.

    To be safe, make a full scan with an AntiVirus Scanner like Microsoft Security Essentials/ Defender and also scan your PC with Malwarebytes' Anti-Malware.

    If you can find nothing in the registry, download and run Autoruns from sysinterals and look here for an entry " BackgroundContainer". Look under logon and scheduled task first. When found, left click on the entry to highlight it. Then right click on your mouse and select delete from the menu that comes up for that entry. Right click on delete to delete that entry. Be careful to only delete the entry/entries you want to permanently delete.

  • Related Question

    Why is my windows slow at startup?
  • user3511

    My computer has a weird thing going on. When windows starts up I see the System process using 100% of the CPU for about 2-3 minutes and then it subsides. I wonder why this happens. I'm sure my computer is virus and spyware free. And I don't face no other problems once this 2-3 minutes pass by. Any idea why this happens?

  • Related Answers
  • 8088

    Install Process Explorer, and make sure it runs at startup. It keeps a history of recent processor usage, and tells you which programs were taxing the CPU most at any given time (mouse over the CPU history and a tooltip appears identifying the CPU hog at that time).

    alt text

  • Nate

    If you don't find the culprit in Start, All Programs, Startup Items then you may want to check for other startup items by using msconfig.

    Click on Start, Run (may be different in vista) type in msconfig, press ok, and click on the startup tab at the top.

    These are all of the programs that start with your machine. It is safe to disable all of these items but you shouldn't have to. If you notice the name of a program you don't use anymore uncheck it here. If something seems fishy google it to find out what it does and uncheck it if you want. When you're finished cleaning these out press ok and restart.

  • Umber Ferrule

    Autoruns (from Sysinternals) can be an eye-opener too.

  • MicTech

    Try sysinternals process explorer, maybe you get more information, what exactly
    happening after start.

  • akf

    check what you have in your user profile's start menu->all programs->startup menu item. perhaps you are starting a host (or maybe just one) of items that take time on start up.

  • Roger

    This may be caused by a "zombie" print job (that is, one which could not be successfully printed for some reason, but which was not automatically deleted by the print spooler). When this happens, the system will continue trying to print the document over and over, spiking your System process. Check to see if a document is stuck in your print queue, and if so, delete it.

  • Pär Björklund

    If it's your system process that's using that much cpu it can be the cause of a bad driver or your antivirus software.

    Do you get the same problem if you Windows start in safe mode?

    You can use msconfig to disable most autostart entries.

    Start, type msconfig and press enter. Go to the services tab and mark hide all Microsoft services, (Make sure you did not miss the previous step, your machine will likely not boot)press disable all. Go to the startup tab and press disable all. Click Ok and reboot. Does it work better now?

    If it's working better then you might need to try out the autostart apps one by one to figure out which one is causing your issue.

    If it's not working any better I would suggest checking for new drivers and uninstall any antivirus/firewall software since you cannot disable them reliably.