Its not unusual to receive such an error after using specialized fix tools.
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. ntuser.dll or ntuser.exe
Right-click on the entry and choose delete
your computer and see if the startup error returns.
===========================We Need to check for Rootkits with RootRepeal
- Download RootRepeal from the following location and save it to your desktop.
- Direct Download (Recommended)
- Zip Mirrors (Recommended if you have a slower connection or if the Direct Download mirror is down)
- Rar Mirrors - Only if you know what a RAR is and can extract it.
- Extract RootRepeal.exe from the archive (If you did not use the "Direct Download" mirror).
- Open on your desktop.
- Click the tab.
- Click the button.
- Check all seven boxes:
- Push Ok
- Check the box for your main system drive (Usually C:), and press Ok.
- Allow RootRepeal to run a scan of your system. This may take some time.
- Once the scan completes, push the button. Save the log to your desktop, using a distinctive name, such as RootRepeal.txt. Include this report in your next reply, please.
Please note: If Rootrepeal fails to run, try this step: Click Settings - Options. Set the Disk Access slider to High
Also try: right-click on rootrepeal.exe and rename it to tatertot.scr