It's not unusual to receive such an error after using anti-virus and other security scanning tools to remove malware infection.
A "Cannot find...
", "Could not run..."
, "Error loading...
or "specific module could not be found
" message is usually related to malware that was set to run at startup but has been deleted. Windows is trying to load this file 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
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
, search for the related entry and then delete it.
- Create a new folder on your hard drive called AutoRuns (C:\AutoRuns) and extract (unzip) the file there. (click here if you're not sure how to do this.)
- Open the folder and double-click on autoruns.exe to launch it.
- Please be patient as it scans and populates the entries.
- When done scanning, it will say Ready at the bottom.
- Scroll through the list and look for a startup entry related to the file(s) in the error message.
- Right-click on the entry and choose delete.
- Reboot your computer and see if the startup error returns.
The System32 folder opens at startup because of a corrupt system registry value. The value could have been corrupted for a number of reasons to include malware or installing/uninstalling a program from the Internet which did not install/uninstall itself properly.
Click on the link below:http://www.kellys-korner-xp.com/xp_tweaks.htm
Scroll down to #260 and click "System32 Folder Opens Upon Boot" in the right column. You will be prompted to download xp_systems32opens.vbs
. Save the file to your desktop and double-click on it to run the script. Since the script modifies certain registry settings you may receive an alert from your anti-virus or any script blocking program. Ignore the warning and allow it to continue.
The problem could also be caused by empty run entries in your startup shortcuts which will open the system32 folder. Check the startup run registry entries and remove those entries. See System32 Folder Opens When Logging on to Windows
These steps involves making changes in the registry. Always back up your registry before making any changes
. If you are not familiar with working in the registry, then you should NOT attempt to make any changes on your own. Improper changes to the registry could adversely affect your computer and render it inoperable. ERUNT
is an excellent FREE tool that allows you to to take a snapshot (backup) of your registry before making changes and restore it when needed.